Tests, a matching MIT license, and release notes support a mature package with clear provenance. The repository has no security policy or scanning, and all five workflow actions are unpinned, so maintenance and build hygiene deserve attention.
68%
Total Score
50
50
89
75
Twelve runtime dependencies, including several extensions and supporting libraries, create a moderately broad dependency surface for a CLI client. The signal does not show an unsafe or obviously excessive dependency pattern, so this is only a mild concern.
The package has existed since January 2017 with 28 releases, but it had no releases in the last 12 months after v1.0.2 was published in August 2025. That suggests slowing maintenance rather than abandonment on its own.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with no releases in the last 12 months, this raises maintenance and abandonment risk, though the repository was pushed in January 2026.
There are eight open issues and one open pull request, but no issues or pull requests were opened or closed in the last month. This is consistent with limited current activity.
Composer is used for builds, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
amphp/log Version ^1 | — | — |
kelunik/acme Version ^1 | — | — |
symfony/yaml Version ^5.3.2 | — | — |
amphp/process Version ^1.1 | — | — |
amphp/parallel Version ^1.4 | — | — |
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.