v3.0.1

Warning

This version can silently lose safeNetworks exemptions — but only when @imqueue/net resolves below 3.0.4. It declares ^3.0.0, so a fresh install today picks up a fixed version, while an existing lockfile can still hold an affected one. Check with npm ls @imqueue/net. In affected resolutions, a trusted address is dropped from the exempt set when safeNetworks holds three or more entries and one is a subnet of another, and is then counted, rate-limited and eventually banned with nothing logged. Ban lists were never affected. Fixed by upgrading to v3.0.2, which requires ^3.0.5.

Full Changelog: v3.0.0...v3.0.1

About

@imqueue/http-protect — HTTP DDoS protection middleware. Part of the @imqueue framework for Node.js & TypeScript microservices.

• Docs: https://imqueue.org/
• Guide for AI assistants / LLMs: https://imqueue.org/llms.txt
• Commercial license & support: https://imqueue.com/
• npm i @imqueue/http-protect