geeklab/glpdo2
The repository is not archived and includes tests, a changelog, and a clear README, while the dependency footprint is small. The declared MIT license conflicts with the BSD-3-Clause license file, and recent commit activity is absent despite a later repository push.
58%
Total Score
83
100
81
83
Health Score Breakdown
A license file is present and identifies BSD-3-Clause, but the manifest declares MIT. The release is licensed, yet the mismatch creates avoidable legal and transparency uncertainty.
The latest registry release was on November 25, 2022, with zero releases in the last 12 months. This is a substantial maintenance concern for a package developers may depend on, despite its long release history.
The repository recorded zero commits and zero active maintainers in the last three months. The later push date helps show the repository is not abandoned administratively, but it does not demonstrate ongoing development.
Composer is used as a build tool, but no security scanning tools are present. The build setup is appropriate, while the missing scanning is a modest hygiene gap.
The repository has no security policy. For a small database wrapper this is a transparency gap, though it is less severe than missing source or release artifacts.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 EllisGL |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 8 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.