Skip to main content

Rust Audit

Auditor and auto-fixer for AI-generated Rust code: stubs, demo code, fake tests, fakes/mocks leaking into production, panic/unsafe misuse, swallowed errors, async pitfalls, and fake / hallucinated / typosquatted dependencies (slopsquatting).

Python 3.11+ stdlib only — no dependencies. English output.

Install

pipx install rust-audit      # or: pip install rust-audit
rust-audit selftest          # prints `selftest PASS`

From PyPI as rust-audit, whose wheel installs both commands: rust-audit and rustaudit run the same module. There is no separate one-word project on PyPI — it answers "This project name is too similar to an existing project" — so the spelling is served by this package's own entry point. Nothing is fetched or executed at install time, and the wheel carries the same rust_audit.py as the signed release asset — so the verify-before-use chain below still applies to the script you download.

The wheel's digest is attested by the workflow that built it, so you can check where it came from before running it:

gh attestation verify rust_audit-*-py3-none-any.whl -R Doken-Tokuyama/Rust-Audit

Quick start

# 0) verify before use — check the exact audited bytes before executing them
#    (key pin -> SSH signature -> checksum -> tag identity) and proceed only
#    on VERIFIED (exit 0); see SECURITY.md for the pinned key and the chain
scripts/verify_release.sh v0.2.6 ./rust_audit.py

python3 scripts/rust_audit.py selftest
python3 scripts/rust_audit.py scan  <rust-project> --format terminal,md,json,sarif --fail-on high
python3 scripts/rust_audit.py fix   <rust-project> --dry-run
python3 scripts/rust_audit.py cargo <rust-project> --deep --supply-chain

Exit codes: 0 clean · 1 findings at/above --fail-on · 2 execution error. Every run writes a not-executed report (report/not-executed-<date>.md) listing the checks that could not run and how to enable them — read it before calling an audit complete.

As a Freebuff agent skill: install rust-audit into Freebuff on any machine by following docs/freebuff-skill-install.md.

Tests

Production E2E suite: the real CLI audited against real Rust workspaces (BurntSushi/ripgrep and tokio-rs/tokio, each pinned by commit — no demo fixtures), with per-project goldens. Needs network to fetch the pinned workspaces, Python 3.11+ and pytest in a venv:

python3 -m venv .venv && .venv/bin/pip install pytest
.venv/bin/python -m pytest tests/

CI runs exactly that on every push to main, every v* release tag and every pull request (.github/workflows/tests.yml: Python 3.11 and 3.13, pytest as the only install), so a commit is verified without anyone remembering to type it. tests/test_ci_workflows.py keeps the job honest: it must exist, it must run this suite, it may not swallow a failure, and every action is pinned to one commit SHA across all workflows. A second job audits the published artifact: python -m build, install with --no-index into a clean venv, rust-audit selftest, then the golden scan from both the wheel and the checkout, which scripts/check_wheel_parity.py requires to agree. What the jobs prove — and what they do not, including why they cannot block a direct push to main — is in docs/ci.md.

See SKILL.md for the rule catalog (R01–R21), the auto-fix policy, the CI templates and the honest limitations.

Security

The trust model is explicit: what executes (literal cargo argv, no shell), what leaves the machine (opt-in --online registry/OSV lookups only) and what writes to disk (transactional fix). See SECURITY.md — including the notes for static skill auditors.

Release assets are SSH-signed: an install can verify it has the exact audited rust_audit.py with preinstalled ssh-keygen alone — commands and the pinned signing key live in SECURITY.md.

Hardened scanners can enforce the static-only contract in code: every subcommand accepts --no-exec, under which process creation is impossible (one guarded entry point refuses every spawn) and each check that would have executed is recorded as skipped in the not-executed report.

License

Apache License 2.0 — see LICENSE. Copyright (c) 2026 Antonio Cantallops Alba · contact@exyonq.org

Metadata

Release files for rust-audit 0.2.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rust-audit 0.2.6
File Size Uploaded Provenance
rust_audit-0.2.6.tar.gz 76.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for rust-audit 0.2.6
File Interpreter ABI Platform
rust_audit-0.2.6-py3-none-any.whl Python 3 none any Details

Total release size: 125.9 kB

Release files / rust_audit-0.2.6.tar.gz

Download URL rust_audit-0.2.6.tar.gz
Size 76.4 kB
Tags Source
SHA-256 checksum
How to use checksums
feb8533f613638b30f98df88d4a9c912e73d9b4e23977a784ae1dca4c6a10693
BLAKE2b-256 checksum
How to use checksums
d870aa245788417486afe7ed58678ba19ad8bd8424d82399e78f21f43b24f733
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 Oct 20, 2026.

Transparency log

Release files / rust_audit-0.2.6-py3-none-any.whl

Download URL rust_audit-0.2.6-py3-none-any.whl
Size 49.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
607d14b1cf149e072d29b6cda93bab26da93fa54c1b11f35d13d7ec4d43ced7e
BLAKE2b-256 checksum
How to use checksums
ea7cbb7a0935e314280ae246a0db9586e77750d4219cfd3ddca8d5fb5567b153
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 Oct 20, 2026.

Transparency log

Security for rust-audit 0.2.6

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.

Select from 2 files

Attestation for rust_audit-0.2.6.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 20, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page