Back to Explore

fastify/proxy-addr

GitHub
1 watchersOpen source

Last release:

@fastify/proxy-addr determines the address of a proxied request. It provides `proxyaddr(req, trust)` to return the closest untrusted address, and `proxyaddr.all(req, trust)` to return the full ordered list of request addresses. It can take a trust callback, a string, or lists of trusted IP and CIDR ranges, and supports IPv6 normalization.

Project status

  • Actively maintained: The GitHub source has an upstream push on 2026-08-07, and the most recent tagged update (v5.1.0) was 2025-09-28, indicating ongoing development activity rather than dormancy.
  • Update cadence: Tagged updates appear on a roughly yearly to multi-year pattern (v4.1.0 in 2022, v5.0.0 in 2024, v5.1.0 in 2025), with evidence of additional work in between (recent upstream push in 2026).

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v5.1.0

    v5.1.0 focuses on refactoring and performance micro-optimizations in the main proxyaddr implementation, along with substantial dev tooling and CI updates. The release notes describe the functional code changes (Object.hasOwn usage, loop refactors, and minor perf improvements) and separate build/test/tooling dependency bumps.

  • v5.0.0

    v5.0.0 updates the project primarily through dependency and tooling bumps, along with a few small internal code tweaks (regex refactor, require cache optimization, CI workflow adjustments). The included code diff shows changes to runtime dependencies (notably ipaddr.js), plus a switch in the unit test toolchain from tap to tape with c8 coverage.

  • v4.1.0

    v4.1.0 is a maintenance release focused on NodeNext (ESM/CommonJS interop) compatibility, plus CI tightening via license checking. The code diff shows additional packaging and TypeScript-related changes that are not explicitly called out in the release notes.

    Features
  • v4.0.0

    v4.0.0 release notes describe only CI and tooling updates, mainly GitHub Actions version bumps and workflow changes. There are no documented runtime/API changes or fixes to library behavior in the provided notes.