@gearbox-protocol/ui-kit
Internal UI components
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:slick-carousel | AI (phantom-deps): CSS-only dependency for react-slick; referenced in config/styles, not imported directly. | ai | |
| phantom-deps | phantom-dep:react-markdown-math | AI (phantom-deps): Referenced in config files; stable false positive for this UI kit package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-collapsible | AI (phantom-deps): Radix UI component referenced in config; stable false positive for this UI kit. | ai | |
| phantom-deps | phantom-dep:react-infinite-scroll-component | AI (phantom-deps): Referenced in config files; stable false positive for this UI kit package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; package has 51 versions with consistent publisher history. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.12.2 | 34 / 53 | |
| 3.12.0 | 34 / 53 | |
| 3.11.2 | 34 / 53 | |
| 3.11.0 | 34 / 53 | |
| 3.10.5 | 34 / 53 | |
| 3.10.2 | 34 / 53 | |
| 3.10.1 | 34 / 53 | |
| 3.10.0 | 34 / 53 | |
| 3.9.1 | 34 / 53 | |
| 3.9.0 | 34 / 53 | |
| 3.8.2 | 34 / 53 | |
| 3.7.1 | 34 / 53 | |
| 3.7.0 | 34 / 53 | |
| 3.6.0 | 34 / 53 | |
| 3.5.2 | 34 / 53 | |
| 3.5.1 | 34 / 53 | |
| 3.3.0 | 34 / 53 | |
| 3.1.0 | 34 / 52 | |
| 3.0.2 | 34 / 52 | |
| 3.0.1 | 34 / 52 |
v3.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.