chore(deps): bump `minimatch` to `11.0.1` in `package-lock.json` (1 advisory)

已关闭 适合新手
#2,899 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1-3 小时
新手友好度
76/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
devops, security

调研方向

先阅读 AGENTS.md 中有关依赖项放置位置的指导,并检查 package.json 和 package-lock.json。添加一条 overrides 配置,将 minimatch 固定为 11.0.1,然后检查锁文件是否反映了修复后的版本,以及该安全公告是否已不再适用。

由索引模型根据 Issue 内容生成。

描述

chore dependabot v2

Filed automatically from 1 open Dependabot alert (#2233). The fix is written by hand against v2/main.

Package minimatch
Manifest package-lock.json
Vulnerable on v2/main 10.2.6
Fixed in 11.0.1
Scope development
Highest severity medium

Advisories

GHSA CVE Severity Vulnerable range Summary
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium >= 7.0.0, < 11.0.1 minimatch has potential denial of service via globparts amplification

Fix

Add an overrides entry pinning minimatch to 11.0.1, for the copies below, which no declared range reaches. Not npm audit fix, which "resolves" an advisory with no upward escape by silently downgrading.

Vulnerable copy Version
node_modules/minimatch 10.2.6

[!NOTE]
Priority is a standing rubric override. A routine bump scores Medium; a security bump is filed High so it does not sit.

Where each number comes from. The GHSA, CVE, severity, vulnerable range and summary are the advisory's own, reported by Dependabot. What was verified independently against v2/main is the installed versions, their paths, and whether each advisory's range still matches — GitHub computes alerts from the default branch, so an alert is filed here only after that re-check.

主要语言
TypeScript
星标
11.2k
派生
1.6k
平均合并
3 小时 36 分钟
30 天内合并 PR
154

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

modelcontextprotocol/inspector 的其他 Issue

查看 modelcontextprotocol/inspector 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。