[DGX Spark][Sandbox] Fresh NemoHermes sandbox build fails on v0.0.101 — mcp-tool-discovery-runtime npm audit gate rejects shipped deps (fast-uri/hono/ip-address)

[wangericnv]

Warning

Release-blocker class — fresh NemoHermes onboard is broken on v0.0.101 (no Hermes agent can be built on a clean/uncached build).

Description

A fresh NemoHermes sandbox onboard fails during the Docker image build on v0.0.101. The build reaches the mcp-tool-discovery-runtime stage and runs the in-image install-reviewed-runtime.sh, which succeeds at npm install / test / typecheck / bundle but then fails its npm audit gate: the shipped, pinned dependencies have published CVEs, so audit exits non-zero and the whole sandbox build fails.

Flagged deps at the failing stage:

• fast-uri 3.0.0 - 3.1.4 (high) — host confusion via backslash authority introducer (GHSA-7p8r-x3mc-p8w7)
• hono < 4.12.34 (moderate) — GHSA-8j4g-w8fx-2239
• ip-address <= 10.3.0 (high) — GHSA-mwp4-54f8-5fhr

Supply-chain-gate time-bomb: the build's audit runs against live CVE data, so pinned deps that shipped clean now fail audit. OpenClaw passes the same class of stage only when that layer is already cached (pre-CVE); a fresh OpenClaw/DeepAgents build may hit the same gate.

Platform scope: Reproduced on DGX Spark (GB10, aarch64), NemoClaw v0.0.101, on both a local BuildKit builder and the gateway builder. Not believed platform-specific.
Regression: Pinned deps shipped clean; the audit gate now rejects them after the CVEs were published.

Environment

Device: DGX Spark (GB10, aarch64)   OS: Ubuntu 24.04   Node: v22.22.1
Docker: 28.3.3   OpenShell: 0.0.85   NemoClaw: v0.0.101

Steps to Reproduce

1. On a host with no cached NemoHermes image layers (or use --fresh), export a valid provider (NEMOCLAW_PROVIDER=build + NEMOCLAW_PROVIDER_KEY).
2. nemoclaw onboard --agent hermes --name hermes-buildcheck --no-sandbox-gpu --non-interactive --yes --yes-i-accept-third-party-software --fresh
3. Observe the build around the mcp-tool-discovery-runtime stage and the final exit code.

Expected Result

The NemoHermes image builds and the sandbox reaches Ready. Shipped pinned deps do not hard-fail the in-image audit gate.

Actual Result

#39 [mcp-tool-discovery-runtime 4/5] RUN ./install-reviewed-runtime.sh && rm -f ./install-reviewed-runtime.sh
#39 ... test / typecheck / bundle  (all pass)
#39 ... fast-uri  3.0.0 - 3.1.4  vulnerable to host confusion via backslash authority introducer (GHSA-7p8r-x3mc-p8w7)
#39 ... 3 vulnerabilities (1 moderate, 2 high)
#39 ERROR: process "/bin/sh -c ./install-reviewed-runtime.sh ..." did not complete successfully: exit code: 1
Sandbox creation failed (exit 1).

Reproduced twice with --fresh. Only npm audit fails; install/test/typecheck/bundle all succeed. Blocks the onboarding prerequisite for all NemoHermes cases on v0.0.101.

[wangericnv]

Scope expansion: not Hermes/v0.0.101-specific. Also reproduces on macOS (Apple Silicon), NemoClaw v0.0.97, OpenClaw onboard — nemoclaw onboard --agent openclaw --fresh fails at [6/8] Creating sandbox, same mcp-tool-discovery-runtime → install-reviewed-runtime.sh npm-audit failure on the same 3 CVEs (fast-uri/hono/ip-address). Root cause is version- and agent-independent: install-reviewed-runtime.sh ends with npm audit --omit=dev --audit-level=low under set -eu, and the CVEs post-date the pinned deps, so any fresh (uncached) sandbox build fails — OpenClaw, Hermes, and DeepAgents alike, across at least v0.0.97 and v0.0.101.

[laitingsheng]

Duplicate of #8177.

Fixed on main by #8180 (1ee723a3c), which pins fast-uri@3.1.5, hono@4.12.34, ip-address@10.3.1, and @hono/node-server@2.0.12 in tools/mcp-tool-discovery-runtime/package.json. The v0.0.101 tag was cut at 2026-08-03 19:15 UTC and that fix merged at 2026-08-04 02:29 UTC, so no released version carries it yet. A fresh build from main passes the npm audit --omit=dev --audit-level=low gate in install-reviewed-runtime.sh; the next release will unblock fresh onboards across all three agent images.

The separate concern about the gate resolving live advisory data at build time, so pinned dependencies can fail later, is being handled in #8172.

[wangericnv]

Thanks @laitingsheng — confirmed. Closing as a duplicate of #8177 (fixed on main by #8180, pinning fast-uri@3.1.5 / hono@4.12.34 / ip-address@10.3.1 / @hono/node-server@2.0.12; not in the v0.0.101 tag, will land in the next release). The live-advisory-gate concern from my scope comment is tracked in #8172. QA will re-verify fresh onboards (all agent images) once >v0.0.101 ships.