scriptburn/db-version-update
The package is small and documented, with a clear license and no install-time scripts. Its maintenance and security evidence are too thin for a dependency expected to evolve.
40%
Total Score
0
69
75
Health Score Breakdown
The latest release was in December 2017, with no releases in the last 12 months and only two releases overall. This indicates a long-standing maintenance gap for a database-update library.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the last push occurring in December 2017. There is no observed recent activity to compensate for the aging release.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of an active user or contributor community.
Composer build tooling is present, but no security-scanning tools are configured. This is a modest hygiene gap rather than a severe risk by itself.
The linked repository is not archived, so it has not been explicitly retired. However, its last push was in December 2017, making the non-archived status weak compensation for the inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Rajneesh ojha |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 scriptburn/db-settings Version >=1.0 | — | — |
scriptburn/simple-debug Version >=1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 9 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.