Skip to content

fix: remove unregistered jet-api from Dockerfile.linting (dependency confusion) - #88

Open
Xavier Garceau-Aranda (x4v13r64) wants to merge 1 commit into
microsoft:devfrom
x4v13r64:fix/remove-nonexistent-pypi-packages
Open

fix: remove unregistered jet-api from Dockerfile.linting (dependency confusion)#88
Xavier Garceau-Aranda (x4v13r64) wants to merge 1 commit into
microsoft:devfrom
x4v13r64:fix/remove-nonexistent-pypi-packages

Conversation

@x4v13r64

Copy link
Copy Markdown

Summary

Dockerfile.linting installs jet-api via pip in the jet build stage. jet-api is an internal NVIDIA CI orchestration package that is not published on PyPI.

The private index URL is injected via a Docker build secret (JET_INDEX_URLS) and appended as a trailing positional argument. If the secret is absent or the variable expansion produces an empty string, pip resolves jet-api exclusively from PyPI — where the name is currently unregistered and squattable.

This PR removes jet-api from the install command. jet-client (which is pinned to ~=2.0) is retained as it is the primary package needed for the linting stage.

Changes

  • Dockerfile.linting: remove jet-api from the pip install line in the jet stage

Security Impact

Dependency confusion — jet-api is unregistered on PyPI. An attacker registering the name gains code execution inside CI build environments that use this Dockerfile stage without providing the private index secret.

Test plan

  • Confirm the jet build stage still functions correctly without jet-api
  • If jet-api is required, install it using an explicit --extra-index-url flag (not a trailing positional argument) so the private index is always consulted

…confusion)

jet-api is an internal NVIDIA CI package not published on PyPI. Removing
it from the pip install command prevents dependency confusion attacks
where pip could resolve the name from PyPI when the private index is
unavailable or returns a lower version.
@github-actions

Copy link
Copy Markdown

Marking as stale. No activity in 60 days.

@github-actions github-actions Bot added the stale label May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant