Clear documentation, tests, licensing, and release notes help adoption. Its last registry release was over 10 years ago, with no recent commits or active maintainers, so maintenance risk is substantial.
42%
Total Score
63
78
75
The package has had no release in over 10 years, despite 13 releases during its earlier development. That long gap is strong evidence of abandonment risk.
The repository had zero commits and zero active maintainers in the last 3 months. Combined with the old release history, this is strong evidence that fixes and support are unlikely.
There are 10 open issues but no new or closed issues and no pull-request activity in the last month, indicating unresolved maintenance demand.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap, though it is less significant than the lack of recent development.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The absence adds transparency risk for a library that has seen no recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
zendframework/zend-db Version ^2.4 || ^3.0 | — | — |
zendframework/zend-servicemanager Version ^2.4 || ^3.0 | — | — |
container-interop/container-interop Version ~1.0 | — | — |
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.