Its long history, MIT licensing, small runtime footprint, repository tests, and release notes support dependable use. The main concerns are stalled recent release activity and incomplete workflow hardening.
65%
Total Score
75
100
88
75
The package has 33 releases over more than 14 years, but none in the last 12 months; the latest release was about 15 months ago. This suggests slowing maintenance despite the long release history.
The repository recorded zero commits and zero active maintainers in the last three months. That is a concrete maintenance slowdown, although the recent push evidence and published release notes provide some compensation.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. For a mature library this weakens vulnerability-reporting transparency, though it does not by itself indicate abandonment.
The single workflow was fully analyzed with no untrusted checkouts or script injection, but all nine action references are unpinned and the audit found a high-confidence unpinned container image. This is a workflow reproducibility and supply-chain hygiene concern.
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.