taro/db-model
The MIT license, README, and tests make the project understandable, while its single publisher and absent security tooling limit resilience. There is no practical maintenance evidence beyond the initial releases.
40%
Total Score
25
100
72
83
Health Score Breakdown
The package has only two releases, both published in October 2022, with no releases in the last 12 months and a median interval of about 1.7 hours. This indicates a long-standing lack of release maintenance.
The repository recorded zero commits and zero active maintainers over the last three months. Combined with the last push in 2022, this is strong evidence of abandonment risk.
Only one registry account has publish access. Because the repository is user-owned rather than organization-backed, this represents a thin publishing and maintenance base.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external adoption or review signal to compensate for inactivity.
Composer is used for builds, but no security scanning tools are configured. This is a modest transparency and maintenance gap rather than a severe risk by itself.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 tekku.taro |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 vlucas/phpdotenv Version ^5.4 | — | — |
composer/composer Version ^2.4 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 3 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.