@docsearch/js
JavaScript package for DocSearch, the best search experience for docs.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Official Algolia scoped package; string distance match against 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Official Algolia scoped package; string distance match against 'jest' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Official Algolia scoped package; string distance match against 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Official Algolia scoped package; string distance match against 'rxjs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Official Algolia scoped package; string distance match against 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Official Algolia scoped package; string distance match against 'ajv' is a false positive. | ai | |
| phantom-deps | phantom-dep:htm | AI (phantom-deps): htm is a declared runtime dependency in package.json; used in build/bundle config rather than direct import. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.6.3 | 0 / 6 | |
| 4.6.2 | 0 / 6 | |
| 4.6.1 | 0 / 6 | |
| 4.6.0 | 0 / 6 | |
| 4.5.4 | 0 / 6 | |
| 4.5.3 | 0 / 6 | |
| 4.5.2 | 0 / 6 | |
| 4.5.0 | 0 / 6 | |
| 4.4.0 | 2 / 4 | |
| 4.3.2 | 1 / 5 | |
| 4.3.1 | 1 / 5 | |
| 4.3.0 | 1 / 5 | |
| 4.2.0 | 0 / 5 | |
| 4.1.0 | 0 / 5 | |
| 4.0.1 | 0 / 5 | |
| 4.0.0 | 0 / 5 |
v4.6.3
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.2
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.4
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.3
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
2 findingsPackage name '@docsearch/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.