← Home

@mediapipe/tasks-vision

npm Homepage
24
Versions
—
License
No
Install Scripts
Missing
Provenance

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

mrschmidttmullendancingplatypusgoogle-wombotchuoling

Keywords

ARMLAugmentedMediaPipeMediaPipe Tasks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:eval-usage AI (semgrep): Fires in bundler runtime shim within minified bundle, not attacker-controlled input. ai
npm-metadata bundled-binaries AI (npm-metadata): Expected MediaPipe vision WASM runtime; core to package function, stable across versions. ai
provenance publisher-changed AI (provenance): Publisher change from 2024-12-11 long stable on official @mediapipe scope; no malicious behavior. ai

Versions (showing 24 of 24)

Version Deps Published
0.10.34 0 / 0
0.10.32 0 / 0
0.10.21 0 / 0
0.10.20 0 / 0
0.10.19 0 / 0
0.10.18 0 / 0
0.10.17 0 / 0
0.10.16 0 / 0
0.10.15 0 / 0
0.10.14 0 / 0
0.10.13 0 / 0
0.10.12 0 / 0
0.10.11 0 / 0
0.10.10 0 / 0
0.10.9 0 / 0
0.10.8 0 / 0
0.10.7 0 / 0
0.10.6 0 / 0
0.10.5 0 / 0
0.10.4 0 / 0
0.10.3 0 / 0
0.10.2 0 / 0
0.10.1 0 / 0
0.10.0 0 / 0

v0.10.21

2 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/vision_wasm_internal.wasm • wasm/vision_wasm_nosimd_internal.wasm

LOW No provenance attestation provenance

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

v0.10.20

3 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/vision_wasm_internal.wasm • wasm/vision_wasm_nosimd_internal.wasm

HIGH Publisher changed: mrschmidt → delhibabu (on 2024-12-13) provenance

[Reject — re-review on republish] (prior reject: AI (provenance): Publisher changed from known Google/MediaPipe engineer (mrschmidt) to unaffiliated account (delhibabu) with a poor track record; this is not a legitimate transition for an official Go) This version was published by a different npm account than previous versions on 2024-12-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.10.19

3 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/vision_wasm_internal.wasm • wasm/vision_wasm_nosimd_internal.wasm

HIGH Publisher changed: mrschmidt → delhibabu (on 2024-12-11) provenance

[Reject — re-review on republish] (prior reject: AI (provenance): Publisher changed from known Google/MediaPipe engineer (mrschmidt) to unaffiliated account (delhibabu) with a poor track record; this is not a legitimate transition for an official Go) This version was published by a different npm account than previous versions on 2024-12-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.10.18

3 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/vision_wasm_internal.wasm • wasm/vision_wasm_nosimd_internal.wasm

HIGH Publisher changed: mrschmidt → delhibabu (on 2024-11-04) provenance

[Reject — re-review on republish] (prior reject: AI (provenance): Publisher changed from known Google/MediaPipe engineer (mrschmidt) to unaffiliated account (delhibabu) with a poor track record; this is not a legitimate transition for an official Go) This version was published by a different npm account than previous versions on 2024-11-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.10.16

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

2 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/vision_wasm_internal.wasm • wasm/vision_wasm_nosimd_internal.wasm

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

2 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/vision_wasm_internal.wasm • wasm/vision_wasm_nosimd_internal.wasm

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

2 findings
HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/vision_wasm_internal.wasm • wasm/vision_wasm_nosimd_internal.wasm

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

1 finding
LOW No provenance attestation provenance

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

v0.10.11

1 finding
LOW No provenance attestation provenance

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

v0.10.10

1 finding
LOW No provenance attestation provenance

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

v0.10.9

1 finding
LOW No provenance attestation provenance

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

v0.10.8

1 finding
LOW No provenance attestation provenance

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

v0.10.7

1 finding
LOW No provenance attestation provenance

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

v0.10.6

1 finding
LOW No provenance attestation provenance

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

v0.10.5

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

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