Baseline WordPress hardening, cleanup and mime-type support
67%
Total Score
caution
A brand-new pre-1.0 package has one contributor and three workflow credential findings, despite solid repository documentation and tests.
This is the first release, published 0 days ago, so there is no demonstrated release track record yet. That is an early maturity concern rather than evidence of abandonment.
All 8 recent commits came from one contributor, giving the project a high concentration of maintenance responsibility. Organizational ownership partly offsets handoff risk, but no second active contributor is shown.
Composer build tooling is used, but no security scanning tool was detected. This is a modest transparency and assurance gap for a security-focused WordPress package.
The release is v0.1.0 and the README identifies the public surface as pre-1.0 and subject to breaking changes without deprecation cycles. Consumers should expect API instability.
All three workflows use unpinned actions, and each has a high-confidence medium-severity secrets-inherit finding. There are no untrusted checkouts or script injections, and one workflow scopes permissions at job level, which limits but does not remove the workflow hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
enshrined/svg-sanitize Version ^1.0 | — | — |
siratik/package-loader Version ^0.1 | — | — |
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.