PhpUnit coverage checker, fail if coverage goes below a threshold
42%
Total Score
unhealthy
Risky: no releases or repository activity for about five years.
Only two releases were published, both in July 2021, with no releases in the last 12 months. That long release gap is a substantial abandonment concern for a dependency.
The repository recorded no commits and no active maintainers in the last three months, consistent with the package having received no visible development since July 2021.
The repository has 0 stars and 0 forks, with only 1 watcher. This is supporting evidence of limited adoption, but it does not independently establish that the package is unsafe to use.
Composer is used for the build, but no security-scanning tools are configured. The missing scanning is a modest hygiene weakness for a package that processes coverage files.
The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This is a transparency and maintenance gap, though not a severe risk by itself.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.