Conversation
…lnate/once (CVE-2026-3449) Instead of pinning @tootallnate/once to a vulnerable v2.0.0, resolve http-proxy-agent to v7 which dropped the @tootallnate/once dependency entirely. This forces all consumers (codecov/teeny-request, jest/jsdom, lerna/make-fetch-happen) to use http-proxy-agent@7.0.0 which only depends on agent-base@7 and debug@4. This completely removes @tootallnate/once from the dependency tree, fully resolving CVE-2026-3449 without the ESM/CJS compatibility issues of @tootallnate/once@3.0.1.
otaviomacedo
approved these changes
Mar 9, 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
Resolves CVE-2026-3449 (Incorrect Control Flow Scoping) in @tootallnate/once by eliminating the vulnerable dependency entirely.
Changes
"http-proxy-agent": "^7.0.0"Strategy
@tootallnate/once< 3.0.1 is vulnerable, but v3.0.1 is ESM-only (breaks CJS consumers with ERR_REQUIRE_ESM). Instead of pinning the vulnerable package, we resolved its parenthttp-proxy-agentto v7 which dropped the dependency entirely.Traced via
yarn why:codecov@3→teeny-request→http-proxy-agent@4→@tootallnate/once@1jest@27→jsdom→http-proxy-agent@4→@tootallnate/once@1lerna@5→make-fetch-happen→http-proxy-agent@5→@tootallnate/once@2All now resolve to http-proxy-agent@7.0.0 (no @tootallnate/once dependency).
Verification
yarn why @tootallnate/once→ "We couldn't find a match!" ✅grep @tootallnate/once yarn.lock→ 0 occurrences ✅lerna run build✅lerna run test✅yarn extract-dependency-licenses✅