Is @camdh/https-proxy-agent safe to use?

@camdh/https-proxy-agent has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 37/100 (critical risk).

What is the latest version of @camdh/https-proxy-agent?

The latest version of @camdh/https-proxy-agent is 1.0.0, released 2021-09-15.

Does @camdh/https-proxy-agent have known vulnerabilities?

No known vulnerabilities on the latest version of @camdh/https-proxy-agent.

Is @camdh/https-proxy-agent deprecated?

No, @camdh/https-proxy-agent is actively maintained. Latest release: 1.0.0 (2021-09-15).

What are alternatives to @camdh/https-proxy-agent?

Popular alternatives to @camdh/https-proxy-agent in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @camdh/https-proxy-agent use?

@camdh/https-proxy-agent is licensed under MIT.

@camdh/https-proxy-agent

npmv1.0.0

An HTTP(s) proxy `http.Agent` implementation for HTTPS

License MITpermissive1 versions2 maintainers2 deps

CambridgeDigitalHealth/node-https-proxy-agent

/ 100

Health

use with caution

@camdh/[email protected] low health (37/100) — consider alternatives

Moderate health score (37/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

agent-base debug

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@camdh/https-proxy-agent