[Snyk] Upgrade @grpc/grpc-js from 1.11.1 to 1.12.5

[Abuchtela]

Snyk has created this PR to upgrade @grpc/grpc-js from 1.11.1 to 1.12.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 8 versions ahead of your current version.

• The recommended version was released a month ago.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• 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 upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gitpod-dashboard	❌ Failed (Inspect)			Jan 17, 2025 11:42pm

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@gitpod/[email protected]	None	0	0 B
npm/@gitpod/[email protected]	None	0	0 B
npm/@gitpod/[email protected]	None	0	0 B
npm/@gitpod/[email protected]	None	0	0 B
npm/@gitpod/[email protected]	None	0	0 B
npm/@gitpod/[email protected]	None	0	0 B
npm/@gitpod/[email protected]	None	0	0 B
npm/@types/[email protected]	None	0	82.2 kB	types
npm/@types/[email protected]	None	0	8.98 kB	types
npm/@types/[email protected]	None	0	12.1 kB	types
npm/[email protected]	None	0	14 kB	jdalton
npm/[email protected]	None	0	8.7 kB	sindresorhus
npm/[email protected]	None	0	295 kB	rbuckton
npm/[email protected]	None	0	116 kB	ctavan
npm/[email protected]	network	0	122 kB	lpinca

🚮 Removed packages: npm/@bufbuild/[email protected], npm/@craco/[email protected], npm/@stripe/[email protected], npm/@stripe/[email protected], npm/@tailwindcss/[email protected], npm/@tailwindcss/[email protected], npm/@tanstack/[email protected], npm/@tanstack/[email protected], npm/@tanstack/[email protected], npm/@tanstack/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@typescript-eslint/[email protected], npm/@typescript-eslint/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	CI
Critical CVE	npm/[email protected]	CVE: GHSA-xvch-5gv4-984h Prototype Pollution in minimist (CRITICAL) Affected versions: < 0.2.4 Patched version: 0.2.4	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.