@cosmjs/cosmwasm — Greenflagged

CosmWasm SDK

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

webmaster128kiki-skip

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): willclarktech is a named contributor in package.json and a long-standing CosmJS team member; the publisher transition from webmaster128 is a documented legitimate handoff, not a compromise.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Cosmetic signals only (short README, no keywords); @cosmjs/cosmwasm is a well-known CosmWasm SDK package in the cosmos/cosmjs monorepo.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): kiki-skip added as part of normal CosmJS team evolution; primary publisher webmaster128 unchanged with strong track record.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): willclarktech and ethanfrey removal consistent with team changes in a large open-source monorepo; no takeover indicators.	ai	2026/04/23
source-diff	source-size-tripled	AI (source-diff): Size increase reflects a major version rewrite from a thin launchpad wrapper to a full CosmWasm SDK with 9 legitimate first-party dependencies.	ai	2026/04/23

Versions (showing 23 of 23)

Version	Deps	Published
0.39.0	9 / 23	2026-05-04
0.38.1	9 / 23	2025-12-31
0.38.0	9 / 23	2025-12-30
0.25.6	1 / 0	2021-07-26
0.25.5	1 / 0	2021-06-23
0.25.4	1 / 0	2021-05-31
0.25.3	1 / 0	2021-05-18
0.25.2	1 / 0	2021-05-11
0.25.1	1 / 0	2021-05-06
0.25.0	1 / 0	2021-05-05
0.24.1	1 / 0	2021-03-12
0.24.0	1 / 0	2021-03-11
0.23.2	6 / 2	2021-01-06
0.23.1	6 / 2	2020-10-27
0.23.0	7 / 2	2020-10-09
0.22.3	7 / 2	2020-09-15
0.22.2	7 / 2	2020-08-11
0.22.1	7 / 2	2020-08-11
0.22.0	8 / 2	2020-08-03
0.21.1	8 / 2	2020-07-01
0.21.0	8 / 2	2020-06-28
0.20.1	8 / 2	2020-06-30
0.20.0	8 / 2	2020-06-10

v0.39.0

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 → kiki-skip (on 2026-05-04) provenance

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

v0.38.0

1 finding

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

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

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.

LOW No provenance attestation provenance

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

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

LOW No provenance attestation provenance

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

v0.24.0

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-03-11) provenance

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

v0.23.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-01-06) provenance

[Accepted risk] 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.

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.1

1 finding

LOW No provenance attestation provenance

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

v0.21.0

1 finding

LOW No provenance attestation provenance

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

v0.20.1

1 finding

LOW No provenance attestation provenance

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

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