The release has useful notes, repository tests, a matching source project, and a clear MIT license. Its workflow leaves all five actions unpinned and the project has no security policy or scanning, so future maintenance deserves attention.
68%
Total Score
50
86
50
The package has existed since November 2016 with seven releases, but none in the last 12 months and the latest release was about 21 months ago. This indicates slowing maintenance rather than abandonment by itself.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the latest release being about 21 months ago. This lowers confidence in prompt maintenance, though it is not proof that the stable library is unusable.
Composer build tooling is present, but no security-scanning tools were detected. For a small library this is a modest supply-chain hygiene gap, not a severe risk on its own.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This is a transparency weakness, but the package is not deprecated or archived.
The sole workflow was fully analyzed with no dangerous triggers or audit findings, but all five action references are unpinned. That leaves avoidable workflow supply-chain 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.