http-cache-semantics (npm)

RFC 7234 in JavaScript. Parses HTTP headers to correctly compute cacheability of responses, even in complex cases

Advisories

Latest version

4.3.0

Released Oct 4, 2026

License

BSD-2-Clause

OpenSSF Scorecard

2.1 / 10

How to fix

Upgrading to 4.1.1 or later clears every advisory below that has a fix.

Upgrade commands

npm

npm install http-cache-semantics@4.3.0

yarn

yarn add http-cache-semantics@4.3.0

pnpm

pnpm add http-cache-semantics@4.3.0

Known vulnerabilities

Advisory	Severity	Affected	Fixed in
GHSA-ch52-4w7c-c8xp Withdrawn Advisory: http-cache-semantics max-stale handling can disclose cross-user cached responses Withdrawn	High EPSS 0.57%	`<= 4.2.0`	No fix yet
GHSA-ch52-4w7c-c8xp Withdrawn Advisory: http-cache-semantics max-stale handling can disclose cross-user cached responses Withdrawn	High EPSS 0.57%	`<= 4.2.0`	No fix yet
GHSA-rc47-6667-2j5j http-cache-semantics vulnerable to Regular Expression Denial of Service	High EPSS 1.61%	`< 4.1.1`	`4.1.1`

Source: git+https://github.com/kornelski/http-cache-semantics.git

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor