@gradio/statustracker
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): Same-org monorepo dep; may be used transitively or via Svelte compilation, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/sanitize | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.15.1 | 4 / 1 | |
| 0.15.0 | 4 / 1 | |
| 0.14.1 | 4 / 1 | |
| 0.14.0 | 4 / 1 | |
| 0.13.1 | 4 / 1 | |
| 0.13.0 | 4 / 1 | |
| 0.12.5 | 4 / 1 | |
| 0.12.4 | 4 / 1 | |
| 0.12.3 | 4 / 1 | |
| 0.12.2 | 4 / 1 | |
| 0.12.1 | 4 / 1 | |
| 0.12.0 | 4 / 1 | |
| 0.11.1 | 4 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.18 | 4 / 1 | |
| 0.10.17 | 5 / 1 | |
| 0.10.16 | 5 / 1 | |
| 0.10.15 | 5 / 1 | |
| 0.10.14 | 5 / 1 | |
| 0.10.13 | 5 / 1 | |
| 0.10.12 | 5 / 1 | |
| 0.10.11 | 5 / 1 | |
| 0.10.10 | 5 / 1 | |
| 0.10.9 | 5 / 1 | |
| 0.10.8 | 5 / 1 | |
| 0.10.7 | 5 / 1 | |
| 0.10.6 | 5 / 1 | |
| 0.10.5 | 5 / 1 | |
| 0.10.4 | 5 / 1 | |
| 0.10.3 | 5 / 1 | |
| 0.10.2 | 5 / 1 | |
| 0.10.1 | 5 / 1 | |
| 0.10.0 | 5 / 1 | |
| 0.9.7 | 5 / 1 | |
| 0.9.6 | 5 / 1 | |
| 0.9.5 | 5 / 1 | |
| 0.9.4 | 5 / 1 | |
| 0.9.3 | 5 / 1 | |
| 0.9.2 | 5 / 1 | |
| 0.9.1 | 5 / 1 | |
| 0.9.0 | 5 / 1 | |
| 0.8.1 | 5 / 1 | |
| 0.8.0 | 5 / 1 | |
| 0.7.6 | 5 / 1 | |
| 0.7.5 | 5 / 1 | |
| 0.7.4 | 5 / 1 | |
| 0.7.3 | 5 / 1 | |
| 0.7.2 | 5 / 1 | |
| 0.7.1 | 3 / 1 | |
| 0.7.0 | 3 / 1 | |
| 0.6.0 | 3 / 1 | |
| 0.5.5 | 4 / 1 | |
| 0.5.4 | 4 / 1 | |
| 0.5.3 | 4 / 1 | |
| 0.5.2 | 4 / 1 |
v0.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.