Compliance Health Scanner - Like Lynis, but for regulations. The Diaper Protocol for busy parents.
Project description
TIBET Audit
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โข)
The 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
The Full Diaper Toolkit
| 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.
Installation
pip install tibet-audit
With TIBET vault integration (for cryptographic audit trails):
pip install "tibet-audit[tibet]"
Usage
Scan for Issues
# 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
# Mercury (JIS + sovereignty)
audit-tool scan --categories jis,sovereignty,provider
# Signed handshake (opt-in)
audit-tool scan --high-five
Fix Issues
# 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
List Available Checks
# Show all checks
tibet-audit list
# Filter by category
tibet-audit list --category gdpr
tibet-audit list --category ai_act
Call Mama (Send Report)
# 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
Mercury Commands
# Compliance roadmap
audit-tool roadmap ./my-ai-project
# Value-based upgrade suggestions
audit-tool upgrades ./my-ai-project
# Compliance drift (JSON reports)
audit-tool diff report_old.json report_new.json
Cry Mode (Verbose)
# See EVERYTHING - passed checks, references, fix commands
tibet-audit scan --cry
Available Checks
GDPR Compliance
| 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 | โ |
EU AI Act Compliance
| 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 | โ |
๐ฐ๐ท South Korea PIPA Compliance
| 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!
๐ฏ๐ต Japan APPI Compliance
| 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 | โ |
๐ธ๐ฌ Singapore PDPA Compliance
| 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 | โ |
๐ฆ๐บ Australia Privacy Act Compliance
| 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 | โ |
๐ง๐ท Brazil LGPD Compliance
| 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 | โ |
๐ธ๐ฆ๐ฆ๐ช Gulf PDPL Compliance (Saudi Arabia, UAE)
| 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!
๐ณ๐ฌ Nigeria NDPR Compliance
| 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!
๐ง Penguin Act (Antarctica)
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. ๐ง
Global Coverage Summary
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 |
Scoring
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 Integration
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" โ
For Enterprise
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)
Philosophy
"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
Contributing
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
License
MIT License - Use it, fork it, make money with it. Just don't blame us if the auditor still asks questions.
Credits
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"
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file tibet_audit-0.9.0.tar.gz.
File metadata
- Download URL: tibet_audit-0.9.0.tar.gz
- Upload date:
- Size: 54.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.5
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
85766c16d95beacd7f283212f035c86d01fff5698fcfea34a9341c14ba70ece4
|
|
| MD5 |
355ce67f29becfcff73bbc59d2ca338f
|
|
| BLAKE2b-256 |
325ebf0d91aa3080d10f00686171b623a3ec321d10461611e167f0c4618b7422
|
File details
Details for the file tibet_audit-0.9.0-py3-none-any.whl.
File metadata
- Download URL: tibet_audit-0.9.0-py3-none-any.whl
- Upload date:
- Size: 72.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.5
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
c9bd4d4866135608313a725af6e92c29ba96df1a4bc55266dd3f1c7596de09e7
|
|
| MD5 |
bda1c0aef0d27d3233d20b173855c0e6
|
|
| BLAKE2b-256 |
6273405b1123a7a7aae8259ff74167d4d40d726b27df80c0e98ee8486633b748
|