Clear documentation, tests, and licensing make integration easier. The project has no security policy or scanning, increasing maintenance uncertainty.
45%
Total Score
50
79
83
The latest release was published in August 2016, and there were no releases in the last 12 months. This long release gap is a substantial abandonment concern.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the absence of recent releases and indicating inactive maintenance.
Composer build tooling is present, but no security scanning tools were detected. The build setup is established, though security maintenance coverage is limited.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency and maintenance gap.
Version 0.7.1 is not marked as a prerelease, which avoids prerelease uncertainty, but the stable-looking version has not been updated for roughly 10 years.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ramsey/uuid Version 3.3.* | — | — |
net_bazzline/component_lock Version 2.1.* | — | — |
net_bazzline/php_component_csv Version 1.5.* | — | — |
net_bazzline/php_component_toolbox Version 1.9.* | — | — |
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.