flashytime/db-cache
A clear README, tests, MIT licensing, and a small dependency surface make the package straightforward to inspect and integrate. Its missing security policy and minimal adoption provide little extra assurance.
42%
Total Score
0
100
72
83
Health Score Breakdown
The package has had only one release, published over eight years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a library a developer may need maintained.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. No provided maintenance signal compensates for this inactivity.
The repository has only 1 star, 1 fork, and 1 watcher, providing little evidence of broad community adoption or external maintenance capacity. Popularity is supporting evidence, so this reinforces rather than independently determines the risk.
Composer is used as a build tool, but no security scanning tools are detected. The build setup is appropriate for the ecosystem, while the missing scanning adds a minor hygiene concern.
The repository is not archived, which preserves a path for future maintenance, but its last push was over eight years ago. The non-archived status does not offset the observed inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 flashytime |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.