TrustLint

Offline Node.js compliance linter for AI agents — scans text against the bundled ComplyEdge rule corpus using Tier 1 regex patterns. No API key required.
Catches EU AI Act, SOX, HIPAA, GDPR, COPPA, and PCI DSS violations before they reach production.
Hosted API vs. Offline Linter
TrustLint runs locally and needs no API key. For runtime policy enforcement and
an application-facing evidence trail, use the hosted
ComplyEdge Python SDK.
Installation
This is the npm package README. PyPI uses its own
Python-first long description, while both distributions use
the same bundled rule corpus.
Node.js:
npm install trustlint
Python:
pip install trustlint
Both bundle the rule corpus, so neither needs a local rules/ directory.
Limitations (Node vs. Python)
- The npm and PyPI packages share a rule corpus but not the same engine. Python
TrustLint evaluates temporal and effective-date rule state; the Node engine
runs Tier 1 regex and hybrid Tier-1 patterns only. Semantic-only YAML
conditions are skipped.
- In the current npm release, 52 Tier-1 rules load from 64 bundled YAML files.
A version number is not a parity claim with PyPI TrustLint.
Quick Start
trustlint check --text "We expect revenue to increase by 25% next quarter"
trustlint check prompt.txt
echo "Deploy social credit score for citizens" | trustlint check
trustlint check --text "social credit score" --jurisdiction EU
trustlint check --text "earnings forecast" -v
Commands
trustlint check
Scan text for compliance violations against the loaded rule corpus.
trustlint check --text "your AI prompt here"
trustlint check myfile.py
trustlint check --text "text" -j EU
trustlint check --text "text" -v
Exit codes:
0 — No critical/high violations (CI pass)
1 — Critical or high severity violations found (CI fail)
2 — Input error (missing file, no rules loaded)
trustlint rules list
Show all loaded compliance rules with severity and jurisdiction.
trustlint rules list
trustlint rules list -j US
trustlint init
Create a .trustlint.yaml configuration file in the current directory.
trustlint init
trustlint init --force
Example Output
TrustLint Report
────────────────────────────────────────────────────────────
[CRITICAL] SOX_HYBRID_MATERIAL_DISCLOSURE_001
Hybrid SOX Material Information Disclosure Prevention
Jurisdiction: US | Matched: Forward-looking statements requiring analysis
────────────────────────────────────────────────────────────
1 critical/high, 0 medium/low (12 rules evaluated)
How It Works
TrustLint loads YAML rule files from the ComplyEdge rule corpus (rules/regulations/). Each rule contains regex patterns for Tier 1 (fast, deterministic) detection. The engine:
- Loads all
.yaml rule files from the rules directory
- Extracts
regex conditions and hybrid_detection.tier1_config.risk_flag_patterns
- Matches patterns against the input text
- Reports violations with rule ID, severity, jurisdiction, and citation
No API calls are made in offline mode. For deeper Tier 2 LLM analysis, set the COMPLYEDGE_API_KEY environment variable (requires a ComplyEdge account).
CI/CD Integration
GitHub Actions
- name: Compliance check
run: |
pip install trustlint
trustlint check --text "${{ github.event.pull_request.body }}"
Pre-commit hook
#!/bin/sh
trustlint check "$1" || exit 1
Rules Coverage
| EU | EU AI Act Article 5 | Social scoring, subliminal manipulation, biometric categorisation |
| US | SOX, HIPAA, COPPA, TCPA | Material disclosure, PHI protection, child data |
| Global | PCI DSS | Payment card data detection |
Configuration
Create .trustlint.yaml with trustlint init:
Development
pip install -e packages/trustlint/
python -m pytest tests/unit/trustlint/ -v
License
Apache-2.0 — ComplyEdge