Skip to main content

tibet-report

Audit dossier assembler with TIBET provenance — verifiable remediation reports.

Part of the TIBET ecosystem by Humotica.

What it does

tibet-report assembles evidence from TIBET token chains, wayback seals, pol health checks, and Phantom sessions into a single verifiable audit dossier.

The report is not the proof — the chain of tokens, seals, and manifests is. tibet-report makes that chain readable for humans and verifiable for auditors.

Install

pip install tibet-report

Quick start

from tibet_report import ReportSession, build_dossier

session = ReportSession(
    report_id="RPT-001",
    title="Security Remediation — Example Corp",
    customer="Example Corp",
    created_by="Jasper van de Meent — Humotica",
)

session.add_finding("SSL chain broken", "Intermediate cert missing")
session.add_action("Added intermediate cert to nginx", status="fixed")
session.add_verification("SSL verified with openssl", status="verified")

report_path, manifest = build_dossier(session, output_dir="./reports")

CLI

# Build a dossier
tibet-report build \
  --customer "Example Corp" \
  --assessor "Jasper van de Meent" \
  --tokens remediation_chain.json \
  --pre-seal pre_fix.json \
  --post-seal post_fix.json \
  --out ./reports

# Verify dossier integrity
tibet-report verify reports/RPT-001.md --manifest reports/RPT-001.manifest.json

Chain of custody

Every dossier includes a manifest that binds the report to its source evidence:

  • SHA256 hashes of all input artifacts (tokens, seals, pol runs)
  • SHA256 hash of the generated report
  • Chain-of-custody hash combining all above
  • Optional TIBET dossier token for provenance

Tampering with the report after generation is detectable via tibet-report verify.

Input sources

Source Package What it provides
TIBET tokens tibet-core Step-by-step provenance chain
Wayback seals tibet-wayback Pre/post system state snapshots
Wayback diffs tibet-wayback What changed between states
Pol runs tibet-pol Health check results
Phantom sessions phantom Session context (who/when/where)

Output

  • Markdown — readable, diffable, git-friendly
  • HTML — formatted for clients and auditors
  • JSON manifest — machine-readable chain-of-custody

Enterprise

For private hub hosting, SLA support, custom integrations, or compliance guidance:

Enterprise enterprise@humotica.com
Support support@humotica.com
Security security@humotica.com

License

MIT

Credits

Designed by Jasper van de Meent. Built by Jasper and Root AI as part of HumoticaOS.


Stack-positie: Groep evidence · Bootstrap = OSAPI-handshake naar tibet + jis (fail → snaft-rule + tibet-pol-rapport) · ← tibet-nis2 · See STACK.md · See demo/golden-path/ for the spine end-to-end.

Metadata

Release files for tibet-report 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tibet-report 0.1.2
File Size Uploaded Provenance Actions
tibet_report-0.1.2.tar.gz 18.9 kB Without provenance Details for tibet_report-0.1.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tibet-report 0.1.2
File Interpreter ABI Platform Actions
tibet_report-0.1.2-py3-none-any.whl Python 3 none any Details for tibet_report-0.1.2-py3-none-any.whl

Total release size: 34.9 kB

Release files / tibet_report-0.1.2.tar.gz

Download URL tibet_report-0.1.2.tar.gz
Size 18.9 kB
Tags Source
SHA-256 checksum
How to use checksums
ed309813181bb2c913138de9789f6a2b8bf12079308bdc26e3b7595f3ac755ec
BLAKE2b-256 checksum
How to use checksums
4f72553ad1bfdc70f1bc409aaa32baceecb98eb9b1f83a531cdb8aa7a7b29cf1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.5

Release files / tibet_report-0.1.2-py3-none-any.whl

Download URL tibet_report-0.1.2-py3-none-any.whl
Size 16.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e8c384cdeff121149aa50deb66c2ba02aa6e7a4f2d8853fb6dcd8fcc5b5fb5e4
BLAKE2b-256 checksum
How to use checksums
47455a3d911cc86753dbadda53203f90138ffdaa645b43fe8742483b574f7ac5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.5

Security for tibet-report 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page