The project has a clear README, tests, MIT licensing, and a documented release history. Repository activity has stopped recently, and its workflows use unpinned images; the single registry maintainer also leaves little visible redundancy.
65%
Total Score
50
100
100
67
The registry lists one publishing account. Because the repository is user-owned rather than organization-owned, this leaves limited visible publishing redundancy, but registry access alone does not prove the project lacks contributors.
The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful recent maintenance gap, though the established release history partly offsets abandonment risk.
The repository has no security policy. This reduces transparency for reporting vulnerabilities, although the package's small scope and other collected project evidence partly limit the impact.
All three workflows were analyzed, but all seven action references are unpinned and the audit found a high-confidence unpinned container image. This is a workflow hygiene and build-reproducibility concern, not a standalone reason to reject the package.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.