[Snyk] Security upgrade lodash-es from 4.17.21 to 4.17.23

[iamdrewfortini]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• frontend/package.json
• frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-LODASHES-15053836	117

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

[gemini-code-assist]

Summary of Changes

Hello @iamdrewfortini, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, focuses on enhancing the security posture of the frontend dependencies. It primarily upgrades the lodash-es package to mitigate a known Prototype Pollution vulnerability, ensuring the application uses a more secure version of this widely used utility library. The update also includes routine adjustments to the dependency lock file, reflecting modern package manager conventions.

Highlights

• Security Upgrade: The lodash-es dependency has been upgraded from version 4.17.21 to 4.17.23 to address a critical Prototype Pollution vulnerability (SNYK-JS-LODASHES-15053836).
• Dependency Manifest Updates: The frontend/package.json and frontend/package-lock.json files have been updated to reflect the new version of lodash-es and to standardize dependency metadata, including the removal of redundant "dev": true flags and the introduction of "devOptional": true for certain development-related packages within package-lock.json.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly upgrades lodash-es to version 4.17.23, addressing a security vulnerability. The change in package.json is correct. However, the package-lock.json file contains extensive changes beyond the dependency upgrade, most notably removing the dev flag from many development dependencies. I've added a specific comment regarding this potential issue, which could affect your production build size.

[gemini-code-assist]

This change removes the dev: true flag from chokidar, and this pattern is repeated for many other development dependencies throughout the file. This effectively promotes them to production dependencies, which could unintentionally increase the size of your production builds. This might be a side effect of the tool that generated this PR using a different npm version or configuration. Please verify if this is the intended behavior. If not, you might need to regenerate the package-lock.json file using your project's standard npm install command to ensure development dependencies are correctly marked.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​lodash-es@​4.17.21 ⏵ 4.17.23		+2	+1

View full report