Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Package Postman with proxy-compatible Node

Abierto
  • ¿Algo no está bien?
#1,195 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

  • #1197 de @danbarr — cerrado sin fusionar

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, github, go, node.js
Área
devtools, infrastructure

Línea de trabajo

Start by inspecting the Dockyard package definitions and the upstream postman-mcp-server provenance and license information; the issue does not name specific files or tests. Check how existing packages pin signed images, configure Node proxy support, and preserve toolsets and authentication. Done means amd64 and arm64 images pass security scans and isolated thv run discovery, and a dummy-key API call reaches Postman with the expected authentication rejection; document mounts and network access.

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

Descripción

needs-triage

Package Postman's first-party postman-mcp-server in a pinned, signed Dockyard image with a Node runtime that supports ToolHive's egress proxy.

The currently published Docker MCP image mcp/postman@sha256:73f715030cbe553836532116e5597cedcc601c40f79b9650f72227af17ee3b10 contains Postman 2.11.0 on Node 22.16.0. Local thv run initialization and discovery succeed, but getAuthenticatedUser with a dummy API key fails with AggregateError before reaching Postman: the client uses Node fetch, which ignores the proxy environment on this runtime. This prevents verifying even the expected invalid-key API response with ToolHive's default network isolation.

Acceptance criteria:

  • Package the upstream npm server for amd64 and arm64 with verified provenance and license.
  • Use a supported Node version with environment proxy support, and configure/document the setting needed for fetch to honor ToolHive's HTTP_PROXY/HTTPS_PROXY (for example NODE_USE_ENV_PROXY=1 where supported).
  • Preserve Minimal/Full toolset selection and POSTMAN_API_KEY authentication.
  • Pass normal security scans and thv run discovery with network isolation enabled. Verify an API call reaches Postman, at minimum an expected authentication rejection using a dummy key; report real-account checks separately.
  • Document file mounts and network access for collection execution, including explicit host-gateway access when needed.
Lenguaje dominante
Go
Estrellas
8
Forks
7
Merge medio
22 h 6 min
PR fusionados (30 d)
136

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 stacklok/dockyard

Todos los issues de stacklok/dockyard

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.