Clear documentation, a long release history, and a recent release make the project easier to adopt. The small scope and single maintainer limit resilience if ownership changes.
67%
Total Score
63
100
94
100
One registry publishing maintainer is consistent with a small user-owned project, but it leaves limited publishing redundancy if that person becomes unavailable.
The registry namespace and repository are owned by the same individual account, providing consistent ownership context but no organizational redundancy.
The repository recorded zero commits and zero active maintainers in the last three months. Although the release was recently published, the lack of recent development activity is a maintenance concern.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and hygiene gap.
The workflow uses read-only permissions and the audit found no injection or high-confidence security findings, but both analyzed action references are unpinned, weakening 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.