dapepe/microdb
The license files disagree, and the project has no security scanning or published security policy. One maintainer and roughly seven years without commits or a new release make future fixes uncertain.
38%
Total Score
50
100
72
75
Health Score Breakdown
The latest release was published roughly seven years ago, with no releases in the last 12 months; this is strong evidence of stagnation for a dependency.
There were no commits and no active maintainers in the last three months, consistent with the roughly seven-year gap since the last repository update.
The manifest declares GPL-3.0-or-later, while the artifact license file is detected as LGPL-3.0; although license files are present, the mismatch creates adoption and compliance uncertainty.
The repository has zero stars and forks and only one watcher, providing little supporting evidence of community review or continued use.
Composer build tooling is present, but no security scanning tools were detected, leaving a meaningful maintenance and security-process gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Peter Haider |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 11 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.