clue/http-proxy-react
Clear documentation, MIT licensing, release notes, and repository tests make this straightforward to evaluate and integrate. Maintenance is concentrated in one contributor, while workflow references are not pinned and no security policy or scanning is present.
76%
Total Score
63
100
94
83
Health Score Breakdown
The repository is owned by an individual account rather than an organization, so the single-contributor concentration is not offset by visible organizational backing.
All recent repository commits came from one contributor, so maintenance depends heavily on a single person and has limited handoff resilience.
One commit was made in the last three months by one active maintainer. The recent release compensates for the low short-term activity, but this still indicates limited maintenance capacity.
Composer build tooling is present, but no repository security scanning tools were detected, leaving security-quality automation less evident.
The repository has no security policy, making the process for privately reporting and handling vulnerabilities unclear.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Christian Lück |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 react/socket Version ^1.17 | — | — |
react/promise Version ^3.3 || ^2.1 || ^1.2.1 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.