Risky to adopt: the package has had no release or repository activity for about 13 years. It is licensed, documented, and tested, but its very small project footprint and long inactivity make future maintenance unlikely.
42%
Total Score
25
71
75
The latest release was published about 13 years ago, and there have been no releases in the last 12 months. That long release gap is a substantial abandonment concern for a dependency.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the roughly 13-year release gap and indicating no visible ongoing maintenance.
There are no open issues or pull requests and no recent issue or pull-request activity. This is not harmful on its own, but alongside the lack of commits it provides no evidence of current project engagement.
The repository has only 3 stars, 2 forks, and 0 watchers. Popularity is not decisive by itself, but this very small footprint provides little supporting evidence of an active user or contributor base.
Composer build tooling is present, but no security-scanning tooling is configured. The missing scanner is a transparency gap, though the lack of workflows and the package's small, inactive codebase limit its impact.
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.