A clear README, release notes, and a recent release help with adoption. The very small project has no security scanning or security policy, so ongoing maintenance and security visibility remain limited.
64%
Total Score
50
86
50
There have been only three releases across about 5 years, with a median interval of about 2.5 years. One release in the last 12 months shows recent activity but does not establish a strong cadence.
One contributor made all recent commits, leaving maintenance dependent on a single person. The repository is user-owned rather than organization-backed, so there is no shown handoff capacity to compensate.
The repository had only one commit in the last 3 months, indicating limited observed maintenance activity, although it was recent.
Composer is used for the build, but no security-scanning tools were detected. That reduces security-process visibility for a package intended to construct shell commands.
The repository has no security policy, leaving reporting and response expectations undocumented. The package is small and has recent release activity, but that does not replace a published process.
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.