Repository navigation
bump: multiple to fix audit, trying the new prompt cp-13.54.0 cp-13.55.0 - #47302
Conversation
…torybook, stream-json - update dompurify to 3.4.17 and re-create its yarn patch - raise `toml` resolution to ^5.0.1 - raise `ip-address` resolution to ^10.7.4 - raise `stream-json` resolution to ^3.7.0 - bump storybook packages to 9.1.21 Claude-Session: https://claude.ai/code/session_01DQZWqehXrCZzNT8F5Xrp2U
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
|
@SocketSecurity ignore npm/storybook@9.1.21 |
Builds ready [dca0494]
⚡ Performance Benchmarks (Total: 🟢 8 pass · 🟡 2 warn · 🔴 3 fail)
Bundle Size Diffs [🚨 Warning! Bundle size has increased!]
|
|
|
No release label on PR. Adding release label release-13.56.0 on PR, as PR was added to branch 13.56.0 when release was cut. |



Howard intro
This was done by Claude Sonnet 5.5 executing on this prompt, and the description was written by Claude. We're testing to see if AI is ready to do this all by itself.
Description
I fixed 13 of the 14 advisories in the four new issues with a validated change that sits uncommitted in the checkout. The remaining advisory (
@vitest/mocker) has no fix at this storybook major. I did not commit or push, because you only authorized pushing totrigger-ci-auditfor the last run. I haven't run tests,yarn auditor the storybook build, and I haven't regenerated LavaMoat policies. The post-changeyarn npm auditno longer lists the fixed packages,yarn lint:lockfile:dedupe:fixcaused no further change, andgit diff --checkis clean.Audit Triage: #47251, #47258, #47297, #47299
Target checked:
mainat6b79fa62(fetched 2026-10-22). The earlier fix is merged and its four issues are closed.Result: 6 release-blocking advisory groups plus 1 low-severity production one, all fixable. Informational:
storybook(3 advisories) andstream-jsonare fixable,@vitest/mockeris not, and the Electron cluster is report-only.A. Already Resolved
None.
B. Easy To Resolve
metamask-crx -> dompurify.dompurifyfrom 3.4.16 to 3.4.17.<!-->literals rewritten as"<!" + "--" + ">"). The old patch didn't apply to 3.4.17, so I recreated it with the same two substitutions indist/purify.cjs.js,purify.es.mjsandpurify.js. The old patch file is removed. Please review this patch.metamask-crx -> @metamask/eth-trezor-keyring -> @trezor/connect-web -> @trezor/connect -> @trezor/blockchain-link -> @stellar/stellar-sdk@13.3.0 -> toml@4.3.0.^4.2.0to^5.0.1.@stellar/stellar-sdklatest is 17.3.0, and it is a major jump through trezor.stellar-sdk@13.3.0asks fortoml@^3, which the resolution already overrides, so the major jump has precedent. I did not exercise stellar at runtime.-> socksand-> @modelcontextprotocol/sdk -> express-rate-limit -> ip-address.^10.7.2to^10.7.4.storybook,@storybook/addon-a11y,@storybook/addon-docsand@storybook/react-webpack5from 9.1.20 to 9.1.21, a patch bump that exists for all four.metamask-crx -> @metamask/test-dapp-solana -> ... -> jayson@4.2.0 -> stream-json@3.6.0.^3.5.0to^3.7.0.C. Difficult To Resolve
metamask-crx -> storybook -> @vitest/mocker@3.2.4.storybook@9.1.21still pins@vitest/mockerto exactly 3.2.4, and the fix needs 4.1.12 or later.electron@23.3.0.metamask-crx -> react-devtools@6.1.5 -> electron.react-devtoolslatest is 8.0.0 and still declareselectron@^23.1.2, while the advisories need 42.11.9 or later.Development-only Leftovers
@tootallnate/once,basic-ftp,bigint-buffer,braces,decode-uri-component,got,ip,micromatch,nanoid,postcssandsprintf-jsare unchanged from last time. None are fixable now, for the same reasons as before: no patch exists, the patch is ESM-only, or the fix needs a major bump through an old parent.Raw Recursive Audit
No numeric advisories outside these four issues' packages are new. The only change in the leftover list is the new
@vitest/mockeradvisory, GHSA-qxg6-89mg-rqv8 (#47258).Changelog
CHANGELOG entry: null
Related issues
Fixes: #47251
Fixes: #47258
Fixes: #47297
Fixes: #47299
Note
Medium Risk
Production bumps include dompurify (HTML sanitization), a major toml resolution override, and patched dist edits that need review; Storybook is dev-only.
Overview
This PR bumps dependencies to clear security advisories, with
yarn.lockregenerated to match.Production-facing changes:
dompurifymoves from 3.4.16 to 3.4.17 via an updated Yarn patch that keeps the same two string-splitting edits for empty-input and node-import paths (HTML comment literals built as"<!" + "--" + ">"instead of a single literal). Yarn resolutions raiseip-addressto ^10.7.4,tomlto ^5.0.1 (Stellar/Trezor chain), andstream-jsonto ^3.7.0.Dev-only: Storybook packages (
storybook,@storybook/addon-a11y,@storybook/addon-docs,@storybook/react-webpack5) go from 9.1.20 to 9.1.21.No application source changes—only
package.json, lockfile, and the dompurify patch file.Reviewed by Cursor Bugbot for commit dca0494. Bugbot is set up for automated code reviews on this repo. Configure here.