Skip to content

chore: Remediate 5 of 8 Dependabot security alerts (lockfile only) - #244

Merged
ernst-dev merged 1 commit into
mainfrom
roko-dependabot/security-remediation-20260806
Aug 6, 2026
Merged

chore: Remediate 5 of 8 Dependabot security alerts (lockfile only)#244
ernst-dev merged 1 commit into
mainfrom
roko-dependabot/security-remediation-20260806

Conversation

@ernst-dev

Copy link
Copy Markdown
Member

Automated Dependabot security-alert remediation

Alert-driven remediation of this repository's open Dependabot security alerts.
Baseline: 9e19b1a32 on main.

Alerts resolved (5 of 8)

AlertSevPackageMajor lineVulnerable rangeFirst patchedNow resolved toAdvisory
#206mediumundici7.x>= 7.0.0, < 7.29.07.29.07.29.0, 6.28.0GHSA-8xcm-r25x-g524 (CVE-2026-16728)
#207highundici7.x>= 7.0.0, < 7.29.07.29.07.29.0, 6.28.0GHSA-4cwx-7wf7-3272 (CVE-2026-13697)
#208mediumundici7.x>= 7.0.0, < 7.29.07.29.07.29.0, 6.28.0GHSA-v3r7-h72x-cjcm (CVE-2026-16729)
#209mediumundici7.x>= 7.0.0, < 7.29.07.29.07.29.0, 6.28.0GHSA-jr45-8vmc-qm54 (CVE-2026-14643)
#210mediumundici7.x>= 7.0.0, < 7.29.07.29.07.29.0, 6.28.0GHSA-m8rv-5g2x-5cg5 (CVE-2026-15157)

❌ Alerts NOT resolved by this PR (3) — human decision required

AlertSevPackageVulnerable rangeFirst patchedStill installedAdvisory
#199mediumreact-router>= 6.0.0, < 7.18.07.18.06.30.4GHSA-wrjc-x8rr-h8h6 (CVE-2026-53669)
#198mediumreact-router-dom>= 6.30.2, <= 6.30.4none published6.30.4GHSA-jjmj-jmhj-qwj2 (CVE-2026-53668)
#197mediumreact-router>= 6.4.0, < 7.18.07.18.06.30.4GHSA-337j-9hxr-rhxg (CVE-2026-53666)

Why these are not fixed here:

  • react-router-domhas no patched version at all on the 6.x line (advisory GHSA-jjmj-jmhj-qwj2 lists >= 6.30.2, <= 6.30.4 with no first-patched release). The only remediated package in that advisory is react-router >= 7.13.0.
  • react-router is only patched at 7.18.0 — a major v6→v7 upgrade. It is installed here transitively via react-router-dom@6.30.4, so bumping react-router alone to 7.x would pair a v7 core with a v6 dom package and break at runtime. Pinning it via overrides would produce exactly that broken combination, so it was deliberately not attempted.
  • A real fix therefore means migrating off react-router-dom 6.x to react-router 7.x, which is a framework migration, not a dependency bump. That is out of scope for automated remediation and needs an owner decision.

How this was remediated

  • Rung 1 — npm audit fix --package-lock-only --ignore-scripts (no --force was used anywhere in this run).
  • The repo's own prepare-package-lock convention (postinstall in @cloudscape-design/build-tools) was applied afterwards, so no @cloudscape-design/* entries are (re-)introduced into the lockfile.
  • npm's full reconciliation additionally healed unrelated pre-existing lockfile drift (stale entries, dev/optional flags, unrelated minor bumps). That collateral was deliberately discarded: only the security-relevant entries from npm's computed result were applied on top of the committed lockfile, so this diff contains alert-driven changes only.
  • Verified with npm ls --package-lock-only --all: zero new unmet/invalid dependency problems versus main.

Lockfile changes (6)

PackageFromToScopeLockfile path
brace-expansion2.1.32.1.4devnode_modules/glob/node_modules/brace-expansion
brace-expansion2.1.32.1.4devnode_modules/readdir-glob/node_modules/brace-expansion
brace-expansion5.0.85.0.9devnode_modules/test-exclude/node_modules/brace-expansion
undici7.28.07.29.0devnode_modules/undici
yaml2.3.12.9.0devnode_modules/yaml
yaml(new)2.3.1devnode_modules/lint-staged/node_modules/yaml

NPMPM (NpmPrettyMuch) availability — internal build safety

Not applicable — 0 non-dev dependencies changed. Every version bump in this PR is dev: true, which the NPMPM availability check skips, so there is no internal-build (Brazil) impact and the check should come back green.

Does merging clear this repository's alert list?

No — partially. Merging this PR is expected to close 5 of 8 open alerts. 3 will remain open: #199, #198, #197 (react-router / react-router-dom), which need the v6→v7 migration decision described above.


Existing Dependabot-authored PRs were deliberately not touched, reviewed, rebased, or closed by this run.

Opened by roko-dependabot on behalf of @ernst-dev. Alert-driven remediation; not merged — a human must review and merge.

Alert-driven lockfile remediation via npm audit fix (rung 1); repo's own prepare-package-lock convention applied. Non-dev upgrades verified available in NpmPrettyMuch.
@ernst-dev
ernst-dev requested a review from a team as a code ownerAugust 6, 2026 11:31
@ernst-dev
ernst-dev requested review from SpyZzey and removed request for a teamAugust 6, 2026 11:31
@codecov

codecovBot commented Aug 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.07%. Comparing base (9e19b1a) to head (7b52158).

Additional details and impacted files
@@ Coverage Diff @@## main #244 +/- ##
=======================================
Coverage 98.07% 98.07% =======================================
Files 52 52 Lines 1764 1764 Branches 514 492 -22 =======================================
Hits 1730 1730 - Misses 33 34 +1 + Partials 1 0 -1 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ernst-devernst-dev changed the title chore(deps): remediate open Dependabot security alerts (5/8)chore: Remediate 5 of 8 Dependabot security alerts (lockfile only)Aug 6, 2026
@ernst-dev
ernst-dev added this pull request to the merge queueAug 6, 2026
Merged via the queue into main with commit f0f459eAug 6, 2026
44 of 45 checks passed
@ernst-dev
ernst-dev deleted the roko-dependabot/security-remediation-20260806 branch August 6, 2026 12:30
Sign up for freeto 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.

2 participants

@ernst-dev@SpyZzey