chore: Remediate 2 Dependabot security alerts (lockfile only) - #122
Merged
Conversation
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.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #122 +/- ##
=======================================
Coverage 94.57% 94.57%
=======================================
Files 11 11
Lines 516 516
Branches 142 142
=======================================
Hits 488 488
Misses 28 28 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
SpyZzey
approved these changes
Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Dependabot security-alert remediation
Alert-driven remediation of this repository's open Dependabot security alerts.
Baseline:
5c84a544eonmain.Alerts resolved (2 of 2)
brace-expansion< 1.1.162.1.4, 1.1.18postcss<= 8.5.178.5.25How this was remediated
npm audit fix --package-lock-only --ignore-scripts(no--forcewas used anywhere in this run).prepare-package-lockconvention (postinstallin@cloudscape-design/build-tools) was applied afterwards, so no@cloudscape-design/*entries are (re-)introduced into the lockfile.dev/optionalflags, 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.npm ls --package-lock-only --all: zero new unmet/invalid dependency problems versusmain.Lockfile changes (6)
brace-expansionnode_modules/@typescript-eslint/typescript-estree/node_modules/brace-expansionbrace-expansionnode_modules/brace-expansionbrace-expansionnode_modules/glob/node_modules/brace-expansionnanoidnode_modules/nanoidpostcssnode_modules/postcssyamlnode_modules/vitest/node_modules/yamlNPMPM (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?
Yes. Merging this PR is expected to close all 2 of this repository's currently-open Dependabot security alerts.
Existing Dependabot-authored PRs were deliberately not touched, reviewed, rebased, or closed by this run.