@gradio/model3d
Gradio UI packages
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/wasm | AI (phantom-deps): Same org scope; used via Gradio's WASM runtime convention, not direct import. Stable for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/icons | AI (phantom-deps): Same-org Gradio component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/upload | AI (phantom-deps): Same-org Gradio component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gradio/statustracker | AI (phantom-deps): Same-org Gradio component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babylonjs/core | AI (phantom-deps): BabylonJS 3D engine; referenced in config, legitimate dependency for a 3D model viewer. | ai | |
| phantom-deps | phantom-dep:@gradio/atoms | AI (phantom-deps): Same-org Gradio component; phantom-dep heuristic unreliable for Svelte component packages. | ai | |
| phantom-deps | phantom-dep:@babylonjs/loaders | AI (phantom-deps): BabylonJS loaders; referenced in config, legitimate dependency for a 3D model viewer. | ai | |
| phantom-deps | phantom-dep:gsplat | AI (phantom-deps): Gaussian splat rendering library; expected for a 3D model viewer component. | ai | |
| phantom-deps | phantom-dep:dequal | AI (phantom-deps): Deep equality utility; stable false positive for this Svelte component package. | ai | |
| phantom-deps | phantom-dep:@types/babylon | AI (phantom-deps): Type definitions for BabylonJS; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:@babylonjs/viewer | AI (phantom-deps): BabylonJS viewer; referenced in config, legitimate dependency for a 3D model viewer. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 12 / 1 | |
| 0.18.0 | 12 / 1 | |
| 0.17.0 | 12 / 1 | |
| 0.16.9 | 12 / 1 | |
| 0.16.8 | 12 / 1 | |
| 0.16.7 | 12 / 1 | |
| 0.16.6 | 12 / 1 | |
| 0.16.5 | 12 / 1 | |
| 0.16.4 | 12 / 1 | |
| 0.16.3 | 12 / 1 | |
| 0.16.2 | 12 / 1 | |
| 0.16.1 | 12 / 1 | |
| 0.16.0 | 12 / 1 | |
| 0.15.1 | 12 / 1 | |
| 0.15.0 | 12 / 1 | |
| 0.14.26 | 13 / 1 | |
| 0.14.25 | 13 / 1 | |
| 0.14.24 | 13 / 1 | |
| 0.14.23 | 13 / 1 | |
| 0.14.22 | 13 / 1 | |
| 0.14.21 | 13 / 1 | |
| 0.14.20 | 13 / 1 | |
| 0.14.19 | 13 / 1 | |
| 0.14.18 | 13 / 1 | |
| 0.14.17 | 13 / 1 | |
| 0.14.16 | 13 / 1 | |
| 0.14.15 | 13 / 1 | |
| 0.14.14 | 13 / 1 | |
| 0.14.13 | 13 / 1 | |
| 0.14.12 | 13 / 1 | |
| 0.14.11 | 13 / 1 | |
| 0.14.10 | 13 / 1 | |
| 0.14.9 | 13 / 1 | |
| 0.14.8 | 11 / 1 | |
| 0.14.7 | 11 / 1 | |
| 0.14.6 | 12 / 1 | |
| 0.14.5 | 12 / 1 | |
| 0.14.4 | 12 / 1 | |
| 0.14.3 | 12 / 1 | |
| 0.14.2 | 12 / 1 | |
| 0.14.1 | 12 / 1 | |
| 0.14.0 | 12 / 1 | |
| 0.13.15 | 12 / 1 | |
| 0.13.14 | 12 / 1 | |
| 0.13.13 | 12 / 1 | |
| 0.13.12 | 12 / 1 | |
| 0.13.11 | 12 / 1 | |
| 0.13.10 | 12 / 1 | |
| 0.13.9 | 12 / 1 | |
| 0.13.8 | 12 / 1 | |
| 0.13.7 | 12 / 1 | |
| 0.13.6 | 12 / 1 | |
| 0.13.5 | 12 / 1 | |
| 0.13.4 | 12 / 1 | |
| 0.13.3 | 12 / 1 | |
| 0.13.2 | 12 / 1 | |
| 0.13.1 | 12 / 1 | |
| 0.13.0 | 12 / 1 | |
| 0.12.2 | 12 / 1 |
v0.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
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.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
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.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.