invariant-sast 0.1.0__tar.gz

invariant_sast-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing
+      the origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Invariant contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

invariant_sast-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+Invariant
+Copyright 2026 Invariant contributors
+
+This product includes software developed as part of the Invariant project
+(SMT-based guardrail SAST for AWS SCP/RCP JSON).

invariant_sast-0.1.0/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.4
+Name: invariant-sast
+Version: 0.1.0
+Summary: SMT-based guardrail SAST for AWS SCP/RCP JSON (baseline + regression checks)
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://ikurira.github.io/invariant/
+Project-URL: Issues, https://github.com/Ikurira/invariant/issues
+Project-URL: Repository, https://github.com/Ikurira/invariant
+Classifier: Environment :: Console
+Classifier: Intended Audience :: System Administrators
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: z3-solver
+Provides-Extra: docs
+Requires-Dist: mkdocs>=1.6; extra == "docs"
+Requires-Dist: mkdocs-material>=9.5; extra == "docs"
+Dynamic: license-file
+
+# Invariant
+
+SMT-based guardrail SAST for AWS Service Control Policies (SCPs) and Resource
+Control Policies (RCPs). Instead of pattern-matching JSON, Invariant hands
+your policies to the [Z3](https://github.com/Z3Prover/z3) theorem prover and
+asks a precise question:
+
+> Is there any `(action, resource, principal)` request that used to be
+> denied, but isn't anymore?
+
+If Z3 finds one, that's a guardrail regression, and you get a concrete
+counterexample instead of a vague warning.
+
+## Why
+
+Checkov, cfn-nag, and friends are great at "does this statement look
+dangerous," but they can't tell you whether an edit to a `Condition` block
+quietly widened who a `Deny` statement applies to. That requires reasoning
+about the full set of requests a policy allows, not just its syntax. Invariant
+answers that question with a solver instead of a regex.
+
+## Two checks, one engine
+
+- **`invariant scan`** — baseline check. Point it at a directory and it
+  proves each `service-control-policies/*.json` / `rcp-policies/*.json` file
+  still upholds the security properties of the **default AWS Landing Zone
+  Accelerator (LZA) guardrails**, a copy of which ships inside the package
+  (`src/invariant/baseline/`). No reference file, no manifest, nothing to set
+  up — this is the "just run it" entry point.
+
+- **`invariant regression --manifest manifest.json`** — diff check. Proves
+  each candidate still denies everything *its own paired reference* denied.
+  Use this when you want to check against something other than the bundled
+  LZA defaults — your org's own last-known-good policies, an upstream
+  release, whatever you supply. `build_manifest.py` derives the pairing from
+  a git diff so you don't hand-maintain it (see [CI integration](#ci-integration)).
+
+Both share the same check registry, output formats, and exit-code
+convention: `0` = no findings (or `--soft-fail`), `1` = a check failed.
+
+## Install
+
+Requires Python 3.10+. `z3-solver` is installed automatically as a
+dependency.
+
+```bash
+# from a package index, once published
+pip install invariant
+
+# or straight from source
+git clone https://github.com/YOUR_ORG/invariant.git
+cd invariant
+pip install .
+```
+
+## Quickstart
+
+From the root of your AWS LZA config repo (wherever your
+`service-control-policies/` and `rcp-policies/` directories live):
+
+```bash
+invariant scan
+```
+
+```
+[PASS] INV_AWS_001  service-control-policies/lza-core-guardrails-1.json  No regression found.
+[PASS] INV_AWS_001  service-control-policies/lza-quarantine.json         No regression found.
+[FAIL (critical)] INV_AWS_001  service-control-policies/lza-quarantine.json  Candidate no longer denies a request the reference denied: {'action': '""', 'resource': '""', 'principal': '""'}
+```
+
+A `FAIL` line means Z3 found a concrete `(action, resource, principal)`
+tuple that the bundled baseline guardrail denies but your policy no longer
+does. Exit code is `1` whenever any check fails, so it's CI-friendly out of
+the box.
+
+Only files with a same-named counterpart in the bundled baseline catalog are
+checked. A custom SCP with no LZA-default analog has nothing to prove a
+baseline property against yet — `invariant scan` reports it (to stderr) as
+skipped rather than silently ignoring it. Pair it against something of your
+own choosing with `invariant regression` instead.
+
+## CLI reference
+
+Both subcommands accept:
+
+| Flag | Default | Meaning |
+|---|---|---|
+| `--check IDS` | all | Comma-separated check IDs to run |
+| `--skip-check IDS` | none | Comma-separated check IDs to exclude |
+| `--output`, `-o` | `cli` | `cli`, `json`, and/or `sarif` — repeatable |
+| `--soft-fail` | off | Always exit `0`, regardless of findings |
+| `--compact` | off | Suppress `PASS` lines in `cli` output |
+| `--out-dir` | `solver-results` | Where `json`/`sarif` reports get written |
+
+`invariant scan` also takes:
+
+| Flag | Default | Meaning |
+|---|---|---|
+| `--directory`, `-d` | `.` | Root to scan for `service-control-policies/` and `rcp-policies/` |
+
+`invariant regression` also takes:
+
+| Flag | Default | Meaning |
+|---|---|---|
+| `--manifest`, `-m` | `manifest.json` | Reference↔candidate pairing (see `build_manifest.py`) |
+
+## Suppressing a finding
+
+A candidate JSON file can carry a top-level `_suppressions` array (raw AWS
+policy JSON has no comment syntax to piggyback a suppression on, unlike
+HCL/YAML checks):
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [ ... ],
+  "_suppressions": [
+    {"check_id": "INV_AWS_001", "reason": "JIRA-1234: intentional widen"}
+  ]
+}
+```
+
+This key is stripped before the policy is handed to the solver, so it never
+affects the request semantics Z3 reasons about.
+
+## Checks
+
+| ID | Severity | What it proves |
+|---|---|---|
+| `INV_AWS_001` | CRITICAL | The candidate SCP/RCP denies every `(action, resource, principal)` request its reference (baseline or paired manifest entry) explicitly denied. |
+
+Failing `INV_AWS_001`: review the counterexample. If the widened permission
+is intentional, add a `_suppressions` entry (or update your own reference,
+for `regression`) and document why in the PR description. If not, revert the
+`Condition`/`Resource`/`Action` change that removed the denial.
+
+## How the solver works, and where it's intentionally conservative
+
+Every `Deny` statement becomes a Z3 predicate over a symbolic request
+context (one variable per condition key actually observed in the LZA
+guardrail set); wildcard `Action`/`Resource`/ARN patterns compile to Z3
+regular expressions. `invariant` then asks the solver to find a request the
+reference denies that the candidate doesn't. See `policy_check.py` for the
+full model. A few gaps are called out there and worth knowing about:
+
+- **`aws:CalledVia`** is modeled as a single representative string, not a
+  true call chain, so `ForAllValues:StringNotEquals` on it is sound for
+  catching "the whole chain is now unconstrained" but can miss a regression
+  that only appears with one specific multi-hop chain.
+- **`aws:ResourceTag/*` (`StringEquals`)** is left unconstrained — there's no
+  resource-tag model — which makes the checker conservative (won't
+  false-negative a real regression) but can over-report on tag-gated
+  statements.
+- Any condition operator not in the model (currently seen in the wild:
+  `StringLike`, `StringNotLike`, `ForAnyValue:StringLike` on keys like
+  `rds:DatabaseEngine`) is treated as **non-constraining** and prints a
+  `WARNING`. A statement using one of these may be reported as denying more
+  than it actually does — verify those findings by hand.
+
+None of this changes the exit-code contract; it just means a `PASS` on a
+statement using one of the flagged operators is a weaker guarantee than a
+`PASS` elsewhere, and the tool tells you when that's the case.
+
+## CI integration
+
+`.gitlab-ci.yml` and `.github/workflows/invariant.yml` are **templates**,
+meant to be copied into your own AWS LZA config repo (not into a fork of
+this one) — each wires up a diff-scoped `regression` job plus a full-sweep
+`scan` job, and publishes `solver-results*/results.sarif` so GitLab/GitHub
+render findings natively. Both assume `invariant` is installed from wherever
+you publish it — set `INVARIANT_PIP_SPEC` (GitLab) / `INVARIANT_PIP_SPEC` env
+(GitHub) to your private index, package registry, or a `git+https://` URL.
+
+## Development
+
+```bash
+git clone https://github.com/YOUR_ORG/invariant.git
+cd invariant
+python -m venv .venv
+. .venv/Scripts/activate   # .venv/bin/activate on macOS/Linux
+pip install -e .
+invariant --help
+```
+
+## License
+
+Apache-2.0 — see [LICENSE](LICENSE).

invariant_sast-0.1.0/README.md

@@ -0,0 +1,187 @@
+# Invariant
+
+SMT-based guardrail SAST for AWS Service Control Policies (SCPs) and Resource
+Control Policies (RCPs). Instead of pattern-matching JSON, Invariant hands
+your policies to the [Z3](https://github.com/Z3Prover/z3) theorem prover and
+asks a precise question:
+
+> Is there any `(action, resource, principal)` request that used to be
+> denied, but isn't anymore?
+
+If Z3 finds one, that's a guardrail regression, and you get a concrete
+counterexample instead of a vague warning.
+
+## Why
+
+Checkov, cfn-nag, and friends are great at "does this statement look
+dangerous," but they can't tell you whether an edit to a `Condition` block
+quietly widened who a `Deny` statement applies to. That requires reasoning
+about the full set of requests a policy allows, not just its syntax. Invariant
+answers that question with a solver instead of a regex.
+
+## Two checks, one engine
+
+- **`invariant scan`** — baseline check. Point it at a directory and it
+  proves each `service-control-policies/*.json` / `rcp-policies/*.json` file
+  still upholds the security properties of the **default AWS Landing Zone
+  Accelerator (LZA) guardrails**, a copy of which ships inside the package
+  (`src/invariant/baseline/`). No reference file, no manifest, nothing to set
+  up — this is the "just run it" entry point.
+
+- **`invariant regression --manifest manifest.json`** — diff check. Proves
+  each candidate still denies everything *its own paired reference* denied.
+  Use this when you want to check against something other than the bundled
+  LZA defaults — your org's own last-known-good policies, an upstream
+  release, whatever you supply. `build_manifest.py` derives the pairing from
+  a git diff so you don't hand-maintain it (see [CI integration](#ci-integration)).
+
+Both share the same check registry, output formats, and exit-code
+convention: `0` = no findings (or `--soft-fail`), `1` = a check failed.
+
+## Install
+
+Requires Python 3.10+. `z3-solver` is installed automatically as a
+dependency.
+
+```bash
+# from a package index, once published
+pip install invariant
+
+# or straight from source
+git clone https://github.com/YOUR_ORG/invariant.git
+cd invariant
+pip install .
+```
+
+## Quickstart
+
+From the root of your AWS LZA config repo (wherever your
+`service-control-policies/` and `rcp-policies/` directories live):
+
+```bash
+invariant scan
+```
+
+```
+[PASS] INV_AWS_001  service-control-policies/lza-core-guardrails-1.json  No regression found.
+[PASS] INV_AWS_001  service-control-policies/lza-quarantine.json         No regression found.
+[FAIL (critical)] INV_AWS_001  service-control-policies/lza-quarantine.json  Candidate no longer denies a request the reference denied: {'action': '""', 'resource': '""', 'principal': '""'}
+```
+
+A `FAIL` line means Z3 found a concrete `(action, resource, principal)`
+tuple that the bundled baseline guardrail denies but your policy no longer
+does. Exit code is `1` whenever any check fails, so it's CI-friendly out of
+the box.
+
+Only files with a same-named counterpart in the bundled baseline catalog are
+checked. A custom SCP with no LZA-default analog has nothing to prove a
+baseline property against yet — `invariant scan` reports it (to stderr) as
+skipped rather than silently ignoring it. Pair it against something of your
+own choosing with `invariant regression` instead.
+
+## CLI reference
+
+Both subcommands accept:
+
+| Flag | Default | Meaning |
+|---|---|---|
+| `--check IDS` | all | Comma-separated check IDs to run |
+| `--skip-check IDS` | none | Comma-separated check IDs to exclude |
+| `--output`, `-o` | `cli` | `cli`, `json`, and/or `sarif` — repeatable |
+| `--soft-fail` | off | Always exit `0`, regardless of findings |
+| `--compact` | off | Suppress `PASS` lines in `cli` output |
+| `--out-dir` | `solver-results` | Where `json`/`sarif` reports get written |
+
+`invariant scan` also takes:
+
+| Flag | Default | Meaning |
+|---|---|---|
+| `--directory`, `-d` | `.` | Root to scan for `service-control-policies/` and `rcp-policies/` |
+
+`invariant regression` also takes:
+
+| Flag | Default | Meaning |
+|---|---|---|
+| `--manifest`, `-m` | `manifest.json` | Reference↔candidate pairing (see `build_manifest.py`) |
+
+## Suppressing a finding
+
+A candidate JSON file can carry a top-level `_suppressions` array (raw AWS
+policy JSON has no comment syntax to piggyback a suppression on, unlike
+HCL/YAML checks):
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [ ... ],
+  "_suppressions": [
+    {"check_id": "INV_AWS_001", "reason": "JIRA-1234: intentional widen"}
+  ]
+}
+```
+
+This key is stripped before the policy is handed to the solver, so it never
+affects the request semantics Z3 reasons about.
+
+## Checks
+
+| ID | Severity | What it proves |
+|---|---|---|
+| `INV_AWS_001` | CRITICAL | The candidate SCP/RCP denies every `(action, resource, principal)` request its reference (baseline or paired manifest entry) explicitly denied. |
+
+Failing `INV_AWS_001`: review the counterexample. If the widened permission
+is intentional, add a `_suppressions` entry (or update your own reference,
+for `regression`) and document why in the PR description. If not, revert the
+`Condition`/`Resource`/`Action` change that removed the denial.
+
+## How the solver works, and where it's intentionally conservative
+
+Every `Deny` statement becomes a Z3 predicate over a symbolic request
+context (one variable per condition key actually observed in the LZA
+guardrail set); wildcard `Action`/`Resource`/ARN patterns compile to Z3
+regular expressions. `invariant` then asks the solver to find a request the
+reference denies that the candidate doesn't. See `policy_check.py` for the
+full model. A few gaps are called out there and worth knowing about:
+
+- **`aws:CalledVia`** is modeled as a single representative string, not a
+  true call chain, so `ForAllValues:StringNotEquals` on it is sound for
+  catching "the whole chain is now unconstrained" but can miss a regression
+  that only appears with one specific multi-hop chain.
+- **`aws:ResourceTag/*` (`StringEquals`)** is left unconstrained — there's no
+  resource-tag model — which makes the checker conservative (won't
+  false-negative a real regression) but can over-report on tag-gated
+  statements.
+- Any condition operator not in the model (currently seen in the wild:
+  `StringLike`, `StringNotLike`, `ForAnyValue:StringLike` on keys like
+  `rds:DatabaseEngine`) is treated as **non-constraining** and prints a
+  `WARNING`. A statement using one of these may be reported as denying more
+  than it actually does — verify those findings by hand.
+
+None of this changes the exit-code contract; it just means a `PASS` on a
+statement using one of the flagged operators is a weaker guarantee than a
+`PASS` elsewhere, and the tool tells you when that's the case.
+
+## CI integration
+
+`.gitlab-ci.yml` and `.github/workflows/invariant.yml` are **templates**,
+meant to be copied into your own AWS LZA config repo (not into a fork of
+this one) — each wires up a diff-scoped `regression` job plus a full-sweep
+`scan` job, and publishes `solver-results*/results.sarif` so GitLab/GitHub
+render findings natively. Both assume `invariant` is installed from wherever
+you publish it — set `INVARIANT_PIP_SPEC` (GitLab) / `INVARIANT_PIP_SPEC` env
+(GitHub) to your private index, package registry, or a `git+https://` URL.
+
+## Development
+
+```bash
+git clone https://github.com/YOUR_ORG/invariant.git
+cd invariant
+python -m venv .venv
+. .venv/Scripts/activate   # .venv/bin/activate on macOS/Linux
+pip install -e .
+invariant --help
+```
+
+## License
+
+Apache-2.0 — see [LICENSE](LICENSE).

invariant_sast-0.1.0/pyproject.toml

@@ -0,0 +1,40 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "invariant-sast"
+version = "0.1.0"
+description = "SMT-based guardrail SAST for AWS SCP/RCP JSON (baseline + regression checks)"
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.10"
+dependencies = [
+    "z3-solver",
+]
+classifiers = [
+    "Environment :: Console",
+    "Intended Audience :: System Administrators",
+    "Topic :: Security",
+    "Topic :: Software Development :: Quality Assurance",
+]
+
+[project.optional-dependencies]
+docs = [
+    "mkdocs>=1.6",
+    "mkdocs-material>=9.5",
+]
+
+[project.urls]
+Homepage = "https://ikurira.github.io/invariant/"
+Issues = "https://github.com/Ikurira/invariant/issues"
+Repository = "https://github.com/Ikurira/invariant"
+
+[project.scripts]
+invariant = "invariant.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+invariant = ["baseline/**/*.json"]

invariant_sast-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

invariant_sast-0.1.0/src/invariant/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.1.0"