[Snyk] Security upgrade cross-spawn from 7.0.3 to 7.0.5

[jimjonesbabyfreshout]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• npm-js/kalix-scripts/package.json
• npm-js/kalix-scripts/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	828

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
kalix-javascript-sdk	❌ Failed (Inspect)			Nov 9, 2024 1:11am

[codeautopilot]

PR summary

This Pull Request aims to address a security vulnerability in the cross-spawn package by upgrading it from version 7.0.3 to 7.0.5. The vulnerability, identified as a Regular Expression Denial of Service (ReDoS), has a high severity score of 828. The changes involve updating the package.json and package-lock.json files to reflect the new version of cross-spawn. This upgrade is expected to mitigate the identified security risk without introducing breaking changes.

Suggestion

Ensure that the updated version of cross-spawn is compatible with the rest of the project's dependencies and that the upgrade does not introduce any unexpected behavior in the application. Running a full suite of tests after the upgrade would be advisable to confirm stability and functionality. Additionally, consider setting up automated dependency checks to proactively manage future vulnerabilities.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 16.20%

Have feedback or need help?
Discord
Documentation
[email protected]