🛡️ Anchor Core (anchor-audit)
The Deterministic Runtime Governance & Compliance Kernel for Autonomous AI Systems.
Current release: 6.0.4 · Python 3.10–3.13
Anchor is a high-performance, dual-language (Rust/Python) infrastructure library designed to enforce strict regulatory invariants, architectural boundaries, and safety safeguards around autonomous AI agents and LLM application pipelines in real-time.
By executing compiled Abstract Syntax Tree (AST) query matchers and single-pass Deterministic Finite Automaton (DFA) regex sets, Anchor operates with zero-copy memory boundaries—designed to keep per-call overhead low. See benchmarks/bench_guard.py to measure it on your hardware.
🏎️ Core Architectural Horsepower
- Fast static scanning: Rust backend engine utilizing parallel directory walking via
rayonand memory-mapped files (memmap2). - Zero-Copy Memory Boundaries: Leverages PyO3 zero-copy buffer bridges to consume incoming network data frames straight from host ASGI server pools (like FastAPI) with zero heap allocation overhead.
- Asymmetric Cryptographic Identity: Every compiled audit log is bundled into an tamper-evident Decision Audit Chain (DAC) block, sealed locally using Ed25519 asymmetric keys and verified via constant-time hashing (
subtle::ConstantTimeEq). - Active Self-Healing Interception: Moves beyond passive post-mortem dashboards. If an active consumer agent drifts into an invariant violation, Anchor's runtime layer intercepts the thread, halts execution, and injects dynamic, domain-agnostic rerouting directives on the fly.
🏛️ Comprehensive Regulatory Scope
Anchor maps rules to the provisions they relate to (a pattern match is not a legal finding). Coverage includes:
- EU Artificial Intelligence Act (Regulation EU 2024/1689): Complete mapping from Chapter II Article 5 Prohibited Practices (subliminal manipulation, facial scraping safeguards) to Chapter III Articles 6–27 High-Risk System obligations (6-month log retention tracking under Art 12/19, Article 14 human override levers), stretching up to Article 99 turnover penalty metrics.
- U.S. Securities and Exchange Commission (SEC / FINRA): Hard automated boundaries protecting algorithmic trading setups under SEC Regulation SCI (System capacity loop circuit breakers), Exchange Act Rule 15c3-5 (Pre-trade credit and risk limit validation), and Cybersecurity Form 8-K outbound data exfiltration gates.
- Industry Frameworks: Built-in support for FINOS OSERA AI supply-chain resiliency blueprints, OWASP Top 10 LLM security controls, NIST AI RMF, and ISO/IEC 42001 standards.
📦 High-Velocity Installation
Deploy the compiled binary kernel straight into your production cluster workspace:
pip install anchor-audit
Anchor pulls in its runtime dependencies automatically (Click, HTTPX, PyYAML,
cryptography, wrapt, GitPython and the tree-sitter grammars), so the anchor
command is usable straight after install.
Optional extras:
pip install "anchor-audit[providers]" # OpenAI, Anthropic, Groq, Cohere, Ollama, ...
pip install "anchor-audit[server]" # FastAPI/ASGI gateway (anchor.app) + uvicorn
pip install "anchor-audit[dev]" # pytest, black, mypy
The CLI, the @guard decorator and the static scanner need none of these extras.
6.0.3 release highlights
- Telemetry remains explicitly opt-in and performs no network dispatch by default.
- Governance signatures are line-ending independent across Windows, macOS, and Linux.
- The package metadata, wheel smoke test, secret scanning, and developer extras are
aligned with the
pyproject.tomlbuild. - The committed governance public key is rotated; the private signing key is generated and retained outside the repository.
Initialize your local asymmetric cryptographic repository identity:
anchor init
Run a parallel static code safety audit across your local workspace:
anchor check .
🔌 Runtime Integration
Wrap a high-privilege agent routine or LLM invocation with a decorator. @guard only protects functions you wrap; unwrapped code is not covered.
from anchor import guard
@guard(domain="finance")
def execute_algorithmic_trade(order_payload):
# If the autonomous agent tries to route an un-vetted market order,
# Anchor audits the call payload before the function body runs and returns a BLOCKED_BY_ANCHOR directive on a match.
return route_order_to_exchange(order_payload)
from anchor.guard import guard is the equivalent spelling if you prefer to
import the decorator directly. Both are exercised by
tests/test_readme_example.py.
🌐 The AnimusLab Institution Network
Anchor Core acts as the local spoke auditing engine that feeds seamlessly into the wider, unified decentralized coordination hub ecosystem:
- Central Portal Hub: animuslab.dev
- Enterprise Fleet Cockpit: hub.animuslab.dev
- Statutory Rules Documentation: animuslab.dev/rules
- Authoritative Engineering Profile: tan.animuslab.dev
Maintained by AnimusLab.
⚠️ Limitations
@guard(Layer 2) covers only the functions you decorate. Keyword/pattern checks can be rephrased around; treat Anchor as one deterministic layer in defense-in-depth.- Telemetry is off by default. Set
ANCHOR_TELEMETRY=onto opt in; see docs/telemetry.md for exactly what is sent. - Static rules are pattern/AST based. Known detection gaps are tracked as
xfailtests intests/unit/test_detection_gaps.py.
1 maintainer
Metadata
1 maintainer
Release files for anchor-audit 6.0.5
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 | |
|---|---|---|---|---|
| anchor_audit-6.0.5.tar.gz | 226.7 kB | Without provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| anchor_audit-6.0.5-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details |
| anchor_audit-6.0.5-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| anchor_audit-6.0.5-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| anchor_audit-6.0.5-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details |
| anchor_audit-6.0.5-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 8.0 MB
Release files / anchor_audit-6.0.5.tar.gz
| Download URL | anchor_audit-6.0.5.tar.gz |
|---|---|
| Size | 226.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a63f016f160ad0aa39b442525b2be47eff6ad87f129c2484dcb8b3f36dfc5d29
|
|
BLAKE2b-256 checksum How to use checksums |
787ad0aa0bd84df28ab3e0db5daf73e9530281a4eaf4adafc73514d8fb9e7983
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / anchor_audit-6.0.5-cp310-abi3-win_amd64.whl
| Download URL | anchor_audit-6.0.5-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
9a779d765aabcbbb347f0f044afb8b8200e0ac5feb0bce7af641f793af02ab16
|
|
BLAKE2b-256 checksum How to use checksums |
23e94567204b317acc58a00def4b2c3fa7b08f604fdb0e02b52c00517c289fcd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / anchor_audit-6.0.5-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | anchor_audit-6.0.5-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
4a8a25d8eb867efe1aa71b40cfd0123fa57cb54983b418d7e858c15ec6bfc28d
|
|
BLAKE2b-256 checksum How to use checksums |
fd7a8efb479c3cc779719412c3d187b82df79c4b26d8bbcb3e202f359e9e8b75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / anchor_audit-6.0.5-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | anchor_audit-6.0.5-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
752e321c24e7b9eb67eb59584da97fefd9ec871afa824fedef9e71be1f2204ad
|
|
BLAKE2b-256 checksum How to use checksums |
b3904ca8a671ee17a15e670150942f2cd0bd0c86463e5740fd9b5fd062dc2558
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / anchor_audit-6.0.5-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | anchor_audit-6.0.5-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
27870754c0c78b4235c98cc00d8acea6391f9ccfa7ae62410cadfae244ecccf0
|
|
BLAKE2b-256 checksum How to use checksums |
7a2c16021f202652df6c76837fb10490c12678981ac503567014e86cef819591
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / anchor_audit-6.0.5-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | anchor_audit-6.0.5-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
89d398cc3345f8b11e03efcbe250b8eb34b42f251521869137998cea78cb1621
|
|
BLAKE2b-256 checksum How to use checksums |
fb33237e8729540783a5835ddbf2b25cc8e9a730458d441902280981f2c40a65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for anchor-audit 6.0.5
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
