@choice-ui/command
A command palette component for quick actions, search, and keyboard navigation
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): New publisher without CI provenance setup; no other risk signals present to elevate this. | ai | |
| typosquat | typosquat.levenshtein:commander | AI (typosquat): Scoped UI component package; 'command' is a UI pattern name, not an impersonation of the 'commander' CLI library. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 6 / 7 | |
| 0.0.9 | 6 / 7 | |
| 0.0.8 | 6 / 7 | |
| 0.0.7 | 6 / 7 | |
| 0.0.6 | 6 / 7 | |
| 0.0.5 | 6 / 7 | |
| 0.0.4 | 6 / 7 |
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.