CLI: OAuth mcp-remote fallback via \ px -y\ has no integrity pin (supply-chain risk)

Aperta
#13,453 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 8 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
25/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
node.js, typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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:

  1. depend on a fixed mcp-remote version inside the CLI package and invoke the local bin, or
  2. invoke npx mcp-remote@<pinned> where <pinned> is reviewed in releases, or
  3. if npx -y must 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.

Lingua principale
TypeScript
Stelle
36.5k
Fork
5.6k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di continuedev/continue

Tutte le issue di continuedev/continue

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.