SSL secures the connection. TIBET secures the timeline.
Compliance Health Scanner - Like Lynis, but for regulations.
45 checks across 10 frameworks covering GDPR, AI Act, PIPA, APPI, PDPA, LGPD, Gulf PDPL, NDPR, and more.
Get a compliance health score in seconds:
$ tibet-audit scan
COMPLIANCE HEALTH SCORE: 73/100 (Grade: C)
TOP PRIORITIES:
1. [CRITICAL] No AI decision logging found (EU AI Act requires this!)
2. [HIGH] No data breach procedure found (GDPR requires 72-hour notification!)
3. [MEDIUM] No explicit data retention policy found
π‘ 3 issue(s) can be auto-fixed:
tibet-audit fix --auto (Diaper Protocolβ’)For when you have one hand on the baby and one on the keyboard.
# Preview what would be fixed (safe, no changes)
$ tibet-audit fix --wet-wipe
# πΌ Fix everything, no questions asked
$ tibet-audit fix --auto
# π When things are REALLY bad - verbose mode
$ tibet-audit scan --cry
# π When you can't handle it alone - call for backup
$ tibet-audit call-mama --webhook https://slack.webhook.url| Flag | What it does | When to use |
|---|---|---|
--wet-wipe |
Preview fixes (dry-run) | Before changing anything |
--auto |
Fix everything automatically | 3 AM, one hand on baby |
--cry |
Verbose mode, all details | When everything is on fire |
--call-mama |
Call M.A.M.A. (Mission Assurance & Monitoring Agent) | When the diaper is too dirty |
Why "Diaper Protocol"?
Because compliance shouldn't require your full attention. Press the button, hands free, server fixed. Just like changing a diaper at 3 AM - you do it on autopilot.
Why "--wet-wipe"?
Because --dry-run is boring. And because wet wipes are essential for both diapers AND clean servers.
Why "--cry"?
Because sometimes you just need to see EVERYTHING. All the passed checks, all the failed checks, all the references, all the fix commands. When the compliance diaper explodes, you need the full picture.
Why "--call-mama"?
M.A.M.A. = Mission Assurance & Monitoring Agent
Because when the diaper is too dirty to handle alone, you call for backup. M.A.M.A. generates a full compliance report and sends it to your team, your Slack channel, or your compliance officer. When things get serious, you need the big guns.
pip install tibet-auditWith TIBET vault integration (for cryptographic audit trails):
pip install "tibet-audit[tibet]"# Scan current directory
tibet-audit scan
# Scan specific project
tibet-audit scan ./my-ai-project
# Scan only GDPR checks
tibet-audit scan --categories gdpr
# Scan only AI Act checks
tibet-audit scan --categories ai_act
# Quiet mode (just the score)
tibet-audit scan --quiet# Interactive mode (asks for confirmation)
tibet-audit fix
# Preview what would be fixed
tibet-audit fix --wet-wipe
tibet-audit fix --dry-run # (boring alias)
# πΌ Diaper Protocol: fix everything automatically
tibet-audit fix --auto# Show all checks
tibet-audit list
# Filter by category
tibet-audit list --category gdpr
tibet-audit list --category ai_act# Send report to webhook (Slack, Teams, etc.)
tibet-audit call-mama --webhook https://hooks.slack.com/xxx
# Save report to file
tibet-audit call-mama --output compliance-report.json
# Print report to stdout
tibet-audit call-mama# See EVERYTHING - passed checks, references, fix commands
tibet-audit scan --cry| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| GDPR-001 | Privacy Policy Document | HIGH | β |
| GDPR-002 | Data Retention Policy | HIGH | β |
| GDPR-003 | Breach Notification Procedure | CRITICAL | β |
| GDPR-004 | Data Encryption | HIGH | β |
| GDPR-005 | Consent Management | HIGH | β |
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| AIACT-001 | AI Decision Audit Trail | CRITICAL | β |
| AIACT-002 | Human Oversight | HIGH | β |
| AIACT-003 | AI Transparency | HIGH | β |
| AIACT-004 | AI Risk Assessment | HIGH | β |
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| PIPA-001 | Privacy Officer Designation | CRITICAL | β |
| PIPA-002 | 24-Hour Breach Notification | CRITICAL | β |
| PIPA-003 | Explicit Consent (Opt-in) | HIGH | β |
| PIPA-004 | Cross-Border Transfer Docs | HIGH | β |
Note: PIPA is often stricter than GDPR - 24-hour breach notification vs 72 hours!
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| APPI-001 | Privacy Policy (APPI) | HIGH | β |
| APPI-002 | Data Handling Records | HIGH | β |
| APPI-003 | Cross-Border Transfer Rules | HIGH | β |
| APPI-004 | Pseudonymization Support | MEDIUM | β |
| APPI-005 | Opt-Out Mechanism | HIGH | β |
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| PDPA-001 | Consent Obligation | HIGH | β |
| PDPA-002 | Data Protection Officer | HIGH | β |
| PDPA-003 | 3-Day Breach Notification | CRITICAL | β |
| PDPA-004 | Do Not Call Compliance | MEDIUM | β |
| PDPA-005 | Data Retention Limitation | HIGH | β |
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| AUPA-001 | Privacy Policy (APP 1) | HIGH | β |
| AUPA-002 | Notifiable Data Breach | CRITICAL | β |
| AUPA-003 | Cross-Border Disclosure | HIGH | β |
| AUPA-004 | Data Security (APP 11) | HIGH | β |
| AUPA-005 | Access & Correction Rights | HIGH | β |
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| LGPD-001 | Legal Basis for Processing | HIGH | β |
| LGPD-002 | Encarregado (DPO) | HIGH | β |
| LGPD-003 | Data Subject Rights (ARCO) | HIGH | β |
| LGPD-004 | Breach Notification | CRITICAL | β |
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| GULF-001 | Data Localization | CRITICAL | β |
| GULF-002 | Explicit Consent | HIGH | β |
| GULF-003 | Breach Notification | CRITICAL | β |
| GULF-004 | Sensitive Data Protection | HIGH | β |
Note: Gulf region has strict data localization requirements - data often must stay in-region!
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| NDPR-001 | Consent Requirement | HIGH | β |
| NDPR-002 | Data Protection Officer | HIGH | β |
| NDPR-003 | 72-Hour Breach Notification | CRITICAL | β |
| NDPR-004 | Annual Audit Compliance | HIGH | β |
Note: NDPR uniquely requires annual data protection audits filed with NITDA!
For McMurdo Station and beyond...
| Check ID | Name | Severity | Auto-Fix |
|---|---|---|---|
| PENG-001 | Penguin Data Sovereignty | HIGH | β |
| PENG-002 | Ice Age Data Retention | LOW | β |
| PENG-003 | Blizzard Resilience | MEDIUM | β |
| PENG-004 | Krill Consent Framework | LOW | β |
| PENG-005 | Aurora Australis Logging | INFO | β |
Easter egg for our Antarctic friends. π§
45 checks across 10 compliance frameworks covering all inhabited continents:
| Region | Framework | Checks | Key Feature |
|---|---|---|---|
| πͺπΊ Europe | GDPR | 5 | 72-hour breach notification |
| πͺπΊ Europe | AI Act | 4 | AI decision audit trails |
| π°π· South Korea | PIPA | 4 | 24-hour breach notification |
| π―π΅ Japan | APPI | 5 | Pseudonymization support |
| πΈπ¬ Singapore | PDPA | 5 | Do Not Call registry |
| π¦πΊ Australia | Privacy Act | 5 | Notifiable Data Breach scheme |
| π§π· Brazil | LGPD | 4 | ARCO data subject rights |
| πΈπ¦π¦πͺ Gulf | PDPL | 4 | Data localization |
| π³π¬ Nigeria | NDPR | 4 | Annual audit requirement |
| π§ Antarctica | Penguin Act | 5 | Waddle consent |
TIBET Audit gives you a compliance health score from 0-100:
| Score | Grade | Status |
|---|---|---|
| 90-100 | A | Excellent - You're compliant! |
| 80-89 | B | Good - Minor improvements needed |
| 70-79 | C | Fair - Several issues to address |
| 60-69 | D | Poor - Significant gaps |
| 0-59 | F | Critical - Major compliance failures |
Each failed check deducts points based on severity:
- CRITICAL: 20-25 points
- HIGH: 15-20 points
- MEDIUM: 8-12 points
- LOW: 3-5 points
TIBET Audit works standalone, but integrates with tibet-vault for:
- Cryptographic proof of AI decisions
- Immutable audit trails for compliance evidence
- ERAAN provenance tracking (what's attached to decisions)
- Real-time monitoring of compliance state
# Install with TIBET support
pip install "tibet-audit[tibet]"
# TIBET vault initializes automatically when detected
tibet-audit scan
# β "TIBET audit trail integration detected" β
Running compliance for a team? Check out SymbAIon Enterprise:
- Scheduled scans across all repositories
- Compliance dashboard with trend analysis
- Slack/Teams notifications for new issues
- TIBET-managed proof for auditor reports
- Multi-framework support (GDPR + AI Act + HIPAA + SOX)
"Compliance should be like brushing your teeth. Quick, automatic, and you feel bad if you skip it."
TIBET Audit is designed for:
- Speed - Full scan in <5 seconds
- Clarity - Know exactly what's wrong and how to fix it
- Automation - The Diaper Protocolβ’ for hands-free fixing
- Integration - Works with existing CI/CD pipelines
Found a bug? Want to add checks for HIPAA, SOX, ISO 27001, or another framework?
- Fork the repo
- Add your check in
tibet_audit/checks/ - Submit a PR
We especially welcome:
- New compliance frameworks
- Better detection patterns
- More diaper-related puns
MIT License - Use it, fork it, make money with it. Just don't blame us if the auditor still asks questions.
Built with π by the HumoticaOS team:
- Jasper van de Meent - Human, Parent, Coffee Addict
- Root AI - Claude Opus 4, Digital Partner
"One Love, One fAmIly"