disclude.iouv 0.13.4
- Source
- https://github.com/astral-sh/uv
- Tag scanned
0.13.4- Compared with
0.13.3(1 signals introduced since)- Files
- 1177 scanned, 652 skipped (binary, oversized, or unrecognised)
- Signals
- 1 critical · 10 warn · 108 info
- Scan time
- 74.9 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 70 of 80 warn and critical signals; 69 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-21 11:27
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
IMPORTS_FILE="/-coff-imports.txt" if ; then -
-
-
-
-
-
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME} --help -
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME}_build --help -
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME} --help -
ub const READ_ONLY_GITHUB_SSH_DEPLOY_KEY: &str = "LS0tLS1CRUdJTiBPUEVOU1NIIFBSSVZBVEUgS0VZLS0tLS0KYjNCbGJuTnphQzFyWlhrdGRqRUFBQUFBQkc1dmJtVUFBQUFFYm05dVpRQUFBQUFBQUFBQkFBQUFNd0FBQUF0emMyZ3RaVwpReU5UVXhPUUFBQUNBeTF1SnNZK1JXcWp1NkdIY3Z6a3AwS21yWDEwdmo3RUZqTkpNTkRqSGZPZ0FBQUpqWUpwVnAyQ2FWCmFRQUFBQXR6YzJndFpXUXlOVFV4T1FBQUsuspicious A hardcoded base64-encoded OpenSSH private deploy key constant in a test library.Reasoning
The constant base64-decodes to an OpenSSH private key header, so it is a hardcoded private deploy key in source. It is most likely a test fixture or a deliberately published read-only key, but committed private key material is a genuine secret-exposure risk and cannot be verified from the snippet.
-
info
warn→ info by reviewdynamic-executiondocs/getting-started/installation.md:28:5new in this releaselikely benign Documentation showing a version-pinned uv install script piped to sh.Reasoning
Documented installer pinned to a specific version from the project's own domain. This is a normal install instruction, not a covert dropper.
-
likely benign CI smoke test invoking the package's module-named CLI after install.
Reasoning
The `${MODULE_NAME} --help` line runs the freshly built package's own console entry point in a release smoke test. The variable is a workflow-level name, not attacker input, and the same file builds and installs the package it runs.
-
likely benign CI smoke test of the uv-build CLI after installing the built wheel or sdist.
Reasoning
This is the same post-install smoke test pattern for the uv-build package, running its own installed entry point. It is a normal release verification step.
-
likely benign Verification step installing the locally built package and checking its help output.
Reasoning
Installs a locally built package from dist/ and runs its help output to verify the artifact. The variable-named command is an expected part of testing the built binary.
-
likely benign Verification step installing the uv-build artifact and running its help.
Reasoning
Installs the uv-build artifact from a local directory and runs its help command. This is standard release artifact verification.
-
# Namespace runners do not include winget.likely benign Pinned NASM version variable used in a Windows build-tool installation step.Reasoning
The flag is a PowerShell variable being treated as a command by the parser. The step downloads the official NASM installer from nasm.us for a pinned version. This is a build dependency, not execution of untrusted code.
-
likely benign Hardcoded SHA-256 checksum for the NASM installer, used for integrity checking.
Reasoning
The SHA-256 is a hardcoded hash for the pinned NASM installer. Its presence suggests the download is meant to be verified, which is the opposite of obfuscation. The flag is a parser artifact on a variable assignment.
-
likely benign Downloads the NASM installer from nasm.us to a temp path before running it silently.
Reasoning
Downloads the NASM installer from the official upstream host into a temp path. The 'command' is a file path variable being run by Start-Process. This is standard toolchain setup for a Windows build.
-
if ()likely benign Silent NASM installer run with exit-code check in a Windows CI step.Reasoning
Runs the NASM installer with silent flags and checks the exit code. This is the usual way CI installs a build dependency. The flag is a parser artifact on a PowerShell variable.
-
if ()likely benign Exit-code check after the NASM installer run in a Windows CI step.Reasoning
Checks the NASM installer's exit code and throws on failure. This is defensive scripting, and the flagged variable is only a PowerShell expression.
-
if () |likely benign Adds the NASM install directory to the GitHub Actions PATH.Reasoning
Appends the NASM install directory to GITHUB_PATH so later steps can find the assembler. This is ordinary CI PATH configuration with no hidden or remote execution.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME}-build --helplikely benign CI step that runs the just-built package's --help as a smoke test, with the command name taken from a MODULE_NAME variable.Reasoning
The command name comes from a workflow variable, a common pattern in release CI where the module name is a fixed value in the job's env or matrix. The shown code only builds and smoke-tests the package it just installed from /dist. Nothing here is attacker-controlled input, though the variable's definition is outside the snippet.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME} --helplikely benign Release smoke test running the built package's --help via a MODULE_NAME variable.Reasoning
Same pattern as the other build-release-binaries findings: a release-verification step that installs the local wheel and runs its --help. The variable is most likely a constant defined elsewhere in the workflow.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME}-build --helplikely benign Release smoke test invoking the built -build helper via a MODULE_NAME variable.Reasoning
Repeats the same release smoke-test pattern: install from /dist with --no-index, then run the module's --help. No untrusted input reaches the command name in the snippet.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # .venv/bin/python -m ${MODULE_NAME} --helplikely benign Venv smoke test that runs the installed package's entry point via a MODULE_NAME variable.Reasoning
Venv-based smoke test that installs the locally built package from /dist and runs its entry point. The variable-named command is a routine CI verification pattern.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here.likely benign Venv smoke test of the built -build helper's --help output.Reasoning
Venv smoke test of the locally built -build helper with --no-index installation from /dist. Consistent with legitimate release verification.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # .venv/bin/python -m ${MODULE_NAME} --helplikely benign Venv smoke test that runs the built package's CLI via a MODULE_NAME variable.Reasoning
Venv-based smoke test installing the local wheel and running its CLI. The variable command name is a standard CI pattern and the surrounding steps are verification only.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME} --helplikely benign Release smoke test running the built module's --help via a MODULE_NAME variable.Reasoning
Repeats the release smoke-test pattern: install from local /dist and run the module's --help. The TODO comments show it is maintained verification code.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here.likely benign Venv smoke test of the built -build helper's --help output.Reasoning
Venv smoke test of the locally built -build helper. The variable command is not attacker-controlled in the shown context and the step is consistent with release verification.
-
# TODO(konsti): Enable this test on all platforms, currently `find_uv_bin` is failing to discover uv here. # python -m ${MODULE_NAME}_build --helplikely benign Release smoke test of the built -build helper's --help using a MODULE_NAME variable.Reasoning
Same release smoke-test structure, with a commented alternative using the underscore module name. Nothing in the snippet suggests malicious execution.
-
|likely benign CI step that downloads the cargo-hawk installer script from an astral-sh GitHub release and pipes it to sh.Reasoning
Piping a remote installer into sh is a risky supply-chain pattern, but this one is the vendor's own installer from astral-sh GitHub releases, pinned to a HAWK_VERSION variable, and fetched over HTTPS with TLS 1.2 enforced. That matches the standard install instructions for such tools. The residual risk is the unpinned-hash trust in the release artifact.
-
if [; then comment=" An upstream pull request was already created at [#](https://github.com/astral-sh/uv/pull/)." fi marker="<!-- uv-promotion-rejection:: -->" -
if ; then elselikely benign Workflow step executes a command name held in a loop variable, a common CI test-runner pattern.Reasoning
The loop runs commands taken from a variable set by the workflow's own test matrix. The uv-prefixed branch runs a local ./uv binary, which is normal for CI test runners. Nothing in the snippet fetches or decodes a payload.
-
else filikely benign Same loop's fallback branch runs the workflow-provided command variable.Reasoning
This is the else branch of the same loop over matrix-defined commands. It is a standard CI construct, and the command comes from the workflow configuration rather than from attacker-controlled input.
-
# Call Python Install Manager's py.exe by full path to avoid legacy py.exe &likely benign PowerShell invokes py.exe from a full Windows path to install Python 3.14.Reasoning
The line calls Python Install Manager's py.exe by a full Windows path under LOCALAPPDATA, as the comment says. The $env: prefix is PowerShell syntax that the bash-embedded parser misreads as a variable command name. This is a routine Windows CI setup step.
-
if ! ; then -
if ! ; then -
likely benign Activates a virtualenv created earlier in the same CI step.
Reasoning
The script sources the activate file of a virtualenv that the same step just created with uv venv at $PYODIDE_VENV. The path is set by the workflow, not by external input, so this is a normal venv activation.
-
&likely benign PowerShell activates a native Windows venv and runs the pyodide CLI.Reasoning
The 'backslash escapes' are ordinary Windows path separators in a relative venv Activate.ps1 path. The command is a standard PowerShell venv activation followed by a pyodide CLI call. Nothing is hidden.
-
likely benign PowerShell sets pyodide environment variables and exports them to GITHUB_ENV.
Reasoning
The flagged token is the PowerShell $env: variable assignment syntax, which the bash parser misreads as a command name. The step sets PYODIDE env values from the pyodide CLI and writes them to GITHUB_ENV, a normal CI pattern.
-
likely benign PowerShell exports further pyodide index settings to GITHUB_ENV.
Reasoning
This is the same PowerShell $env: assignment and GITHUB_ENV export pattern as the preceding line. It is a parser artifact on routine CI configuration code.
-
&likely benign PowerShell runs uv and pip from a Windows venv to install numpy for a Pyodide test.Reasoning
The backslashes are Windows path separators for .\uv.exe and the venv Activate.ps1 script. The rest of the step is an ordinary pip install and import check, with no concealed command.
-
# Add pyenv-win to PATH for this sessionlikely benign PowerShell prepends pyenv-win directories to PATH for the CI session.Reasoning
The line sets PYENV and PATH for pyenv-win using PowerShell $env: syntax, which the parser misreads as a variable command name. It is ordinary Windows CI environment setup.
-
# Add to GITHUB_PATH so WSL can find the shimslikely benign PowerShell updates PATH with pyenv-win directories for later CI steps.Reasoning
This is the same $env: PATH assignment as the previous line. It sets up pyenv-win shims for later steps and does not run any fetched or encoded content.
-
& &likely benign PowerShell uses pyenv-win to install and set global Python 3.11.9.Reasoning
The step runs pyenv.bat from the PYENV directory the workflow itself set to install and select Python 3.11.9. The $env: prefix is a parser artifact, and the command is a standard toolchain install.
-
& &likely benign PowerShell sets pyenv-win's global Python version to 3.11.9.Reasoning
This line repeats the pyenv-win global-version call from the previous line. It is an ordinary Windows CI toolchain command with no evidence of obfuscation.
-
&dismissed PowerShell step in a CI workflow that runs pyenv-win to list installed versions.Reasoning
The flagged line is a PowerShell call operator invoking pyenv-win from a known install path under $env:PYENV, and the step only prints versions. The bash-style parser misreads PowerShell syntax as a dynamic command name, so this is a false positive in a CI test workflow.
-
likely benign Evals uv's self-generated bash completion script inside a CI smoke test.
Reasoning
The eval runs the output of the project's own freshly built uv binary to generate shell completions, a documented pattern. It is a CI smoke test in the project's repository, not an attacker-controlled input.
-
likely benign Evals uvx's self-generated bash completion script inside a CI smoke test.
Reasoning
Same pattern as the adjacent line: eval of the locally built uvx's generated completion output in a CI smoke test, with no external or attacker-controlled input.
-
likely benign Repeated eval of uv/uvx self-generated completions in another smoke-test job.
Reasoning
Identical generated-completion eval in the same workflow file, repeated across jobs. It is the project's own binary output in CI.
-
likely benign Repeated eval of uvx self-generated completions in a smoke-test job.
Reasoning
Same generated-completion eval repeated in a CI job. No sign of tampering or external input.
-
likely benign Repeated eval of uv/uvx self-generated completions in a further smoke-test job.
Reasoning
Same generated-completion eval in another CI job of the same workflow, using the project's own binaries.
-
likely benign Repeated eval of uvx self-generated completions in a smoke-test job.
Reasoning
Same generated-completion eval repeated in the workflow, operating only on output from the project's own binaries.
-
dismissed PowerShell step refreshing PATH and running a repo check script in CI.
Reasoning
The flagged line is PowerShell invoking a repo script with a PATH refresh, misparsed by the bash-style analyzer as a variable command name. This is ordinary CI setup, a false positive.
-
dismissed Passes an environment variable as an argument to a repo check script in CI.
Reasoning
The $env:TEST_PYTHON_VERSION reference is a script argument, not a command name, and sits in the same PowerShell step as the previous finding. Benign CI parameter passing.
-
# Install pyenv | # Set up environment variables for current steplikely benign CI step installs pyenv by piping the official pyenv.run installer into bash.Reasoning
Piping a remote installer straight into bash is a real supply-chain risk pattern, but here it fetches pyenv's official installer in a CI setup step. The risk is accepted practice rather than obfuscation or malicious intent.
-
# Install Python 3.9likely benign Evals pyenv's standard shell init output to activate pyenv in CI.Reasoning
eval of 'pyenv init -' is the standard documented shell integration for pyenv, and pyenv is installed in the preceding step. Routine CI setup, not malicious.
-
|dismissed PowerShell step capturing cargo bloat output in a CI workflow.Reasoning
$output is a PowerShell variable holding cargo bloat output, and the bash-style parser misreads it as a command name. This is a false positive in a benign CI step.
-
| |dismissed PowerShell pipeline filtering cargo bloat output in a CI workflow.Reasoning
$filteredOutput is a PowerShell pipeline variable being filtered with Select-String. The analyzer misclassified it as a command name, so this is a false positive in benign CI code.
-
| | if ()dismissed A PowerShell if-condition on a variable, misclassified as a variable command name.Reasoning
The flagged token is a PowerShell variable used as a boolean condition in an if statement. It is not a command invocation, so the scanner misread the syntax. Nothing in the snippet is dynamic execution.
-
if ()dismissed A PowerShell if-branch that exits on a pattern match, misread as dynamic execution.Reasoning
Same false positive: `if ($containsPatterns)` followed by `Exit 1` is a normal conditional, not a variable being executed as a command.
-
# On macOS and Linux. |likely benign Documentation for installing uv via curl piped to sh from astral.sh.Reasoning
This is the documented official uv installer one-liner. Piping a vendor install script to sh is a common but still trust-based pattern, and in a README it is the expected install method.
-
dismissed IPA pronunciation notation for 'uv' in the README.
Reasoning
The characters are IPA phonetic symbols in a pronunciation guide, which legitimately mix Latin and IPA scripts in prose.
-
dismissed IPA pronunciation notation for 'uv' in the README.
Reasoning
Same IPA pronunciation notation; mixed scripts are expected here.
-
<h1>Links for h1> <a href="/whl/Jinja2-3.1.2-py3-none-any.whl#sha256%3D4095ada29e51070f7d199a0a5bdf5c8d8e238e03f0bf4dcc02571e78c9ae800d">Jinja2-3.1.2-py3-none-any.a><br/> </body> </html>dismissed A sha256 hash fragment in a test HTML page for a package index.Reasoning
The matched text is a hex sha256 digest in a URL fragment inside an HTML test fixture. It is not a meaningful base64 payload.
-
1..=0x5e, r##"__import__("os").fsdecode(b"/foo/\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f !\"#$%&\'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^/bar")"##, ),likely benign A Rust test table of Python byte-string escapes for path decoding tests.Reasoning
The escapes encode byte sequences inside a Python fsdecode snippet used as a test string for path handling. This is test data exercising byte-path conversion, not hidden code.
-
0x5f..=0xa3, r#"__import__("os").fsdecode(b"/foo/_`abcdefghijklmnopqrstuvwxyz{|}~\x7f\x80\x81\x82\x83\x84\x85\x86\x87\x88\x89\x8a\x8b\x8c\x8d\x8e\x8f\x90\x91\x92\x93\x94\x95\x96\x97\x98\x99\x9a\x9b\x9c\x9d\x9e\x9f\xa0\xa1\xa2\xa3/bar")"#, ),likely benign A Rust test case enumerating byte escapes for fsdecode path tests.Reasoning
The same test table contains a range of byte escapes covering non-ASCII bytes to validate fsdecode behaviour. The consistent structure indicates deliberate test coverage.
-
0xa4..=0xd1, r#"__import__("os").fsdecode(b"/foo/\xa4\xa5\xa6\xa7\xa8\xa9\xaa\xab\xac\xad\xae\xaf\xb0\xb1\xb2\xb3\xb4\xb5\xb6\xb7\xb8\xb9\xba\xbb\xbc\xbd\xbe\xbf\xc0\xc1\xc2\xc3\xc4\xc5\xc6\xc7\xc8\xc9\xca\xcb\xcc\xcd\xce\xcf\xd0\xd1/bar")"#, ),likely benign A Rust test enumerating byte escapes for path decoding.Reasoning
The escapes are a systematic enumeration of byte values in a test string for Python path decoding. This is a legitimate exhaustive test.
-
0xd2..=u8MAX, r#"__import__("os").fsdecode(b"/foo/\xd2\xd3\xd4\xd5\xd6\xd7\xd8\xd9\xda\xdb\xdc\xdd\xde\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf7\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff/bar")"#, ), ]likely benign A Rust test enumerating high-byte escapes for path decoding.Reasoning
This is the high byte range of the same systematic test enumeration, consistent with a deliberate byte-coverage test.
-
/// the formatter out of line to avoid duplicating it at call sites. -
"space in middle", "alpha-α", ]; for input in failures -
assert_snapshot! -
@" Expected either `,` (separating extras) or `]` (ending the extras section), found `α` foo[bar α] ^ -
Expected either `,` or `]` , found `α` foo ^ " -
assert_snapshot! -
Expected one of `@`, ` -
assert_snapshot! -
assert_snapshot! -
@r#" Unexpected character 'α', expected 'and', 'or' or end of input foo; python_version == "3.12" αx ^^ -
Unexpected character 'α', expected 'and', 'or' or end of input foo; python_version == "3.12" αx ^^ "# -
Unexpected character 'α', expected 'and', 'or' or end of input foo; python_version == "3.12" αx ^^ "# -
-
-
@r#" Unexpected character 'α', expected end of input os_name == "nt" αx ^^ -
Unexpected character 'α', expected end of input os_name == "nt" αx ^^ "# -
Unexpected character 'α', expected end of input os_name == "nt" αx ^^ "# -
// Unicode "α", "férrîs", "안녕하세요", -
// Python implementations vary // https://github.com/pypa/pyproject-metadata/pull/150/files#diff-7d938dbc255a08c2cfab1b4f1f8d1f6519c9312dd0a39d7793fa778474f1fbd1L135-R141 let _ = writeln!; } -
"cGF0Cg==", "MTFBQlVDUjZBMERMUTQ3aVphN3hPdV9qQmhTMkZUeHZ4ZE13OHczakxuZndsV2ZlZjc2cE53eHBWS2tiRUFwdnpmUk8zV0dDSUhicDFsT01aago=", ];likely benign A test fixture array of base64-encoded strings.Reasoning
The entries decode to short plain strings such as 'pat' and a test token-like value, in a fixture array. The base64 is used as test input data.
-
"cGF0Cg==", "MTFBQlVDUjZBMDJTOFYwMTM4YmQ0bV9uTXpueWhxZDBrcllROTQ5SERTeTI0dENKZ2lmdzIybDFSR2s1SE04QW8xTUVYQ1I0Q1YxYUdPRGpvZQo=", ];likely benign A test fixture array of base64-encoded values.Reasoning
The blobs are base64-encoded fixture strings in a test array, with a trailing newline typical of test data. Nothing indicates a live credential or executable payload.
-
// scripts, we can consider reverting https://github.com/astral-sh/uv/pull/5750/files#diff-969979506be03e89476feade2edebb4689a9c261f325988d3c7efc5e51de26d1L273-L277. canonicalize.unwrap_or_else -
let first = Named;dismissed A test requirement URL containing a package URL with a sha256 fragment in a Rust test file.Reasoning
A base64-like string inside a test fixture is a URL with a sha256 fragment and a hex-looking hash, not an encoded payload. The raw pass has a high false-positive rate, and this is a plain test URL.
-
] sdist = wheels = -
] sdist = wheels = -
, ] "# -
, ] -
let requirements_in = context.temp_dir.child; requirements_in.write_str?; uv_snapshot! -
sdist = wheels = -
, ] -
sdist = wheels = -
, ] -
version = "2.0.0" archive = ----- stderr ----- -
hint: You're on , but `a` only has wheels for the following platform: `macosx_10_0_ppc64`; consider adding "sys_platform == '[PLATFORM]' and platform_machine == '[MACHINE]'" to `tool.uv.required-environments` to ensure uv resolves to a version with compatible wheels "#); -
, , ] -
likely benign Documentation showing the official curl-pipe-to-sh install command for uv.
Reasoning
This is the standard documented installer one-liner for uv, a widely used and legitimate project. It is a markup prose example, so the pipe-to-shell pattern is the documented install method rather than hidden execution. Users are told the command, not made to run it covertly.
-
likely benign Documentation showing the wget-based uv install command piped to sh.
Reasoning
Same legitimate documented uv installer pattern using wget, shown as a shell example in documentation.
-
likely benign Project index docs showing the standard curl-pipe-to-sh uv installer.
Reasoning
Repeated official uv install one-liner in the project index docs. Legitimate installation guidance.
-
()dismissed Documentation example comparing pip and uv pip list output with diff.Reasoning
This is a diff of pip list and uv pip list output in a console example. The variable command name is just the diff utility in an illustrative shell snippet; there is no malicious payload.
-
likely benign Installer reference doc showing the official uv install script piped to sh with --help.
Reasoning
Documented uv installer one-liner with a help flag, in a console example. Legitimate install documentation.
-
if [; then elselikely benign Cargo wrapper script that execs either a configured real cargo binary or cargo itself.Reasoning
A wrapper that execs cargo auditable, using REAL_CARGO from the environment if set. This is a typical cargo wrapper pattern. The dynamic path is a configured tool path, not attacker-controlled input, though an env var could redirect it.
-
CC=gcc else -
else -
# Make mold the default linker -
if [; then -
MANIFEST="artifacts/dist-manifest.json" assets=() while ;likely benign Release script invoking a helper located relative to its own directory.Reasoning
The script calls a sibling helper resolved from SCRIPT_DIR, a normal repo-local pattern. SCRIPT_DIR is derived from the script's own location, so this is ordinary project tooling, not obfuscation.
-
if ; then filikely benign Test setup hook that runs a sibling codesign helper script.Reasoning
A test setup hook calls codesign-macos.sh from SCRIPT_DIR with arguments. This is a repo-local helper invocation typical of build tooling.
-
fi for; dolikely benign Release-testing script that installs built wheels and smoke-tests the binaries with --help.Reasoning
Installs wheels into a Python environment and then runs the installed binaries with --help. The command name comes from a loop over fixed names under a venv path set earlier in the script; the venv path is a locally created value, so this is ordinary release testing.
-
for; dolikely benign Loop running the installed uv binaries from a test virtualenv with --help.Reasoning
Runs the fixed binary names uv, uvx and uv-build from a virtualenv directory created by the same script. The variable path is a local build-test artifact, not untrusted input, so this is a normal smoke test.
Reproduce This Scan
Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
&&