@gradio/image
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): Transition to GitHub Actions publisher is confirmed legitimate by SLSA/Sigstore attestation from the official gradio-app CI pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by migration to GitHub Actions CI publishing; SLSA attestation confirms integrity of this release. | ai | |
| phantom-deps | phantom-dep:@gradio/wasm | AI (phantom-deps): Same-org sibling package; phantom-dep pattern is stable for bundled Gradio components. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same-org Svelte component dependency; build-time resolution pattern. | ai | |
| phantom-deps | phantom-dep:cropperjs | AI (phantom-deps): Svelte component; deps resolved at build time, not via direct JS imports. | ai | |
| phantom-deps | phantom-dep:resize-observer-polyfill | AI (phantom-deps): Svelte component; deps resolved at build time, not via direct JS imports. | ai | |
| phantom-deps | phantom-dep:@gradio/upload | AI (phantom-deps): Same-org Svelte component dependency; build-time resolution pattern. | ai | |
| phantom-deps | phantom-dep:lazy-brush | AI (phantom-deps): Svelte component; deps resolved at build time, not via direct JS imports. | ai | |
| phantom-deps | phantom-dep:@gradio/atoms | AI (phantom-deps): Same-org Svelte component dependency; build-time resolution pattern. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.26.3 | 9 / 1 | |
| 0.26.2 | 9 / 1 | |
| 0.26.1 | 9 / 1 | |
| 0.26.0 | 9 / 1 | |
| 0.25.4 | 9 / 1 | |
| 0.25.3 | 9 / 1 | |
| 0.25.2 | 9 / 1 | |
| 0.25.1 | 9 / 1 | |
| 0.25.0 | 9 / 1 | |
| 0.24.0 | 9 / 1 | |
| 0.23.1 | 9 / 1 | |
| 0.23.0 | 9 / 1 | |
| 0.22.18 | 10 / 1 | |
| 0.22.17 | 10 / 1 | |
| 0.22.16 | 10 / 1 | |
| 0.22.15 | 10 / 1 | |
| 0.22.14 | 10 / 1 | |
| 0.22.13 | 10 / 1 | |
| 0.22.12 | 10 / 1 | |
| 0.22.11 | 10 / 1 | |
| 0.22.10 | 10 / 1 | |
| 0.22.8 | 10 / 1 | |
| 0.22.7 | 10 / 1 | |
| 0.22.6 | 10 / 1 |
v0.26.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.1
2 findingsThis version was published by a different npm account than previous versions on 2025-09-25. 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.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.