@interchainjs/crypto
Cryptography resources 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:libsodium-wrappers-sumo | AI (phantom-deps): libsodium-wrappers-sumo is a legitimate cryptographic library; phantom-dep reflects indirect usage. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): bn.js is a legitimate cryptographic dependency; phantom-dep pattern is common in crypto libraries with indirect imports. | ai | |
| phantom-deps | phantom-dep:elliptic | AI (phantom-deps): elliptic is a standard ECC library; phantom-dep pattern reflects indirect usage through re-exports. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): @noble/hashes is a legitimate cryptographic dependency; phantom-dep is stable for this package. | ai | |
| phantom-deps | phantom-dep:@interchainjs/math | AI (phantom-deps): Internal monorepo dependency; phantom-dep pattern is expected for same-org scoped packages. | ai | |
| phantom-deps | phantom-dep:@interchainjs/utils | AI (phantom-deps): Internal monorepo dependency; phantom-dep pattern is expected for same-org scoped packages. | ai | |
| phantom-deps | phantom-dep:@interchainjs/encoding | AI (phantom-deps): Internal monorepo dependency; phantom-dep pattern is expected for same-org scoped packages. | ai | |
| dependencies | unvetted-dep:libsodium-wrappers-sumo | AI (dependencies): libsodium-wrappers-sumo is a well-known, widely-used cryptographic library. Its use in a blockchain crypto package is expected and appropriate; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): pyramation is a highly trusted publisher (2694 approved/0 rejected, 2767 days history) taking over from zetazz within the same hyperweb-io/interchainjs ecosystem — consistent with a legitimate org-level maintainer transition. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 57 versions and strong publisher track record; lack of Sigstore provenance is a minor hygiene issue, not a security risk for this package. | ai | |
| dependencies | unvetted-dep:@interchainjs/math | AI (dependencies): First-party sibling package in the interchainjs monorepo; always published in lockstep with this package. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@interchainjs/utils | AI (dependencies): First-party sibling package in the interchainjs monorepo; always published in lockstep with this package. Not an independent risk. | ai | |
| dependencies | unvetted-dep:@interchainjs/encoding | AI (dependencies): First-party sibling package in the interchainjs monorepo; always published in lockstep with this package. Not an independent risk. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): elliptic is a well-established cryptographic library widely used in blockchain ecosystems; its use here is expected and stable across versions of this package. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): @interchainjs/crypto is a scoped blockchain crypto utility with no resemblance to bcrypt in purpose or branding; the levenshtein match is a false positive stable across all versions. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.21.0 | 7 / 4 | |
| 1.19.2 | 7 / 3 | |
| 1.17.0 | 7 / 2 | |
| 1.16.7 | 7 / 2 | |
| 1.16.6 | 7 / 2 | |
| 1.16.0 | 7 / 2 | |
| 1.13.0 | 7 / 2 | |
| 1.12.0 | 7 / 2 | |
| 1.11.10 | 7 / 2 | |
| 1.11.5 | 7 / 2 | |
| 1.11.4 | 7 / 2 | |
| 1.11.3 | 7 / 2 | |
| 1.11.0 | 7 / 2 | |
| 1.9.15 | 7 / 2 | |
| 1.9.13 | 7 / 2 | |
| 1.9.5 | 7 / 2 |
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.19.2
2 findings[Accepted risk] Package 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-02-27. This could indicate a legitimate maintainer transition or an account compromise.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.