Skip to content

Bump dependencies to patched versions (security bundle)#43

Merged
feruzm merged 1 commit into
masterfrom
deps/security-bundle
Jun 9, 2026
Merged

Bump dependencies to patched versions (security bundle)#43
feruzm merged 1 commit into
masterfrom
deps/security-bundle

Conversation

@feruzm

@feruzm feruzm commented Jun 9, 2026

Copy link
Copy Markdown
Member

What

Bundles the outstanding npm Dependabot security updates into one change by extending the existing yarn resolutions block (plus an axios bump), so the vulnerable transitive versions are removed from yarn.lock. Each corresponding Dependabot PR should auto-close once this merges.

No build-toolchain changes — webpack 3 / babel 6 / node-sass 4.x stay put, so the build is unaffected.

Verification

Built against the actual deploy toolchain (node:8, the Dockerfile-web base):

  • yarn install regenerates the lock with patched versions
  • yarn build ✅ succeeds (production bundle emitted)
  • yarn test ✅ 14/15 (the 1 failure is a pre-existing stale snapshotlinkify expects the old steemit.com domain; unrelated to deps and not run at deploy time)

Key bumps (via resolutions, unless noted)

dep to note
axios ^0.28.0 (direct) resolved 0.28.1
lodash / lodash-es ^4.17.21 floats to 4.18.1, clears GHSA-r5fr-rjxr-66jc (≤4.17.23)
handlebars ^4.7.8 4.7.9
elliptic ^6.6.1
minimist ^1.2.8
qs ^6.5.3
url-parse ^1.5.10
decode-uri-component ^0.2.2
cross-fetch ^3.1.5
urijs ^1.19.11
http-proxy ^1.18.1
ini ^1.3.7
y18n ^3.2.2
tmpl / path-parse / dns-packet / hosted-git-info / express latest patched
node-sass ^4.14.1 stays on 4.x (5+ needs newer node)

Expected to auto-close

Dependabot PRs: #40 #39 #37 #36 #35 #34 #31 #26 #25 #22 #21 #19 #17 #14 #12 #10 #9

Deferred (require modernization, not this PR)

These, plus the remaining build-tooling alerts (webpack/babel/loader-utils/etc., which never ship to the browser), are best handled in a follow-up modernization PR.

Extend yarn resolutions to pull in patched transitive dependencies and
bump axios, closing the outstanding npm Dependabot security PRs without
touching the build toolchain. lodash floats to 4.18.1, which also clears
the recent lodash advisory (<= 4.17.23).

Verified: production build succeeds on the node:8 toolchain; unit tests
pass (the one snapshot diff is a pre-existing stale fixture, unrelated).

Deferred to the toolchain modernization: node-sass 7 / react-dev-utils 11
(need webpack 4+) and the Python deps (need a newer base than 3.5).
@feruzm feruzm merged commit 7e65af8 into master Jun 9, 2026
@feruzm feruzm deleted the deps/security-bundle branch June 9, 2026 06:22

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 056e9c71d4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread react_app/package.json
"dot-prop": "^4.2.1",
"node-sass": "^4.13.1",
"elliptic": "^6.5.3",
"node-sass": "^4.14.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump the actual node-sass dependency

This resolution does not upgrade the top-level devDependencies.node-sass entry, which still requests ^4.9.3; the checked-in lockfile therefore still contains node-sass@^4.9.3 resolved to 4.12.0 at react_app/yarn.lock:5096. In install paths that use the app's direct dev dependency, the security bundle leaves the older node-sass installed while adding a separate 4.14.1 lock entry, so this patch does not actually remove the vulnerable direct dependency unless the devDependency range is bumped too.

Useful? React with 👍 / 👎.

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