Skip to content

Review licenses for redistributing the v1 images #13524

Open

Description

@cv

Problem

Publishing the v1 images (#13516) redistributes third-party software, and each license sets conditions for that:

  • Permissive licenses (MIT, Apache-2.0, BSD) require shipping their license and notice text.
  • Copyleft licenses (GPL, LGPL, MPL) also require that recipients can get the source of the exact versions shipped.
  • Proprietary terms can forbid redistribution outright.

NVIDIA's open-source review board (OSRB) must sign off before the images are published.

Goal

For each image a release publishes:

  1. List its components and licenses from its SBOM.
  2. Confirm the image keeps the required notices and that recipients can get any required source.
  3. Fix what is missing.
  4. Get OSRB sign-off.

Scope

Releases publish 14 images: codex, deepagents, hermes, mini-swe-agent, nooa, nooa-bench, openclaw, opencode, pi, remote-agent, ollama-proxy, vllm, ollama, and llama-cpp, each for AMD64 and ARM64.

Releases don't publish claude (#14694): it bundles Anthropic's proprietary Claude Code CLI, and NVIDIA has no permission to redistribute it. Users build it locally. NIM is also local-build only.

Done

  • SBOMs (feat(release): attach per-platform SBOMs to v1 images #13590): releases attach a package inventory for every image and platform.

  • Notices and review guide (fix(images): retain missing license notices and record the image license review #14594): the images now keep the Node.js, OpenClaw, Bun, and Rust crate notices they had dropped. image-licenses.md records the rc10 review: every image except ollama-proxy needs OSRB review, mainly for GPL/LGPL operating-system packages and MPL packages.

  • claude excluded (ci(release): leave the claude agent image out of releases #14694).

  • rc12 inspection: the rc12 images contain what their SBOMs and notices describe, and pi already ships the source for its native components. No license conflict was found. This checked contents; it is not approval.

  • Additional notices and sources (fix(images): retain dependency notices and native sources #14712, merged November 20): retained Fabric/proxy Cargo sources; OpenClaw native inputs; llama.cpp source/frontend notices; Codex/Bubblewrap/libcap source and notices; matching Rust standard-library notices; and Pillow-HEIF/libheif/libde265/x265 sources with rebuild instructions. Final-image verification and complete per-binary coverage remain open.

  • Codex native notices and V8 source (fix(images): retain Codex V8 and native dependency notices #14735, merged November 20): retained the pinned V8 source archive and original V8, ICU, LLVM runtime, and rusty_v8 notices. Complete per-binary coverage and final-image verification remain open.

  • Post-fix CI artifact verification (3d0553573): checked both platforms of all 11 agent/proxy images (22 manifest digests), matching their SBOM subjects and expected retained materials. Their 93 Debian source versions map to the collected source bundle and matching source-description hashes in signed Debian archive indexes. This is technical evidence for those CI artifacts, not final release promotion, runtime-image verification, source hosting, or approval.

  • Additional native sources and recipient guidance (fix(images): retain native dependency sources and rebuild guidance #14737, merged November 21 as 405b7a7a88f04e8627e08753f8352bf586fb3851): retain orjson, Symphonia, Nucleo, colored, and option-ext sources with their original notices; correct Codex workspace-lock preparation; use the canonical libcap source URL; and document custom/unpublished harness images. This addresses those named gaps, not complete transitive coverage or release approval.

  • Build-from-source guide (docs: say who builds NemoClaw from source and when, and restructure the build guide #14711, merged November 21): the separate guide is merged.

  • Draft v0.1.0-rc.1 artifact verification (November 21, release commit df0d62f1168098677072b11124819f41d310fbb6): checked all 28 staged platform manifests and their SBOM subjects, then 206 retained-file checks including 90 pinned-hash comparisons; all passed, including fix(images): retain native dependency sources and rebuild guidance #14737's new source archives. Reconciled 475 OS source versions: 439 match the existing local distro-source candidate, and the new nghttp2 1.64.0-1.1+deb13u2 source was collected with file hashes bound to a verified signed Debian index. The other 35 records remain component-specific/outside the tested distro source collection, as in the earlier audit. This checks named materials for this draft, not complete per-binary coverage, a published source offer, or approval. Recheck if the selected digests change.

  • Dependency sources and build evidence (fix(images): retain compiled dependency sources and notices #14761, merged November 22): retained additional Codex, native-wheel, Nemo Relay CLI, and ripgrep dependency sources and notices; built Tiktoken from unmodified source with a retained Cargo lock; and corrected source-directory permissions. Tiktoken qualification passed on AMD64 and ARM64. The four audited AMD64 images had no unmatched versioned Rust source paths. This does not establish complete stripped-code/non-Cargo coverage or release approval.

Remaining

What Why Owner Tracked in
Resolve the Hermes fonts: confirm redistribution rights, or remove or replace the fonts, preferably upstream Hermes's dashboard ships seven commercial font files from Blaze Type and Pangram Pangram. Their npm package says MIT, but the foundries license fonts under separate EULAs Release owner (unassigned) with Legal #14719
Find license evidence for @nous-research/ui, unicode-animations, react-remove-scroll-bar, and Fetch Use 0.4.0 They declare MIT but the inspected artifacts lack original notices. #14712 now retains the recovered upstream @alcalzone/ansi-tokenize notice; the exact-version evidence and remaining gaps are in #14719 Image engineering #14719
Decide how recipients get copyleft source GPL, LGPL, and MPL require source for what we ship. OSRB decides whether pointing to Debian's and Ubuntu's archives is enough or NVIDIA must publish the sources. Bun statically links LGPL code, which also requires relinking materials Image engineering proposes; OSRB decides This issue
Complete evidence for stripped code and non-Cargo native dependencies, and resolve missing original notices #14761 merged the additional Cargo/wheel source closures and Tiktoken build evidence. Its versioned Rust-path checks cover the audited AMD64 images; they do not identify every component in stripped code or establish complete non-Cargo static linkage. The original MIT notice for the deno_core_icudata 0.77.0 Rust wrapper also remains unavailable in its published crate and recorded source tree Image engineering This issue; #14719 for the other notice findings
Check the CUDA terms for vllm, ollama, and llama-cpp These ship NVIDIA CUDA libraries, whose license has its own redistribution terms Release owner (unassigned) This issue
Get OSRB sign-off (see the questions below) The original goal of this issue Release owner (unassigned) This issue
Inspect final release images containing #14761 on both architectures and record their digests The draft v0.1.0-rc.1 named-material checks predate #14761. Verify the retained notices, sources, and build evidence against the exact release digests on AMD64 and ARM64, and repeat if those digests change. Font rights and release approval remain unresolved Release engineering This issue

Questions for OSRB

  1. Which images need sign-off? The guide says images with only permissive licenses need none; fix(images): retain dependency notices and native sources #14712 preserves the rule and explicitly records that OSRB has not confirmed the permissive-only exemption.
  2. Do existing NVIDIA approvals of the upstream base images (such as vLLM, Ollama, or CUDA) cover those layers, so the review covers only what NemoClaw adds?
  3. Is linking to Debian's and Ubuntu's source archives enough for the operating-system packages?

Done When

Each published image, on both architectures, has OSRB sign-off; its notices and source delivery match the published image; and the required fixes and documentation have merged.

Activity

  1. added
    v1NemoClaw v1 branch
    on Oct 20, 2026
  2. added
    area: packagingPackages, images, registries, installers, or distribution
    on Oct 27, 2026
  3. added theissue type on Oct 27, 2026
  4. added and removed on Nov 17, 2026
  5. added this to the Roadmap: GTC DC 2026 milestone on Nov 17, 2026
  6. removed this from the Roadmap: GTC DC 2026 milestone on Nov 17, 2026
  7. added this to the Roadmap: GTC DC 2026 milestone on Nov 18, 2026
  8. self-assigned this
    on Nov 18, 2026
  9. jyaunches commented on Nov 18, 2026

    @jyaunches
    Contributor

    could guide users on how to handle harnesses we haven't built images for

  10. cv commented on Nov 20, 2026

    @cv
    CollaboratorAuthor

    Decision: releases won't publish the claude agent image. It bundles the Claude Code CLI, which is Anthropic's proprietary software, and we don't have Anthropic's permission to redistribute it. CI keeps building and testing the image, and users build it locally (cargo images build --platform linux/arm64 claude).

    The other images proceed per the audit in image-licenses.md. #14694 removes claude from release staging and records the decision.

  11. jyaunches commented on Nov 20, 2026

    @jyaunches
    Contributor

    Images that need OSRB sign-off

    Under the current rule in image-licenses.md, 13 of the 14 release images need OSRB sign-off. An image needs it when it contains any third-party proprietary, copyleft, or unknown license.

    Image Needs OSRB Main reason
    codex, nooa, nooa-bench, remote-agent, pi, deepagents, mini-swe-agent Yes Debian GPL/LGPL packages; certifi (MPL-2.0), plus orjson and tqdm (MPL-2.0) in some
    hermes Yes The same, plus pathspec (MPL-2.0) and the commercial fonts (#14719)
    openclaw Yes The same, plus eight MPL-2.0 npm packages and MPL-2.0 native code (UBJS addon, CUA driver)
    opencode Yes The same, plus Bun's statically linked LGPL-2.1 code
    vllm Yes Ubuntu packages; GPL, LGPL, and MPL-2.0 Python packages; FFmpeg and other components with unknown licenses
    ollama Yes Ubuntu GPL/LGPL packages
    llama-cpp Yes, by the rule; not yet classified Ubuntu packages; FFmpeg, x264, and x265 under GPL
    ollama-proxy No, under the current rule Every component is permissive; OSRB hasn't confirmed that permissive-only images need no sign-off

    Every image that contains an operating system needs OSRB sign-off; only the proxy has none.

    Limits

    • The verdicts come from the rc10 review of images built from 5716c39. rc10 didn't stage llama-cpp, so its row applies the rule to the components the guide lists.
    • Images built from later commits, such as the vLLM 0.34.0 and Hermes Agent 0.22.7 upgrades, need their own review. The final release images must be classified again before sign-off.
  12. prekshivyas commented on Nov 21, 2026

    @prekshivyas
    Collaborator

    Recording the two remaining upstream-notice findings here; no new upstream issues will be opened as part of this follow-up.

    Package Finding What remains
    unicode-animations 1.0.3 The published package metadata and README declare MIT, but the inspected archive lacks the original license/copyright notice. Obtain the applicable original notice or record the release reviewer's accepted disposition.
    deno_core_icudata 0.77.0 The crate declares MIT, but its archive and recorded source tree (83537ba16a4bf1645fc8322e81f7aaf0149a8922) lack the Rust wrapper's original MIT notice. Obtain the applicable wrapper notice or record the release reviewer's accepted disposition.

    The ICU data notice is already retained: the package embeds ICU 77 data, and ICU release-77-1's LICENSE is byte-for-byte identical to the retained codex-icu-LICENSE (SHA256 451167c55c0fa447cc2d5632714f5e3c567fe4f1e1badefab2c1333852198aca). The remaining Deno finding concerns the Rust wrapper's MIT notice, not a missing ICU 77 license text.

    No upstream requests have been sent. Documenting these findings does not resolve the missing notices or establish redistribution approval. The other package-notice findings and Hermes font-rights decision remain tracked above and in #14719.

  13. prekshivyas commented on Nov 22, 2026

    @prekshivyas
    Collaborator

    @cv The dependency-source and notice fixes are in PR #14761, pending merge.

    Remaining engineering work:

    • Complete evidence for native components whose version or build information is unavailable.
    • Verify the exact final release images on both architectures and record their digests.

    Remaining licensing decisions:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: packagingPackages, images, registries, installers, or distributionv1NemoClaw v1 branch

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions