馃敀 Patch audited transitive dependencies - #347
Merged
Merged
Conversation
Robdel12
force-pushed
the
rd/security-js-yaml
branch
from
August 29, 2026 23:38
96e9e74 to
788ec23
Compare
Resolve the vulnerable js-yaml, socket.io-parser, and tmp versions through the workspace override configuration so pnpm installs the fixed packages consistently across runtime and Ember tooling.
Robdel12
force-pushed
the
rd/security-js-yaml
branch
from
August 29, 2026 23:43
788ec23 to
37b033d
Compare
Robdel12
enabled auto-merge (squash)
August 29, 2026 23:44
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
1 participant
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.
Why
The current dependency graph contains vulnerable transitive versions of
js-yaml,socket.io-parser, andtmp. Thejs-yamlissue affects the runtimecosmiconfigpath used to load project configuration, while the other findings are in Ember test tooling.Approach
Use the repository鈥檚 existing
pnpm-workspace.yamloverride configuration to resolve the affected packages to patched versions and regeneratepnpm-lock.yaml. This keeps the fix scoped to dependency resolution, leaves workflows unchanged, and does not introduce a pnpm 12 migration while pnpm 12 remains a release candidate.Evidence
The full workspace audit reports zero vulnerabilities after the update, including the production dependency graph. The frozen lockfile install, build, type definitions, lint, and full unit suite all pass.