Trust & security

Your data never leaves your infrastructure.

The tools are built to run inside your own environment. Nothing is sent to us, because there is nowhere to send it to.

  • Runs locally
  • Zero telemetry
  • Apache 2.0
  • No accounts

How your data is handled

Four guarantees, by architecture, not by promise.

These are not policy commitments we ask you to trust. They are properties of how the tools are built, verifiable in the open-source code before you install anything.

  • Runs locally

    Executes on your infrastructure and reads your code. You control where it runs and what it touches.

  • Zero telemetry

    No phone-home. The default screening path makes zero outbound calls, enforced by a CI socket gate.

  • No data leaves

    Your code and the artefacts the tools emit never reach us. There is no server to send them to.

  • Apache 2.0

    Full grant, patent included. Read every line before you trust it, then run it under your own terms.

Security posture

How the tools are built to be safe to run.

Each control below carries a proof-tag pointing at the mechanism that enforces it, in CI or in the CLI, not at a paragraph of reassurance.

  • No network at run time

    Default-mode screening makes zero outbound calls, enforced by a CI socket gate rather than documented in a policy.

    pytest-socket · CI-gated

  • No accounts, no keys

    Install from PyPI and run. No sign-in, no licence server, no export gate holding your evidence hostage.

    pip install · run

  • Tamper-evident output

    RiskForge hash-chains every audit entry with SHA-256; `riskforge verify` recomputes the chain and exits non-zero on any break.

    SHA-256 chained

  • Auditable supply chain

    Public source, pinned dependencies and CycloneDX SBOM output let you vet exactly what you run before it touches your systems.

    SBOM · pinned deps

Standards alignment

We align with the frameworks. We don't claim certification.

Tool outputs map to recognised control frameworks so your evidence is portable. Alignment is not the same as a certification, and we won't imply it is.

  • NIST AI RMF

    RiskForge dimensions map to GOVERN / MAP / MEASURE / MANAGE, so a single assessment serves both the EU AI Act and the US framework.

    Aligns, does not certify

  • ISO/IEC 42001

    Outputs map to Annex A controls to support an AI management system, increasingly a procurement gate for enterprise buyers.

    Aligns, does not certify

Responsible disclosure

Found something? Tell us privately first.

Report a security issue to security@aiexponent.com. We acknowledge reports, coordinate a fix, and credit reporters who want it. Machine-readable contact details are published at /.well-known/security.txt. For non-security bugs, use the public GitHub issues.

Disclosure contacts

See also the legal notices for the warranty disclaimer.

Related

Last reviewed: 2026-07-14