The project has a clear README, MIT licensing, repository tests, release notes, and automated dependency scanning. Recent commit activity is absent, and the workflows use unpinned references without a security policy, leaving maintenance and build-transparency concerns.
62%
Total Score
75
100
94
75
The package has existed for about 3 years and has 7 releases, but only 1 release in the last 12 months. The latest release is recent, so this suggests a small or intermittent maintenance cadence rather than abandonment.
There were 0 commits and 0 active maintainers in the last 3 months. A recent repository push and release provide some counterevidence, but the current pause still raises a maintenance concern.
No security policy was found in the repository. That is a transparency gap for reporting and handling vulnerabilities, though it does not by itself show that the package is unsafe.
All 8 analyzed action references are unpinned, and the audit reports high-confidence bot-condition and unpinned-container findings. The pull_request_target workflow has no untrusted checkout or script-injection sink, so these are workflow-hygiene concerns rather than severe exposure.
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.