The package has no declared or detected license, which creates a legal adoption risk. The repository has no security policy or scanning, and activity is sparse, although organizational backing and a non-archived repository provide some support.
38%
Total Score
50
50
50
The latest registry release was about six years ago, with zero releases in the last 12 months despite 141 historical releases. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the stale release history, this indicates limited current maintenance capacity.
No license is declared, detected, or present in the package or repository. Without licensing terms, legal reuse and dependency adoption are materially uncertain.
Composer build tooling is present, but no security-scanning tools are configured. This is a modest transparency and maintenance gap rather than evidence of unsafe behavior.
The repository has no security policy. That leaves vulnerability-reporting and response expectations unclear, which lowers transparency for a dependency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.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.