Documentation, tests, licensing, and repository ownership are clear, with no install-time scripts or deprecation. Maintenance is the main concern: only two releases exist, the latest was over four years ago, and the repository has no security policy or scanning.
62%
Total Score
67
100
78
83
One registry maintainer is consistent with the individually owned repository shown by project backing. It indicates a thin publishing base, but does not by itself show a maintenance failure.
The package has only two releases, with none in the last four years and a median interval of about 1,361 days. This is a meaningful maintenance concern for a dependency, though the repository is not archived.
There are no open issues or pull requests and no recent activity. A clean tracker is not inherently negative, but combined with the old last release it offers no evidence of ongoing maintenance.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little evidence of a broad user or contributor community.
Composer is used for the build, which is appropriate for a PHP package. No security scanning tools are configured, leaving a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpseclib/phpseclib Version ~2.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.