[Snyk] Security upgrade rimraf from 2.7.1 to 6.1.1

[MHxGH-ServiceAccount]

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

Snyk changed the following file(s):

• packages/navy/package.json
• packages/navy/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-15309438	170

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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)

---

Note

Medium Risk
Major-version dependency upgrades (rimraf, glob, minimatch) can change filesystem deletion and globbing behavior, potentially affecting CLI scripts at runtime.

Overview
Upgrades rimraf in packages/navy from 2.7.1 to 6.1.1 to address a reported ReDoS vulnerability in the dependency chain.

This updates the lockfile to the newer rimraf dependency graph, including major bumps to glob (7→12) and minimatch (3→10) plus new transitive packages (e.g., path-scurry, foreground-child, jackspeak).

^{Written by Cursor Bugbot for commit e0c51b7. This will update automatically on new commits. Configure here.}

[MHxGH-ServiceAccount]

This is a major version upgrade from v2 to v6, introducing several significant breaking changes that require code and environment updates.

Key Breaking Changes:

• Node.js Requirement: Version 6.x requires Node.js v20 or higher.
• ESM Imports: v5.x removed the default export. You must now use named imports. For example, const rimraf = require('rimraf') must be changed to const { rimraf } = require('rimraf') or import { rimraf } from 'rimraf'.
• Promise-based API: v4.x changed the asynchronous API to return Promises instead of using callbacks. Code using callbacks with rimraf will need to be updated to use async/await or .then().
• Globbing Disabled by Default: Starting with v4.x, glob patterns are no longer matched by default. To remove files using glob patterns, you must set the glob option to true.

Recommendation:
Due to the multiple breaking changes, this upgrade requires careful code review and refactoring. Pay close attention to asynchronous calls, import statements, and any usage of glob patterns. Ensure your Node.js environment meets the new version requirement.

Source: Package documentation

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[MHxGH-ServiceAccount]

✅ 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
✅	Licenses	0	0	0	0	0 issues

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Breaking rimraf v6 upgrade without updating source code

High Severity

Upgrading rimraf from v2 to v6 is a major breaking change that removes the default export. In v2, require('rimraf') returned a callable function, but in v6 it returns an object with named exports (rimraf, rimrafSync, etc.). Since rimraf is a production dependency and no source code was updated alongside this version bump, any existing require('rimraf') usage will silently get an object instead of a function, causing runtime errors. Additionally, v6 requires Node.js v20+, which may not match the project's supported Node versions.