Healthy and suitable to depend on, with a maintainability caveat: the repository is active and well documented, but all recent commits come from one contributor and it has no security policy.
78%
Total Score
50
100
94
90
One contributor made all 10 commits in the last 3 months, creating a low bus factor and a genuine continuity risk. The recent release cadence and active repository partly compensate, but do not remove the concentration concern.
The repository received 10 commits in the last 3 months, showing current development activity. However, that activity is concentrated in one maintainer, which limits resilience if that person stops maintaining it.
Composer and Phing provide build tooling, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting and handling vulnerabilities. The package's tests, CI, and recent activity provide some compensating project evidence, so this is a caution rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.1 || ^2.0 || ^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.