Healthy and usable for a legacy Zend Framework 1 integration, with recent releases and an active organization-owned repository. The main caveats are very concentrated recent maintenance and no repository tests, changelog, or security policy.
78%
Total Score
67
100
83
88
A README documents installation and the package's monorepo origin, but neither the artifact nor repository contains tests or a changelog. Those omissions reduce transparency for maintenance, though the README explains where contributions and documentation belong.
All recent commits came from one contributor, creating a concentrated maintenance dependency. The organization-owned repository provides some ability to hand maintenance off, but no second active contributor is shown.
There was one commit in the last 3 months from one active maintainer, which shows some current activity but provides only limited evidence of ongoing maintenance capacity.
The repository has no stars or forks and only one watcher, offering little community validation. Popularity is supporting evidence rather than a decisive health measure, especially for a specialized legacy component.
Composer is used as a build tool, but no security-scanning tools are reported. The missing scanning is a transparency gap, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
zf1s/zend-xml Version ^1.16.2 | — | — |
zf1s/zend-http Version ^1.16.2 | — | — |
zf1s/zend-mime Version ^1.16.2 | — | — |
zf1s/zend-version Version ^1.16.2 | — | — |
zf1s/zend-exception Version ^1.16.2 | — | — |
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.