Tests, documentation, release notes, and a small dependency set provide useful support. The license mismatch, absent security policy, and limited recent maintenance reduce confidence in long-term support.
58%
Total Score
75
100
75
75
A license file is present, but the manifest declares OSL while the artifact license file is detected as MIT. This mismatch creates a real licensing transparency concern.
The latest release was published over five years ago, with no releases in the last 12 months. This is a meaningful maintenance concern despite a history of six stable releases.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates limited ongoing maintenance capacity.
The repository name matches the package, but its README does not mention the package name. This weakens the link between the published package and its source documentation.
Composer and Phing build tooling are present, but no security-scanning tool was detected. That is a moderate repository hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog 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.