The Apache-2.0 license, substantial README, tests, and exact-version release notes provide useful adoption and maintenance context. Nearly five years without a registry release and no recent commits make future fixes uncertain, while the repository has no security policy or scanning.
58%
Total Score
67
100
75
75
The latest registry release was nearly five years ago, with no releases in the last 12 months. This materially raises abandonment and compatibility risk despite the 12-release history.
The repository recorded no commits and no active maintainers in the last three months, reinforcing that current maintenance is weak.
There were no new or closed issues or pull requests in the last month, while eight issues and three pull requests remain open. This suggests limited recent project activity and unresolved work.
Composer and Phing provide build tooling, but no security scanning tools were detected. That is a hygiene gap, though it is less significant than the maintenance slowdown.
No repository security policy was found, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but is not by itself evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version >= 1.0.0 | — | — |
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.