Package Postman with proxy-compatible Node
维护者通常 2 天内回复
还没有人认领这个 Issue。
- #1197 来自 @danbarr —— 已关闭，未合并
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- docker, github, go, node.js
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
fetchto honor ToolHive'sHTTP_PROXY/HTTPS_PROXY(for exampleNODE_USE_ENV_PROXY=1where supported). - Preserve Minimal/Full toolset selection and
POSTMAN_API_KEYauthentication. - Pass normal security scans and
thv rundiscovery 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.
- 主要语言
- Go
- 星标
- 8
- 派生
- 7
- 平均合并
- 22 小时 6 分钟
- 30 天内合并 PR
- 136
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stacklok/dockyard 的其他 Issue
-
critical grype security
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 2 天内回复
-
grype high security
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
Package the official Firebase MCP server可能已有人在做 @danbarr 于 1 天前认领。 未关闭needs-triage
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 2 天内回复
-
grype high security
难度 2/5 1-3 小时 新手友好度 52/100
维护者通常 2 天内回复
-
grype high security
难度 3/5 1-2 天 新手友好度 48/100
维护者通常 2 天内回复
查看 stacklok/dockyard 的全部 Issue
相似的 Issue
-
Object Manager 1.13 resets a vCLU after sending a project可能已有人在做 @tciunelis 今天认领。 未关闭bug ready ticket
难度 2/5 1-3 小时 新手友好度 84/100
Domktorymysli/vclu#152 ·
维护者通常 1 天内回复
-
bug converter
难度 2/5 1-3 小时 新手友好度 62/100
grafana/sigma-rule-deployment#435 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
🤖 verification skills: harden check.sh and verify.sh argument and file handling (#391 follow-ups)未关闭
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
google/go-containerregistry#2491 ·
维护者通常 1 天内回复