← Home

@cosmjs/cosmwasm-launchpad

npm Repository

CosmWasm SDK for Launchpad

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

Maintainers

webmaster128willclarktechethanfrey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): webmaster128 is the primary CosmJS maintainer; transition from willclarktech (a contributor) was a legitimate handoff within the same project team in 2021. ai
phantom-deps phantom-dep:@cosmjs/utils AI (phantom-deps): @cosmjs/utils is a same-org monorepo sibling; indirect usage is a normal pattern in the CosmJS monorepo and not a security concern. ai

Versions (showing 9 of 9)

Version Deps Published
0.25.6 6 / 2
0.25.5 6 / 2
0.25.4 6 / 2
0.25.3 6 / 2
0.25.2 6 / 2
0.25.1 6 / 2
0.25.0 6 / 2
0.24.1 6 / 2
0.24.0 6 / 2

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

2 findings
HIGH Publisher changed: willclarktech → webmaster128 (on 2021-05-31) provenance

This version was published by a different npm account than previous versions on 2021-05-31. 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.3

2 findings
HIGH Publisher changed: willclarktech → webmaster128 (on 2021-05-18) provenance

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.

LOW No provenance attestation provenance

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

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
LOW No provenance attestation provenance

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. Only ~12% of npm packages have provenance, so this is common but not ideal.