The MIT license, clear README, matching repository, and small dependency surface make the package understandable to adopt. Its minimal project footprint and lack of security tooling add little ongoing assurance.
34%
Total Score
50
75
50
The package has made only one release, 0 releases in the last 12 months, and no release since July 2017—about 9 years ago. This is strong evidence that maintenance has stopped.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history showing no activity since July 2017. There is no observed maintenance capacity for a dependency this old.
Composer build tooling is present, but no security-scanning tools are reported. That reduces assurance for a database extension, especially when the project has not been maintained recently.
The repository has no security policy, leaving no published process for reporting or handling vulnerabilities. This is a transparency gap, though it is less serious than the lack of maintenance.
Version 0.1.0 is not a stable major release, so its API maturity is uncertain. The absence of later releases provides no evidence that the early API was hardened.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mrjgreen/database Version ^2.5 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.