@xsolla/xui-context-menu
A cross-platform React context menu component that can be triggered by a button or right-click, supporting various item types including checkboxes and radio buttons.
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-radio | AI (phantom-deps): Monorepo sibling; likely re-exported or transitively used by other deps. | ai | |
| phantom-deps | phantom-dep:@xsolla/xui-checkbox | AI (phantom-deps): Monorepo sibling; likely re-exported or transitively used by other deps. | ai | |
| phantom-deps | phantom-dep:@xsolla/xui-primitives-core | AI (phantom-deps): Monorepo sibling; likely re-exported or transitively used by other deps. | ai |
Versions (showing 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 0.170.0 | 8 / 7 | |
| 0.169.0 | 8 / 7 | |
| 0.168.1 | 8 / 7 | |
| 0.168.0 | 8 / 7 | |
| 0.167.0 | 8 / 7 | |
| 0.166.0 | 8 / 7 | |
| 0.165.0 | 8 / 7 | |
| 0.164.0 | 8 / 7 | |
| 0.163.0 | 8 / 7 | |
| 0.162.0 | 8 / 7 | |
| 0.161.3 | 8 / 7 | |
| 0.161.2 | 8 / 7 | |
| 0.161.1 | 8 / 7 | |
| 0.161.0 | 8 / 7 | |
| 0.160.2 | 8 / 7 | |
| 0.160.1 | 8 / 7 | |
| 0.160.0 | 8 / 7 | |
| 0.159.0 | 8 / 7 | |
| 0.158.0 | 8 / 7 | |
| 0.157.0 | 7 / 7 | |
| 0.156.0 | 7 / 7 | |
| 0.155.0 | 7 / 7 | |
| 0.154.2 | 7 / 7 | |
| 0.154.1 | 7 / 7 | |
| 0.154.0 | 7 / 7 | |
| 0.153.2 | 7 / 7 | |
| 0.153.1 | 7 / 7 | |
| 0.153.0 | 7 / 7 | |
| 0.152.0 | 7 / 7 | |
| 0.151.0 | 7 / 7 | |
| 0.150.0 | 7 / 7 | |
| 0.149.1 | 7 / 7 | |
| 0.149.0 | 7 / 7 | |
| 0.148.2 | 7 / 7 | |
| 0.148.1 | 7 / 7 | |
| 0.148.0 | 7 / 7 | |
| 0.147.1 | 7 / 7 | |
| 0.141.1 | 7 / 7 | |
| 0.141.0 | 7 / 7 | |
| 0.140.0 | 7 / 7 | |
| 0.139.0 | 7 / 7 | |
| 0.138.5 | 7 / 7 | |
| 0.138.4 | 7 / 7 | |
| 0.138.3 | 7 / 7 | |
| 0.138.2 | 7 / 7 | |
| 0.138.1 | 7 / 7 | |
| 0.138.0 | 7 / 7 | |
| 0.137.0 | 7 / 7 | |
| 0.136.0 | 7 / 7 | |
| 0.135.0 | 7 / 7 | |
| 0.134.0 | 7 / 7 |
v0.170.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.138.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.138.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.138.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.137.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.136.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.