The package has had no registry release since July 2017, and the repository shows no active contributors or commits in the last three months. It remains unarchived, documented, tested, licensed, and has a small dependency set, which limits—but does not remove—the maintenance concern.
58%
Total Score
25
100
81
50
The latest release was in July 2017, with no releases in the last 12 months and only four releases overall. This is a substantial maintenance and compatibility concern for a dependency.
The repository had zero commits and zero active maintainers in the last three months. Combined with the old registry release, this points to limited ongoing maintenance capacity.
One registry maintainer is consistent with a small user-owned project, but it leaves little visible publishing redundancy if that maintainer becomes unavailable.
Composer is used for builds, but no security-scanning tooling is present. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, reducing transparency about how vulnerabilities are reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mikehaertl/php-shellcommand Version ^1.2 | — | — |
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.