The source includes tests and a clear README, and the package is backed by an organization. Its small dependency set limits maintenance complexity, but security scanning is absent and workflow actions are unpinned.
52%
Total Score
50
79
50
Only two releases exist, with the latest published nearly five years ago and none in the last 12 months. This indicates a substantially slowed maintenance cadence.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
There were no new or closed issues or pull requests in the last month. Combined with the stale commit history, this provides little evidence of active project maintenance.
Composer build tooling is present, but no security-scanning tools were detected. That is a transparency and maintenance gap for a package intended to process application logs.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a modest transparency gap, not evidence of a vulnerability.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version 2.3.5 | — | — |
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.