Risky to adopt: the package has seen no releases for over six years and no commits for more than five years. It is small and clearly linked to its own repository, but its minimal maintenance and lack of security or test tooling leave meaningful abandonment risk.
48%
Total Score
25
75
50
The latest release was published over six years ago, with no releases in the last 12 months; the four releases were concentrated within about one day. This is strong evidence of a dormant project, despite the package not being deprecated.
The repository recorded no commits and no active maintainers in the last three months, while its last push was in January 2021. The long period without observed development materially increases abandonment risk.
Only one registry account has publish access, which limits apparent publishing redundancy. Because the repository is user-owned and the package is clearly tied to it, this supports a thin maintainer-base concern rather than proving abandonment by itself.
Composer is used as a build tool, providing basic ecosystem integration, but no security scanning tools are present. This is a modest transparency and maintenance concern rather than evidence of an unfit release.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. For an HTTP request library, this is a meaningful but secondary maintenance concern.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.