[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
	Directory Traversal SNYK-JS-TAR-15032660	693
	Prototype Pollution SNYK-JS-LODASH-15053838	631

---

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
🦉 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 posture by resolving two identified vulnerabilities. It achieves this by updating specific npm dependencies in the frontend directory, ensuring the application benefits from the latest security patches without introducing breaking changes.

Highlights

• Dependency Upgrades: Updated @angular/cli from ^20.3.3 to ^20.3.15 and @types/cypress from ^1.1.3 to ^1.1.6 in frontend/package.json.
• Vulnerability Fixes: Addressed two security vulnerabilities: Directory Traversal (SNYK-JS-TAR-15032660) and Prototype Pollution (SNYK-JS-LODASH-15053838), as identified by Snyk.

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, automatically generated by Snyk, updates two dependencies to fix security vulnerabilities: @angular/cli and @types/cypress. The updates themselves are correct for patching the specified vulnerabilities. However, the review identified a significant issue with your project's Angular dependency versions. The version of @angular/cli is inconsistent with other @angular/* packages, which are on different major versions (17, 19, and 20). This can cause significant build and runtime issues and should be addressed to ensure project stability. A specific comment has been added to highlight this problem.

[gemini-code-assist]

While this upgrade to @angular/cli is necessary to patch a security vulnerability, it highlights a significant version mismatch across your Angular dependencies. The Angular CLI version should align with the version of your Angular framework packages (e.g., @angular/core, @angular/common).

Currently, your project uses a mix of Angular versions 17, 19, and 20 (for the CLI). This is highly likely to cause build failures, runtime errors, and other unpredictable behavior.

It is strongly recommended to align all @angular/* packages to the same major version to ensure compatibility and stability. For example, if your project is based on Angular 17, the @angular/cli package should also be on a corresponding v17 release.