zf1/zend-registry
It has a clear BSD-3-Clause license, a README, and minimal runtime dependencies. Its contents are easy to identify, but the project lacks a security policy and automated workflow coverage, so this legacy component should be pinned carefully.
43%
Total Score
50
100
75
88
Health Score Breakdown
The latest release was in July 2017, with no releases in the last 12 months. That long release gap is strong evidence of an abandoned maintenance cycle, although the stable version may still be intentionally frozen.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old last release, this materially raises abandonment risk.
Composer is used for build and dependency management, which is appropriate for the package. No security-scanning tooling is present, leaving a modest transparency and maintenance gap.
The linked repository is not archived, but its last push was in July 2017, so the unarchived status does not compensate for the lack of current activity.
The repository has no security policy. For a small, inactive legacy component this weakens the documented process for handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 zf1/zend-exception Version self.version | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 12 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.