The package is well documented and tested, with a minimal runtime dependency. Workflow pinning and the absent security policy leave modest hygiene concerns.
78%
Total Score
67
100
94
75
The registry namespace and repository are owned by the same individual account. This supports ownership continuity but provides no organizational handoff capacity to offset the concentrated contributor activity.
All three recent commits came from one contributor, so maintenance depends heavily on a single person. The repository is active, but there is little demonstrated redundancy.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance-process gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability-reporting expectations and response procedures undocumented. This modestly reduces project transparency.
The workflow audit completed cleanly with no untrusted checkouts, script injection, or audit findings, but all four action references are unpinned. That leaves avoidable reproducibility and action-substitution risk.
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.