Clear licensing, a readable README, repository tests, and organizational ownership support adoption. Install-time scripting and missing security scanning add modest operational risk.
58%
Total Score
75
79
50
A post-install command runs during Composer installation, adding execution behavior to dependency installation. No provided signal shows that this behavior is unsafe, so this is an operational caution rather than a severe risk.
The latest release was over 2 years ago, and there were no releases in the last 12 months. The earlier median interval of about 29 days shows that this is a meaningful change in maintenance activity.
The repository had no commits and no active maintainers in the last 3 months, consistent with the long release gap. The repository is not archived, but it shows little recent maintenance.
Composer is used as the build tool, providing normal ecosystem packaging support. The repository has no reported security scanning, leaving a modest transparency and maintenance gap.
The repository has no security policy. For a command-line utility that can interact with application files and processes, the absence reduces transparency for reporting and handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^6.0 | — | — |
symfony/process Version ^6.0 | — | — |
symfony/filesystem Version ^6.0 | — | — |
jawira/case-converter Version ^3.4 | — | — |
symfony/event-dispatcher Version ^6.0 | — | — |
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.