@cosmjs/launchpad — Greenflagged

A client library for the Cosmos SDK 0.37 (cosmoshub-3), 0.38 and 0.39 (Launchpad)

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

webmaster128willclarktechethanfrey

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Trusted long-standing CosmJS maintainer (webmaster128); missing gitHead reflects a build environment change, not a supply chain concern for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance adoption; publisher has 1026 approved / 0 rejected packages and is the canonical CosmJS maintainer.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): willclarktech is a long-standing npm publisher (2452 days, 984 approved packages) and is listed as a contributor in package.json. This is a documented team transition within the CosmJS project.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): willclarktech is a known, trusted contributor to the CosmJS ecosystem with a strong track record. The addition reflects a legitimate maintainer transition.	ai	2026/04/24

Versions (showing 25 of 25)

Version	Deps	Published
0.27.1	7 / 36	2022-01-26
0.27.0	7 / 36	2022-01-10
0.26.6	7 / 36	2022-01-10
0.26.5	7 / 36	2021-11-20
0.26.4	7 / 36	2021-10-28
0.26.3	7 / 36	2021-10-25
0.26.2	7 / 36	2021-10-12
0.26.1	7 / 36	2021-09-30
0.26.0	7 / 36	2021-08-24
0.25.6	7 / 1	2021-07-26
0.25.5	7 / 1	2021-06-23
0.25.4	7 / 1	2021-05-31
0.25.3	7 / 1	2021-05-18
0.25.2	7 / 1	2021-05-11
0.25.1	7 / 1	2021-05-06
0.25.0	7 / 1	2021-05-05
0.24.1	6 / 1	2021-03-12
0.24.0	6 / 1	2021-03-11
0.23.2	5 / 1	2021-01-06
0.23.1	5 / 1	2020-10-27
0.23.0	5 / 1	2020-10-09
0.22.3	5 / 1	2020-09-15
0.22.2	5 / 1	2020-08-11
0.22.1	5 / 1	2020-08-11
0.22.0	6 / 1	2020-08-03

v0.27.1

1 finding

LOW No provenance attestation provenance

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

v0.27.0

1 finding

LOW No provenance attestation provenance

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

v0.26.6

1 finding

LOW No provenance attestation provenance

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

v0.26.5

1 finding

INFO No provenance attestation provenance

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

v0.26.4

2 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: webmaster128.

LOW No provenance attestation provenance

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

v0.26.3

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

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

v0.26.2

2 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: webmaster128.

LOW No provenance attestation provenance

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

v0.26.1

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

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

v0.26.0

2 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: webmaster128.

LOW No provenance attestation provenance

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

v0.25.6

1 finding

LOW No provenance attestation provenance

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

v0.25.5

1 finding

LOW No provenance attestation provenance

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

v0.25.4

1 finding

LOW No provenance attestation provenance

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

v0.25.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: willclarktech → webmaster128 (on 2021-05-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-05-18. This could indicate a legitimate maintainer transition or an account compromise.

v0.25.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: webmaster128 → willclarktech (on 2021-05-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-05-11. This could indicate a legitimate maintainer transition or an account compromise.

v0.25.1

1 finding

LOW No provenance attestation provenance

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

v0.25.0

1 finding

LOW No provenance attestation provenance

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

v0.24.1

1 finding

INFO No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.2

2 findings

HIGH Publisher changed: webmaster128 → willclarktech (on 2021-01-06) provenance

This version was published by a different npm account than previous versions on 2021-01-06. 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.23.1

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.3

1 finding

LOW No provenance attestation provenance

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

v0.22.2

1 finding

LOW No provenance attestation provenance

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

v0.22.1

1 finding

LOW No provenance attestation provenance

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

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