Recent repository work, tests, release notes, and organization backing support continued maintenance. Workflow references are unpinned, and recent commits come from one contributor; the missing security policy is a smaller transparency gap.
67%
Total Score
83
86
75
Only two releases exist, with no registry release in the last 12 months and a median interval of about 251 days. This indicates a slow release cadence, although recent repository activity provides some compensation.
All three recent commits came from one contributor, creating a meaningful continuity risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, but not evidence of unsafe code by itself.
Version 0.1.1 is not a stable major release, but it is not marked as a prerelease and has no recent prerelease pattern. This is a mild maturity limitation rather than a severe risk.
Both workflows were fully analyzed with no trigger or audit findings, but all seven action references are unpinned. That weakens build reproducibility and supply-chain hygiene without showing an active exploit path.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
chevere/http Version ^0.5.0 | — | — |
symfony/yaml Version ^6|^7 | — | — |
chevere/action Version ^1.0.2 | — | — |
chevere/router Version ^0.7.0 | — | — |
chevere/schwager Version ^0.2.1 | — | — |
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.