[Snyk] Fix for 3 vulnerabilities

[Dargon789]

Snyk has created this PR to fix 3 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
	Race Condition SNYK-JS-MODELCONTEXTPROTOCOLSDK-15208843	641
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235959	498
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235969	498

---

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:

🦉 Race Condition
🦉 Server-side Request Forgery (SSRF)

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, 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, aims to enhance the project's security posture by upgrading specific npm dependencies. The updates target known vulnerabilities, ensuring the application benefits from the latest security patches and improvements provided by the updated packages.

Highlights

• Vulnerability Fixes: This pull request addresses and fixes 3 identified vulnerabilities in the project's npm dependencies, including a high-severity Race Condition and two low-severity Server-side Request Forgery (SSRF) issues.
• Dependency Updates: The @angular-devkit/build-angular dependency has been updated from version ^17.3.16 to ^20.3.15, and @angular/cli has been updated from ^20.3.3 to ^20.3.16.

Changelog

• frontend/package.json
  • Updated @angular-devkit/build-angular dependency to ^20.3.15.
  • Updated @angular/cli dependency to ^20.3.16.

Activity

• This pull request was automatically created by Snyk to propose fixes for identified vulnerabilities.

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. ↩

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Code Review

This pull request from Snyk updates two Angular dependencies to fix security vulnerabilities. However, one of these updates, for @angular-devkit/build-angular, is a major version jump from v17 to v20. This creates a significant version incompatibility with other core Angular packages in the project, which are on versions 17 and 19. This mixed-version state for Angular packages is unsupported and will very likely break the build. I've added a critical review comment recommending a full, coordinated upgrade of all Angular dependencies to a consistent major version instead of merging this partial update.

[gemini-code-assist]

This PR upgrades @angular-devkit/build-angular to major version 20, while other @angular/* packages like @angular/core remain on version 17, and some on v19. Mixing major versions of Angular packages is not supported and will almost certainly break your build. All @angular/* packages in package.json should be on the same major version.

While this automated change fixes security vulnerabilities, it's unsafe to merge as is. It should be part of a larger, coordinated upgrade of all Angular dependencies to a consistent major version.