smoldot — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

paritytech-ci

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/cjs/internals/bytecode/wasm0.js	AI (source-diff): smoldot ships Rust-compiled WASM as encoded strings in bytecode JS files — this is the package's core distribution mechanism, stable across all versions.	ai	2026/04/24
source-diff	encoded-string-file:dist/mjs/internals/bytecode/wasm0.js	AI (source-diff): smoldot ships Rust-compiled WASM as encoded strings in bytecode JS files — this is the package's core distribution mechanism, stable across all versions.	ai	2026/04/24
source-diff	encoded-string-file:dist/cjs/internals/bytecode/wasm1.js	AI (source-diff): smoldot ships Rust-compiled WASM as encoded strings in bytecode JS files — this is the package's core distribution mechanism, stable across all versions.	ai	2026/04/24
source-diff	encoded-string-file:dist/mjs/internals/bytecode/wasm1.js	AI (source-diff): smoldot ships Rust-compiled WASM as encoded strings in bytecode JS files — this is the package's core distribution mechanism, stable across all versions.	ai	2026/04/24
source-diff	encoded-string-file:dist/cjs/internals/bytecode/wasm2.js	AI (source-diff): smoldot ships Rust-compiled WASM as encoded strings in bytecode JS files — this is the package's core distribution mechanism, stable across all versions.	ai	2026/04/24
source-diff	encoded-string-file:dist/mjs/internals/bytecode/wasm2.js	AI (source-diff): smoldot ships Rust-compiled WASM as encoded strings in bytecode JS files — this is the package's core distribution mechanism, stable across all versions.	ai	2026/04/24

Versions (showing 48 of 48)

Version	Deps	Published
3.2.0	1 / 7	2026-06-02
3.1.4	1 / 7	2026-06-01
3.1.3	1 / 7	2026-05-13
3.1.2	1 / 7	2026-05-07
3.1.1	1 / 7	2026-04-22
3.1.0	1 / 7	2026-04-17
3.0.0	1 / 7	2026-04-10
2.0.40	1 / 7	2025-12-02
2.0.39	1 / 7	2025-09-15
2.0.38	1 / 7	2025-09-03
2.0.37	1 / 7	2025-08-29
2.0.36	1 / 7	2025-06-06
2.0.35	1 / 7	2025-05-27
2.0.34	1 / 7	2024-11-25
2.0.33	1 / 7	2024-11-19
2.0.32	1 / 7	2024-11-18
2.0.31	1 / 7	2024-11-08
2.0.30	1 / 7	2024-08-16
2.0.29	1 / 7	2024-06-17
2.0.28	1 / 7	2024-05-30
2.0.27	1 / 7	2024-05-29
2.0.26	1 / 7	2024-05-07
2.0.25	1 / 7	2024-04-29
2.0.24	1 / 7	2024-04-16
2.0.23	1 / 7	2024-03-20
2.0.22	1 / 7	2024-03-04
2.0.21	1 / 7	2024-02-06
2.0.20	1 / 7	2024-01-30
2.0.19	1 / 7	2024-01-26
2.0.18	1 / 7	2024-01-24
2.0.17	1 / 7	2024-01-17
2.0.16	1 / 7	2023-12-29
2.0.15	1 / 7	2023-12-20
2.0.14	1 / 7	2023-12-11
2.0.13	1 / 7	2023-11-28
2.0.12	1 / 7	2023-11-27
2.0.11	1 / 7	2023-11-27
2.0.10	1 / 7	2023-11-17
2.0.9	1 / 7	2023-11-16
2.0.8	1 / 7	2023-11-15
2.0.7	1 / 7	2023-11-02
2.0.6	1 / 7	2023-10-13
2.0.5	1 / 7	2023-10-12
2.0.4	1 / 7	2023-10-11
2.0.3	1 / 7	2023-09-28
2.0.2	1 / 7	2023-09-25
2.0.1	1 / 7	2023-09-08
2.0.0	1 / 7	2023-09-07

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: paritytech-ci.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: paritytech-ci.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.0

7 findings

HIGH Long encoded string in modified file: dist/cjs/internals/bytecode/wasm0.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/mjs/internals/bytecode/wasm0.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/cjs/internals/bytecode/wasm1.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/mjs/internals/bytecode/wasm1.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/cjs/internals/bytecode/wasm2.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/mjs/internals/bytecode/wasm2.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.