Quick Start
Prerequisites
Section titled “Prerequisites”- Bun ≥ 1.1 or Node.js ≥ 18
Install
Section titled “Install”# with Bunbun install -g rulestatus
# with npm / npx (no install needed)npx rulestatus init-
Create your config
Run in your project root:
Terminal window rulestatus initThe first prompt asks what’s driving the setup. Select the option that matches your situation — if an enterprise customer asked for EU AI Act compliance, pick that and the rest of the prompts will pre-fill the right defaults.
This creates
.rulestatus.yaml. -
Generate compliance templates
Terminal window rulestatus generate --allCreates all required documentation stubs in
docs/andconfig/. Each file has inline comments explaining what every field means and what auditors look for. -
Fill in the TODOs
Open the generated files and replace every
# TODOwith your actual system details. The more complete the information, the higher the evidence strength score. -
Run checks
Terminal window rulestatus runOutput:
Rulestatus v1.0 — EU AI Act (2024/1689)System: My AI System v1.0Actor: provider | Risk level: high-risk──────────────────────────────────────────────────Art. 9 - Risk ManagementPASS ASSERT-EU-AI-ACT-009-001-01 Risk management system documentation existsFAIL ASSERT-EU-AI-ACT-009-002-B-01 Risk register includes emerging risks-> No risk entries with source: emerging or category: misuse found.──────────────────────────────────────────────────Results: 38 passed | 5 gaps | 0 warnings | 2 attested | 1 manual -
Fix each gap
Terminal window rulestatus explain ASSERT-EU-AI-ACT-009-002-B-01Shows the legal basis, what was scanned, what was found, and exactly what to add. For EU AI Act rules it also shows why that specific gap blocks enterprise deals — useful context when you’re fixing gaps ahead of a security review.
Next steps
Section titled “Next steps”- Configuration reference — all
.rulestatus.yamlfields - GitHub Actions — block PRs on evidence gaps
- EU AI Act checks — all 43 assertions explained