follow-redirects 1.16.0
PkgFire would install this release with a warning.·Checked 13 hours ago·Published 13 April 2026
Why
-
warnVulnerability
follow-redirects sensitiveHeaders regex escaping can expose credential headers (fixed in 1.16.1)
-
warnVulnerability
follow-redirects: Cross-realm sensitiveHeaders arrays are discarded and custom credentials can follow redirects (fixed in 1.16.2)
-
warnVulnerability
follow-redirects array-form headers bypass cross-origin credential stripping (fixed in 1.16.1)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Verified against the registry's key
- Build provenance
- None, and no earlier version had any
Licence and upkeep
- Licence
- MIT
- OpenSSF Scorecard
- 4.6 / 10
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.