imiphp/imi-zookeeper
The package includes a README, repository tests, a declared license, and organization backing. Its workflows were fully audited, but all four action references are unpinned and no security policy is present.
38%
Total Score
50
75
50
Health Score Breakdown
Only one release exists, published about four years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended as a dependency.
The repository has recorded no commits and no active maintainers in the last three months, consistent with the long release gap and indicating that maintenance has stopped.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it is less serious than the package's stalled maintenance.
The assessed release is v2.1.0-beta1, and all recent releases are prereleases. The package's own README also describes it as still under development and unsuitable for production.
All four workflows were analyzed successfully with no reported audit findings, unsafe triggers, or broad top-level write permissions. However, all four action references are unpinned, leaving a modest workflow hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 imiphp/imi-config-center Version ~2.1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 4 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.