chore(security): bump dependencies to resolve Dependabot alerts - #567
Conversation
Patches 34 of 39 open Dependabot alerts via resolution/override bumps to the first patched release; no source changes. Root (resolutions + turbo devDep): - shell-quote -> 1.8.4 (critical) - @xmldom/xmldom 0.8.12 -> 0.8.13, fast-uri -> 3.1.2, @babel/plugin-transform-modules-systemjs -> 7.29.4 (high) - tmp 0.2.4 -> 0.2.6 (high) - ws ^8.18.1 -> ^8.20.1, qs 6.14.2 -> 6.15.2, postcss 8.4.31 -> 8.5.10 (medium) - turbo 2.5.5 -> 2.9.14 (medium/low) Example app (examples/expo-multichain overrides): - hono 4.12.12 -> 4.12.21 (10 alerts) - @xmldom/xmldom 0.8.13, fast-uri 3.1.2, shell-quote 1.8.4 (critical/high) - ws 8.20.1, postcss 8.5.10, brace-expansion 5.0.5 -> 5.0.6 (medium) The remaining 5 alerts are dismissed separately (not exploitable in this tree, or no published patch): uuid x2, ip-address, bigint-buffer x2. Verified: yarn build, yarn test, yarn lint all pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
Claude finished @ignaciosantise's task in 2m 11s —— View job Review complete
✅ No issues found Summary:
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Pull request overview
This PR addresses Dependabot security alerts by bumping pinned transitive dependency versions via Yarn resolutions (repo root) and npm overrides (Expo example), and refreshing the corresponding lockfiles.
Changes:
- Update root
resolutionsand devDependencyturboto patched versions (e.g.,shell-quote,fast-uri,postcss,qs,tmp,@xmldom/xmldom,@babel/plugin-transform-modules-systemjs,ws). - Update Expo example app
overridesto patched versions (e.g.,hono,brace-expansion,@xmldom/xmldom,postcss,ws, etc.). - Refresh
yarn.lockand the example app’spackage-lock.jsonto reflect the new dependency graph.
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
package.json |
Bumps turbo and updates root Yarn resolutions to patched dependency versions. |
yarn.lock |
Regenerated Yarn lockfile reflecting updated root resolutions/dependency versions. |
examples/expo-multichain/package.json |
Updates npm overrides to patched versions for the example app. |
examples/expo-multichain/package-lock.json |
Regenerated npm lockfile reflecting updated example app overrides/dependency tree. |
Files not reviewed (1)
- examples/expo-multichain/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Forcing ws to a single hoisted version (8.20.1) changed Metro module
resolution so the example bundles ws's Node build (which does
`require('stream')`) instead of the React-Native/browser shim it used
before. This broke `expo export`/`expo run` for the example with:
"Unable to resolve module stream from .../ws/lib/stream.js".
The example has no metro.config.js to shim Node core modules (unlike
apps/native), so the ws security bump can't be applied here without
breaking the bundle. Dropping the override restores a clean bundle
(verified: `expo export --platform ios` -> 4060 modules, exit 0).
The example's ws alert (#272) is dismissed separately as tolerable_risk
(sample app, not published; patched ws breaks Metro resolution).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Summary
Addresses the 39 open Dependabot alerts: 33 patched by bumping pinned transitive-dependency versions to their first patched release, 6 dismissed (not exploitable in this tree, no published patch, or would break the build).
No source code and no published package manifests changed — only the root
resolutions(Yarn, dev/CI-only, not published) and the example app'soverrides, plus refreshed lockfiles. Nopackages/*/package.jsonwas touched, so the published SDK's dependency contracts and compiled output are unchanged.Patched (33)
Root
package.json—resolutions+turbodevDep (14 alerts)shell-quote1.8.4@xmldom/xmldom0.8.12→0.8.13fast-uri3.1.2@babel/plugin-transform-modules-systemjs7.29.4tmp0.2.4→0.2.6ws^8.18.1→^8.20.1qs6.14.2→6.15.2postcss8.4.31→8.5.10turbo2.5.5→2.9.14Example app
examples/expo-multichain/package.json—overrides(19 alerts)hono4.12.12→4.12.21@xmldom/xmldom0.8.12→0.8.13fast-uri3.1.2shell-quote1.8.4postcss8.5.10brace-expansion5.0.5→5.0.6Dismissed (6) — evaluated and intentionally excluded from the bumps
uuid(fix: ui changes in social webview to solve android issues #277, fix: refresh balance #273, medium) — bug is a missing buffer bounds check in v3/v5/v6 with abufarg; all consumers usev4()withoutbuf. Forcing11.1.1violatesxcode/@expo/*/@metamask/utilsranges. →tolerable_risk.ip-address(fix: siwe import #259, medium) — XSS lives inAddress6HTML-emitting methods; sole consumersocksis parse-only. Forcing10.1.1breakssocks'^9.0.5range. →tolerable_risk.bigint-buffer(chore: prep for v1.0.0-beta.1 #95, chore: ui fixes #96, high) — transitive via@solana/web3.js; no published fix. →no_bandwidth.wsin the example app (chore: small changes #272, medium) — the example has nometro.config.jsto shim Node core modules. Forcingws@8.20.1as a single hoisted version makes Metro bundle ws's Node build (require('stream')) instead of the React-Native/browser shim, breakingexpo export/expo runwith "Unable to resolve module stream from ws/lib/stream.js". The override was removed from the example; the rootwsbump is unaffected (apps/nativehas a resolver and bundles cleanly). →tolerable_risk.Verification
yarn install/npm installresolve cleanlyyarn build(9/9 packages, turbo 2.9.14)yarn test(152 tests pass)yarn lintapps/nativeMetro bundle: web (2647 modules) + iOS (2947 modules)examples/expo-multichainexpo export --platform ios→ 4060 modules (after removing the ws override)🤖 Generated with Claude Code