← Home

@docsearch/react

npm Repository Homepage

React package for DocSearch, the best search experience for docs.

8
Versions
MIT
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

shortcutsnyagudayevdylantientcheu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@docsearch/css AI (dependencies): First-party Algolia/DocSearch sibling package from the same monorepo; stable false positive. ai
dependencies unvetted-dep:@docsearch/core AI (dependencies): First-party Algolia/DocSearch sibling package from the same monorepo; stable false positive. ai
dependencies unvetted-dep:@algolia/autocomplete-core AI (dependencies): First-party Algolia autocomplete package; stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
4.6.3 3 / 11
4.3.2 8 / 6
4.3.1 8 / 6
4.3.0 8 / 6
4.2.0 7 / 6
4.1.0 7 / 6
4.0.1 7 / 6
4.0.0 6 / 7

v4.6.3

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.

v4.3.2

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.

v4.3.1

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.

v4.3.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.

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.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.

v4.0.1

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.

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