[Snyk] Fix for 2 vulnerabilities

[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
	Cross-site Scripting (XSS) SNYK-JS-ANGULARCOMPILER-14157154	706
	Insertion of Sensitive Information Into Sent Data SNYK-JS-ANGULARCOMMON-14135651	671

---

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:

🦉 Cross-site Scripting (XSS)

[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 security posture of the project by resolving two high-severity vulnerabilities found in the frontend's npm dependencies. It achieves this by upgrading specific Angular packages to their patched versions, thereby mitigating potential risks like Cross-site Scripting and sensitive data exposure.

Highlights

• Security Vulnerability Fix: This PR addresses two high-severity vulnerabilities: Cross-site Scripting (XSS) and Insertion of Sensitive Information Into Sent Data, identified by Snyk.
• Dependency Upgrades: The fix involves upgrading @angular/common from ^17.3.1 to ^19.2.16 and @angular/compiler from ^17.3.1 to ^19.2.17.

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 failed. 4 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (4)
⛔	Open Source Security	0	1	3	0	4 issues

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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to resolve two high-severity vulnerabilities by upgrading @angular/common and @angular/compiler dependencies. However, the upgrade introduces a significant issue: it moves these two packages to major version 19, while other core Angular packages like @angular/core remain on version 17. This version mismatch will almost certainly break the application build. To correctly apply this security fix, all @angular/* packages must be upgraded to the same major version. I have left a critical comment detailing the necessary changes.

[gemini-code-assist]

This automated dependency upgrade introduces a critical version mismatch between Angular packages. Upgrading @angular/common and @angular/compiler to major version 19 while other essential Angular packages like @angular/core (line 68), @angular/animations (line 64), @angular/forms (line 69), and @angular-devkit/build-angular (line 63) remain on version 17 will cause build failures or runtime errors.¹

To resolve this, you must update all @angular/* packages in this file to the same major version. For example, if you are targeting version 19, all related packages should be updated to a compatible version like ~19.2.17.

Rules References

Footnotes

1. All Angular packages within a project should be on the same major version. Angular's packages are versioned and released together, and mixing major versions can lead to API incompatibilities, dependency resolution conflicts, and subtle runtime bugs that are difficult to debug. ↩