The package is clearly licensed, documented, tested in its repository, and has a small runtime dependency footprint. However, no commits were recorded in the last three months, releases are infrequent, and workflow references are unpinned. Keep the caveats in mind when adopting it.
65%
Total Score
75
100
86
50
The package has existed for over 8 years and published two releases in the last 12 months, but its median release interval is about 579 days, indicating slow maintenance between releases.
The repository recorded zero commits and zero active maintainers in the last three months. Although the release was pushed recently, the measured activity shows limited ongoing development capacity.
Composer build tooling is present, but no security-scanning tooling was detected. This is a transparency and maintenance hygiene gap rather than evidence that the package is unsafe.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All three workflows were analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all six action references are unpinned, so workflow dependencies can change without a reviewed commit.
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.