← Home

@heroku-cli/command

npm Repository Homepage
13
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

heroku-front-endijanakntonollierelzoonacmarcojoscbaxtersfdhagberg-sfjondaniel-sfdcbrittany.jonesnilamuthukpremkumarcv88xx-sfdc-npmbeanieboisbosio_sfptemporinitcareysmith-sfdcjlopezdanrobinson.mrdagg-herok80bowmansheax0rdpark.herokudaniel.brightabhinavkouleblackk.plentykdreyerorenmbuschherokubeckychenmarsnlanattavlazukawchrisjohnsonlucaszhoupfuentemimengkomminenisarassassinlmckenziejwadsworthsfzli-sfkumardinesh2vjohnekharlowsfcsinghaus-sfdcheroku-johnnymichael.malaveerika.wallacevalluri056

Keywords

heroku

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:commander AI (typosquat): Scoped @heroku-cli/command is the official Heroku CLI base class, not a typosquat of commander. ai

Versions (showing 13 of 13)

Version Deps Published
12.3.3 9 / 24
12.3.2 9 / 24
12.3.1 9 / 24
12.3.0 11 / 31
12.2.3 9 / 24
12.2.2 9 / 27
12.2.1 9 / 27
12.2.0 9 / 29
12.1.3 9 / 29
12.1.2 9 / 29
12.1.1 9 / 29
12.1.0 9 / 29
12.0.2 9 / 29

v12.3.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.3.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.3.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.2.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.2.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.1.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.1.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v12.1.1

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.

v12.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.

v12.0.2

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.