Its small footprint and Composer-only build keep the dependency surface understandable. The package has no visible security policy, and the linked repository does not identify the package, making ownership and future support harder to verify.
38%
Total Score
0
69
75
Only two releases were published, both in August 2022, with no releases in roughly four years. That is strong evidence of abandonment for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the latest push being roughly four years ago.
The artifact includes a README, but it is only 10 characters long; the absence of published tests and a changelog is normal packaging practice and is not itself a concern.
The repository name does not match the package name and its README does not mention the package, so the linkage and project ownership are difficult to verify.
Composer is used for the build, which is appropriate, but no security scanning tooling is present. This is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version ^3.1 | — | — |
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.