Rector upgrades rules for WordPress
70%
Total Score
caution
Usable with caveats: maintenance is concentrated in one contributor and all workflow actions are unpinned.
The package declares a post-update-cmd lifecycle script. An update-time script adds some execution and maintenance surface, although this signal alone is not severe.
The repository owner is a user account rather than an organization, so the concentrated recent activity is not offset by visible organizational backing. This supports the bus-factor concern.
One contributor made all two commits in the last three months, giving the repository a 100% top-contributor share. That concentration increases continuity risk for a user-owned project.
Only two commits were made in the last three months, so activity is present but light. This warrants some caution about the depth of ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
rector/rector Version ^2.0 | — | — |
webmozart/assert Version ^1.11 | — | — |
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.