@gradio/upload
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 Svelte component; imports resolved by bundler, not direct JS require. | ai | |
| phantom-deps | phantom-dep:@gradio/atoms | AI (phantom-deps): Same-org Svelte component; imports resolved by bundler, not direct JS require. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same-org Svelte component; imports resolved by bundler, not direct JS require. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 4 / 0 | |
| 0.18.0 | 4 / 0 | |
| 0.17.10 | 4 / 0 | |
| 0.17.9 | 4 / 0 | |
| 0.17.8 | 4 / 0 | |
| 0.17.7 | 4 / 0 | |
| 0.17.6 | 4 / 0 | |
| 0.17.5 | 4 / 0 | |
| 0.17.4 | 4 / 0 | |
| 0.17.3 | 4 / 0 | |
| 0.17.2 | 4 / 0 | |
| 0.17.0 | 4 / 0 | |
| 0.16.17 | 5 / 0 | |
| 0.16.16 | 5 / 0 | |
| 0.16.15 | 5 / 0 | |
| 0.16.14 | 5 / 0 | |
| 0.16.13 | 5 / 0 | |
| 0.16.12 | 5 / 0 | |
| 0.16.11 | 5 / 0 | |
| 0.16.10 | 5 / 0 | |
| 0.16.9 | 5 / 0 | |
| 0.16.8 | 5 / 0 | |
| 0.16.7 | 5 / 0 | |
| 0.16.6 | 5 / 0 | |
| 0.16.5 | 5 / 0 | |
| 0.16.4 | 5 / 0 | |
| 0.16.3 | 5 / 0 | |
| 0.16.2 | 5 / 0 | |
| 0.16.1 | 5 / 0 | |
| 0.16.0 | 5 / 0 | |
| 0.15.7 | 5 / 0 | |
| 0.15.6 | 5 / 0 | |
| 0.15.5 | 5 / 0 | |
| 0.15.4 | 5 / 0 | |
| 0.15.3 | 5 / 0 | |
| 0.15.2 | 5 / 0 | |
| 0.15.1 | 5 / 0 | |
| 0.15.0 | 5 / 0 | |
| 0.14.8 | 5 / 0 | |
| 0.14.7 | 5 / 0 | |
| 0.14.6 | 5 / 0 | |
| 0.14.5 | 5 / 0 | |
| 0.14.4 | 5 / 0 | |
| 0.14.3 | 5 / 0 | |
| 0.14.2 | 5 / 0 | |
| 0.14.1 | 5 / 0 | |
| 0.14.0 | 5 / 0 | |
| 0.13.5 | 5 / 0 | |
| 0.13.4 | 5 / 0 | |
| 0.13.3 | 5 / 0 | |
| 0.13.2 | 5 / 0 | |
| 0.13.1 | 5 / 0 | |
| 0.13.0 | 5 / 0 | |
| 0.12.4 | 5 / 0 | |
| 0.12.3 | 5 / 0 | |
| 0.12.2 | 5 / 0 | |
| 0.12.1 | 5 / 0 | |
| 0.12.0 | 5 / 0 | |
| 0.11.5 | 5 / 0 | |
| 0.11.4 | 5 / 0 | |
| 0.11.3 | 5 / 0 | |
| 0.11.2 | 5 / 0 |
v0.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.