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

@nvidia/cloudxr npm package declares no `license` field, so scanners report it as unlicensed

Abierto
  • ¿Algo no está bien?
#884 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@yanziz-nvidia ya está trabajando en esto.

Desde el 4/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Describe the bug

@nvidia/cloudxr — which deps/cloudxr/webxr_client consumes via "@nvidia/cloudxr": "file:../nvidia-cloudxr-<ver>.tgz" — ships no license field in its package.json. OSS license scanners resolve the package name against the public npm registry and report the component as having no license associated with it.

To reproduce

  1. curl -s https://registry.npmjs.org/@nvidia%2Fcloudxr | jq '[.versions[] | {version, license}]'
  2. Observe "license": null for both published versions (6.1.0, 6.2.0).
  3. Run any SBOM/license scanner over a build of deps/cloudxr/webxr_client.

Expected behavior

The package declares a machine-readable license so scanners can attribute it.

Observed behavior

The LICENSE file (NVIDIA proprietary SLA) is bundled inside the tarball, but the license field is absent — and scanners key on the field, not the file. Compounding it: npm dist-tags.latest is 6.2.0, so a scanner resolving a newer local tarball finds no matching published version, falls back to latest, and attributes the finding to 6.2.0 regardless of which version is actually vendored.

Screenshots

N/A.

Platforms

  • Isaac Teleop Version: main (webxr_client pins 6.3.0-rc2)
  • OS: N/A — build/scan time
  • Integrations: WebXR client
  • XR Device: N/A
  • Additional Devices: N/A

Additional context

The fix belongs upstream in the CloudXR.js package, not in this repo. npm does not allow overwriting a published version, so clearing this requires a patch republish carrying the license field plus a dist-tag move (and/or npm deprecate on the old ones). Publishing a 6.3.0 line would additionally stop the latest fallback.

Note that "license": "SEE LICENSE IN LICENSE" is a valid npm convention but is not an SPDX identifier, so strict scanners may still flag it; a LicenseRef--style identifier is the safer value going forward.

Filing here for tracking because this repo is the consumer — it cannot land the fix itself.

Lenguaje dominante
Python
Estrellas
412
Forks
97
Merge medio
2 d 3 h
PR fusionados (30 d)
141

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 NVIDIA/IsaacCapture

Todos los issues de NVIDIA/IsaacCapture

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.