proxy-addr 2.0.1
Determine address of proxied request
proxy-addr@2.0.1 was published on 2017-09-11. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.10.
All proxy-addr versions · Permanent reference to 2.0.1 · Latest release
Package specifications
| Version | 2.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2017-09-11T01:11:33.860Z |
| Node.js requirement | >= 0.10 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 1 |
| Resolved graph dependencies | 2 |
| Repository stars | 142 |
| Repository forks | 33 |
Install proxy-addr 2.0.1
npm install proxy-addr@2.0.1 pnpm add proxy-addr@2.0.1 yarn add proxy-addr@2.0.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.
- forwarded@0.1.2 — direct
- ipaddr.js@1.5.2 — direct
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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 3/10 — Found 4/11 approved changesets -- score normalized to 3 |
| Pinned-Dependencies | 6/10 — dependency not pinned by hash detected -- score normalized to 6 |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 9/10 — security policy file detected |
| SAST | 8/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/proxy-addr/2.0.1 — retrieved 2026-10-29T11:42:52.493Z
- https://api.deps.dev/v3/projects/github.com%2Fjshttp%2Fproxy-addr — retrieved 2026-10-29T05:58:33.359Z
- https://api.deps.dev/v3/systems/npm/packages/proxy-addr/versions/2.0.1 — retrieved 2026-10-29T11:42:53.035Z
- https://api.deps.dev/v3/systems/npm/packages/proxy-addr/versions/2.0.1:dependencies — retrieved 2026-10-29T11:42:53.055Z