← Home

fuzzy-search

npm Repository Homepage

Simple fuzzy search

30
Versions
ISC
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

wouter2203

Keywords

fuzzysearchjavascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package with 10-year history and clean track record; lack of Sigstore provenance is a hygiene issue, not a security risk for this package. ai

Versions (showing 30 of 30)

Version Deps Published
3.2.1 0 / 6
3.2.0 0 / 6
3.1.0 0 / 6
3.0.2 0 / 6
3.0.1 0 / 6
3.0.0 0 / 5
2.2.1 0 / 6
2.2.0 0 / 5
2.1.0 0 / 6
2.0.1 0 / 6
2.0.0 1 / 5
1.5.0 1 / 5
1.4.0 0 / 11
1.3.8 0 / 9
1.3.7 0 / 9
1.3.6 0 / 9
1.3.5 0 / 11
1.3.4 0 / 11
1.3.3 0 / 11
1.3.1 0 / 11
1.3.0 0 / 11
1.2.5 0 / 11
1.2.4 0 / 10
1.2.3 0 / 10
1.2.2 0 / 9
1.2.1 0 / 9
1.2.0 0 / 8
1.1.1 0 / 8
1.1.0 0 / 8
1.0.0 0 / 8

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.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.

v3.1.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wouter2203.

LOW No provenance attestation provenance

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

v3.0.2

1 finding
INFO No provenance attestation provenance

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

v3.0.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.

v3.0.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.

v2.2.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.

v2.2.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.

v2.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.

v2.0.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.

v2.0.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.