@cosmjs/amino — Greenflagged

Helpers for Amino based signing.

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	no-provenance	AI (provenance): Package predates Sigstore provenance adoption; publisher has strong track record. Low risk for this established ecosystem package.	ai	2026/04/22
provenance	missing-githead	AI (provenance): CosmJS is a well-established project; missing gitHead reflects a publish environment change, not a supply chain compromise. Publisher has 168 approved packages and 0 rejections.	ai	2026/04/22
source-diff	encoded-string-file:build/testutils.spec.js	AI (source-diff): Long strings are Bech32-encoded public keys used as test fixtures in a Cosmos cryptography library — not obfuscated payloads.	ai	2026/04/22
source-diff	encoded-string-file:build/testutils.spec.d.ts	AI (source-diff): Long strings are Bech32-encoded public keys in TypeScript declaration test fixtures — not obfuscated payloads.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): Signals (short README, no keywords) are cosmetic and not indicative of malicious intent for this well-known CosmJS library.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): Publisher change from webmaster128 to willclarktech occurred in 2021 as a legitimate CosmJS org transition; willclarktech has 86 approved packages and 0 rejected since then.	ai	2026/04/22
dependencies	unvetted-dep:@cosmjs/encoding	AI (dependencies): Sibling package from the same CosmJS monorepo, published by the same trusted maintainer.	ai	2026/04/21
dependencies	unvetted-dep:@cosmjs/crypto	AI (dependencies): Sibling package from the same CosmJS monorepo, published by the same trusted maintainer.	ai	2026/04/21
dependencies	unvetted-dep:@cosmjs/utils	AI (dependencies): Sibling package from the same CosmJS monorepo, published by the same trusted maintainer.	ai	2026/04/21
dependencies	unvetted-dep:@cosmjs/math	AI (dependencies): Sibling package from the same CosmJS monorepo, published by the same trusted maintainer.	ai	2026/04/21
typosquat	typosquat.levenshtein:pino	AI (typosquat): @cosmjs/amino is a scoped Cosmos blockchain package with no relation to 'pino'. The Levenshtein match is purely coincidental; this is a stable false positive for this package.	ai	2026/04/21

Versions (showing 60 of 60)

Show 4 prereleases

Version	Deps	Published
0.39.0	4 / 21	2026-05-04
0.38.1	4 / 21	2025-12-31
0.38.0	4 / 21	2025-12-30
0.37.1	4 / 21	2025-12-31
0.37.0	4 / 21	2025-10-29
0.36.2	4 / 21	2025-10-24
0.36.1	4 / 21	2025-10-02
0.36.0	4 / 21	2025-08-14
0.35.2	4 / 21	2025-10-29
0.35.1	4 / 21	2025-10-22
0.35.0	4 / 21	2025-08-13
0.34.1	4 / 23	2025-10-22
0.34.0	4 / 23	2025-07-11
0.33.1	4 / 32	2025-03-13
0.33.0	4 / 32	2025-01-15
0.32.4	4 / 32	2024-06-26
0.32.3	4 / 32	2024-03-08
0.32.2	4 / 32	2023-12-19
0.32.1	4 / 32	2023-12-04
0.32.0	4 / 32	2023-11-23
0.31.3	4 / 32	2023-10-25
0.31.2	4 / 32	2023-10-24
0.31.1	4 / 32	2023-08-21
0.31.0	4 / 32	2023-06-22
0.30.1	4 / 32	2023-03-22
0.30.0	4 / 32	2023-03-09
0.29.5	4 / 32	2022-12-07
0.29.4	4 / 32	2022-11-15
0.29.3	4 / 32	2022-10-25
0.29.2	4 / 32	2022-10-13
0.29.1	4 / 32	2022-10-09
0.29.0	4 / 32	2022-09-15
0.28.13	4 / 32	2022-08-18
0.28.11	4 / 32	2022-07-13
0.28.10	4 / 32	2022-06-29
0.28.9	4 / 32	2022-06-21
0.28.7	4 / 32	2022-06-14
0.28.6	4 / 32	2022-06-14
0.28.4	4 / 32	2022-04-15
0.28.3	4 / 33	2022-04-11
0.28.2	4 / 33	2022-04-07
0.28.1	4 / 33	2022-03-30
0.28.0	4 / 33	2022-03-17
0.27.1	4 / 34	2022-01-26
0.27.0	4 / 34	2022-01-10
0.26.8	4 / 32	2022-06-21
0.26.6	4 / 34	2022-01-10
0.26.5	4 / 34	2021-11-20
0.26.4	4 / 34	2021-10-28
0.26.3	4 / 34	2021-10-25
0.26.2	4 / 34	2021-10-12
0.26.1	4 / 34	2021-09-30
0.26.0	4 / 34	2021-08-24
0.25.6	4 / 0	2021-07-26
0.25.5	4 / 0	2021-06-23
0.25.4	4 / 0	2021-05-31
0.25.3	4 / 0	2021-05-18
0.25.2	4 / 0	2021-05-11
0.25.1	4 / 0	2021-05-06
0.25.0	4 / 0	2021-05-05

