← Home

ink-select-input

4
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

vdemedessindresorhus

Keywords

inkink-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:arr-rotate AI (dependencies): arr-rotate is a simple array rotation utility; its use in a select input component for cycling through options is entirely expected and benign. ai
dependencies unvetted-dep:figures AI (dependencies): figures is a well-known sindresorhus utility package for terminal symbols; legitimate and expected dependency in Ink ecosystem components. ai
dependencies unvetted-dep:to-rotated AI (dependencies): to-rotated is a simple array rotation utility from the same ecosystem; no malicious indicators and appropriate for a select-input component. ai
provenance no-provenance AI (provenance): Established package from a highly trusted publisher; lack of provenance is common and not a meaningful risk signal here. ai

Versions (showing 4 of 4)

Version Deps Published
6.2.0 2 / 18
6.1.0 2 / 18
6.0.0 3 / 18
5.0.0 3 / 18

v6.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.