zf1/zend-tag
The package has a clear README, a matching BSD-3-Clause license, and a small dependency surface. It lacks a security policy and has no recent repository activity, so long-term maintenance should be treated as a liability.
42%
Total Score
25
100
72
88
Health Score Breakdown
The latest release was published in July 2017, with no releases in the last 12 months. Nearly nine years without a release is strong evidence of abandonment risk, despite the 18-release history.
The repository had zero commits and zero active maintainers in the last three months. Combined with the last push in 2017, this materially increases abandonment risk.
The registry namespace and repository owner match, but the owner is a user account rather than an organization. This supports identity consistency without demonstrating active institutional backing.
The repository has zero stars, one fork, and one watcher. Popularity is supporting evidence rather than a verdict, but these very low figures provide no meaningful community-maintenance buffer.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a moderate hygiene gap rather than proof of unsafe code.
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-loader Version self.version | — | — |
zf1/zend-exception Version self.version | — | — |
Weekly Downloads
Info
- Last Published
- 11 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.