The MIT license, clear README, matching repository, and repository tests provide a solid foundation. Maintenance has gone quiet for nearly two years, with only two releases and no commits in the last three months; the project also lacks security scanning and a security policy.
55%
Total Score
50
100
86
75
The package has only two releases, both within nine days in 2024, and none in the following nearly two years. That limited history and long pause reduce confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release pause. The repository is not archived, but current maintenance capacity is not demonstrated.
Composer build tooling is present, but no security scanning tools were detected. That weakens supply-chain hygiene without showing that the package is unsafe.
The repository has no security policy. This is a transparency and reporting gap, though it is less serious for a small static analysis rules package than for software handling sensitive data.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rector/rector Version ^1.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.