The MIT license and focused artifact make inspection straightforward. No security policy or repository security scanning adds little assurance for future changes.
36%
Total Score
0
71
50
The package has only one release, published over six years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the lack of recent releases and indicating no observed maintenance capacity.
The repository name matches the package, but its README does not mention this package and instead references a different package name, which weakens transparency about the source-to-package relationship.
Composer build tooling is present, but no security scanning tools were detected. That provides basic project structure without evidence of ongoing security checks.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react/http-client Version ^0.5.9 | — | — |
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.