lum/lum-db-pdo
The package includes a clear README, changelog, and small dependency footprint. Its absent security policy and scanning, low repository traction, and limited release history leave less evidence of ongoing project support.
61%
Total Score
50
100
83
75
Health Score Breakdown
The repository is owned by an individual account rather than an organization, so there is no demonstrated organizational support to compensate for the limited maintenance evidence.
Only two releases have been published, with no releases in the last 12 months and a median interval of about 560 days. The latest release is recent enough to avoid an abandonment verdict, but the cadence indicates limited maintenance.
The repository has zero stars and forks and only one watcher, offering little independent evidence of adoption or community support. Popularity is supporting evidence, so this is a modest concern rather than a decisive risk.
Composer is used for builds, but no security-scanning tooling is present. That weakens supply-chain transparency and automated oversight.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Timothy Totten |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 lum/lum-db Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 2 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.