</>PackageGraphPackageGraph

https-proxy-agent

npmv9.1.0

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

Safe to adopt

Yes — https-proxy-agent scores well across adoption, maintenance, weight, supply chain, and licensing. 225.1M downloads per week and 10 known dependents. Last published 93 days ago. 4 releases in the last 2 years.

  • AAdoption: grade A, Excellent.

    225.1M downloads per week and 10 known dependents.

  • BMaintenance: grade B, Good.

    Last published 93 days ago. 4 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Pulls in 4 transitive packages, about 106 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding https-proxy-agent to a project.

3
Direct dependencies

Runtime packages this one declares itself.

4
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

106 KB
Install size

Unpacked size of this package plus its entire runtime tree.

2
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing https-proxy-agent, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >= 20
Module format
ESM only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the https-proxy-agent README.

import * as https from 'https';
import { HttpsProxyAgent } from 'https-proxy-agent';

const agent = new HttpsProxyAgent('http://168.63.76.32:3128');

https.get('https://example.com', { agent }, (res) => {
  console.log('"response" event!', res.headers);
  res.pipe(process.stdout);
});

https-proxy-agent vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
https-proxy-agentthis page225.1M10MIT3 months ago
http-proxy-agent05MIT1 day ago
socks-proxy-agent03MIT1 day ago
pac-proxy-agent01MIT1 day ago
proxy-agent01MIT1 day ago
agent-base06MIT1 day ago

Dependencies

Declared by https-proxy-agent v9.1.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (8)

@types/async-retry ^1.4.5@types/debug ^4.1.7@types/node ^22.13.0async-listen ^3.0.0async-retry ^1.3.3proxy 4.1.0tsconfig 0.0.0typescript ^5.1.6

Used by

Popular packages that depend on https-proxy-agent.

Relationship graph

Dependencies (left) and dependents (right) of https-proxy-agent.

Frequently installed together

Release history

4 releases in the last two years, typically about 47 days apart.

Recent versions of https-proxy-agent
VersionPublishedSizeLicense
9.1.0latest3 months ago33 KBMIT
9.0.05 months ago25 KBMIT
8.0.06 months ago25 KBMIT
7.0.61 year ago34 KBMIT
7.0.52 years ago34 KBMIT
7.0.42 years ago34 KBMIT
7.0.32 years ago34 KBMIT
7.0.23 years ago34 KBMIT
7.0.13 years ago34 KBMIT
7.0.03 years ago34 KBMIT
6.2.13 years ago34 KBMIT
6.2.03 years ago34 KBMIT
6.1.03 years ago34 KBMIT
6.0.03 years ago31 KBMIT
5.0.14 years ago25 KBMIT

Overview

https-proxy-agent is an npm package that an HTTP(s) proxy `http.Agent` implementation for HTTPS. It is extremely widely used, with about 225.1M downloads per week and 10 known dependents in the graph. The latest version is 9.1.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need an HTTP(s) proxy `http.Agent` implementation for HTTPS and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (225.1M weekly downloads).
  • Clear open-source license (MIT).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use https-proxy-agent?

Yes — https-proxy-agent scores well across adoption, maintenance, weight, supply chain, and licensing. 225.1M downloads per week and 10 known dependents. Last published 93 days ago. 4 releases in the last 2 years.

How do I install https-proxy-agent?

Run `npm install https-proxy-agent` to add https-proxy-agent to your npm project.

How many dependencies does https-proxy-agent have?

https-proxy-agent declares 11 direct dependencies and pulls in 4 packages in total once its runtime tree is resolved totalling about 106 KB on disk.

What license is https-proxy-agent released under?

https-proxy-agent is distributed under the MIT license.

How popular is https-proxy-agent?

https-proxy-agent has approximately 225,102,746 downloads per week and 10 known dependent packages.

Is https-proxy-agent still maintained?

The most recent release of https-proxy-agent (v9.1.0) was published 3 months ago.

Does https-proxy-agent run install scripts?

No. https-proxy-agent does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.