The package is small and easy to inspect, with a README, matching repository, explicit Unlicense, and no install scripts. It lacks tests and security tooling, while its age makes future compatibility and support uncertain.
38%
Total Score
0
75
75
The package has had only 3 releases, all concentrated between January 24 and January 26, 2013, with none in the last 12 months. This is strong evidence of abandonment for a dependency last released over 13 years ago.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, and its last push was in January 2013. The long absence of activity materially increases maintenance and compatibility risk.
The repository has 3 stars, 0 forks, and 1 watcher, indicating a very small user and contributor base. This provides little evidence of external review or shared maintenance capacity.
The repository uses Composer, which fits the package ecosystem, but it reports no security-scanning tools. This is a hygiene gap rather than evidence that the release is unsafe by itself.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. For an old library with no recent maintenance, this adds a meaningful transparency gap.
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.