@algolia/client-search No license 46 versions

@algolia/client-search

npm Repository Homepage

46

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

haroenvshortcutseric-zahariafluf

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Package has 302 versions over 2338 days; apparent dormancy is an artifact of scoped package tracking, not actual inactivity. SLSA attestation confirms legitimate publish.	ai	2026/04/24
source-diff	obfuscated-file:dist/browser.d.ts	AI (source-diff): TypeScript declaration files (.d.ts) with long lines from union types and JSDoc are a known false positive for obfuscation detection. Content is clearly readable type definitions.	ai	2026/04/24
source-diff	obfuscated-file:dist/fetch.d.ts	AI (source-diff): TypeScript declaration files (.d.ts) with long lines from union types and JSDoc are a known false positive for obfuscation detection. Content is clearly readable type definitions.	ai	2026/04/24
source-diff	obfuscated-file:dist/node.d.ts	AI (source-diff): TypeScript declaration files (.d.ts) with long lines from union types and JSDoc are a known false positive for obfuscation detection. Content is clearly readable type definitions.	ai	2026/04/24
source-diff	obfuscated-file:dist/worker.d.ts	AI (source-diff): TypeScript declaration files (.d.ts) with long lines from union types and JSDoc are a known false positive for obfuscation detection. Content is clearly readable type definitions.	ai	2026/04/24
source-diff	obfuscated-file:dist/node.d.cts	AI (source-diff): TypeScript declaration files (.d.cts) with long lines from union types and JSDoc are a known false positive for obfuscation detection. Content is clearly readable type definitions.	ai	2026/04/24
dependencies	unvetted-dep:@algolia/requester-browser-xhr	AI (dependencies): First-party Algolia monorepo sibling package, always published at the same version as this package. Not an independent risk.	ai	2026/04/23
dependencies	unvetted-dep:@algolia/requester-node-http	AI (dependencies): First-party Algolia monorepo sibling package, always published at the same version as this package. Not an independent risk.	ai	2026/04/23
dependencies	unvetted-dep:@algolia/requester-fetch	AI (dependencies): First-party Algolia monorepo sibling package, always published at the same version as this package. Not an independent risk.	ai	2026/04/23

Versions (showing 46 of 146)

Version	Deps	Published
4.19.0	3 / 0	2023-07-18
4.18.0	3 / 0	2023-06-23
4.17.2	3 / 0	2023-06-08
4.17.1	3 / 0	2023-05-24
4.17.0	3 / 0	2023-04-03
4.16.0	3 / 0	2023-03-23
4.15.0	3 / 0	2023-03-02
4.14.3	3 / 0	2022-12-19
4.14.2	3 / 0	2022-07-27
4.14.1	3 / 0	2022-07-20
4.14.0	3 / 0	2022-07-18
4.13.1	3 / 0	2022-05-18
4.13.0	3 / 0	2022-03-14
4.12.2	3 / 0	2022-03-02
4.12.1	3 / 0	2022-01-28
4.12.0	3 / 0	2022-01-07
4.11.0	3 / 0	2021-10-20
4.10.5	3 / 0	2021-08-26
4.10.4	3 / 0	2021-08-23
4.10.3	3 / 0	2021-07-05
4.10.2	3 / 0	2021-06-23
4.10.0	3 / 0	2021-06-23
4.9.3	3 / 0	2021-06-15
4.9.2	3 / 0	2021-06-10
4.9.1	3 / 0	2021-04-26
4.9.0	3 / 0	2021-04-13
4.8.6	3 / 0	2021-03-08
4.8.5	3 / 0	2021-02-08
4.8.4	3 / 0	2021-01-20
4.8.3	3 / 0	2020-12-03
4.8.2	3 / 0	2020-11-26
4.8.1	3 / 0	2020-11-25
4.8.0	3 / 0	2020-11-19
4.7.0	3 / 0	2020-11-16
4.6.0	3 / 0	2020-11-02
4.5.1	3 / 0	2020-09-14
4.5.0	3 / 0	2020-09-14
4.4.0	3 / 0	2020-08-06
4.3.1	3 / 0	2020-07-20
4.3.0	3 / 0	2020-06-11
4.2.0	3 / 0	2020-04-21
4.1.0	3 / 0	2020-03-09
4.0.3	3 / 0	2020-02-13
4.0.2	3 / 0	2020-02-07
4.0.1	3 / 0	2020-02-03
4.0.0	3 / 0	2020-02-03

v4.19.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.18.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.17.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.17.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.17.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.16.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.15.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.14.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.14.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.14.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.14.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.13.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.13.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.12.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.12.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.12.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.11.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.10.5

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

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.10.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.10.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.10.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.9.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.9.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.9.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.9.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.8.6

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

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

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.8.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.8.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.8.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.8.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.7.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.6.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.5.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.5.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.4.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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