Its documentation, tests, and release notes make integration straightforward. The repository lacks a security policy and explicit workflow token permissions, so its security hygiene is less complete than its maintenance signals.
82%
Total Score
90
100
94
80
The package and repository are owned by the same individual user, so there is no organizational backing to offset maintainer concentration; active recent work partly compensates.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest security-process gap.
The repository has no security policy, which weakens vulnerability-reporting transparency even though the package otherwise has active maintenance.
The CI workflow does not declare top-level token permissions. No write permissions were observed, but explicit least-privilege settings would provide stronger safeguards.
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.