http-proxy-middleware

The one-liner node.js proxy middleware for connect, express, next.js and more

http-proxy-middleware@4.2.1 was published on 2026-10-24. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^22.15.0 || ^24.0.0 || >=26.0.0.

All http-proxy-middleware versions · Permanent reference to 4.2.1

Package specifications

Version4.2.1
License declarationMIT
Published2026-10-24T18:24:13.128Z
Node.js requirement^22.15.0 || ^24.0.0 || >=26.0.0
Type declarationsBundled declarations
Runtime dependency count5
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size95.14 KiB
Published file count67
Package typemodule
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies12
Repository stars11130
Repository forks877

Install http-proxy-middleware 4.2.1

npm install http-proxy-middleware@4.2.1
pnpm add http-proxy-middleware@4.2.1
yarn add http-proxy-middleware@4.2.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review0/10 — Found 1/30 approved changesets -- score normalized to 0
Maintained10/10 — 24 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Packaging10/10 — packaging workflow detected
Branch-Protection1/10 — branch protection is not maximal on development and all release branches
SAST9/10 — SAST tool is not run on all commits -- score normalized to 9

Evidence and freshness