The MIT license, usable readme, and stable release format help consumers, but the single-maintainer project offers little evidence of resilience. Its small scope is clear, yet there is limited supporting evidence for long-term dependency maintenance.
38%
Total Score
25
100
78
75
The last release was about eight years ago, with no releases in the past 12 months and only four releases overall. This is strong evidence of abandonment risk despite the package not being deprecated.
The repository had no commits and no active maintainers in the past three months, consistent with the long release gap. The repository is not archived, but observed activity still indicates very limited maintenance.
One registry maintainer is consistent with a small personal project, but it provides little redundancy if that maintainer stops responding or publishing.
The repository has 5 stars and 1 fork, so there is limited community evidence to compensate for the lack of recent maintenance. Popularity is supporting evidence rather than a verdict by itself.
Composer is used for builds, which is appropriate, but no security scanning tooling was detected. This is a modest transparency and hygiene gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
zendframework/zend-mvc Version ^3.0 | — | — |
zendframework/zend-i18n Version ^2.6 | — | — |
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.