The single-maintainer project has no visible security scanning and only four stars, limiting confidence in ongoing support. Its README, tests, MIT declaration, and matching repository provide useful transparency, but adoption carries substantial abandonment risk.
42%
Total Score
33
78
75
The package has had only two releases, both in 2017, with no release in more than eight years. This strongly raises abandonment risk despite the stable 1.0.1 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in November 2017. No newer activity compensates for this prolonged inactivity.
Only one registry account can publish the package, creating a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
One issue remains open, with no issues or pull requests opened or closed in the last month. This offers no evidence of an active support channel.
The repository has four stars, zero forks, and one watcher, indicating limited visible adoption and review. Popularity is supporting evidence rather than a verdict, but it provides little compensating confidence here.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.0|~5.3 | — | — |
phpseclib/phpseclib Version ~2.0|~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.