Skip to content

[Snyk] Security upgrade lodash from 4.17.21 to 4.17.23 #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Dustin4444 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade lodash from 4.17.21 to 4.17.23 #11

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
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@
"js-green-licenses": "^4.0.0",
"klaw-sync": "^6.0.0",
"license-check-and-add": "^4.0.5",
"lodash": "^4.17.21",
"lodash": "^4.17.23",
Copy link

@gemini-code-assist gemini-code-assist bot Jan 22, 2026

Choose a reason for hiding this comment

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

security-critical critical

While the lodash version is correctly updated in package.json, the package-lock.json file has not been updated. This means that any build or deployment process that relies on the lock file (e.g., using npm ci) will still install the vulnerable version of lodash. To fix this and ensure the security patch is applied, you need to run npm install and commit the updated package-lock.json.

"mock-fs": "^5.5.0",
"prettier": "^3.5.3"
},
Expand Down