@gradio/video
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@gradio/wasm | AI (phantom-deps): Same org scope (@gradio); intra-monorepo dependency pattern, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/atoms | AI (phantom-deps): Same-org Gradio component; phantom-dep heuristic fires on Svelte/bundled packages routinely. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same-org Gradio component; phantom-dep heuristic fires on Svelte/bundled packages routinely. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): @gradio/video is a scoped Gradio UI component; Levenshtein match to 'vite' is a false positive with no plausible squatting intent. | ai | |
| phantom-deps | phantom-dep:@gradio/upload | AI (phantom-deps): Same-org Gradio component; phantom-dep heuristic fires on Svelte/bundled packages routinely. | ai | |
| phantom-deps | phantom-dep:hls.js | AI (phantom-deps): hls.js is a legitimate video streaming dep for a video component; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:@gradio/image | AI (phantom-deps): Same-org Gradio component; phantom-dep heuristic fires on Svelte/bundled packages routinely. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.20.8 | 11 / 1 | |
| 0.20.7 | 11 / 1 | |
| 0.20.6 | 11 / 1 | |
| 0.20.5 | 11 / 1 | |
| 0.20.4 | 11 / 1 | |
| 0.20.3 | 11 / 1 | |
| 0.20.2 | 11 / 1 | |
| 0.20.1 | 11 / 1 | |
| 0.20.0 | 11 / 1 | |
| 0.19.0 | 11 / 1 | |
| 0.18.0 | 11 / 1 | |
| 0.17.0 | 11 / 1 | |
| 0.16.0 | 11 / 1 | |
| 0.14.24 | 12 / 1 | |
| 0.14.23 | 12 / 1 | |
| 0.14.22 | 12 / 1 | |
| 0.14.17 | 12 / 1 | |
| 0.14.16 | 12 / 1 | |
| 0.14.15 | 12 / 1 |
v0.20.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.