mcl-wasm — Greenflagged

mcl ; A portable and fast pairing-based cryptography library for Node.js by WebAssembly

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

herumi

elliptic curveWebAssemblypairing

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/mcl_c.js	AI (source-diff): Base64-encoded wasm binary embedded in JS; standard pattern for this package.	ai	2026/06/10
source-diff	encoded-string-file:browser/mcl.js	AI (source-diff): Same wasm binary embedding pattern in browser bundle; stable for this package.	ai	2026/06/10
publish-pattern	dormant-publish	AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish despite dormancy gap.	ai	2026/06/10
semgrep	semgrep:base64-decode	AI (semgrep): Fires on webpack-bundled WASM browser output; standard pattern for mcl-wasm across all versions.	ai	2026/05/10
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): @types/node is a type-only dep listed in dependencies by convention; not a real phantom dep concern.	ai	2026/05/10

3 findings

HIGH Long encoded string in modified file: dist/mcl_c.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: browser/mcl.js source-diff

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

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.

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.