The MIT declaration, README, matching repository, and minimal Composer dependency profile make the package straightforward to inspect and integrate. Its lack of tests, security policy, and scanning adds modest uncertainty on top of the long maintenance gap.
38%
Total Score
0
100
71
75
The package has only two releases, both in 2017, with no releases in the last 12 months and the latest published about nine years ago. This strongly raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since June 2017.
The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broader support base.
Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, but it is less significant than the observed maintenance inactivity.
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.