It includes tests, a README, a changelog, MIT licensing, and a small runtime dependency set. Missing security scanning and a security policy add some transparency risk, while the single-person project provides limited maintenance capacity.
60%
Total Score
33
100
88
83
There were no commits and no active maintainers in the last three months, consistent with the longer release gap and indicating current maintenance has stopped or substantially slowed.
One individual has registry publishing access. For this user-owned project that indicates a thin maintenance base, although the repository and package are clearly linked.
The repository is owned by the same individual namespace as the package rather than an organization, so there is no visible organizational backing to compensate for the thin maintainer base.
Only two releases were published, both within two days in July 2023, with no releases in the subsequent 12 months. This indicates a mature-looking but inactive release line and lowers confidence in ongoing maintenance.
Composer is used for builds, but no security scanning tools were detected. The build setup is present while automated security coverage is limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.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.