Description
Verifiable Audit Logging for Laravel. Unlike traditional activity log packages, Chronicle records events in an append-only ledger protected by hash chaining, allowing audit history to be verified for tampering.
Chronicle is designed for systems that require reliable audit trails such as:
- security logging
- financial systems
- compliance and regulatory reporting
- forensic analysis
- operational observability
Why Chronicle?
Most activity-log packages store events in a database table. Those records can usually be modified, deleted, or reordered - which makes them unreliable for security auditing or compliance.
Chronicle takes a different approach. Events are recorded in an append-only ledger protected by cryptographic hashing, and each entry is linked to the previous one through a hash chain. If any entry is modified, deleted, or reordered, ledger verification fails. This makes Chronicle logs tamper-detectable.
| Feature | Chronicle | Traditional Activity Logs |
|---|---|---|
| Append-only ledger | ✓ | ✗ |
| Immutable entries | ✓ | ✗ |
| Hash chaining | ✓ | ✗ |
| Tamper detection | ✓ | ✗ |
| Verifiable exports | ✓ | ✗ |
| Signed checkpoints | ✓ | ✗ |
| Key rotation | ✓ | ✗ |
| External anchoring | ✓ | ✗ |
Requirements
- PHP
^8.2 - Laravel
^12.0, or^13.0 - The
ext-sodiumextension (Ed25519 signing) - The
ext-opensslextension (ECDSA P-256 signing and verification)