← Home

@acusti/dropdown

React component that renders a dropdown with a trigger and supports searching, keyboard access, and more

24
Versions
Unlicense
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

acusti

Keywords

a11yaccessibilitycomboboxdropdownkey-navigationmenureactreact-componentsearchssrtstypeaheadtypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@acusti/styling AI (dependencies): Same-author monorepo sibling; consistent with package's dependency pattern across versions. ai
provenance no-provenance AI (provenance): Long-established package; lack of provenance is consistent across all versions and not a meaningful risk signal here. ai

Versions (showing 24 of 24)

Version Deps Published
0.57.0 3 / 10
0.56.0 3 / 13
0.55.1 3 / 13
0.55.0 3 / 13
0.54.1 4 / 13
0.54.0 4 / 13
0.53.0 5 / 13
0.52.0 5 / 13
0.51.0 5 / 13
0.50.1 5 / 13
0.50.0 5 / 13
0.49.0 5 / 13
0.48.0 5 / 13
0.47.0 5 / 13
0.46.1 5 / 9
0.46.0 5 / 9
0.45.0 5 / 9
0.44.1 6 / 9
0.44.0 6 / 9
0.43.0 6 / 9
0.42.0 6 / 9
0.41.0 6 / 9
0.40.1 6 / 9
0.40.0 6 / 9

v0.57.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.

v0.51.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.

v0.50.1

1 finding
INFO No provenance attestation provenance

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

v0.50.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.

v0.49.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.

v0.46.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.

v0.45.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.

v0.44.1

1 finding
INFO No provenance attestation provenance

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

v0.44.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.

v0.43.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.

v0.42.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.

v0.41.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.

v0.40.1

1 finding
INFO No provenance attestation provenance

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

v0.40.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.