The package is clearly licensed, stable, and has a minimal runtime dependency. However, its last release and repository push were in July 2017, with no recent commits or security tooling, making maintenance uncertain.
43%
Total Score
0
100
81
75
The package has 18 releases since January 2014, but its latest release was in July 2017 and it has had no releases in the last 12 months. This is strong evidence of abandonment risk despite its established history.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long period without releases. No provided signal shows current maintenance capacity.
Composer is used as the build tool, which fits the package ecosystem, but no security-scanning tools were detected. The missing scanning is a modest hygiene concern alongside the broader maintenance gap.
No repository security policy was found. For a small legacy component this is a transparency gap, though it is less consequential than the lack of recent release and commit activity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.