The package has a clear README, an MIT declaration, and only one runtime dependency. Its tiny, single-owner project has little supporting process, so long-term fixes may be difficult.
38%
Total Score
25
100
72
83
The package is about 3 years and 8 months old but has had no release in roughly 3 years and 8 months, with zero releases in the last 12 months. This is strong evidence that maintenance has stopped.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the stalled release history. The repository is not archived, but there is no observed recent development.
Only one registry account has publishing access, and project_backing identifies the repository owner as an individual rather than an organization. This leaves limited visible maintainer capacity if the owner becomes unavailable.
The repository has 1 star, 0 forks, and 1 watcher, so there is little visible community adoption or backup interest. Popularity is supporting evidence, but it reinforces the broader maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version 2.8.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.