The package has a clear MIT license, tests, a readable README, release notes, and a matching organization-owned repository. It has had no registry releases or repository commits since March 2020, with no security policy or scanning tools, so maintenance risk is significant.
58%
Total Score
67
88
83
The package has made no releases in about 6 years, despite 13 releases earlier in its history. This strongly lowers confidence in ongoing maintenance, though the package is not deprecated.
The repository recorded zero commits and zero active maintainers over the last three months, a strong sign that maintenance has stopped. Its non-archived status is only limited compensation because observed activity is absent.
There have been no new or closed issues or pull requests in the last month, alongside six open issues and one open pull request. This is consistent with an inactive project and adds maintenance concern.
Composer build tooling is present, but no security scanning tools are configured. This is a transparency and maintenance-hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, reducing transparency around vulnerability reporting and response. This matters more alongside the prolonged lack of maintenance activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/composer Version >=1.4 | — | — |
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.