@polkadot/primitives
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:codec/block/encode.spec.js | AI (source-diff): Long byte array in a test file is a Uint8Array expected-value fixture for codec unit tests, not an obfuscated payload. Normal pattern for serialization libraries. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Type definitions package for Polkadot network; size growth reflects addition of new type definitions as the network evolves. No malicious indicators present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @babel/runtime is a canonical Babel helper package; adding it is a routine Babel 7 migration step with no malicious indicators for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established polkadot-js package predating Sigstore provenance; trusted publisher with 2313 approved packages and 0 rejections. | ai |
Versions (showing 14 of 214)
| Version | Deps | Published |
|---|---|---|
| 0.4.7 | 2 / 1 | |
| 0.4.6 | 2 / 1 | |
| 0.4.5 | 2 / 1 | |
| 0.4.4 | 2 / 1 | |
| 0.4.3 | 2 / 1 | |
| 0.4.2 | 2 / 1 | |
| 0.4.1 | 2 / 1 | |
| 0.3.1 | 2 / 1 | |
| 0.2.1 | 2 / 1 | |
| 0.1.5 | 0 / 1 | |
| 0.1.4 | 0 / 1 | |
| 0.1.3 | 0 / 1 | |
| 0.1.2 | 0 / 1 | |
| 0.1.1 | 0 / 1 |
v0.4.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.
v0.4.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.
v0.4.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.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.