Shared rules for Rector
78%
Total Score
healthy
Active releases, tests, and organization backing support the package, while unpinned workflow actions and no security policy reduce transparency.
The project uses Make and Composer build tooling, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.
The repository has no security policy. For a package distributed to developers, this leaves vulnerability-reporting expectations unclear.
Both workflows were analyzed successfully with no untrusted checkouts, script injection, or high-severity findings, but all 20 action references are unpinned. That weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rector/rector Version ^1.2.7 || ^2.0.10 | — | — |
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.