sweetchuck/robo-drush
The source includes tests, a matching repository, and a declared GPL-2.0+ license. Install-time scripts and the lack of a security policy add modest operational risk for an otherwise small, lightly used project.
56%
Total Score
50
79
50
Health Score Breakdown
The package runs post-install and post-update Composer scripts, adding execution during dependency operations and therefore some supply-chain exposure. No other provided signal shows those scripts are unsafe.
Only one release exists, published over nine years ago, with no releases in the last 12 months. This makes the assessed version materially stale despite the repository remaining available.
There were no commits and no active maintainers in the three months measured. This is a meaningful maintenance concern, even though the repository was pushed in December 2024.
The repository uses Composer and Robo for builds, but no security scanning tool was detected. That is a modest transparency and hygiene gap rather than evidence of unsafe code.
No security policy was found in the repository. This reduces disclosure transparency, though it does not by itself indicate abandonment or an unsafe release.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 drush/drush Version ^8.1 | — | — |
symfony/yaml Version ^2.8||^3.1 | — | — |
consolidation/robo Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.