@interchainjs/pubkey
Pubkey helpers for blockchain projects
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@interchainjs/cosmos-types | AI (phantom-deps): Same-org dependency likely re-exported or transitively used; common pattern in monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@interchainjs/math | AI (phantom-deps): Same-org dependency likely re-exported or transitively used; common pattern in monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@interchainjs/amino | AI (phantom-deps): Same-org dependency likely re-exported or transitively used; common pattern in monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@interchainjs/encoding | AI (phantom-deps): Same-org dependency likely re-exported or transitively used; common pattern in monorepo-style packages. | ai | |
| dependencies | unvetted-dep:@interchainjs/encoding | AI (dependencies): Sibling package in the same @interchainjs monorepo, co-versioned. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@interchainjs/cosmos-types | AI (dependencies): Sibling package in the same @interchainjs monorepo, co-versioned. Not a third-party risk. | ai | |
| provenance | publisher-changed | AI (provenance): pyramation is the established hyperweb-io/interchainjs org lead with 2683 approved versions; transition from zetazz is a legitimate maintainer handoff within the same org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and empty entry point are artifacts of monorepo versioning and TypeScript barrel exports in the interchainjs monorepo; not indicative of spam or malice. | ai | |
| phantom-deps | phantom-dep:@interchainjs/types | AI (phantom-deps): @interchainjs/types is declared in dependencies and used for TypeScript types; phantom-dep false positive for type-only imports in TS monorepos. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 1.21.0 | 5 / 1 | |
| 1.20.0 | 5 / 1 | |
| 1.19.2 | 5 / 1 | |
| 1.19.1 | 5 / 1 | |
| 1.19.0 | 5 / 1 | |
| 1.18.0 | 5 / 1 | |
| 1.17.8 | 5 / 1 | |
| 1.17.7 | 5 / 1 | |
| 1.17.6 | 5 / 1 | |
| 1.17.5 | 5 / 1 | |
| 1.17.4 | 5 / 0 | |
| 1.17.3 | 5 / 0 | |
| 1.17.2 | 5 / 0 | |
| 1.17.0 | 5 / 0 | |
| 1.16.7 | 5 / 0 | |
| 1.16.6 | 5 / 0 | |
| 1.16.5 | 5 / 0 | |
| 1.16.4 | 5 / 0 | |
| 1.16.3 | 5 / 0 | |
| 1.16.2 | 5 / 0 | |
| 1.16.1 | 5 / 0 | |
| 1.16.0 | 5 / 0 | |
| 1.13.5 | 5 / 0 | |
| 1.13.0 | 5 / 0 | |
| 1.12.2 | 5 / 0 | |
| 1.12.1 | 5 / 0 | |
| 1.12.0 | 5 / 0 | |
| 1.11.18 | 5 / 0 | |
| 1.11.15 | 5 / 0 | |
| 1.11.14 | 5 / 0 | |
| 1.11.13 | 5 / 0 | |
| 1.11.12 | 5 / 0 | |
| 1.11.11 | 5 / 0 | |
| 1.11.10 | 5 / 0 | |
| 1.11.9 | 5 / 0 | |
| 1.11.8 | 5 / 0 | |
| 1.11.7 | 5 / 0 | |
| 1.11.6 | 5 / 0 | |
| 1.11.5 | 5 / 0 | |
| 1.11.4 | 5 / 0 | |
| 1.11.3 | 5 / 0 | |
| 1.11.2 | 5 / 0 | |
| 1.11.1 | 5 / 0 | |
| 1.11.0 | 5 / 0 | |
| 1.10.1 | 5 / 0 | |
| 1.10.0 | 5 / 0 | |
| 1.9.16 | 5 / 0 | |
| 1.9.15 | 5 / 0 | |
| 1.9.14 | 5 / 0 | |
| 1.9.13 | 5 / 0 | |
| 1.9.12 | 5 / 0 | |
| 1.9.11 | 5 / 0 | |
| 1.9.10 | 5 / 0 | |
| 1.9.8 | 5 / 0 | |
| 1.9.7 | 5 / 0 | |
| 1.9.6 | 5 / 0 | |
| 1.9.5 | 5 / 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.