Calculate code coverage for git diff (changed lines only)
58%
Total Score
33
100
78
83
There were zero commits and zero active maintainers in the last three months, consistent with no observed development since the initial release burst.
Only one registry publishing account is listed. Because the repository is user-owned rather than organization-backed, this indicates limited publishing redundancy.
All three releases occurred on January 25, 2026, with a median interval of about 6 minutes; this shows an initial publication burst but no later release cadence across about eight months.
There were no new or closed issues or pull requests in the last month. With no open work either, this provides no evidence of active maintenance.
The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, but popularity alone is not decisive for a small package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
exussum12/coverage-checker Version ^1.0 | — | — |
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.