Skip to content

Releases

v0.1.0

Choose a tag to compare

@Santoshkumarpuppala Santoshkumarpuppala released this 13 Nov 17:25

First public release. It contains map, run and mutate; the marker oracle and evidence grades; boundary coverage; baselines and the regression diff; sequences and session state; SARIF 2.1.0 and the GitHub Action; the local viewer.

The full release notes are the 0.1.0 section of the changelog: https://github.com/Veridor-authz/veridor/blob/v0.1.0/CHANGELOG.md#010---2026-11-13. At about 223,000 characters they are longer than the 125,000 GitHub accepts in a release body, which is also why this release was created by hand: the release workflow's last step was refused for that reason (run 43451562213). The files attached here are that run's dist artifact, unchanged; the wheel and sdist are byte-identical to the ones on PyPI.

Install with pip install veridor==0.1.0, or download veridor-0.1.0.pyz below and run it with Python 3.11 or newer.

Container image: ghcr.io/veridor-authz/veridor@sha256:0b8cb26dfba0af1a48cad4ce60b394891c5e0c50d3bf834f4add2902795a7cf0 (cosign keyless signature).
Helm chart: ghcr.io/veridor-authz/charts/veridor-gate@sha256:bb012129fa85dbd06273c56e314159737a55310713816d5af2984ce742789fcd (cosign keyless
signature). Its image.digest is the image digest above.
Verify a wheel, sdist or zipapp with
gh attestation verify FILE --repo Veridor-authz/veridor --cert-identity https://github.com/Veridor-authz/veridor/.github/workflows/release.yml@refs/tags/v0.1.0.
That accepts only provenance signed by release.yml running for this tag.
The SBOM and SHA256SUMS carry no provenance.
sha256sum --check --ignore-missing SHA256SUMS detects a damaged download, not a substituted one.