An HTTP(s) proxy `http.Agent` implementation for HTTPS
77%
Total Score
50
100
89
75
100
There were no commits and no active maintainers in the last three months. Although the recent release and September repository push provide some compensation, this is a meaningful maintenance slowdown.
The repository has recent issue and pull-request activity, including one new issue and two new pull requests in the last month, but none of those pull requests were merged. This suggests attention exists without clear recent delivery.
The repository name does not match the package name and its README does not mention this package, creating some uncertainty about the linkage. The repository is a multi-package project, which partly explains the name mismatch but not the absent README mention.
The repository uses TypeScript, npm scripts, Vitest, and Turbo, showing established build and test tooling. No security scanning tools were detected, leaving a modest security-hygiene gap.
The repository has no security policy. That weakens vulnerability-reporting transparency, though it does not by itself indicate abandonment.
| Title | Versions | Severity |
|---|---|---|
CVE-2018-3739 https-proxy-agent is vulnerable to Out-of-bounds Read in versions 0.0.0 - 2.2.0. | 0.0.0 - 2.2.0 | Critical |
| Dependency | Last Release | Score |
|---|---|---|
debug Version ^4.3.4 | — | — |
agent-base Version 9.0.0 | — | — |
proxy-agent-negotiate Version 1.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.