# apify/proxy-chain

Node.js implementation of a proxy server (think Squid) with support for SSL, HTTP/HTTPS, SOCKS5, authentication, and upstream proxy chaining.

Repository: https://github.com/apify/proxy-chain
Canonical: https://ross.abutalabs.com/products/proxy-chain
Homepage: https://www.npmjs.com/package/proxy-chain
Language: TypeScript
License: Apache-2.0
License Family: permissive
Topics: javascript-library, proxy-server, proxychains, headless-chrome, http, socks5
Last push: 2026-09-02T19:53:25+00:00

## Health v2 (maintenance only)
Score: 90/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 100, release rhythm 72, longevity 100
- inputs: {"age_days": 3222, "days_push": 0, "days_rel": 106, "gap_med": 32.5, "n_releases_24m": 11}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1020, forks 167 (observed 2026-09-03T02:15:09.245329+00:00)

## What it is
A programmable HTTP/HTTPS proxy server library for Node.js, similar to Squid, with support for SSL/TLS, SOCKS4/5, authentication, upstream proxy chaining, and custom HTTP responses. It is commonly used to let tools like headless Chrome and Puppeteer work with upstream proxies that require username/password authentication.

## Use cases
- run a local proxy server so headless Chrome can use an authenticated upstream proxy
- chain multiple upstream proxies programmatically in Node.js
- build a custom HTTP/HTTPS proxy with dynamic authentication rules
- tunnel arbitrary protocols like HTTPS or FTP through an HTTP proxy
- intercept requests and return custom HTTP responses through a proxy
- collect traffic statistics through a programmable proxy

## When to choose
- you need a proxy server whose authentication and chaining logic is defined in code and fully dynamic
- you use Puppeteer or headless Chrome with proxies that require credentials
- you need SOCKS4/5 and HTTP CONNECT tunneling support in a Node.js proxy
- you are building scraping infrastructure on top of residential or datacenter proxy pools

## When to avoid
- you just need a simple static forward proxy with a config file - Squid or nginx may be simpler
- you need proxy protocols beyond Basic Proxy-Authorization
- your project is not on the Node.js platform

## Facets
- artifact type: library
- maturity: active
- function: proxy, http-server, auth, networking, web-scraping
- domain: networking, web-development, developer-tools, crawlers
- platform: cross-platform
- tags: proxy-server, proxy-chaining, socks5, http-proxy, headless-chrome, puppeteer, ssl-tls, traffic-statistics, nodejs, javascript

## Member repositories
- apify/proxy-chain (main) score 90

## Provenance
- Observed fields: from GitHub, fetched 2026-09-03T02:15:09.245329+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:09:27.486485+00:00, confidence not recorded.
  - readme: https://github.com/apify/proxy-chain (fetched 2026-09-03T02:15:09.245329+00:00, sha c2c910c877f9)
- Data as of 2026-08-30T08:39:29.467469+00:00.