Clear documentation, release notes, and recent contributions support continued maintenance. The workflows are fully analyzed and use pinned actions, but their reported template-injection issues warrant cleanup; no untrusted trigger or checkout was found.
82%
Total Score
100
100
94
50
Composer build tooling is present, though no security scanning tool was detected; the missing scanner is a modest transparency gap rather than evidence of abandonment.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear for a package intended for WordPress installations.
All three workflows were analyzed, use five pinned actions, and have no untrusted checkout or script-injection findings. Six high-confidence template-injection findings remain in the release workflow, which is a workflow hygiene concern but not a severe standalone risk without a dangerous trigger.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ^1.0 || ^2.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.