Skip to content

[Snyk] Fix for 1 vulnerabilities#4

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

[Snyk] Fix for 1 vulnerabilities#4
noom-snyk-bot wants to merge 1 commit intomainfrom
snyk-fix-9e52761d8bb6c7a7a02a3daa82b74de3

Conversation

@noom-snyk-bot
Copy link

@noom-snyk-bot noom-snyk-bot commented Feb 27, 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 Inefficient Algorithmic Complexity
SNYK-JS-MINIMATCH-15353389
  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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


Note

Medium Risk
Upgrades glob to a new major version and minimatch to a patched release, which could subtly change file-matching behavior used by the utils config parsing logic.

Overview
Updates @noom/symbolism-utils dependencies by bumping glob from ^8.0.3 to ^12.0.0 and minimatch from ^5.1.0 to ^5.1.8 to remediate a reported vulnerability.

No code changes accompany the upgrade, but glob is a major-version jump and may affect how packages/utils/src/config.ts expands entry point patterns.

Written by Cursor Bugbot for commit bad238b. 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 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

"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 glob version bump likely breaks existing sync API usage

High Severity

Upgrading glob from ^8.0.3 to ^12.0.0 spans four major versions with significant breaking API changes. The existing code in config.ts uses import { glob } from "glob" and then calls glob.sync(pattern, { cwd }), which was the native v8 API but is only a backward-compatibility alias in v9.3+. Additionally, glob v11+ requires Node.js 20+, while the project targets Node 18 (per @types/node@^18). The yarn.lock was also not updated, so dependency resolution is unverified. Snyk's own metadata flags this as a breaking change.

Additional Locations (1)

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