@gradio/atoms
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @gradio/* dependency swap within same monorepo org. | ai | |
| dependencies | unvetted-dep:@gradio/markdown | AI (dependencies): Sibling package within the same gradio monorepo/org. | ai | |
| phantom-deps | phantom-dep:@gradio/markdown | AI (phantom-deps): Same-org monorepo package, re-exported not directly imported. | ai | |
| dependencies | unvetted-dep:@gradio/markdown-code | AI (dependencies): Same @gradio org scope; consistent with monorepo dependency pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@gradio/markdown-code | AI (phantom-deps): Same @gradio org monorepo dep; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same-org Gradio monorepo dep; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 2 / 0 | |
| 0.25.0 | 2 / 0 | |
| 0.24.0 | 2 / 0 | |
| 0.23.1 | 2 / 0 | |
| 0.23.0 | 2 / 0 | |
| 0.22.2 | 3 / 0 | |
| 0.22.1 | 3 / 0 | |
| 0.22.0 | 3 / 0 | |
| 0.21.0 | 3 / 0 | |
| 0.20.1 | 3 / 0 | |
| 0.20.0 | 3 / 0 | |
| 0.19.0 | 3 / 0 | |
| 0.18.1 | 3 / 0 | |
| 0.18.0 | 3 / 0 | |
| 0.17.0 | 3 / 0 | |
| 0.16.5 | 3 / 0 | |
| 0.16.3 | 3 / 0 | |
| 0.16.0 | 3 / 0 | |
| 0.14.1 | 3 / 0 | |
| 0.13.2 | 3 / 0 | |
| 0.11.0 | 3 / 0 | |
| 0.10.0 | 3 / 0 | |
| 0.9.1 | 3 / 0 | |
| 0.9.0 | 2 / 0 | |
| 0.8.1 | 2 / 0 | |
| 0.8.0 | 2 / 0 | |
| 0.7.9 | 2 / 0 | |
| 0.7.8 | 2 / 0 | |
| 0.7.7 | 2 / 0 | |
| 0.7.6 | 2 / 0 | |
| 0.7.5 | 2 / 0 | |
| 0.7.4 | 2 / 0 | |
| 0.7.3 | 2 / 0 |
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.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
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.14.1
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.11.0
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.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.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.