Risky to adopt for new projects: the latest release was published nearly nine years ago and the repository has had no commits in the last three months. It remains licensed, documented, non-deprecated, and backed by a matching organization repository, but its long inactivity makes maintenance and compatibility a liability.
42%
Total Score
50
100
72
50
The package has only four releases, with no release in nearly nine years and none in the last 12 months. That strongly suggests abandonment risk despite the package's long history.
There were no commits and no active maintainers in the last three months. This is strong evidence that fixes and compatibility updates are unlikely to arrive promptly.
The repository has zero stars and forks and only five watchers, offering little community support or independent adoption evidence. Popularity is supporting evidence rather than decisive on its own.
The repository uses Composer, but it has no security-scanning tools. With no workflows and no recent development activity, this is a transparency and maintenance gap rather than an immediate severe risk.
The repository is not archived, which leaves a path for maintenance, but its last push was nearly nine years ago and therefore does not counter the inactivity evidence.
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.