v0.39.0

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.37.0

1 finding

LOW No provenance attestation provenance

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

v0.36.2

1 finding

LOW No provenance attestation provenance

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

v0.36.1

1 finding

LOW No provenance attestation provenance

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

v0.36.0

1 finding

LOW No provenance attestation provenance

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

v0.35.2

1 finding

LOW No provenance attestation provenance

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

v0.35.1

1 finding

LOW No provenance attestation provenance

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

v0.35.0

1 finding

LOW No provenance attestation provenance

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

v0.34.1

1 finding

LOW No provenance attestation provenance

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

v0.34.0

1 finding

LOW No provenance attestation provenance

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

v0.33.1

2 findings

HIGH Publisher changed: webmaster128 → kiki-skip (on 2025-03-13) provenance

This version was published by a different npm account than previous versions on 2025-03-13. 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.33.0

1 finding

LOW No provenance attestation provenance

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

v0.32.4

1 finding

LOW No provenance attestation provenance

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

v0.32.3

1 finding

LOW No provenance attestation provenance

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

v0.32.2

1 finding

LOW No provenance attestation provenance

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

v0.32.1

1 finding

LOW No provenance attestation provenance

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

v0.32.0

1 finding

LOW No provenance attestation provenance

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

v0.31.3

1 finding

LOW No provenance attestation provenance

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

v0.31.2

1 finding

LOW No provenance attestation provenance

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

v0.31.1

1 finding

LOW No provenance attestation provenance

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

v0.31.0

1 finding

LOW No provenance attestation provenance

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

v0.30.1

1 finding

LOW No provenance attestation provenance

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

v0.30.0

1 finding

LOW No provenance attestation provenance

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

v0.29.5

1 finding

LOW No provenance attestation provenance

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

v0.29.4

1 finding

LOW No provenance attestation provenance

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

v0.29.3

1 finding

LOW No provenance attestation provenance

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

v0.29.2

1 finding

LOW No provenance attestation provenance

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

v0.29.1

1 finding

LOW No provenance attestation provenance

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

v0.29.0

1 finding

LOW No provenance attestation provenance

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

v0.28.13

1 finding

LOW No provenance attestation provenance

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

v0.28.11

1 finding

LOW No provenance attestation provenance

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

v0.28.10

1 finding

LOW No provenance attestation provenance

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

v0.28.9

1 finding

LOW No provenance attestation provenance

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

v0.28.7

1 finding

LOW No provenance attestation provenance

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

v0.28.6

1 finding

LOW No provenance attestation provenance

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

v0.28.4

1 finding

LOW No provenance attestation provenance

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

v0.28.3

1 finding

LOW No provenance attestation provenance

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

v0.28.2

1 finding

LOW No provenance attestation provenance

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

v0.28.1

1 finding

LOW No provenance attestation provenance

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

v0.28.0

1 finding

LOW No provenance attestation provenance

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

v0.27.1

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.

v0.27.0

3 findings

HIGH Long encoded string in modified file: build/testutils.spec.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: build/testutils.spec.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.26.8

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

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

HIGH Long encoded string in modified file: build/testutils.spec.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: build/testutils.spec.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.26.5

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

HIGH Long encoded string in modified file: build/testutils.spec.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: build/testutils.spec.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.26.4

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

HIGH Long encoded string in modified file: build/testutils.spec.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: build/testutils.spec.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.26.3

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

HIGH Long encoded string in modified file: build/testutils.spec.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: build/testutils.spec.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.26.2

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

HIGH Long encoded string in modified file: build/testutils.spec.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: build/testutils.spec.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.26.1

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

HIGH Long encoded string in modified file: build/testutils.spec.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: build/testutils.spec.d.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

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

1 finding

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

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