← Home

@vscode/sudo-prompt

npm Repository Homepage

Run a command using sudo, prompting the user with an OS dialog if necessary

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kaimaetzellszomorualexandrudimasbattenjoaomoreno.msmicrosoft1esrebornixvscode-bot

Keywords

sudoosdialogpromptcommandexecuser access controlUACprivilegesadministrativeelevaterun as administrator

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:index.js AI (source-diff): The APPLET base64 string is a documented macOS applet bundle embedded intentionally; the code comments explain its purpose and update procedure. Stable for this package. ai
semgrep semgrep:child-process-import AI (semgrep): child_process is core to this package's purpose: executing commands with elevated sudo privileges. Expected and legitimate. ai

Versions (showing 3 of 3)

Version Deps Published
9.3.2 0 / 0
9.3.1 0 / 0
9.3.0 0 / 0

v9.3.2

4 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoft1es.

HIGH Publisher changed: bpasero → microsoft1es (on 2026-01-08) provenance

This version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.

HIGH Long encoded string in modified file: index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.