@polkadot/extrinsics-codec
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @polkadot scoped packages, consistent with intra-ecosystem dependency management by the established Polkadot.js maintainer. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance availability; no provenance is expected for packages of this age from this publisher. | ai | |
| phantom-deps | phantom-dep:@polkadot/params | AI (phantom-deps): Same-org scoped package; phantom dep finding is a false positive for intra-org dependency declarations in the Polkadot.js ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Cosmetic issue in a well-established ecosystem package from a trusted publisher; not indicative of malice. | ai | |
| source-diff | encoded-string-file:encode/unchecked.spec.js | AI (source-diff): Long hex strings in spec files are expected test vectors for a codec library, not obfuscated payloads. This pattern is stable across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal documentation is typical for internal codec utility in established monorepo; not a spam indicator given publisher reputation. | ai | |
| phantom-deps | phantom-dep:@polkadot/util-keyring | AI (phantom-deps): Same-org monorepo dependency; phantom classification is expected in polkadot-js workspace structure. | ai | |
| phantom-deps | phantom-dep:@polkadot/extrinsics | AI (phantom-deps): Same-org monorepo dependency; phantom classification is expected in polkadot-js workspace structure. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is framework-scoped and loaded by convention; stable pattern in @polkadot packages. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): bn.js is a direct dependency used in crypto/codec contexts; phantom classification is a false positive for this package. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 0.25.3 | 6 / 0 | |
| 0.25.2 | 6 / 0 | |
| 0.25.1 | 6 / 0 | |
| 0.20.3 | 6 / 0 | |
| 0.20.2 | 6 / 0 | |
| 0.20.1 | 6 / 0 | |
| 0.19.5 | 6 / 0 | |
| 0.19.4 | 6 / 0 | |
| 0.19.3 | 6 / 0 | |
| 0.19.2 | 6 / 0 | |
| 0.19.1 | 6 / 0 | |
| 0.18.2 | 6 / 0 | |
| 0.17.28 | 6 / 0 | |
| 0.17.27 | 6 / 0 | |
| 0.17.26 | 6 / 0 | |
| 0.17.25 | 6 / 0 | |
| 0.17.24 | 6 / 0 | |
| 0.17.23 | 6 / 0 | |
| 0.17.22 | 6 / 0 | |
| 0.17.21 | 6 / 0 | |
| 0.17.20 | 6 / 0 | |
| 0.17.19 | 6 / 0 | |
| 0.17.18 | 6 / 0 | |
| 0.17.17 | 6 / 0 | |
| 0.17.16 | 6 / 0 | |
| 0.17.15 | 6 / 0 | |
| 0.17.14 | 6 / 0 | |
| 0.17.13 | 6 / 0 | |
| 0.17.12 | 6 / 0 | |
| 0.17.11 | 6 / 0 | |
| 0.17.10 | 6 / 0 | |
| 0.17.9 | 5 / 0 | |
| 0.17.8 | 5 / 0 | |
| 0.17.7 | 5 / 0 | |
| 0.17.6 | 5 / 0 | |
| 0.17.5 | 5 / 0 | |
| 0.17.4 | 5 / 0 | |
| 0.17.3 | 5 / 0 | |
| 0.17.2 | 5 / 0 | |
| 0.17.1 | 5 / 0 | |
| 0.16.15 | 5 / 0 | |
| 0.16.14 | 5 / 0 | |
| 0.16.13 | 5 / 0 | |
| 0.16.12 | 5 / 0 | |
| 0.16.11 | 5 / 0 | |
| 0.16.10 | 5 / 0 | |
| 0.16.9 | 5 / 0 | |
| 0.16.8 | 5 / 0 | |
| 0.16.7 | 5 / 0 | |
| 0.16.6 | 5 / 0 | |
| 0.16.5 | 5 / 0 |
v0.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.2
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.