sebastianbergmann/php-code-coverage
This system is a PHP code coverage analysis library that collects, processes, and reports on the execution of source code. It supports line, branch, and path coverage metrics using PCOV or Xdebug drivers, and provides detailed reporting in HTML, XML, and text formats. The system also integrates static analysis to identify dead code and executable lines, enabling precise coverage calculations and test size filtering.
68.4
Adequate · 2 August 2026
17k
lines of production code
PHP
primary language
1
bus factor · 125 authors in all
3
measurements over time
How it got here
2009–2016 · Code coverage architecture overhaul
This period marks a comprehensive refactoring of the code coverage library, replacing legacy implementations with a modern, object-oriented architecture. The changes introduce new abstractions for drivers, data structures, and report generation, while significantly enhancing HTML report capabilities and static analysis tooling.
18 changes
2019–2024 · Code coverage data model and static analysis refactoring
This period focused on refactoring the static analysis subsystem to support disk-based caching and improved isolation, while introducing typed data models to track execution hit counts for more granular coverage reports. Extensive test coverage was added for the new data structures, report generators, and utility classes to ensure reliability.
15 changes
2025–2026 · Class-oriented HTML report and static analysis improvements
This period focused on introducing a new class-oriented HTML report structure, including the necessary data models, builders, and renderers to display coverage by class and namespace. Concurrently, the static analysis capabilities were enhanced with new visitors for dead code and executable lines, supported by updated PHPStan dependencies and stubs for better type checking.
15 changes
Survey your own repository
sebastianbergmann/php-code-coverage 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 2 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 6541e4009b — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.