The project has had no commits or releases for about 10 years, with no security scanning and almost no community activity. Tests, release notes, a matching repository, and a clear MIT license provide useful transparency, but do not offset the maintenance risk.
45%
Total Score
50
100
75
88
The latest release was published in February 2016, and there have been no releases in the last 12 months. This long period without updates is a significant abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months; combined with the old latest release, this indicates sustained inactivity rather than a brief pause.
The repository has 0 stars, 0 forks, and 1 watcher, providing little evidence of broad community adoption or external maintenance capacity.
Composer is used for the build, but no security scanning tools are configured. The missing scanning is more concerning in an otherwise inactive project.
No security policy is present, leaving vulnerability reporting and response expectations undocumented. This is a hygiene and transparency gap, not evidence of malicious behavior.
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.