The package is small and focused, with a clear README, one runtime dependency, and matching repository documentation. Organization backing and an MIT declaration add useful transparency, but the repository has no security policy and little public adoption.
53%
Total Score
67
100
83
75
Only one registry account has publish access, which is a modest operational concern. The organization-owned repository provides some compensating project backing, so this is not a severe risk.
The package has 14 releases over roughly eight years, but none in the last three years; the latest release was in May 2023. This materially raises maintenance and abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. This is the clearest evidence of possible abandonment.
The repository has zero stars and forks and only two watchers, showing very limited community adoption. Popularity is supporting evidence rather than a verdict, but it offers little reassurance when activity is also absent.
Composer is used as the build tool, but no security-scanning tool is configured. The missing scanning is a hygiene gap, while the standard build tooling supports reproducibility.
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.