@gradio/file
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 sibling dep used indirectly via Svelte/bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same-org sibling dep used indirectly via Svelte/bundled output; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Legitimate @gradio/* monorepo component; no impersonation of vite — Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@gradio/atoms | AI (phantom-deps): Same-org monorepo dependency; not directly imported at source level but used via Svelte component composition. | ai | |
| phantom-deps | phantom-dep:@gradio/upload | AI (phantom-deps): Same-org monorepo dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/statustracker | AI (phantom-deps): Same-org monorepo dependency; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.14.8 | 6 / 1 | |
| 0.14.7 | 6 / 1 | |
| 0.14.6 | 6 / 1 | |
| 0.14.5 | 6 / 1 | |
| 0.14.4 | 6 / 1 | |
| 0.14.3 | 6 / 1 | |
| 0.14.2 | 6 / 1 | |
| 0.14.1 | 6 / 1 | |
| 0.14.0 | 6 / 1 | |
| 0.13.1 | 6 / 1 | |
| 0.13.0 | 6 / 1 | |
| 0.12.29 | 7 / 1 | |
| 0.12.27 | 7 / 1 | |
| 0.12.23 | 7 / 1 | |
| 0.12.21 | 7 / 1 | |
| 0.12.20 | 7 / 1 | |
| 0.12.19 | 7 / 1 | |
| 0.12.18 | 7 / 1 |
v0.14.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.