Skip to content

[Snyk] Fix for 1 vulnerabilities#3

Open
noom-snyk-bot wants to merge 1 commit intomainfrom
snyk-fix-ed3ed949fc6213d5eff172901e051c43
Open

[Snyk] Fix for 1 vulnerabilities#3
noom-snyk-bot wants to merge 1 commit intomainfrom
snyk-fix-ed3ed949fc6213d5eff172901e051c43

Conversation

@noom-snyk-bot
Copy link

@noom-snyk-bot noom-snyk-bot commented Feb 19, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/utils/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-15309438
  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)


Note

Medium Risk
Dependency-only change, but major-version bumps to glob/minimatch could introduce breaking behavior in config file globbing/exclusion matching used by packages/utils/src/config.ts.

Overview
Upgrades packages/utils dependencies to glob@^12 and minimatch@^10 (from glob@^8/minimatch@^5) to remediate the Snyk-reported ReDoS vulnerability.

No code changes accompany the bumps, but these are major-version upgrades that may affect how entry-point discovery and exclude patterns are resolved at runtime.

Written by Cursor Bugbot for commit 4d18ccf. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

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

"glob": "^8.0.3",
"minimatch": "^5.1.0",
"glob": "^12.0.0",
"minimatch": "^10.2.1",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Major version bump breaks minimatch default import

High Severity

Upgrading minimatch from ^5.1.0 to ^10.2.1 is a breaking change. The code in packages/utils/src/config.ts uses import minimatch from "minimatch" (a default import), but minimatch v9+ removed the default export and only provides named exports. At runtime, minimatch will be undefined or a module object rather than a callable function, causing the exclude function to crash when it calls minimatch(relativePath, pattern). The import needs to change to import { minimatch } from "minimatch".

Fix in Cursor Fix in Web

"commander": "^9.3.0",
"glob": "^8.0.3",
"minimatch": "^5.1.0",
"glob": "^12.0.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Major version bump breaks glob.sync API call

High Severity

Upgrading glob from ^8.0.3 to ^12.0.0 is a breaking change. The code in packages/utils/src/config.ts calls glob.sync(pattern, { cwd: baseDir }), but in glob v10+ the .sync property on the glob function was removed. This will throw TypeError: glob.sync is not a function at runtime. The code needs to switch to importing and calling globSync directly from glob.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants