@gradio/dropdown
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Gradio org migrated to GitHub Actions CI publishing with SLSA attestation; this transition is legitimate and expected to persist. | ai | |
| phantom-deps | phantom-dep:@gradio/atoms | AI (phantom-deps): Svelte component; imports resolved at compile time, not via direct JS import. Same-org package. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Svelte component; imports resolved at compile time, not via direct JS import. Same-org package. | ai | |
| phantom-deps | phantom-dep:@gradio/statustracker | AI (phantom-deps): Svelte component; imports resolved at compile time, not via direct JS import. Same-org package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.12.1 | 4 / 1 | |
| 0.12.0 | 4 / 1 | |
| 0.11.8 | 4 / 1 | |
| 0.11.7 | 4 / 1 | |
| 0.11.6 | 4 / 1 | |
| 0.11.5 | 4 / 1 | |
| 0.11.4 | 4 / 1 | |
| 0.11.3 | 4 / 1 | |
| 0.11.2 | 4 / 1 | |
| 0.11.1 | 4 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.7 | 4 / 1 | |
| 0.10.6 | 4 / 1 | |
| 0.10.5 | 4 / 1 | |
| 0.10.4 | 4 / 1 | |
| 0.10.3 | 4 / 1 | |
| 0.10.2 | 4 / 1 | |
| 0.10.1 | 4 / 1 | |
| 0.10.0 | 4 / 1 | |
| 0.9.25 | 4 / 1 | |
| 0.9.24 | 4 / 1 | |
| 0.9.23 | 4 / 1 | |
| 0.9.22 | 4 / 1 | |
| 0.9.21 | 4 / 1 |
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.