The MIT license, matching repository, and single PHP dependency reduce adoption friction. Basic security and workflow safeguards are incomplete, leaving maintenance and release hygiene as the main concerns.
64%
Total Score
75
100
88
75
The package has made no release in the last 12 months, despite eight releases overall and a latest release about 15 months ago. This indicates a meaningful maintenance slowdown, though the project is not evidently abandoned.
There were no commits and no active maintainers in the most recent three months, consistent with the release pause. This lowers confidence in prompt maintenance, although the repository is not archived.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tooling was detected. The missing scanning is a modest transparency and hygiene gap.
The repository has no security policy. For a small wrapper this is not severe, but it leaves vulnerability reporting and response expectations undocumented.
The sole workflow was fully analyzed with no dangerous triggers or audit findings, but all four action references are unpinned. That leaves workflow dependencies exposed to upstream changes, while the absence of a top-level permissions block is acceptable on its own.
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.