EventSaucePHP/EventSauce
This system is an event sourcing library that provides a modernized architecture for managing aggregate roots, message dispatching, and event consumption. It features a flexible serialization layer, automatic code generation for payloads, and support for snapshotting and message replay. The framework also includes an anti-corruption layer for message filtering and transformation, alongside comprehensive testing utilities for verifying aggregate behavior and message handling.
63.8
Adequate · 4 August 2026
5.7k
lines of production code
PHP
primary language
1
bus factor · 57 authors in all
3
measurements over time
How it got here
2017–2018 · Event sourcing architecture modernization
This period focused on modernizing the event sourcing core by removing legacy components like the old repository and clock abstractions, while introducing a new message-based architecture with header-based metadata. The code generation system was refactored to support nullable types and user-defined interfaces, and the serialization layer was restructured to support flexible payload strategies and simplified upcasting.
12 changes
2019–2021 · Snapshotting and test infrastructure
This period focused on introducing a snapshotting subsystem for aggregate roots, enabling state persistence and restoration. Concurrently, the codebase underwent significant refactoring of test utilities and message handling, including the addition of UUID decorators and the organization of test suites for event consumption and dispatching.
11 changes
2022–2023 · Anti-corruption layer and testing infrastructure
This period focused on introducing an Anti-Corruption Layer for message filtering and translation, alongside a new message replay capability. The team also significantly expanded test coverage for aggregate roots and the new layer, while establishing a Pest-based testing utility suite to streamline test writing.
9 changes
Survey your own repository
EventSaucePHP/EventSauce was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 4 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 33ea9b97ec — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.