Clear licensing, tests, documentation, and package-to-repository alignment provide useful maintenance context. The native Berkeley DB extension requirement and absent security policy add friction, while the long inactivity makes future compatibility and support uncertain.
38%
Total Score
0
50
75
83
The package has had only two releases, with the latest in September 2018 and none in the last 12 months; this is strong evidence of prolonged inactivity.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the release-history concern rather than showing ongoing maintenance.
The package requires PHP and the native ext-db4 extension, creating substantial deployment and compatibility friction for consumers even though the dependency list is small.
Composer build tooling is present, but no security scanning tools are configured, leaving a modest transparency and maintenance gap.
The repository is not archived, which is a positive counter-signal, but its last push was in September 2018 and does not offset the prolonged inactivity.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.