Skip to content

Address critical npm vulnerabilities in builder frontend - #495

Open
prestoncabe wants to merge 2 commits into
mainfrom
492-address-critical-npm-vulnerabilities-in-builder-frontend
Open

Address critical npm vulnerabilities in builder frontend#495
prestoncabe wants to merge 2 commits into
mainfrom
492-address-critical-npm-vulnerabilities-in-builder-frontend

Conversation

@prestoncabe

Copy link
Copy Markdown
Collaborator

Summary

  • remove the unused direct fast-xml-parser dependency
  • refresh transitive dependencies to patched releases within the existing version ranges
  • resolve all 22 npm audit findings without forced or major-version upgrades

Critical findings reviewed

Vulnerable package Dependency path Resolution
fast-xml-parser 5.2.5 direct dependency removed because it was unused
protobufjs 7.5.3 firebase@firebase/firestore@grpc/proto-loaderprotobufjs updated to 7.6.6
seroval 1.3.2 solid-jsseroval updated to 1.5.6
tar 7.4.3 @tailwindcss/postcss@tailwindcss/oxidetar updated to 7.5.22
websocket-driver 0.7.4 firebase@firebase/databasefaye-websocketwebsocket-driver updated to 0.7.5

The associated high, moderate, and low findings were also resolved by the same lockfile refresh, so no follow-up vulnerability issues are needed.

Validation

  • npm ci
  • npm audit — 0 vulnerabilities
  • npm test — 35 tests passed
  • npm run build

Closes #492

prestoncabe and others added 2 commits September 4, 2026 13:21
The previous commit resolved the fast-xml-parser critical advisory
(GHSA affecting <=5.6.0) by bumping it 5.2.5 -> 5.11.1. That works, but
5.11 decomposed the library, so the bump pulled six brand-new runtime
packages into the shipped production graph: @nodable/entities,
fast-xml-builder, is-unsafe, path-expression-matcher, xml-naming, and
anynum via strnum.

Nothing in the repo imports it. A search for fast-xml-parser, XMLParser,
XMLBuilder, and XMLValidator finds no hits outside the package.json entry
itself, so the upgrade expanded the production supply-chain surface by
seven packages in exchange for no functionality.

Remove the dependency and re-lock instead. This clears the same advisory
and drops the whole subtree.

Verified on devbox's Node 22.23.2: `npm ci` clean, `npm audit` reports 0
vulnerabilities, `npm test` 35/35 pass, and `npm run build` succeeds.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01W8h2QpmBtXzzVBUcJQydrR
@prestoncabe prestoncabe linked an issue Sep 4, 2026 that may be closed by this pull request
7 tasks
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.

Address critical npm vulnerabilities in builder-frontend

1 participant