Skip to content

Releases

v0.3.5

Choose a tag to compare

@github-actions github-actions released this 03 Nov 16:27
ee626f4

What's Changed

  • Release invariant-sast 0.3.5: generate docs/checks.md from the check registry by @Ikurira in #2

Full Changelog: v0.3.4...v0.3.5

v0.3.4

Choose a tag to compare

@github-actions github-actions released this 03 Nov 16:13
043e4cc

Repository moved to heimdallsystems

invariant-sast now lives at heimdallsystems/invariant and is published from there. Earlier releases (0.1.0 to 0.3.3) were published from the previous Ikurira/invariant repository, which is no longer public.

About PyPI's "Change of provenance" warning on 0.3.4: this is expected. It appears because 0.3.4 is the first release published from the new repository. You can confirm the release is genuine from its attestations on PyPI, which identify the publisher as:

  • Repository: heimdallsystems/invariant
  • Workflow: publish.yml
  • Environment: pypi

Later releases are published from the same workflow.

The code is the same as 0.3.3. The only changes are:

What's Changed

New Contributors

Full Changelog: v0.3.3...v0.3.4

v0.3.3

Choose a tag to compare

@Ikurira Ikurira released this 29 Oct 13:44

Full Changelog: v0.3.2...v0.3.3

v0.3.2

Choose a tag to compare

@Ikurira Ikurira released this 29 Oct 13:44

Full Changelog: v0.3.1...v0.3.2

v0.3.1

Choose a tag to compare

@Ikurira Ikurira released this 29 Oct 13:43

Highlights

  • Readability fix: invariant scan/run no longer buries a real regression or privilege-escalation finding under duplicate, repeated engine-level narration. The Z3 engine functions are now pure (no more side-effect [REGRESSION FOUND]/[OK]/[PRIVESC] printing); cli.py is the single source of truth for output. The "unhandled condition operator" soundness caveat now prints at most once per operator per run, to stderr, instead of once per statement/check/file.
  • Failure summary: CLI output now ends with a clear, most-severe-first summary block listing every failed check, so it's the last (and most visible) thing before the exit code.

Patch release -- no new user-facing capability, just this output fix.

Publishes invariant-sast 0.3.1 to PyPI via Trusted Publishing.

v0.3.0

Choose a tag to compare

@Ikurira Ikurira released this 29 Oct 13:43

Highlights

  • Recursive policy-directory discovery: invariant scan/run now finds service-control-policies/, rcp-policies/, and iam-policies/ at any depth under --directory (Checkov-style), instead of requiring them to be direct children of the path you pass.
  • CI template fixes: .github/workflows/invariant.yml now declares the GITHUB_TOKEN permissions the SARIF-upload step needs, and no longer fails the whole job when the repo doesn't have code scanning enabled.

Publishes invariant-sast 0.3.0 to PyPI via Trusted Publishing.

v0.2.0

Choose a tag to compare

@Ikurira Ikurira released this 29 Oct 13:43

Highlights

  • Z3 correctness fix: wildcard (*/?) matching was silently broken under z3-solver>=5.0; policies with wildcard actions/resources are now solved correctly.
  • IAM identity-policy checks: INV_AWS_002 (grant-permissiveness regression) and INV_AWS_003 (privilege-escalation primitives) now run on iam-policies/*.json.
  • INV_AWS_004: structural diff guard that flags regressions introduced through operators the SMT model does not yet represent.
  • invariant run: single entry point that runs the baseline scan tier always and the diff-scoped regression tier when --diff-base is given — no need to choose between scan and regression.
  • Policy-type subdirectory names centralized in a dependency-free invariant.policy_dirs module.
  • Expanded README: IAM support, the Z3 fix, performance notes, and why CI keeps scan/regression as separate jobs.

Publishes invariant-sast 0.2.0 to PyPI via Trusted Publishing.

v0.1.0

Choose a tag to compare

@Ikurira Ikurira released this 29 Oct 13:43

Initial PyPI release of invariant-sast (SMT-based guardrail SAST for AWS SCP/RCP JSON).