@miden-sdk/miden-sdk — Greenflagged

Miden Wasm SDK

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

domi2000wiktor.midenhuna1

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dist/st/Cargo-CgOCogcE.js	AI (source-diff): Same Dexie.js bundle pattern; stable false positive for this package.	ai	2026/05/23
source-diff	net-exec-file:dist/mt/workers/Cargo-DcB9UMnw-w3wXmKCr.js	AI (source-diff): Same Dexie.js bundle pattern; stable false positive for this package.	ai	2026/05/23
source-diff	net-exec-file:dist/mt/Cargo-DcB9UMnw.js	AI (source-diff): Same Dexie.js bundle pattern; stable false positive for this package.	ai	2026/05/23
source-diff	net-exec-file:dist/st/workers/Cargo-CgOCogcE-dIBKWd7c.js	AI (source-diff): Bundled Dexie.js (declared dep) in Rollup output; CommonJS wrapper triggers net-exec heuristic but is benign.	ai	2026/05/23
source-diff	net-exec-file:dist/mt/workers/web-client-methods-worker.js	AI (source-diff): Documented wasm-bindgen worker initialization pattern; no malicious network calls.	ai	2026/05/13
source-diff	net-exec-file:dist/st/workers/web-client-methods-worker.js	AI (source-diff): Documented wasm-bindgen worker initialization pattern; no malicious network calls.	ai	2026/05/13
source-diff	net-exec-file:dist/st/Cargo-jOTNoFyS.js	AI (source-diff): Bundled Dexie.js + wasm-bindgen glue; standard rollup output for this WASM SDK.	ai	2026/05/13
source-diff	net-exec-file:dist/mt/workers/Cargo-DKB2aRX--C6T4l3AF.js	AI (source-diff): Bundled Dexie.js + wasm-bindgen glue; standard rollup output for this WASM SDK.	ai	2026/05/13
source-diff	net-exec-file:dist/mt/Cargo-DKB2aRX-.js	AI (source-diff): Bundled Dexie.js + wasm-bindgen glue; standard rollup output for this WASM SDK.	ai	2026/05/13
source-diff	net-exec-file:dist/st/workers/Cargo-jOTNoFyS-DRTcF6wf.js	AI (source-diff): Bundled Dexie.js + wasm-bindgen glue; standard rollup output for this WASM SDK.	ai	2026/05/13
phantom-deps	phantom-dep:glob	AI (phantom-deps): Runtime dependency used indirectly; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@rollup/plugin-typescript	AI (phantom-deps): Framework-scoped build tool loaded by convention; stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:dexie	AI (phantom-deps): Runtime dependency; stable false positive for this package.	ai	2026/04/29

Versions (showing 7 of 7)

Version	Deps	Published
0.14.10	2 / 15	2026-05-19
0.14.9	2 / 15	2026-05-13
0.14.5	3 / 20	2026-04-27
0.14.4	3 / 20	2026-04-20
0.14.3	3 / 20	2026-04-16
0.14.2	3 / 20	2026-04-16
0.14.1	3 / 20	2026-04-14

v0.14.10

6 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: GitHub Actions.

HIGH New file with network + code execution: dist/st/workers/Cargo-CgOCogcE-dIBKWd7c.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/st/Cargo-CgOCogcE.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/mt/workers/Cargo-DcB9UMnw-w3wXmKCr.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/mt/Cargo-DcB9UMnw.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.14.9

9 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: GitHub Actions.

HIGH Publisher changed: wiktor.miden → GitHub Actions (on 2026-05-13) provenance

This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: dist/mt/workers/Cargo-DKB2aRX--C6T4l3AF.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/mt/Cargo-DKB2aRX-.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/st/workers/Cargo-jOTNoFyS-DRTcF6wf.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/st/Cargo-jOTNoFyS.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/mt/workers/web-client-methods-worker.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/st/workers/web-client-methods-worker.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.14.4

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.

v0.14.3

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.

v0.14.2

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.

v0.14.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.