@gradio/dialogue
Gradio dialogue component
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/atoms | AI (phantom-deps): Svelte component package; deps consumed at framework level, not via direct JS imports. Same org scope. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same as above — Svelte component pattern within @gradio org. | ai | |
| phantom-deps | phantom-dep:@gradio/textbox | AI (phantom-deps): Same as above — Svelte component pattern within @gradio org. | ai | |
| phantom-deps | phantom-dep:@gradio/dropdown | AI (phantom-deps): Same as above — Svelte component pattern within @gradio org. | ai | |
| phantom-deps | phantom-dep:@gradio/statustracker | AI (phantom-deps): Same as above — Svelte component pattern within @gradio org. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.3.9 | 6 / 1 | |
| 0.3.8 | 6 / 1 | |
| 0.3.7 | 6 / 1 | |
| 0.3.6 | 6 / 1 | |
| 0.3.5 | 6 / 1 | |
| 0.3.4 | 6 / 1 | |
| 0.3.3 | 6 / 1 | |
| 0.3.2 | 6 / 1 | |
| 0.3.1 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.5 | 6 / 1 | |
| 0.2.4 | 6 / 1 | |
| 0.2.3 | 6 / 1 | |
| 0.2.2 | 6 / 1 | |
| 0.2.1 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.2 | 6 / 1 | |
| 0.1.1 | 6 / 1 | |
| 0.1.0 | 6 / 1 |
v0.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.