Building the standard open stack for deterministic AI safety and runtime governance.
Our core systems are Apache-2.0 licensed, public, and built in the open. We welcome software engineers, security researchers, and policy analysts to collaborate on our core repositories.
- Track
- Open Source Contributors
- Targets
- 3
- Access
- By inquiry
The AnimusLab ecosystem relies on open infrastructure. Contributors work across high-performance Rust scanning engines, PyO3 bindings, Tree-sitter AST queries, Next.js sovereign portals, and .anchor policy rule DSLs.
AnimusLab open-sourced the Anchor kernel, animus-manifesto frontend, and the animuslab-case-studies forensic archive containing 5 deep real-world incident models.
# Contributor Build Workflow
$ git clone https://github.com/AnimusLab/Anchor.git
$ cd Anchor
$ maturin develop # Build PyO3 Rust bindings locally
$ pytest tests/ # Run core governance test suiteWhat the track produces.
- 01
Source Adapters: Writing custom AST pattern matchers and crawlers for Canon monitoring.
- 02
Compiler Speed: Improving WASM sandbox runtime overhead and PyO3 zero-copy memory boundaries.
- 03
Policy DSL: Expanding statutory rule definitions for new regional regulatory frameworks.
- 04
Documentation: Refining tutorials, CLI references, and architecture guides.
Open workstreams.
Rust Engine Optimization
Refining parallel directory walking and SIMD regex matching in src/scanner/walker.rs.
Forensic Case Study Modeling
Documenting major real-world systemic failures (e.g. Citi Revlon $893M wire, TSB £600M outage) in .anchor policy formats.
Control Plane UI & Telemetry
Enhancing Next.js glassmorphism control plane applications and WebSocket stream visualizations.
How to start.
- 01
Star and fork our primary repository: github.com/AnimusLab/Anchor.
- 02
Explore open issues on GitHub tagged 'good first issue' or 'help wanted'.
- 03
Read our Contributor License Agreement & Developer Certificate of Origin (DCO).
- 04
Connect with maintainers via GitHub Discussions or email tan@animuslab.dev.