MIT licensing, tests, and a focused dependency set support straightforward adoption. Organization backing and recent repository activity help, though one contributor and unpinned workflow actions reduce resilience.
82%
Total Score
83
100
100
75
All recent commits come from one contributor, creating a real continuity risk. Organization backing provides some handoff capacity but does not remove the concentration.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, not evidence of unsafe code.
The single workflow was fully analyzed with no injection or high-severity findings, but both action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1 || ^2 || ^3 | — | — |
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.