Is this PowerShell installer command safe to run?

If you do not specifically need uv, don’t install it just because another application casually requests it. Confirm that Open Jarvis comes from a source you trust and that uv is its documented dependency. Running a script with elevated privileges would increase the risk, so avoid administrator PowerShell unless the official installation instructions genuinely require it.

The script appears to be an installer for uv, Astral’s Python package manager. It detects your Windows architecture, downloads the matching uv archive, extracts the binaries, and may add the installation directory to your PATH. It also stores installation metadata and can install an updater. Nothing in the reviewed portion looks obviously malicious, but you should only run it if uv is actually required by the software you’re installing.

The bigger issue is the command pattern, not necessarily this particular script. `irm ... | iex` downloads whatever the server returns and executes it immediately, while `-ExecutionPolicy Bypass` avoids the usual PowerShell script-policy restriction. Even if the site is trustworthy today, a compromised website, altered DNS, malicious proxy, or compromised account could change the script later.

You can inspect the script without executing it by saving or copying the response first, for example: $iwrResult = Invoke-WebRequest https://astral.sh/uv/install.ps1 $iwrResult.Content | Set-Clipboard Review the complete script, verify that its download URLs and version match the project’s official documentation, and consider checking published hashes or signatures for the downloaded release. Also remember that the installer changes PATH and writes configuration under your user profile or registry, so review those parts before proceeding.