The project is small and lightly documented beyond its README, with no security policy and no recent issue activity. Its organization-backed repository and stable 1.0.0 release provide some continuity, but the package should be adopted with maintenance risk in mind.
58%
Total Score
75
100
72
75
There have been only 2 releases, and none in the last 12 months; the latest release was about 14 months ago. This is meaningful evidence of slow maintenance for a package developers may depend on.
There is one open issue but no new or closed issues and no merged pull requests in the last month. This shows little visible recent maintenance activity.
The repository name does not match the package name and its README does not mention this package. Although subpackages can use a monorepo, the available evidence leaves some uncertainty that this repository specifically owns the published package.
The repository has 0 stars, 0 forks, and 1 watcher. This provides little supporting evidence of community adoption, but popularity is only secondary evidence and is not decisive for a small package.
Composer is used as the build tool, but no security-scanning tooling is present. The missing scanning is a modest transparency and maintenance gap, not evidence of abandonment by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version * | — | — |
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.