Clear documentation, licensing, release notes, and organization backing reduce adoption risk. The small repository has no security policy, no security scanning, and inactive recent commit activity, while workflow references need tighter pinning.
66%
Total Score
75
100
88
75
The package has had no releases in the last 12 months, despite nine releases since July 2024. This suggests a meaningful slowdown, although the linked repository remains active enough to avoid treating the project as abandoned.
There were no commits and no active maintainers in the last three months. That weakens evidence of ongoing maintenance, even though the repository is not archived.
Composer build tooling is present, but no security scanning tool is configured. This is a modest transparency and maintenance gap for a small project.
The repository has no security policy. For a small CLI package this is a minor transparency gap rather than a severe dependency risk.
The single workflow was fully analyzed with no unsafe triggers, untrusted checkouts, or audit findings. However, all three action references are unpinned, leaving avoidable build-integrity exposure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/semver Version ^3.4 | — | — |
symfony/console Version ^6.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.