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

[Dargon789]

Snyk has created this PR to fix 2 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
	Command Injection SNYK-JS-GLOB-14040952	706
	Directory Traversal SNYK-JS-TAR-15127355	596

---

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:

🦉 Command Injection
🦉 Directory Traversal

[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 by updating a critical frontend dependency. The primary goal is to remediate known vulnerabilities within the @angular/cli package, ensuring the application remains protected against potential exploits.

Highlights

• Dependency Upgrade: The @angular/cli package has been upgraded from version ^20.3.3 to ^20.3.15 in frontend/package.json.
• Vulnerability Fixes: This upgrade addresses two security vulnerabilities: a high-severity Command Injection (SNYK-JS-GLOB-14040952) and a medium-severity Directory Traversal (SNYK-JS-TAR-15127355).

Changelog

• frontend/package-lock.json
  • This file was updated to reflect the new dependency version and its transitive dependencies, ensuring package consistency.
• frontend/package.json
  • Updated the @angular/cli dependency version from ^20.3.3 to ^20.3.15.

Activity

• This pull request was automatically created by Snyk to address identified security 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 upgrades @angular/cli to fix security vulnerabilities. While the intent is good, the change exposes a critical issue with your project's Angular dependencies. There are multiple, mismatched major versions of @angular/* packages in your package.json. This is an unsupported configuration that can lead to significant problems. My review contains a critical comment on the package.json change, explaining the issue and recommending a comprehensive fix to align all Angular package versions.

[gemini-code-assist]

This change highlights a critical dependency issue. Your project uses mismatched major versions for Angular packages, which is unsupported and can lead to build or runtime errors. For instance, @angular/core is at ^17.3.1, while this PR updates @angular/cli to ^20.3.15. Other packages like @angular/common (^19.2.16) are also out of sync.

According to Angular's versioning guidelines, all @angular/* packages in a project should share the same major version. For @angular/core@^17.3.1, the corresponding @angular/cli version should be ~17.3.x.

Recommendation:
Instead of merging this PR, I strongly advise creating a new one to align all your @angular/* dependencies to a single, consistent version (e.g., the latest v17 patch release). The ng update command can be very helpful for this process. This will create a stable, supported dependency tree and likely resolve the security vulnerability in a correct way.