sebastianbergmann/php-code-coverage

Library that provides collection, processing, and rendering functionality for PHP code coverage information.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 7th, 2026
Created on May 28th, 2009
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 383
Total Stargazers: 8,924 (+0)
Total Subscribers: 56 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.5 hours
Mean response time: 141.3 days
90th percentile: 367.5 days
Tracked items: 87

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,042 days
Stale 30+ days: 3
Stale 90+ days: 2

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type/bug (32)
  • type/enhancement (17)
  • static-analysis (12)
  • report/html (7)
  • type/performance (5)
  • code-unit-targeting (4)
  • data-source/xdebug (4)
  • report/xml (4)

Most active issues this week

Detailed Description

PHP Code Coverage is a library that provides collection, processing, and rendering functionality for PHP code coverage information.

The library solves the problem of measuring which parts of a PHP codebase are executed during testing. It collects coverage data by instrumenting code execution, processes that data to aggregate results, and renders reports in multiple formats so developers can identify untested code paths and assess test quality.

Developers should adopt this library if they need programmatic control over code coverage analysis in PHP projects, particularly when integrating coverage measurement into custom testing workflows or continuous integration pipelines. It works well for projects that require coverage reports beyond what standard test runners provide out of the box, or where coverage data needs to be serialized, stored, and processed separately from test execution. The library is designed as a dependency for testing tools and frameworks rather than as a standalone command-line utility.

The project maintains a focused scope on coverage instrumentation and reporting without attempting to be a complete testing framework. Development activity shows consistent engagement with the codebase through regular updates and maintenance of the core functionality for collecting and rendering coverage data.