← Home

react-hotkeys

A declarative library for handling hotkeys and focus within a React application

29
Versions
ISC
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

chrisuigreena13

Keywords

react-componenthotkeysfocusreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): greena13 is the package author and repo owner; chrisui (Chris Pearce) is listed as contributor. Legitimate maintainer transition. ai
maintainer-change maintainer-added AI (maintainer-change): greena13 is the original author taking over npm publishing from a contributor. Stable for this package. ai

Versions (showing 29 of 29)

Version Deps Published
2.0.0 1 / 39
1.1.4 5 / 42
1.1.3 5 / 42
1.1.2 5 / 42
1.1.1 5 / 42
1.1.0 5 / 42
1.0.6 5 / 42
1.0.5 5 / 42
1.0.4 5 / 42
1.0.3 6 / 42
1.0.2 6 / 38
1.0.1 6 / 37
1.0.0 6 / 37
0.10.0 4 / 0
0.9.0 2 / 0
0.8.0 2 / 0
0.7.1 2 / 0
0.7.0 2 / 0
0.6.0 2 / 0
0.5.0 2 / 0
0.4.0 2 / 0
0.3.3 2 / 0
0.3.2 2 / 0
0.3.1 2 / 0
0.3.0 2 / 0
0.2.0 2 / 0
0.1.1 2 / 0
0.1.0 2 / 0
0.0.1 2 / 0

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

2 findings
HIGH Publisher changed: chrisui → greena13 (on 2018-03-24) provenance

This version was published by a different npm account than previous versions on 2018-03-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

2 findings
HIGH Publisher changed: chrisui → greena13 (on 2018-03-24) provenance

This version was published by a different npm account than previous versions on 2018-03-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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