The repository has no tests or security scanning, and its lone maintainer provides little resilience. MIT licensing, a matching README, and no install scripts reduce adoption friction, but do not offset the long inactivity.
45%
Total Score
25
100
75
75
The package has had only two releases, both in October 2018, with no release in nearly eight years. The exact-version GitHub release notes are a small transparency positive but do not offset the inactivity.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in November 2018. This is strong evidence of abandonment risk.
Four issues remain open, with no issues or pull requests opened or closed in the last month. The small project size limits the significance somewhat, but there is no recent evidence of issue maintenance.
Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. For a small, inactive utility this is a minor maintenance gap, though it leaves no documented channel or process for reporting vulnerabilities.
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.