← Home

@heroui/kbd

The keyboard key components indicates which key or set of keys used to execute a specificv action

20
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

juniorgarciadev

Keywords

kbd

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped @heroui/kbd package; Levenshtein match to 'koa' is a false positive with no brand impersonation. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @heroui/kbd package; Levenshtein match to 'zod' is a false positive with no brand impersonation. ai
phantom-deps phantom-dep:@react-aria/utils AI (phantom-deps): @react-aria/utils is a declared runtime dependency; phantom-dep heuristic fires on config-file references, not a real issue. ai

Versions (showing 20 of 20)

Version Deps Published
2.2.26 3 / 0
2.2.25 3 / 0
2.2.24 3 / 0
2.2.23 3 / 0
2.2.22 3 / 0
2.2.21 3 / 0
2.2.20 3 / 0
2.2.19 3 / 0
2.2.18 3 / 0
2.2.17 3 / 0
2.2.16 4 / 0
2.2.15 4 / 0
2.2.14 4 / 0
2.2.13 4 / 0
2.2.12 4 / 0
2.2.11 4 / 0
2.2.10 4 / 0
2.2.8 4 / 0
2.2.7 4 / 0
2.2.6 4 / 0

v2.2.13

1 finding
LOW No provenance attestation provenance

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

v2.2.12

1 finding
LOW No provenance attestation provenance

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

v2.2.11

1 finding
LOW No provenance attestation provenance

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

v2.2.10

1 finding
LOW No provenance attestation provenance

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

v2.2.8

1 finding
LOW No provenance attestation provenance

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

v2.2.6

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.