The MIT license, matching repository, and documented 0.3.0 release provide useful transparency. Install-time scripts and missing security scanning add maintenance friction.
35%
Total Score
0
100
71
50
The latest release was published about 10 years ago, with no releases in the last 12 months. That strongly indicates abandonment, despite 13 historical releases.
The repository recorded no commits and no active maintainers in the last three months, consistent with the package's long release gap and leaving current maintenance capacity unproven.
The package runs post-install and post-update Composer scripts, increasing installation behavior and maintenance surface compared with a package that only ships library code.
Composer is used for builds, providing basic project tooling, but no security scanning tools were detected, leaving a notable hygiene gap.
The repository is not archived, which is a small positive, but its last push was about 10 years ago, so the non-archived status does not offset the stale activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/semver Version ^1.4 | — | — |
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.