[Snyk] Security upgrade @angular/cli from 20.3.9 to 20.3.13

[Dargon789]

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
	Insecure Default Initialization of Resource SNYK-JS-MODELCONTEXTPROTOCOLSDK-14171914	666

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[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, addresses a critical security vulnerability within the project's frontend dependencies. By updating the @angular/cli package, it ensures that the application is protected against a known "Insecure Default Initialization of Resource" issue, thereby improving the overall security posture of the project.

Highlights

• Security Vulnerability Fix: This PR upgrades the @angular/cli dependency from version 20.3.3 to 20.3.13 to resolve a high-severity vulnerability, SNYK-JS-MODELCONTEXTPROTOCOLSDK-14171914, identified as "Insecure Default Initialization of Resource".

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 upgrades @angular/cli to fix a security vulnerability. The change itself is a minor version bump and is appropriate. However, this change highlights a critical issue with the project's dependency management. There is a major version mismatch between @angular/cli (v20) and other core Angular packages (v17 and v19). This is an unsupported configuration that can lead to application instability. My review includes a critical comment explaining the issue and recommending that all Angular packages be aligned to the same major version.

[gemini-code-assist]

While this upgrade to ^20.3.13 is necessary for security, it highlights a significant underlying issue with your Angular dependencies. The major version of @angular/cli (v20) is out of sync with other core @angular packages in this project, such as @angular/core (^17.3.1), @angular/common (^19.2.16), and @angular/compiler (^19.2.17).

According to the official Angular documentation, all @angular packages within a project should use the same major version. Mixing major versions is not supported and can lead to subtle build or runtime errors that are difficult to debug.

Recommendation:
It is strongly recommended to create a follow-up task to align all @angular/* dependencies to the same major version. A good approach would be to upgrade all packages to the latest stable major version. This will significantly improve the stability and maintainability of your application.