tkfmtz/self-zookeeper
The MIT license and stable 1.0.3 label provide basic clarity. Its repository offers minimal documentation, and the package name does not appear in the README, weakening confidence that it is the intended source.
34%
Total Score
50
75
50
Health Score Breakdown
Only two releases were published, both in December 2020, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk for a package last updated over five years ago.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in December 2020. This materially increases abandonment risk.
The repository name does not match the package name, and the README does not mention the package. A name mismatch can be normal for a sub-package, but the lack of any README reference weakens confidence that this repository is the package's intended source.
Composer is used as the build tool, but no security scanning tooling is present. That is a modest transparency and maintenance gap for a small package.
The linked repository has no security policy. This is a minor transparency gap, especially alongside the lack of recent maintenance, though it is not severe on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 5 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.