← Home

@localstack/lstk_windows_arm64

npm

LocalStack CLI v2 - Start and manage LocalStack emulators

27
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

skyrpexsilv-ioluca.localstackjoe4devdominikschubertstefanie_localstackanisa_oshaficarole-lavillonniereharshcasperwhummerbentsku

Keywords

localstackcliawsemulatordocker

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): New publisher has strong track record (20 approved, 0 rejected); likely org maintainer rotation. ai
maintainer-change maintainer-added AI (maintainer-change): Consistent with publisher change; same trusted account. ai
npm-metadata bundled-binaries AI (npm-metadata): lstk.exe is the intentional CLI binary for this platform-specific distribution package under the @localstack org. ai

Versions (showing 27 of 27)

Version Deps Published
0.17.0 0 / 0
0.16.0 0 / 0
0.15.0 0 / 0
0.14.1 0 / 0
0.14.0 0 / 0
0.13.0 0 / 0
0.12.0 0 / 0
0.11.0 0 / 0
0.10.0 0 / 0
0.8.0 0 / 0
0.7.1 0 / 0
0.7.0 0 / 0
0.6.0 0 / 0
0.5.8 0 / 0
0.5.7 0 / 0
0.5.6 0 / 0
0.5.5 0 / 0
0.5.4 0 / 0
0.5.3 0 / 0
0.5.2 0 / 0
0.5.1 0 / 0
0.5.0 0 / 0
0.4.1 0 / 0
0.4.0 0 / 0
0.3.1 0 / 0
0.3.0 0 / 0
0.2.3 0 / 0

v0.17.0

1 finding
LOW No provenance attestation provenance

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

v0.16.0

2 findings
HIGH Publisher changed: silv-io → anisa_oshafi (on 2026-07-09) provenance

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

LOW No provenance attestation provenance

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

v0.15.0

2 findings
HIGH Publisher changed: silv-io → anisa_oshafi (on 2026-07-02) provenance

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

LOW No provenance attestation provenance

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

v0.14.1

2 findings
HIGH Publisher changed: silv-io → anisa_oshafi (on 2026-06-29) provenance

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

LOW No provenance attestation provenance

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

v0.14.0

2 findings
HIGH Publisher changed: silv-io → anisa_oshafi (on 2026-06-25) provenance

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

LOW No provenance attestation provenance

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

v0.5.5

1 finding
LOW No provenance attestation provenance

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

v0.5.4

1 finding
LOW No provenance attestation provenance

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

v0.5.3

1 finding
LOW No provenance attestation provenance

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

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

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