Skip to content

fix(deps-dev): resolve high severity advisories in the scripts lockfile - #664

Merged
jdrouet merged 1 commit into
mainfrom
chore/scripts-audit-fix
Jul 30, 2026
Merged

fix(deps-dev): resolve high severity advisories in the scripts lockfile#664
jdrouet merged 1 commit into
mainfrom
chore/scripts-audit-fix

Conversation

@jdrouet

@jdrouet jdrouet commented Jul 30, 2026

Copy link
Copy Markdown
Owner

Runs npm audit fix in scripts/, bumping four transitive packages:

package from to
brace-expansion 2.1.0 2.1.3
nanoid 3.3.15 3.3.16
postcss 8.5.16 8.5.25
svgo 4.0.1 4.0.2

Advisories cleared

advisory package summary
GHSA-r28c-9q8g-f849 postcss Path traversal in previous source map auto-loading (sourceMappingURL) leads to arbitrary .map file disclosure
GHSA-2p49-hgcm-8545 svgo removeScripts plugin leaves some executable scripts intact
GHSA-3jxr-9vmj-r5cp brace-expansion DoS via exponential-time expansion of consecutive non-expanding {} groups

postcss and svgo arrived with the mjml 5 bump in #653, which pulled in the PostCSS/cssnano chain.

Knowingly left open

GHSA-mh99-v99m-4gvg (brace-expansion, patched in 5.0.8) is not fixed here. The chain is mjmlmjml-cliglob/minimatchbrace-expansion, and mjml-cli has no release that unpins the vulnerable range — npm audit reports it as mjml-cli <=5.2.2. It needs an upstream fix first; npm audit fix --force would only "resolve" it by downgrading mjml.

Scope and verification

Lockfile-only, and it only affects the tooling that regenerates the comparison fixtures — nothing here ships to users.

Regenerating the whole of packages/mrml-core/resources/compare/ against the new lockfile produces byte-identical output (0 files changed), so resources check stays green.

@jdrouet-datadog-monitor

Copy link
Copy Markdown

Pipelines

⚠️ Warnings

🚦 1 Pipeline job failed

commit-lint | Validate PR title   View in Datadog   GitHub Actions

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: f95cc79 | Docs | Datadog PR Page | Give us feedback!

@jdrouet jdrouet changed the title fix(scripts): resolve high severity advisories in the lockfile fix(deps-dev): resolve high severity advisories in the scripts lockfile Jul 30, 2026
Runs `npm audit fix` in scripts/, bumping four transitive packages:

  brace-expansion  2.1.0  -> 2.1.3
  nanoid           3.3.15 -> 3.3.16
  postcss          8.5.16 -> 8.5.25
  svgo             4.0.1  -> 4.0.2

This clears three high severity advisories:

  GHSA-r28c-9q8g-f849  postcss          path traversal in previous
                                        source map auto-loading
  GHSA-2p49-hgcm-8545  svgo             removeScripts leaves some
                                        executable scripts intact
  GHSA-3jxr-9vmj-r5cp  brace-expansion  DoS via exponential-time
                                        expansion of consecutive
                                        non-expanding {} groups

postcss and svgo arrived with the mjml 5 bump in #653, which pulled in
the PostCSS/cssnano chain.

GHSA-mh99-v99m-4gvg (brace-expansion, patched in 5.0.8) is deliberately
left alone: the chain is mjml -> mjml-cli -> glob/minimatch ->
brace-expansion, and mjml-cli has no release that unpins the vulnerable
range, so this one needs an upstream fix first.

Lockfile-only, and only affects the tooling that regenerates the
comparison fixtures; nothing here ships to users. Regenerating all of
packages/mrml-core/resources/compare/ against the new lockfile produces
byte-identical output, so `resources check` stays green.

Signed-off-by: Jeremie Drouet <jeremie.drouet@gmail.com>
@jdrouet
jdrouet force-pushed the chore/scripts-audit-fix branch from f95cc79 to c3d53d0 Compare July 30, 2026 08:23
@jdrouet
jdrouet merged commit 0261de9 into main Jul 30, 2026
7 checks passed
@jdrouet
jdrouet deleted the chore/scripts-audit-fix branch July 30, 2026 08:30
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