The stable 1.0.0 package has a clear README, a matching repository, and only one runtime dependency. Its maintenance evidence is weak, and the lack of licensing makes adoption a liability.
38%
Total Score
0
60
50
The package has had only one release, on 27 November 2013, with no releases in the last 12 months. Nearly 13 years without a release is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last 3 months. This provides no evidence of current maintenance to offset the stale release history.
No declared license or license file was found in the package or repository. Without licensing terms, dependency adoption carries a material legal and transparency concern.
Composer is used for builds, but no security scanning tools are present. This is a modest hygiene gap rather than evidence of an unsafe package on its own.
The repository has no security policy. For an old package with no recent release or commit activity, this adds a transparency gap and provides no stated channel for handling security issues.
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.