← Home

@pulumi/command

npm Repository Homepage

[![Actions Status](https://github.com/pulumi/pulumi-command/workflows/master/badge.svg)](https://github.com/pulumi/pulumi-command/actions) [![Slack](http://www.pulumi.com/images/docs/badges/slack.svg)](https://slack.pulumi.com) [![NPM version](https://bad

5
Versions
Apache-2.0
License
Yes
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

joeduffypulumi-bot

Keywords

pulumicommandcategory/utilitykind/native

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:install AI (install-scripts): Standard Pulumi plugin binary fetch pattern; stable and documented across all @pulumi/* provider packages. ai
typosquat typosquat.levenshtein:commander AI (typosquat): @pulumi/command is a scoped official Pulumi provider, not a typosquat of commander. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in install script to invoke pulumi plugin download; expected and benign for this package. ai

Versions (showing 5 of 5)

Version Deps Published
1.2.1 1 / 2
1.2.0 1 / 2
1.1.2 1 / 2
1.1.0 1 / 2
1.0.3 1 / 2

v1.2.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.

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.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.

v1.0.3

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.