Clear documentation, tests, release notes, and a valid license support adoption. The small active contributor base and lack of repository security policy leave meaningful maintenance and transparency concerns.
72%
Total Score
88
88
83
All four recent commits came from one contributor, leaving maintenance dependent on a single active developer. Organization ownership offers some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tooling was detected. For a deployment-oriented package, that is a transparency and maintenance gap rather than proof of unsafe code.
The repository has no security policy. This makes vulnerability reporting and response expectations less transparent for a package that contains deployment and automation scripts.
Version 0.6.0 is not a stable major release, so its pre-1.0 status implies greater potential for breaking changes. It is not a prerelease, and recent releases show a consistent stable-version pattern.
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.