Veridor
Veridor is a CI-first authorization regression runner. You declare what each identity is allowed to do; Veridor issues the same request as every declared identity, compares what happened against what you declared, and fails the build when the answer changes. It is not a scanner and not a pentest: it invents no policy, discovers no routes, sends no payloads, and cannot tell you whether your declaration is right — only whether your target still agrees with it. Read what a finding does and does not mean before you read a report. Runtime is the Python standard library only.
This page is the package description. The full documentation is the README in the repository and https://docs.veridor.org/. Each release is listed in CHANGELOG.md. The project is in early alpha: the configuration format, commands, flags and report formats may still change between minor versions, so pin a version.
Install
Python 3.11 or newer, no runtime dependencies. Install into a virtual
environment or with pipx; Homebrew and Debian system Pythons refuse a bare
pip install (PEP 668).
python3.12 -m venv .venv && . .venv/bin/activate
python -m pip install veridor
veridor --version
The wheel carries the veridor package and nothing else. The demo target and
the fixtures the quickstart uses live in the repository, so with a pip install
start from your own API.
The three verbs
| Verb | The question |
|---|---|
map |
What don't I cover, and what would a compromise reach? |
run |
Does the boundary hold, and did it change? |
mutate |
Would my suite actually catch a regression? |
Only run gates on what it discovered. map exits 0 whatever it finds unless
you opt in to --fail-on-drift, and mutate has its own exit code. The
exit codes and the
CI/CD integrations
are in the README.
Links
Metadata
Release files for veridor 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| veridor-0.1.0.tar.gz | 531.5 kB | With provenance | Details for veridor-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| veridor-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for veridor-0.1.0-py3-none-any.whl |
Total release size: 1.0 MB
Release files / veridor-0.1.0.tar.gz
| Download URL | veridor-0.1.0.tar.gz |
|---|---|
| Size | 531.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b79284ae84efc895e3aa8eb7bd9ae4e0cb4f3ab7a1fc0e47807b961136aea06e
|
|
BLAKE2b-256 checksum How to use checksums |
62be419fedf48210b5c18f9a86859198ab1b595710a3ae1ff8457d67cf675bf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / veridor-0.1.0-py3-none-any.whl
| Download URL | veridor-0.1.0-py3-none-any.whl |
|---|---|
| Size | 483.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
67fb7444f25b6efaa501648c40bcf62026896df6df62603ce7379054155c3ab7
|
|
BLAKE2b-256 checksum How to use checksums |
b17eeeb18e716c0228c34b055a90c3e49ee7fc7e8b4d6201fe5d82adadb4203d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logSecurity for veridor 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for veridor-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.