Skip to content
Open
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion webapp/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
"file-saver": "^2.0.5",
"flag-icon-css": "^3.5.0",
"jwt-decode": "^3.1.2",
"lodash": "^4.17.21",
"lodash": "^4.18.1",
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.

P1 yarn.lock not updated — security fixes won't install

webapp/yarn.lock still resolves lodash to 4.17.21 (line 5057 of the lock file). When any developer runs yarn install, Yarn reads the lock file and installs the pinned 4.17.21, completely bypassing the ^4.18.1 range in package.json. This means the two security patches shipped in 4.18.0 — prototype pollution via constructor/prototype traversal in _.unset/_.omit (GHSA-f23m-r3pf-42rh) and code injection via imports keys in _.template (GHSA-r5fr-rjxr-66jc / CVE-2026-4800) — will not be applied until the lock file is regenerated.

Rule Used: When updating dependencies via automated PRs (like... (source)

Learnt From
ever-co/ever-traduora#478

"normalize.css": "^8.0.1",
"normalizecss": "^3.0.0",
"rxjs": "^7.8.1",
Expand Down