Clear documentation, tests, MIT licensing, and a stable major release support adoption. The repository lacks security scanning, and its workflow actions are not pinned, so maintenance and build-integrity checks are limited.
68%
Total Score
50
100
88
75
The package has six releases over about five years, but none in the last 12 months; the latest release was about 15 months ago. This indicates slow maintenance for a package with a stable scope.
There were no commits and no active maintainers in the last three months, consistent with the roughly 15-month gap since the last repository push. This leaves current maintenance capacity uncertain.
Composer build tooling is present, but no security scanning tool was detected. For a small library this is a modest transparency and maintenance gap, not evidence of an unsafe release by itself.
The linked repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This is a transparency gap, though the package's narrow scope limits its effect.
The single workflow was fully analyzed with no untrusted checkouts, script injection, or high-severity findings, and it does not grant top-level write access. However, all three action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
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.