CLI: OAuth mcp-remote fallback via \ px -y\ has no integrity pin (supply-chain risk)
维护者通常 8 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 25/100
- Issue 类型
- 重构
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- node.js, typescript
- 领域
- authentication, cli, security
调研方向
Start from the place in the @continuedev/cli package that spawns npx -y mcp-remote on the OAuth fallback path; the payload does not name the file. Read #13429 first so you don't overlap with its version-selection work. Done means maintainers have picked one of the three options and the invocation is either pinned to a version or documented with a fail-closed warning in interactive mode.
由索引模型根据 Issue 内容生成。
描述
Related
Adjacent to #13429 (no version pin on npx -y mcp-remote after a 401). That issue focuses on reproducible version selection. This one is the supply-chain side of the same code path.
Problem
@continuedev/cli recovers interactive OAuth by spawning roughly:
npx -y mcp-remote <server-url>
-y installs without prompting. Without a version and without an integrity/resolved artifact (npm package dependency, pinned tarball, or npx [email protected] with a lock-known version), a registry compromise or unexpected latest publish is executed with the user's credentials flow. This bridge is the CLI's OAuth path for MCP when static Bearer headers are not enough (#8143).
Expected
Prefer one of:
- depend on a fixed
mcp-remoteversion inside the CLI package and invoke the local bin, or - invoke
npx mcp-remote@<pinned>where<pinned>is reviewed in releases, or - if
npx -ymust stay, document the trust boundary clearly and fail closed in CI/headless (already skipped) while warning in interactive mode
Non-goal
Changing when the 401 fallback triggers — that stays with #13429.
Happy to open a small PR once maintainers pick an option.
- 主要语言
- TypeScript
- 星标
- 36.5k
- 派生
- 5.6k
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
continuedev/continue 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 67/100
continuedev/continue#13486 ·
维护者通常 8 天内回复
-
Chat panel overflows horizontally when VS Code zoom level is increased (Cmd/Ctrl + +)可能已有人在做 @tang-ontheway 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 80/100
continuedev/continue#13483 ·
维护者通常 8 天内回复
-
Docs: show tool selection for a shared remote MCP endpoint可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
continuedev/continue#13464 · 1 条评论 ·
维护者通常 8 天内回复
-
Inline code becomes unreadable in VS Code high-contrast themes可能已有人在做 @aminesayagh 于 21 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 63/100
continuedev/continue#13424 ·
维护者通常 8 天内回复
-
create_new_file writes a JSON file on one line when the model sends its contents as a JSON value可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
continuedev/continue#13363 ·
维护者通常 8 天内回复
查看 continuedev/continue 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
oxc-project/tsrs#1010 ·
维护者通常 1 天内回复
-
area:infra area:storage bug
难度 2/5 1-3 小时 新手友好度 76/100
THU-MAIC/OpenMAIC#2311 · 1 条评论 ·
维护者通常 1 天内回复
-
docs documentation need-triage SaaS
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
enhancement from-app needs-triage
难度 2/5 1-3 小时 新手友好度 68/100
nightly-labs/openbot#10973 ·
维护者通常 1 天内回复
-
status/need-triage
难度 2/5 1-3 小时 新手友好度 76/100
google-gemini/gemini-cli#30328 · 1 条评论 ·
维护者通常 1 天内回复