Clear licensing, documentation, and a changelog help consumers. The tiny, inactive repository and single-release history leave maintenance and ownership confidence too weak for a dependable dependency.
38%
Total Score
0
67
50
The package has only one release, published about 5 years and 5 months ago, with no releases in the last 12 months. That is strong evidence of abandonment for a library intended as an ongoing dependency.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, and its last push was about 5 years and 5 months ago. The lack of recent maintenance materially increases abandonment risk.
The linked repository has 0 stars, 0 forks, and 1 watcher. Popularity is not decisive by itself, but these values provide no supporting evidence of an active project alongside the absent maintenance activity.
Composer build tooling is present, but no security scanning tools were detected. That is a modest supply-chain hygiene gap for a library distributed to applications.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is secondary to the much stronger evidence of inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpseclib/phpseclib Version ^2.0|^3.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.