The package has a README, tests, a focused dependency set, and no install-time scripts. Its last registry release was in 2014, repository commits stopped in 2017, and no security scanning or policy is present.
42%
Total Score
50
100
81
88
The package and repository are owned by the same individual account, so the source appears correctly linked. It does not provide organization-level backing to offset the thin maintenance evidence.
The package has had no releases in more than 12 years, despite 13 historical releases. This is strong evidence of abandonment for a maintained dependency.
There were zero commits and zero active maintainers in the last three months. Combined with the repository's last push in 2017, this indicates a substantial maintenance and abandonment risk.
The repository uses Make and Composer, which supports reproducible project tasks, but no security scanning tooling is present. The missing scanning is a modest transparency and maintenance concern.
The repository is not archived, although its last push was in January 2017. The unarchived status is mildly reassuring but does not compensate for the lack of recent activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version 1.7.* | — | — |
composer/installers Version * | — | — |
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.