Skip to content

fix(deps): pin js-yaml to >=4.2.1 via npm overrides - #324

Open
birme wants to merge 1 commit into
mainfrom
security/279-js-yaml-update
Open

birme wants to merge 1 commit into
mainfrom
security/279-js-yaml-update

Conversation

@birme

@birme birme commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Summary

  • npm ls js-yaml showed js-yaml@3.15.2 pulled in transitively via ts-jest@jest/transformbabel-plugin-istanbul@istanbuljs/load-nyc-config
  • npm audit fix did not address this (npm audit does not flag it as a CVE in the current advisory database, but the version is below the required >=4.2.1 threshold)
  • Added "overrides": { "js-yaml": ">=4.2.1" } to package.json and ran npm install to regenerate the lockfile
  • All resolved versions of js-yaml are now 5.4.2 (satisfies >=4.2.1)

Test plan

  • Run npm ls js-yaml and confirm no version <4.2.1 appears
  • Run npm test — 243 tests pass
  • Run npm run typecheck — no errors

Closes #279

A transitive dependency via ts-jest -> babel-plugin-istanbul ->
@istanbuljs/load-nyc-config required js-yaml@3.x. Add an npm
overrides entry to ensure all resolved versions of js-yaml are
>=4.2.1, eliminating the vulnerable 3.x pin.

All 243 tests pass with the override in place.

Closes #279
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.

Security: js-yaml prototype pollution and quadratic-complexity DoS — update to >=4.2.1

2 participants