Repository navigation
chore(deps): update npm dependencies - #138
Merged
Merged
Conversation
- Remove unused esbuild-jest from dependencies: jest.config uses ts-jest exclusively, and esbuild-jest dragged a jest-26-era subtree with known advisories into the published install tree - Add @graphql-tools/utils override ^12.0.1 to fix GHSA-7mx3-vvmw-hjmv (prototype pollution in mergeDeep, via mockttp); fixed version is not in mockttp's declared range, follows existing overrides pattern - handlebars 4.7.9 -> 4.7.10 (critical; fixes GHSA-xw65-4hp5-5hc7, GHSA-8r5x-fm3f-whwj, GHSA-p8wg-vrv2-v86f; in-range for ts-jest) - @types/node 26.6.4 -> 26.6.5 Prod audit: 0 vulnerabilities. Remaining audit findings are dev-only and have no fixed upstream release without downgrading (braces <=3.0.3 is the latest release; jest-25-era advisories resolve only via downgrades).
xavpaice
approved these changes
Oct 13, 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.
Summary
esbuild-jestfromdependencies:jest.config.tsusests-jestexclusively and nothing references esbuild-jest, yet it dragged a jest-26-era subtree (babel-jest 26, jest-haste-map 26, sane, anymatch 2, js-yaml 3 chain) with known advisories into the published install tree@graphql-tools/utilsoverride^12.0.1to fix GHSA-7mx3-vvmw-hjmv (prototype pollution inmergeDeep, reached via mockttp). The fixed version is outside mockttp's declared^11.0.0range, but@graphql-tools/schema/mergealready require^12.0.1, so this follows the repo's existing overrides pattern (basic-ftp, braces, micromatch, qs)^4.7.9)@types/node26.6.4 -> 26.6.5 (in-range refresh)pako2.x -> 3.x stays in chore(deps): bump pako and @types/pako #137; no other production package had updates availableAudit
npm audit --omit=dev: 0 vulnerabilities (was 14: 5 moderate, 9 high)npm audit: 0 critical / 0 high (was 1 critical / 11 high); remaining 20 findings are dev-only with no fixed upstream release without downgrading (e.g.braces<=3.0.3covers the latest published release; the jest-25-era js-yaml chain only "resolves" by downgrading jest)Verification
make test(96/96 tests passed, 8/8 suites)make ci-check(no uncommitted changes)npm audit/npm audit --omit=devgit diff --check@pact-foundation/pactunchanged at 17.1.4