Skip to content

Bump http-cache-semantics to 4.3.0 for a high-severity advisory - #28

Merged
theumann merged 1 commit into
mainfrom
audit-fix-http-cache-semantics
Oct 26, 2026
Merged

theumann merged 1 commit into
mainfrom
audit-fix-http-cache-semantics

Conversation

@theumann

Copy link
Copy Markdown
Owner

Clears the last npm audit finding: http-cache-semantics 4.2.0 → 4.3.0 (high severity, max-stale handling can disclose cross-user cached responses). Dependabot didn't open a PR for this one.

It's a build-time dependency, so the static site was never exposed.

The lockfile change is three lines: version, resolved URL and integrity. Running npm audit fix with the local npm (11.1.0) also stripped 26 libc fields that Dependabot's newer npm writes, which tell npm which Linux build (glibc or musl) of native packages to install. Those are left as they were.

Testing

  • npm ci from the new lockfile: installs 4.3.0
  • npm audit: 0 vulnerabilities
  • npm run check: 0 errors
  • npm run build: completes

🤖 Generated with Claude Code

npm audit flagged 4.2.0 (max-stale handling can disclose cross-user
cached responses), and Dependabot hadn't opened a PR for it. It's a
build-time dependency, so the static site was never exposed.

Only the version, resolved URL and integrity change. `npm audit fix` on
the local npm (11.1.0) also stripped the lockfile's `libc` fields, which
Dependabot's newer npm writes and which pick the glibc or musl build of
native packages on Linux, so the bump was applied without that churn.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying theapps with  Cloudflare Pages  Cloudflare Pages

Latest commit: f3bbd8d
Status: ✅  Deploy successful!
Preview URL: https://45706c21.theapps-7nt.pages.dev
Branch Preview URL: https://audit-fix-http-cache-semanti.theapps-7nt.pages.dev

View logs

@theumann
theumann merged commit a51430c into main Oct 26, 2026
2 checks passed
@theumann
theumann deleted the audit-fix-http-cache-semantics branch October 26, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant