The package is small and understandable, with tests, a README, MIT licensing, and no install scripts. Its one-person publishing base and lack of security policy leave little evidence of ongoing support.
38%
Total Score
50
100
79
83
The package has had no release in about 13 years: all three releases appeared on April 30, 2013. This is strong evidence of abandonment for a dependency whose compatibility and maintenance may matter over time.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since April 2013.
Only one registry account has publishing access, which is a thin publishing base. The organization-owned repository provides some backing context, so this is a secondary concern rather than a verdict by itself.
The repository uses Composer, which fits the package ecosystem. No security scanning tools are present, a minor hygiene gap given the package's long maintenance silence.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a transparency gap, though it is less significant than the long 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.