Rector rules for upgrading from phpseclib v2 to phpseclib v3
45%
Total Score
75
75
75
The package strongly resembles phpseclib/phpseclib, has only 2 monthly downloads versus 12,342,005, and is marked as borrowing its identity. Although artifact overlap is 0, this creates substantial risk that consumers wanted the established package instead.
This release is the package's only release, published about 1 year 4 months ago, with no releases in the last 12 months. That limited history weakens evidence of sustained maintenance.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. Its later push history provides some evidence the repository is not abandoned, but current development activity remains limited.
The linked repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, though it is not evidence of a security defect by itself.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but both of its 2 action references are unpinned. That leaves the build exposed to moving action revisions and is a moderate hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rector/rector Version ^2.0.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.