@bitgo/wasm-mps MIT 11 versions

@bitgo/wasm-mps

npm Repository Homepage

WebAssembly wrapper for multi-party-schnorr protocol

11

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

louib-bitgobitgobot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): BitGo org placeholder/stub package; sparse metadata is typical for early wasm binding releases in this publisher's ecosystem.	ai	2026/05/29
source-diff	net-exec-file:dist/web/js/wasm/wasm_mps.js	AI (source-diff): wasm-bindgen generated JS glue; network/exec pattern is standard WASM memory/import binding, not malware.	ai	2026/05/27

Versions (showing 11 of 11)

Version	Deps	Published
1.8.1	0 / 4	2026-04-28
1.8.0	0 / 4	2026-04-28
1.7.0	0 / 4	2026-04-22
1.6.0	0 / 4	2026-03-17
1.5.0	0 / 4	2026-03-17
1.4.0	0 / 4	2026-03-11
1.3.0	0 / 4	2026-03-02
1.2.0	0 / 4	2026-02-27
1.1.0	0 / 4	2026-02-20
1.0.0	0 / 4	2026-02-20
0.0.1	0 / 0	2026-02-20

v1.8.1

1 finding

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.

v1.8.0

2 findings

HIGH New file with network + code execution: dist/web/js/wasm/wasm_mps.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.

v1.7.0

1 finding

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.

v1.6.0

1 finding

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.

v1.5.0

1 finding

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.

v1.4.0

1 finding

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.

v1.3.0

1 finding

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.

v1.2.0

1 finding

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.

v1.1.0

1 finding

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.

v1.0.0

1 finding

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