@xsolla/xui-switch
A cross-platform React switch component for toggling between on and off states. Provides a visual alternative to checkboxes for boolean settings.
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:@xsolla/xui-primitives-core | AI (phantom-deps): Shared org dependency; stable pattern for @xsolla scoped packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org component library; missing metadata is normal for scoped packages. | ai |
Versions (showing 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 0.169.0 | 2 / 8 | |
| 0.168.1 | 2 / 8 | |
| 0.168.0 | 2 / 8 | |
| 0.167.0 | 2 / 8 | |
| 0.166.0 | 2 / 8 | |
| 0.165.0 | 2 / 8 | |
| 0.164.0 | 2 / 8 | |
| 0.163.0 | 2 / 8 | |
| 0.162.0 | 2 / 8 | |
| 0.161.3 | 2 / 8 | |
| 0.161.2 | 2 / 8 | |
| 0.161.1 | 2 / 8 | |
| 0.161.0 | 2 / 8 | |
| 0.160.2 | 2 / 8 | |
| 0.160.1 | 2 / 8 | |
| 0.160.0 | 2 / 8 | |
| 0.159.0 | 2 / 8 | |
| 0.158.0 | 2 / 8 | |
| 0.157.0 | 2 / 8 | |
| 0.156.0 | 2 / 8 | |
| 0.155.0 | 2 / 8 | |
| 0.154.2 | 2 / 8 | |
| 0.154.1 | 2 / 8 | |
| 0.154.0 | 2 / 8 | |
| 0.153.2 | 2 / 8 | |
| 0.153.1 | 2 / 8 | |
| 0.153.0 | 2 / 8 | |
| 0.152.0 | 2 / 8 | |
| 0.151.0 | 2 / 8 | |
| 0.150.0 | 2 / 8 | |
| 0.149.1 | 2 / 8 | |
| 0.149.0 | 2 / 8 | |
| 0.148.2 | 2 / 8 | |
| 0.148.1 | 2 / 8 | |
| 0.148.0 | 2 / 8 | |
| 0.147.1 | 2 / 8 | |
| 0.141.1 | 2 / 8 | |
| 0.141.0 | 2 / 8 | |
| 0.140.0 | 2 / 8 | |
| 0.139.0 | 2 / 8 | |
| 0.138.5 | 2 / 8 | |
| 0.138.4 | 2 / 8 | |
| 0.138.3 | 2 / 8 | |
| 0.138.2 | 2 / 8 | |
| 0.138.1 | 2 / 8 | |
| 0.138.0 | 2 / 8 | |
| 0.137.0 | 2 / 8 | |
| 0.136.0 | 2 / 8 | |
| 0.135.0 | 2 / 8 | |
| 0.134.0 | 2 / 8 | |
| 0.133.0 | 2 / 8 |
v0.169.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.168.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.168.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.167.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.166.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.165.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.164.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.163.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.162.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.161.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.161.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.161.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.161.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.160.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.160.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.160.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.159.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.158.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.157.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.156.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.155.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.154.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.154.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.154.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.153.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.153.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.153.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.152.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.151.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.150.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.149.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.149.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.148.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.148.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.148.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.147.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.141.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.141.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.140.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.139.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.138.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.138.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.138.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.138.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.138.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.138.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.137.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.136.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.135.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.134.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.133.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.