[Snyk] Security upgrade glob from 11.0.3 to 12.0.0

[hbmartin]

User description

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-ISAACSBRACEEXPANSION-15208653	853

---

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:

🦉 Allocation of Resources Without Limits or Throttling

---

CodeAnt-AI Description

Upgrade glob to 12.0.0 to fix critical brace-expansion vulnerability

What Changed

• Updated direct dependency "glob" from 11.0.3 to 12.0.0 in package.json and package-lock.json
• Updated transitive packages (brace-expansion, minimatch) in the lockfile to secure versions
• Removes the high-severity SNYK-JS-ISAACSBRACEEXPANSION vulnerability from the dependency tree

Impact

✅ Fixes critical brace-expansion vulnerability
✅ Fewer dependency vulnerabilities reported during audits
✅ Safer installs from updated lockfile

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-b47521e9c94e67d57820f7287eecdcf0

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @hbmartin, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated security fix initiated by Snyk. Its primary purpose is to enhance the project's security posture by upgrading the glob package to its latest major version, thereby mitigating a critical vulnerability. This ensures the application is protected against potential resource exhaustion issues and maintains up-to-date dependencies.

Highlights

• Security Upgrade: Upgraded the glob package from version 11.0.3 to 12.0.0 to address a critical security vulnerability (SNYK-JS-ISAACSBRACEEXPANSION-15208653) related to 'Allocation of Resources Without Limits or Throttling'.
• Dependency Updates: The upgrade of glob also led to the update of its transitive dependencies: minimatch from 10.0.3 to 10.1.2 and @isaacs/brace-expansion from 5.0.0 to 5.0.1.
• License Changes: The licenses for both glob and minimatch have changed from ISC to BlueOak-1.0.0 as part of their respective updates.
• Configuration Files: The package.json and package-lock.json files were updated to reflect the new dependency versions and their associated metadata.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• package-lock.json
  • Updated glob version from 11.0.3 to 12.0.0.
  • Updated @isaacs/brace-expansion version from 5.0.0 to 5.0.1.
  • Updated minimatch version from 10.0.3 to 10.1.2.
  • Changed glob license from ISC to BlueOak-1.0.0.
  • Changed minimatch license from ISC to BlueOak-1.0.0.
• package.json
  • Updated glob dependency from ^11.0.3 to ^12.0.0.

Activity

• This pull request was automatically generated by Snyk to address identified vulnerabilities in the project's dependencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	glob@​11.0.3 ⏵ 12.0.0		+16	+1	+39

View full report

[codeant-ai]

Sequence Diagram

This PR automatically updates the direct dependency "glob" from 11.0.3 to 12.0.0 (and related transitive packages) to remove a high-severity brace-expansion vulnerability. The diagram shows the core automated flow from vulnerability detection through the repository update and dependency resolution that fixes the issue.

sequenceDiagram
    participant Snyk
    participant Repo
    participant PackageManager

    Snyk->>Repo: Detects vulnerability in glob (brace-expansion)
    Snyk->>Repo: Open PR updating package.json & package-lock (glob 11.x -> 12.0.0)
    Repo->>PackageManager: Install/lock updated deps (npm install / lockfile)
    PackageManager-->>Repo: Update transitive packages (brace-expansion, minimatch, etc.)
    PackageManager-->>Snyk: Vulnerability no longer present (issue resolved)

Loading

---

Generated by CodeAnt AI

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[gemini-code-assist]

Code Review

This pull request upgrades the glob package from version 11.0.3 to 12.0.0 to address a security vulnerability. While this is a valid approach, I've noticed the project includes a custom glob implementation in src/tools/glob-tool.ts. This suggests the glob package might be an unused dependency. If so, removing it would be a better solution, as it would resolve the vulnerability and reduce the project's dependency surface. If the package is in use, please note this is a major version upgrade, and any potential breaking changes should be carefully tested.

[gemini-code-assist]

This upgrade to a new major version of glob is intended to fix a security vulnerability. However, based on the custom implementation in src/tools/glob-tool.ts, this glob dependency may be unused.

Consider verifying if this package is actively used. If it's not, removing it would be preferable to upgrading it. This would eliminate the dependency and the associated vulnerability.

If the package is necessary, be aware that this is a major version change and could introduce breaking changes that require thorough testing.