The MIT license, detailed README, repository tests, and regular release history support adoption. A single maintainer and no security policy leave less evidence of long-term resilience.
70%
Total Score
50
100
100
50
Only one registry account has publish access, which limits publishing redundancy. The active release history and linked repository provide some compensation, but not a broad maintainer base.
The repository recorded no commits and no active maintainers in the last three months. Recent releases and a recent push reduce the concern, but the current development pause still lowers maintenance confidence.
The repository has no published security policy. This is a transparency gap for reporting and handling vulnerabilities, though it does not by itself show unsafe code.
All four workflows were analyzed successfully with no detected sinks, dangerous triggers, or audit findings. However, all 14 action references are unpinned, leaving workflow dependencies exposed to upstream changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^2.0 || ^3.0 | — | — |
psr/simple-cache Version ^1.0 || ^2.0 || ^3.0 | — | — |
zircote/swagger-php Version ^5.0 || ^6.0.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.