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

Abierto
#13,453 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 8 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
36.5k
Forks
5.6k
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de continuedev/continue

Todos los issues de continuedev/continue

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.