Documentation, tests, licensing, and a matching source repository make adoption easier. The main concern is that only two releases exist, with none since July 2022, while recent commit activity is also absent. Workflow references are all unpinned, adding a smaller maintenance and build-integrity concern.
61%
Total Score
50
92
50
The package has only two releases and none in the last four years, indicating weak release maintenance. The repository was pushed in January 2026, which provides some evidence of ongoing project activity but does not offset the stale registry release history.
There were no commits and no active maintainers in the last three months, which lowers confidence in current maintenance. This is partly offset by the repository's recorded push in January 2026.
The repository has no security policy, leaving vulnerability-reporting expectations unspecified. This is a transparency gap, but the package has a matching repository, tests, and a documented release.
All four analyzed action references are unpinned, so workflow dependencies can change without a repository commit. The audit found no untrusted checkouts, script injection, dangerous triggers, or other reported findings, keeping this a hygiene concern rather than a severe risk.
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.