@docsearch/css
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:cors | AI (typosquat): Legitimate Algolia scoped package; edit-distance match to 'cors' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Legitimate Algolia scoped package; edit-distance match to 'qs' is coincidental. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.6.3 | 0 / 1 | |
| 4.3.2 | 0 / 1 | |
| 4.3.1 | 0 / 1 | |
| 4.3.0 | 0 / 1 | |
| 4.2.0 | 0 / 1 | |
| 4.1.0 | 0 / 1 | |
| 4.0.1 | 0 / 1 | |
| 4.0.0 | 0 / 1 |
v4.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage 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.