# Rob--W/cors-anywhere

CORS Anywhere is a NodeJS reverse proxy which adds CORS headers to the proxied request.

Repository: https://github.com/Rob--W/cors-anywhere
Canonical: https://ross.abutalabs.com/products/cors-anywhere
Language: JavaScript
License: MIT
License Family: permissive
Last push: 2024-08-16T21:14:49+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 4990, "days_push": 747, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 9376, forks 6525 (observed 2026-08-28T04:10:30.936737+00:00)

## What it is
CORS Anywhere is a Node.js reverse proxy that adds CORS headers to proxied requests, allowing browsers to make cross-origin requests to servers that don't support CORS. The target URL is taken from the request path, and the proxy can be configured with origin whitelists, required headers, and cookie removal.

## Use cases
- add CORS headers to a third-party API that doesn't support them
- make cross-origin requests from a browser to a server without CORS
- self-host a CORS proxy for frontend development
- bypass CORS restrictions when fetching resources client-side
- proxy HTTP requests through a Node.js server with CORS enabled
- test cross-domain API calls during web development

## When to choose
- you need a lightweight, self-hostable CORS proxy in Node.js
- a third-party API lacks CORS headers and you can't modify the server
- you want fine-grained control over origin whitelists and required headers
- you're prototyping a frontend that needs cross-origin data

## When to avoid
- you need a production-grade proxy with rate limiting and authentication at scale
- you want a zero-maintenance hosted service - the public demo requires opt-in and is rate-limited
- you need to proxy websockets or non-HTTP protocols
- security-sensitive contexts where routing traffic through a third-party proxy is unacceptable

## Facets
- artifact type: service
- maturity: maintenance
- function: proxy, http-server, middleware
- domain: web-development, apis, backend, developer-tools
- platform: self-hosted
- tags: cors, cross-origin-requests, reverse-proxy, http-proxy, api-development, frontend-development, heroku, nodejs, web-server, docker

## Member repositories
- Rob--W/cors-anywhere (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:30.936737+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-29T17:22:21.313277+00:00, confidence not recorded.
  - readme: https://github.com/Rob--W/cors-anywhere (fetched 2026-08-28T04:10:30.936737+00:00, sha ae0015ad2cdf)
  - registry_npm: https://registry.npmjs.org/cors-anywhere (fetched 2026-08-29T08:22:29.402408+00:00, sha 585455fce6e6)
- Data as of 2026-08-30T08:39:29.467469+00:00.