zairo
Git-diff-aware security impact analysis. zairo diffs a repository, builds a
dependency subgraph (via Trailmark)
around whatever changed, and can run an LLM vulnerability scan limited to
just that changed code — instead of re-scanning the whole codebase on every
change.
Output is a report.json (raw graph data) and a self-contained
report.html (interactive dependency graph viewer).
Install
pip install zairo
For local development:
python -m venv venv
source venv/bin/activate
pip install -e ".[dev]"
Usage
# Analyze uncommitted changes in a repo
zairo /path/to/repo
# Diff two refs, traverse 2 hops out from changed nodes, run an LLM scan
zairo /path/to/repo --base main --target HEAD --depth 2 --llm
Run zairo --help for the full option list.
Development
pytest
License
MIT — see LICENSE.
Metadata
Release files for zairo 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 |
|---|---|---|---|---|
| zairo-0.1.0.tar.gz | 20.8 kB | With provenance | Details for zairo-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zairo-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for zairo-0.1.0-py3-none-any.whl |
Total release size: 41.8 kB
Release files / zairo-0.1.0.tar.gz
| Download URL | zairo-0.1.0.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0286c0dab96082d8e36a28c604451eae5760f829a066be3b8fc0db49e5ad0807
|
|
BLAKE2b-256 checksum How to use checksums |
3544a199e44ed91102d1877ba51d2e235a19c4cc235a830987011a021d42309d
|
| 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 Aug 29, 2026.
Transparency logRelease files / zairo-0.1.0-py3-none-any.whl
| Download URL | zairo-0.1.0-py3-none-any.whl |
|---|---|
| Size | 21.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd92ad5fe7a5f2008afc4377a7aed37d7b3608aefb3826999bec1d316711736a
|
|
BLAKE2b-256 checksum How to use checksums |
d834dead18e9ae15409a0ef1c31ab8c27cccc4a8ff4559902607c887066a5b6c
|
| 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 Aug 29, 2026.
Transparency logSecurity for zairo 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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zairo-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 Aug 29, 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.