Axiom
Explainable access-risk intelligence for SaaS permissions and smart-contract operations.
Axiom turns an access snapshot into evidence-backed review priorities, identity risk scores, HTML/JSON/Markdown/CLI reports, and a human-approved dry-run remediation plan. It can correlate privileged SaaS access with Vyper Guard contract findings and optionally use Amazon Bedrock for natural-language explanations. Rules and severity remain deterministic; AI is advisory only.
Why Axiom
Access rarely becomes dangerous through one signal. Axiom combines stale identities, unused permissions, excessive scope, peer drift, unusual activity, and contract-control exposure into one explainable review surface. It never revokes access automatically.
Quickstart
python -m venv .venv
.venv/bin/pip install -e '.[dev]'
.venv/bin/axiom access-risk examples/access_risk_demo.json --format cli \
--contract-report examples/access_risk_contract_report.json
Generate the Vyper Guard-style report UI:
.venv/bin/axiom access-risk examples/access_risk_demo.json --format html \
--contract-report examples/access_risk_contract_report.json \
--output /tmp/axiom-access-risk.html
The report contains a score, per-identity risk, evidence tables, correlation notes, limitations, and a simulated before/after projection. No grant is changed.
AWS workflow
The aws/ directory contains a deployable SAM pipeline:
S3 input snapshot → Lambda analysis → S3 JSON/Markdown/HTML reports
↘ SNS aggregate alert
The Lambda has least-privilege object access, encrypted private buckets, CloudWatch logs, and an optional Bedrock explanation path with deterministic fallback. See aws/DEPLOY.md.
Test
.venv/bin/pytest
.venv/bin/ruff check src tests aws
The checked-in synthetic demo is deliberately transparent: it demonstrates behavior and evidence flow, not production accuracy or compliance.
Project boundary and attribution
Axiom is a standalone package focused on access-risk intelligence. Its contract correlation adapter accepts Vyper Guard-style JSON reports as an optional integration. Reusable access-risk components were derived from the MIT-licensed Vyper Guard project; see NOTICE and LICENSE.
Metadata
Release files for axiom-access-risk 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 | |
|---|---|---|---|---|
| axiom_access_risk-0.1.0.tar.gz | 35.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axiom_access_risk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 56.0 kB
Release files / axiom_access_risk-0.1.0.tar.gz
| Download URL | axiom_access_risk-0.1.0.tar.gz |
|---|---|
| Size | 35.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f1763ea421f8f0c8690ed3eb71adbf6e3bf843e7bbe29c81d59c4e098cdcea0
|
|
BLAKE2b-256 checksum How to use checksums |
0048da2d6ce7d859721b8b03d306209f0798686191e83224e5701e3c26bb5f65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 24, 2026.
Transparency logRelease files / axiom_access_risk-0.1.0-py3-none-any.whl
| Download URL | axiom_access_risk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
257c2272ee867253f37a64bf61871a5e3c3739be8c4eea30bb2999c6383c7073
|
|
BLAKE2b-256 checksum How to use checksums |
29c6ed5223763c8d24c0738b057b068a7392d4c1cabf1b32a4827a380386f943
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 24, 2026.
Transparency logSecurity for axiom-access-risk 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 axiom_access_risk-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 Oct 24, 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.