@localstack/lstk_windows_amd64 Apache-2.0 28 versions

@localstack/lstk_windows_amd64

npm

LocalStack CLI v2 - Start and manage LocalStack emulators

28

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.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): New publisher has clean track record; content unchanged vs prior approved version.	ai	2026/07/09
bogus-package	bogus-package	AI (bogus-package): Expected for a minimal platform-binary sub-package under official @localstack scope.	ai	2026/07/09
npm-metadata	bundled-binaries	AI (npm-metadata): Package exists solely to distribute the LocalStack CLI Windows binary; bundling lstk.exe is its documented purpose.	ai	2026/05/04

Versions (showing 28 of 28)

Version	Deps	Published
0.17.1	0 / 0	2026-07-16
0.17.0	0 / 0	2026-07-14
0.16.0	0 / 0	2026-07-09
0.15.0	0 / 0	2026-07-02
0.14.1	0 / 0	2026-06-29
0.14.0	0 / 0	2026-06-25
0.13.0	0 / 0	2026-06-18
0.12.0	0 / 0	2026-06-11
0.11.0	0 / 0	2026-06-04
0.10.0	0 / 0	2026-05-28
0.8.0	0 / 0	2026-05-14
0.7.1	0 / 0	2026-05-07
0.7.0	0 / 0	2026-05-07
0.6.0	0 / 0	2026-04-30
0.5.8	0 / 0	2026-04-23
0.5.7	0 / 0	2026-04-16
0.5.6	0 / 0	2026-04-09
0.5.5	0 / 0	2026-04-02
0.5.4	0 / 0	2026-03-26
0.5.3	0 / 0	2026-03-23
0.5.2	0 / 0	2026-03-19
0.5.1	0 / 0	2026-03-17
0.5.0	0 / 0	2026-03-16
0.4.1	0 / 0	2026-03-12
0.4.0	0 / 0	2026-03-11
0.3.1	0 / 0	2026-03-09
0.3.0	0 / 0	2026-03-05
0.2.3	0 / 0	2026-03-04

v0.17.1

1 finding

LOW No provenance attestation provenance

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

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