Download the PHP package laravel-chronicle/core without Composer
On this page you can find all versions of the php package laravel-chronicle/core. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download laravel-chronicle/core
More information about laravel-chronicle/core
Files in laravel-chronicle/core
Package core
Short Description Tamper-evident audit ledger for Laravel applications.
License MIT
Homepage https://github.com/laravel-chronicle/core
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package core
Chronicle – Verifiable Audit Logging for Laravel
⭐ If you find Chronicle useful, please consider starring the repository.
Chronicle is a cryptographically verifiable audit ledger 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
- reordered
This makes them unreliable for security auditing or compliance purposes.
Chronicle takes a different approach.
Chronicle records events in an append-only ledger protected by cryptographic hashing.
Each entry is linked to the previous entry using a hash chain.
If any entry is modified, deleted, or reordered, the ledger verification fails.
This makes Chronicle logs tamper-detectable.
Feature Comparison
| Feature | Chronicle | Traditional Activity Logs |
|---|---|---|
| Append-only ledger | ✓ | ✗ |
| Immutable entries | ✓ | ✗ |
| Hash chaining | ✓ | ✗ |
| Tamper detection | ✓ | ✗ |
| Verifiable exports | ✓ | ✗ |
| Signed checkpoints | ✓ | ✗ |
Installation
Quick Example
Recording an audit entry:
This records an immutable ledger entry.
Hash Chaining
Chronicle protects the ledger using a cryptographic hash chain.
Each entry references the previous entry:
chain_hash(n) = SHA256(chain_hash(n-1) + payload_hash(n))
If any entry is modified or removed, the chain becomes invalid.
Querying Entries
Chronicle provides expressive query scopes:
These queries are optimized with database indexes.
Streaming Large Ledgers
Chronicle supports streaming entries using database cursors.
This allows processing huge ledgers with constant memory usage.
Cursor Pagination
Chronicle includes cursor pagination for efficient browsing of large audit logs.
Checkpoints
Chronicle can create cryptographic checkpoints that anchor the ledger.
A checkpoint record:
- current chain head
- entry count
- timestamp
- cryptographic signature
This allows auditors to verify ledger integrity even if the database is compromised.
Verifiable Exports
Chronicle can export the ledger as a verifiable dataset.
Exports include:
Example:
Export Verification
Exported datasets can be independently verified.
Verification checks:
- dataset hash
- digital signature
- hash chain integrity
- dataset boundaries
Architecture
Chronicle is designed as a deterministic ledger engine.
See:
- ARCHITECTURE
- DATA_MODEL
- EXPORT_FORMAT
for detailed documentation.
Design Principles
Chronicle is built around several core principles.
Append-only
Entries cannot be modified or deleted.
Explicit intent
Every entry must include:
- actor
- action
- subject
Cryptographic integrity
Entries are protected using hash chaining and signatures.
Low magic
Chronicle avoids automatic logging and hidden behavior.
Entries are recorded explicitly.
Transport agnostic
Chronicle works in:
- HTTP request
- queue workers
- CLI commands
- scheduled jobs
Roadmap
Planned improvements for future versions:
- validation pipeline
- context resolvers
- policy enforcement
- Filament admin UI
- Nova integration
- Chronicle Cloud
Contributing
Contributions are welcome.
Please read: CONTRIBUTING
before submitting pull requests.
Contributors
 Poorna Chandra Dinesh 💻 |
 Vasileios Ntoufoudis 💻 |
 James King 📖 |
Security
If you discover a security vulnerability, please report it responsibly.
See: SECURITY
for details.
License
Chronicle is open-source software licensed under the MIT license.
Credits
Chronicle was created to provide verifiable audit logging for Laravel applications.
If you find Chronicle useful, consider starring the repository ⭐
