donquixote/containerkit
The documented API, matching repository, and MIT license make the package understandable to adopt. Its single-maintainer structure and absent security policy leave limited resilience if maintenance or security issues arise.
38%
Total Score
38
61
83
Health Score Breakdown
The package has only two releases, both published on January 11, 2016, with no releases in the last 12 months; more than 10 years without a release is strong abandonment evidence.
There were zero commits and zero active maintainers in the last three months, consistent with more than 10 years of repository inactivity and materially raising abandonment risk.
The repository is not marked archived, but its last push was on January 11, 2016; the inactivity is more significant than the non-archived status is reassuring.
Only one registry maintainer is listed. That is a limited publishing base for a user-owned project and increases continuity risk if that person stops maintaining it.
The registry namespace and repository owner match, but the owner is an individual rather than an organization, offering limited visible project backing.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Andreas Hennings |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.