The stable API, tests, changelog, and organization backing support adoption, but maintenance appears dormant. No security policy or scanning adds transparency risk, though the repository remains active in name and is not deprecated.
43%
Total Score
50
100
75
83
The package has had no release in about 8 years: its latest release was April 2018, with zero releases in the last 12 months. This strongly raises abandonment risk despite seven historical releases.
The repository had zero commits and zero active maintainers in the last three months, consistent with roughly 8 years since the last push. This is strong evidence of dormant maintenance.
There were no new or closed issues or pull requests in the last month and no merged pull requests. The absence of recent collaboration reinforces the maintenance concern, while the unknown open-issue count limits the conclusion.
The project uses Composer and Phing, showing an established build process, but reports no security-scanning tools. The tooling is a modest positive with a transparency limitation.
The linked repository is not archived, which preserves the possibility of future maintenance. However, its last push was in April 2018, so this does not compensate for the prolonged inactivity.
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.