bloomidea/drush-mcp-bridge
Clear documentation, tests, and release notes make the package straightforward to evaluate. Recent publishing is encouraging, but maintenance is concentrated in one contributor and workflow references are entirely unpinned.
68%
Total Score
83
100
88
75
Health Score Breakdown
All 4 recent commits came from one contributor, creating a concentrated maintenance path; organization ownership provides some capacity for handoff but does not remove the current concentration.
Composer is used as a build tool, but no security-scanning tools were detected, leaving automated security coverage unverified.
The repository has no security policy, making vulnerability reporting and response expectations less transparent for consumers.
Version v0.5.0 is not a prerelease and recent releases are not prereleases, but the package remains below a stable major version, so its API maturity is not fully established.
Both workflows were analyzed without trigger or script-injection findings, but all 6 action references are unpinned. A low-confidence high-severity cache-poisoning pattern was also reported, which is a workflow hygiene concern rather than conclusive evidence of severe risk.
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 ^12 || ^13 | — | — |
Weekly Downloads
Info
- Last Published
- 4 days ago
- Created
- 6 months 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.