@interchainjs/cosmos-types
Cosmos message codecs and query implementation generated by telescope for cosmos chains
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@interchainjs/utils | AI (dependencies): Same-org scoped sibling package from the same trusted publisher (zetazz/hyperweb-io); part of the interchainjs monorepo suite versioned together. | ai | |
| provenance | publisher-changed | AI (provenance): pyramation is a long-standing, highly-approved publisher in the @interchainjs/hyperweb-io ecosystem; transition from zetazz is a legitimate internal maintainer change within the same org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @interchainjs/encoding is a same-scope sibling package in the interchainjs monorepo; adding it is a normal internal refactor, not a suspicious third-party dependency. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver is due to monorepo lockstep versioning across @interchainjs/* packages. README link dump is typical of auto-generated Telescope output. Not indicative of spam or malice. | ai | |
| phantom-deps | phantom-dep:@interchainjs/utils | AI (phantom-deps): Sibling package in the same org scope; phantom import pattern is consistent with generated code in a monorepo. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 1.21.0 | 4 / 1 | |
| 1.20.0 | 4 / 1 | |
| 1.19.1 | 3 / 1 | |
| 1.19.0 | 3 / 1 | |
| 1.18.0 | 3 / 1 | |
| 1.17.8 | 3 / 1 | |
| 1.17.7 | 3 / 1 | |
| 1.17.6 | 3 / 1 | |
| 1.17.5 | 3 / 1 | |
| 1.17.4 | 3 / 0 | |
| 1.17.3 | 3 / 0 | |
| 1.17.2 | 3 / 0 | |
| 1.17.1 | 3 / 0 | |
| 1.17.0 | 3 / 0 | |
| 1.16.7 | 3 / 0 | |
| 1.16.6 | 3 / 0 | |
| 1.16.5 | 3 / 0 | |
| 1.16.4 | 3 / 0 | |
| 1.16.3 | 3 / 0 | |
| 1.16.2 | 3 / 0 | |
| 1.16.1 | 3 / 0 | |
| 1.16.0 | 3 / 0 | |
| 1.13.5 | 3 / 0 | |
| 1.13.0 | 3 / 0 | |
| 1.12.2 | 3 / 0 | |
| 1.12.1 | 3 / 0 | |
| 1.12.0 | 3 / 0 | |
| 1.11.18 | 3 / 0 | |
| 1.11.15 | 3 / 0 | |
| 1.11.14 | 3 / 0 | |
| 1.11.13 | 3 / 0 | |
| 1.11.12 | 3 / 0 | |
| 1.11.11 | 2 / 0 | |
| 1.11.10 | 2 / 0 | |
| 1.11.9 | 2 / 0 | |
| 1.11.8 | 2 / 0 | |
| 1.11.7 | 2 / 0 | |
| 1.11.6 | 2 / 0 | |
| 1.11.5 | 2 / 0 | |
| 1.11.4 | 2 / 0 | |
| 1.11.3 | 2 / 0 | |
| 1.11.2 | 2 / 0 | |
| 1.11.1 | 2 / 0 | |
| 1.11.0 | 2 / 0 | |
| 1.10.1 | 2 / 0 | |
| 1.10.0 | 2 / 0 | |
| 1.9.16 | 2 / 0 | |
| 1.9.15 | 2 / 0 | |
| 1.9.14 | 2 / 0 | |
| 1.9.13 | 2 / 0 | |
| 1.9.12 | 2 / 0 |
v1.21.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v1.19.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.19.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-02-17. This could indicate a legitimate maintainer transition or an account compromise.