Tests, release notes, and organization backing provide useful transparency. Unpinned workflow actions and the lack of a security policy or scanning reduce confidence in long-term maintenance.
59%
Total Score
75
100
88
75
The manifest declares a proprietary license, with no detected license text in the package or repository. That creates a material adoption and redistribution concern for an open-source dependency.
There were no commits and no active maintainers in the three months measured before collection, indicating a thin or recently stalled maintenance stream. The recent release partly offsets this, but does not remove the concern.
Composer build tooling is present, but no security scanning tools were detected. For a logging library, this is a transparency and maintenance gap rather than evidence of a defect.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a dependency used in application infrastructure.
The single workflow was fully analyzed, uses read-only permissions, and has no dangerous audit findings. However, all four action references are unpinned, leaving build inputs less reproducible and increasing workflow supply-chain exposure.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1 | — | — |
monolog/monolog Version ^2 | — | — |
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.