follow-redirects
1.16.3 · 8 Nov 2026MIT149.9M / weekRepositorynpmAtom feed
Upgrading follow-redirects From 0.0.5 to 1.16.3
69 releases in betweennotes for 5
Reading releases, release notes and advisories…
The note of 1.0.0 lists no breaking change or deprecation, which is rare for a major.
- ?
- changes to make
- 5
- advisories fixed
- ?
- new
- ?
- fixes
Counted from 5 of 69 release notes. Advisories are counted from the advisory database, in full.
Security
Fixes 5 advisories affecting 0.0.5
- Exposure of sensitive information in follow-redirectshigh · GHSA-74fj-2j2h-c42q
- follow-redirects' Proxy-Authorization header kept across hostsmoderate · GHSA-cxjh-pqwp-8mfp
- Follow Redirects improperly handles URLs in the url.parse() functionmoderate · GHSA-jchw-25xp-jwwc
- Exposure of Sensitive Information to an Unauthorized Actor in follow-redirectsmoderate · GHSA-pw2r-vq6v-hr8c
- follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Targetsmoderate · GHSA-r4q5-vmmm-2653
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.