@interchainjs/encoding
Encoding 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:readonly-date | AI (dependencies): readonly-date is a stable, well-known utility (read-only Date wrapper) at v1.0.0 with no security concerns; safe for this encoding package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from zetazz to pyramation reflects a legitimate org transition; pyramation is a highly trusted publisher (2681 approved, 0 rejected) managing the broader interchainjs ecosystem. | ai | |
| dependencies | unvetted-dep:@interchainjs/math | AI (dependencies): Sibling package in the same interchainjs monorepo, pinned to the same version. Expected dependency pattern for this package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages); no other risk signals elevate this to a concern for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.20.0 | 4 / 1 | |
| 1.18.1 | 4 / 1 | |
| 1.18.0 | 4 / 1 | |
| 1.17.8 | 4 / 1 | |
| 1.17.7 | 4 / 1 | |
| 1.17.6 | 4 / 1 | |
| 1.17.4 | 4 / 0 | |
| 1.17.3 | 4 / 0 | |
| 1.17.2 | 4 / 0 | |
| 1.17.1 | 4 / 0 | |
| 1.17.0 | 4 / 0 | |
| 1.16.7 | 4 / 0 | |
| 1.16.6 | 4 / 0 | |
| 1.11.5 | 4 / 0 | |
| 1.9.6 | 3 / 0 | |
| 1.9.5 | 3 / 0 |
v1.20.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
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 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.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.9.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.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.