The single-maintainer project has no tests or security policy, and it has almost no adoption evidence. MIT licensing and a repository README improve transparency, but ongoing support is difficult to establish.
43%
Total Score
25
100
67
83
The latest release was published about 10 years ago, with no releases in the last 12 months. The three releases were clustered within about two days, indicating a completed or abandoned project rather than an active release stream.
There were no commits and no active maintainers in the last 3 months. Combined with the old last push, this is strong evidence of inactive maintenance.
One registry maintainer is responsible for publishing the package. For this individually owned project, that creates a limited maintainer base and higher continuity risk.
The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is supporting evidence rather than decisive, but these values provide little evidence of broad review or community support.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was about 7 years ago and does not offset the stale release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
zendframework/zend-http Version ^2.5 | — | — |
zendframework/zend-json Version ^3.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.