A collection for awesome Rector rules
62%
Total Score
caution
Usable with caveats: no new registry release since June 2025 and no commits in the last three months.
One registry publishing account is consistent with a user-owned project, but it provides limited publishing redundancy if that maintainer becomes unavailable.
The package and repository are owned by the same user account, and the repository name matches the package, providing direct ownership evidence but no organizational backing.
This is the only release, published 480 days ago, with no releases in the last 12 months. That leaves maintenance and future compatibility uncertain despite the project's recent repository push.
The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance warning for a package with only one registry release.
All seven workflows were analyzed, but all 18 action references are unpinned and a high-confidence bot-conditions finding indicates that actor context may be spoofable. The pull_request_target workflow has no untrusted checkout or script-injection finding, limiting the immediate severity.
We didn't find any vulnerabilities for this package.
| Version | Published | Vulnerabilities |
|---|---|---|
| 1.0.0 | 3 Jun 2025 | 0 0 critical, 0 total 0 0 high, 0 total 0 0 medium, 0 total 0 0 low, 0 total |
| Dependency | Last Release | Score |
|---|---|---|
rector/rector Version ^2.0.11 | — | — |
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
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.