spier/dblib
Its tiny five-file tree and missing security policy limit transparency for a library. It has no install-time scripts, is not deprecated, and declares MIT licensing.
38%
Total Score
0
75
75
Health Score Breakdown
The latest release was about 5 years ago, with no releases in the past 12 months and only four releases overall. This strongly raises abandonment risk despite the stable 1.0.3 version.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap. No newer activity is provided to offset the maintenance concern.
The package has no README, while the source repository also reports no tests or changelog. Missing tests and changelog are normal for published artifacts, but the absent README is a real consumer-transparency gap for a library.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a hygiene gap that adds concern alongside the signs of inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 rpurant |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spier/logger Version 1.* | — | — |
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.