@workglow/tf-mediapipe
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@mediapipe/tasks-audio | AI (phantom-deps): Browser-target bundle; deps declared for consumers, not directly imported in build entry points. | ai | |
| phantom-deps | phantom-dep:@mediapipe/tasks-genai | AI (phantom-deps): Same pattern — declared for downstream use, referenced in config but not a direct import. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.3.12 | 4 / 5 | |
| 0.3.11 | 4 / 5 | |
| 0.3.10 | 4 / 5 | |
| 0.3.9 | 4 / 5 | |
| 0.3.7 | 4 / 5 | |
| 0.3.6 | 4 / 5 | |
| 0.3.5 | 4 / 5 | |
| 0.3.4 | 4 / 5 | |
| 0.3.3 | 4 / 5 | |
| 0.3.2 | 4 / 5 | |
| 0.3.1 | 4 / 5 | |
| 0.3.0 | 4 / 5 | |
| 0.2.37 | 4 / 5 | |
| 0.2.36 | 4 / 5 | |
| 0.2.35 | 4 / 5 | |
| 0.2.34 | 4 / 5 | |
| 0.2.32 | 4 / 5 | |
| 0.2.30 | 4 / 6 | |
| 0.2.28 | 4 / 6 |
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.