Skip to content

fix(deps): bump vulnerable transitive dependencies - #4

Merged
a-tokyo merged 3 commits into
mainfrom
fix/security-transitive-deps
Oct 14, 2026
Merged

a-tokyo merged 3 commits into
mainfrom
fix/security-transitive-deps

Conversation

@a-tokyo

@a-tokyo a-tokyo commented Oct 14, 2026

Copy link
Copy Markdown
Member

Summary

  • Refresh package-lock.json so the 18 open Dependabot alerts resolve to patched versions (fast-uri, brace-expansion, browserslist, nanoid, postcss, baseline-browser-mapping).
  • Also bump postcss-selector-parser to 7.1.6 (GHSA-rj75-hqrm-r3gf).
  • Override katex to ^0.18.2 (GHSA-238p-pmpm-9mq7) because micromark-extension-math pins ^0.16.0 and cannot reach the patch.

Lockfile-only for the Dependabot set; package.json only gains the katex override. No package release required — npm does not publish the lockfile.

Package From To Advisories
fast-uri 3.1.3 3.1.8 GHSA-qw65-cvwx-89v3, GHSA-jqff-g426-hqxp, GHSA-f65p-4m7j-42xc, GHSA-fph4-wmhf-6fwf, GHSA-5jgf-p345-68v8, GHSA-7p8r-x3mc-p8w7, GHSA-v2hh-gcrm-f6hx
brace-expansion 5.0.7 5.0.12 GHSA-qhr7-859c-m2p7, GHSA-6j4f-fj2g-mc7p, GHSA-rgw5-rvv9-x895, GHSA-mh99-v99m-4gvg
browserslist 4.28.6 4.29.3 GHSA-73wf-gq98-2v4g, GHSA-c83g-rgw3-j3cx
nanoid 3.3.15 3.3.20 GHSA-2v37-7h3g-55p8, GHSA-28wg-ghj8-5hjv
postcss 8.5.17 8.5.30 GHSA-fxqj-rqcc-2cmp, GHSA-r28c-9q8g-f849
baseline-browser-mapping 2.10.43 2.11.28 GHSA-w5vr-8v7q-w6rv
postcss-selector-parser 7.1.4 7.1.6 GHSA-rj75-hqrm-r3gf
katex 0.16.47 0.18.10 GHSA-238p-pmpm-9mq7

Not fixable yet

braces 3.0.3 (GHSA-vfj7-8cjw-p6xm / CVE-2026-93687) still has no published patched release (latest on npm is 3.0.3). npm audit fix --force would downgrade @next/eslint-plugin-next to 14.x, which is a breaking change. After merge, npm audit should report only this braces chain.

Test plan

  • npm run lint
  • npm test (22/22)
  • CI green on Node 22 and 24
  • Dependabot alerts close after merge

Close the open Dependabot alerts by refreshing patched lockfile versions
and overriding katex past 0.16.x, which the parent range cannot reach.

Co-authored-by: 2K AI <svc2kgai@2k.com>
@a-tokyo
a-tokyo requested a balanced review from Copilot October 14, 2026 10:33
@a-tokyo a-tokyo self-assigned this Oct 14, 2026
@a-tokyo
a-tokyo requested a balanced review from Copilot and removed request for Copilot October 14, 2026 10:34
@a-tokyo
a-tokyo merged commit 49199e3 into main Oct 14, 2026
3 checks passed

Copilot AI 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.

🟡 Changes recommended

Package version metadata conflicts with both the PR description and the lockfile root entry.

1 open finding
What changed in this PR

Updates vulnerable transitive npm dependencies and adds a KaTeX security override.

Changes:

  • Refreshes patched transitive dependency versions.
  • Forces KaTeX onto a patched release.
  • Updates package version metadata, currently inconsistently.
File Description
package.json Adds the KaTeX override and changes package metadata.
package-lock.json Locks patched transitive dependencies.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread package.json
"name": "@zoldytech/javascript",
"type": "module",
"version": "0.1.5",
"version": "0.1.6",
@a-tokyo
a-tokyo deleted the fix/security-transitive-deps branch October 14, 2026 10:38
a-tokyo added a commit that referenced this pull request Oct 19, 2026
* fix(deps): bump vulnerable transitive dependencies

Close the open Dependabot alerts by refreshing patched lockfile versions
and overriding katex past 0.16.x, which the parent range cannot reach.

* Bump version from 0.1.5 to 0.1.6

* Bump version to 0.1.6 in package-lock.json

---------
a-tokyo added a commit that referenced this pull request Oct 19, 2026
release.yml only ran on `v*` tag pushes, so merging #4 (0.1.6) released
nothing: no one pushed the tag. Now a push to main that changes
package.json publishes when `v<version>` is not yet tagged, and the
release job creates the tag. Manual tag pushes still work. Publish and
release skip work already done, so re-runs are safe.
a-tokyo added a commit that referenced this pull request Oct 19, 2026
#5)

release.yml only ran on `v*` tag pushes, so merging #4 (0.1.6) released
nothing: no one pushed the tag. Now a push to main that changes
package.json publishes when `v<version>` is not yet tagged, and the
release job creates the tag. Manual tag pushes still work. Publish and
release skip work already done, so re-runs are safe.
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.

2 participants