prooph/event-sourcing
This system is an event-sourcing library for PHP that provides a structured way to manage aggregate roots and their associated domain events. It offers core abstractions for tracking state changes, persisting events to a store, and reconstructing aggregates from their history. The library includes utilities for dependency injection, exception handling, and integration with event stores, all supported by comprehensive test coverage.
56.2
Adequate · 4 August 2026
1.3k
lines of production code
PHP
primary language
1
bus factor · 17 authors in all
4
measurements over time
How it got here
2014–2015 · Core event-sourcing implementation
This period focused on establishing the core event-sourcing architecture, introducing key classes like AggregateRoot and AggregateChanged to manage state and domain events. The work included building integration components for event stores and providing a practical example to demonstrate the library's usage. Comprehensive unit tests were added to validate the new functionality.
8 changes
2016 · Aggregate namespace and repository implementation
This period focused on introducing the new Aggregate namespace, which includes the AggregateRepository class for managing event-sourced aggregates with features like an identity map and configurable stream-per-aggregate behavior. The release also added supporting interfaces, exception types, and a container factory to facilitate dependency injection, accompanied by comprehensive test coverage for these new components.
5 changes
Survey your own repository
prooph/event-sourcing 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 4b8e2e50f9 — 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.