@mediapipe/tasks-genai
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:wasm/genai_wasm_internal.js | AI (source-diff): Emscripten WASM glue code, minified build output not true obfuscation. | ai | |
| source-diff | obfuscated-file:wasm/genai_wasm_nosimd_internal.js | AI (source-diff): Emscripten WASM glue code, minified build output not true obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from new bundled wasm binaries, matches added-files diff. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official Google MediaPipe package, README/deps profile is normal for this monorepo split package. | ai | |
| source-diff | obfuscated-file:genai_bundle.js | AI (source-diff): MediaPipe ships Closure-compiled bundles; minified JS is expected and stable for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.10.29 | 0 / 0 | |
| 0.10.28 | 0 / 0 | |
| 0.10.27 | 0 / 0 | |
| 0.10.26 | 0 / 0 | |
| 0.10.16 | 0 / 0 |
v0.10.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.26
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tmullen) than the most recent previously approved version (mrschmidt) on 2026-01-06, but tmullen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.