The MIT license and one runtime dependency keep integration straightforward. However, the project offers little maintenance or security oversight for a dependency that may need future fixes.
35%
Total Score
50
70
50
This package has only one release, published 11 years ago, with no releases in the last 12 months. That long silence is strong evidence of abandonment risk, despite the package not being registry-deprecated.
The repository has had zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent maintenance. The repository is not archived, but it shows no current development activity.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful sign of an active user or contributor community.
Composer is used for the build, which is appropriate, but no security scanning tools are present. For an old, inactive dependency, the lack of additional security oversight increases maintenance risk.
The repository has no security policy or documented security reporting path. This is a transparency gap, particularly because the project has no recent activity to demonstrate how issues would be handled.
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.