find-yarn-workspace depends on vulnerable package (CVE-2026-93687)
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 52/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- node.js, typescript
- 领域
- devtools
调研方向
Read the two callsites for find-yarn-workspace-root and inspect the dependency tree shown in the npm audit output. Identify a suitable replacement and the changes needed to remove the vulnerable dependency; verify the two callsites still behave correctly and the advisory dependency is no longer present. The issue does not name the callsite files or tests.
由索引模型根据 Issue 内容生成。
描述
Hello,
Please bear in mind that I would create a pull request myself for this issue, but my company has a policy wherein they retain ownership of works generated by me during work hours regardless of said works utility to their business operations. This would put me in conflict with the MIT license of your package. Otherwise I'd love to contribute to your project. Thanks for creating this simple yet very useful software. :)
At my work we do regular security scanning for releases, and patch-package has proved an invaluable little tool for getting our applications off the corporate "no-no" list. However, due to updates in our build pipeline (that's the best explanation I can give), patch-package needed to be moved from devDependency to dependency. Our scanner ignores devDependency packages, so this reclassification brought to light a minor security issue due one of the its sub-dependencies -see github advisory.
NPM audit output
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]
I investigated some and decided to raise the an issue here because because this package is being somewhat actively maintained. find-yarn-workspace receive its last release about six years ago, with similar dates for micromatch and braces.
Please consider replacing find-yarn-workspace-root with some other dependency. From what I saw in the codebase, there are only two real callsites.
Thanks for your consideration.
- 主要语言
- TypeScript
- 星标
- 11.2k
- 派生
- 327
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ds300/patch-package 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 82/100
ds300/patch-package#617 · 1 个 reaction ·
-
No more working under npm 12可能已有人在做 @DinoscapeProgramming 于 79 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
ds300/patch-package#615 · 1 条评论 · 5 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 62/100
ds300/patch-package#216 ·
-
难度 3/5 1-2 天 新手友好度 25/100
ds300/patch-package#611 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
ds300/patch-package#610 · 4 条评论 · 1 个 reaction ·
查看 ds300/patch-package 的全部 Issue
相似的 Issue
-
ready
难度 2/5 1-3 小时 新手友好度 63/100
wheresrhys/totf#1214 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
CodeChefVIT/ffcs#281 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
endora-commerce/endora-commerce#451 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 65/100
vetro-protocol/vetro-monorepo#1007 ·
维护者通常 1 天内回复