Its small six-file codebase and MIT license keep the maintenance burden and usage risk bounded. The project has had no release or commit activity in over seven years, and it has no README or security scanning.
42%
Total Score
33
50
67
83
This is the package's only release, published over seven years ago, with no releases in the last 12 months. That strongly suggests abandonment, despite the package not being deprecated.
There were zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for over seven years. This is strong abandonment evidence.
Four runtime dependencies, including Composer and security-related tooling, create a meaningful dependency surface for this six-file package. The signal does not show that any dependency is unsafe or stale, so this is a limited concern.
The artifact has no README, which makes integration harder for a small library. The absence of tests and a changelog in the published artifact is normal packaging practice and is not penalized separately.
The repository is owned by an individual user rather than an organization, so the single publisher account does not benefit from visible organizational backing. This adds some continuity risk alongside the inactive repository.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/composer Version ^1.8 | — | — |
knplabs/packagist-api Version ^1.5 | — | — |
t4web/composer-lock-parser Version ^1.1 | — | — |
sensiolabs/security-checker Version ^5.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.