⬆️ chore(deps): override glob dependency version to ^11.1.0

[chriskyfung]

Introduces an 'overrides' entry in package.json to force the 'glob' package to version ^11.1.0. This ensures that all transitive dependencies use the specified version, mitigating potential security vulnerabilities or compatibility issues with older versions of 'glob'.

Fixes Dependabot alert #8
glob CLI: Command injection via -c/--cmd executes matches with shell:true

[gemini-code-assist]

Summary of Changes

Hello @chriskyfung, 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 implements a crucial security update by overriding the 'glob' package version to '^11.1.0' within the project's 'package.json'. This change directly resolves a reported Dependabot alert concerning a command injection vulnerability in older 'glob' versions, ensuring that all parts of the application utilize the secure, updated dependency. The update also streamlines the dependency tree by removing several outdated and deprecated packages.

Highlights

• Security Fix: Addresses Dependabot alert ⬆️ chore(deps): Update dependencies and enhance Corel example #8 by upgrading the 'glob' package to version '^11.1.0' to mitigate a command injection vulnerability.
• Dependency Override: Introduces an 'overrides' entry in 'package.json' to enforce the specified 'glob' version across all transitive dependencies, ensuring consistent and secure usage.
• Dependency Updates: Updates 'glob' and several of its sub-dependencies (e.g., 'foreground-child', 'jackspeak', 'minimatch', 'path-scurry') to their latest compatible versions.
• Dependency Cleanup: Removes several deprecated or no longer needed dependencies from 'package-lock.json', such as '@pkgjs/parseargs', 'fs.realpath', 'inflight', and nested 'glob' instances.

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. ↩

[gemini-code-assist]

Code Review

This pull request correctly addresses a security vulnerability in the glob package by using an npm override. The change in package.json to force glob to version ^11.1.0 is the appropriate solution for mitigating the command injection vulnerability found in older transitive versions. The resulting updates in package-lock.json are consistent with this override and have the positive side effect of removing some deprecated or outdated packages. The change is well-explained and correctly implemented.