Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

fix: bump brace-expansion/js-yaml overrides to clear high-severity audit #3133

Closed
HarshMN2345 wants to merge 1 commit into from
Closed

fix: bump brace-expansion/js-yaml overrides to clear high-severity audit #3133

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions bun.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

3 changes: 2 additions & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,8 @@
"overrides": {
"vite": "npm:rolldown-vite@latest",
"minimatch": "10.2.3",
"brace-expansion": ">=5.0.5",
"brace-expansion": ">=5.0.7",

@greptile-apps greptile-apps Bot Jul 21, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Open-Ended Security Override

The brace-expansion override is a lower-bound range, so a future lockfile refresh can satisfy it with a new major version even when the transitive consumer only requested the 5.x line. Since this override is meant to pin the patched dependency for CI, a tighter range such as the patched 5.x line would avoid pulling an unrelated major upgrade into an audit-only change.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: package.json
Line: 107

Comment:
**Open-Ended Security Override**

The `brace-expansion` override is a lower-bound range, so a future lockfile refresh can satisfy it with a new major version even when the transitive consumer only requested the 5.x line. Since this override is meant to pin the patched dependency for CI, a tighter range such as the patched 5.x line would avoid pulling an unrelated major upgrade into an audit-only change.

How can I resolve this? If you propose a fix, please make it concise.

Fix in Claude Code Fix in Codex

"js-yaml": "^4.3.0",
"immutable": "^5.1.5",
"flatted": "^3.4.2",
"devalue": "^5.8.1",
Expand Down