@algolia/client-search
Supply chain provenance
Status for the latest visible version.
Maintainers
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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 100 of 146)
| Version | Deps | Published |
|---|---|---|
| 5.53.0 | 4 / 6 | |
| 5.52.1 | 4 / 6 | |
| 5.52.0 | 4 / 6 | |
| 5.51.0 | 4 / 6 | |
| 5.50.2 | 4 / 6 | |
| 5.50.1 | 4 / 6 | |
| 5.50.0 | 4 / 6 | |
| 5.49.2 | 4 / 6 | |
| 5.49.1 | 4 / 6 | |
| 5.49.0 | 4 / 6 | |
| 5.48.2 | 4 / 6 | |
| 5.48.1 | 4 / 6 | |
| 5.46.0 | 4 / 6 | |
| 5.45.0 | 4 / 6 | |
| 5.44.0 | 4 / 6 | |
| 5.43.0 | 4 / 6 | |
| 5.42.0 | 4 / 6 | |
| 5.41.0 | 4 / 6 | |
| 5.40.1 | 4 / 6 | |
| 5.40.0 | 4 / 6 | |
| 5.39.0 | 4 / 6 | |
| 5.38.0 | 4 / 6 | |
| 5.37.0 | 4 / 6 | |
| 5.36.0 | 4 / 6 | |
| 5.35.0 | 4 / 6 | |
| 5.34.1 | 4 / 6 | |
| 5.34.0 | 4 / 6 | |
| 5.33.0 | 4 / 6 | |
| 5.32.0 | 4 / 6 | |
| 5.31.0 | 4 / 6 | |
| 5.30.0 | 4 / 6 | |
| 5.29.0 | 4 / 6 | |
| 5.28.0 | 4 / 6 | |
| 5.27.0 | 4 / 6 | |
| 5.26.0 | 4 / 6 | |
| 5.25.0 | 4 / 6 | |
| 5.24.0 | 4 / 6 | |
| 5.23.4 | 4 / 6 | |
| 5.23.3 | 4 / 6 | |
| 5.23.2 | 4 / 6 | |
| 5.23.1 | 4 / 6 | |
| 5.23.0 | 4 / 6 | |
| 5.22.0 | 4 / 6 | |
| 5.21.0 | 4 / 6 | |
| 5.20.4 | 4 / 6 | |
| 5.20.3 | 4 / 6 | |
| 5.20.2 | 4 / 6 | |
| 5.20.1 | 4 / 6 | |
| 5.20.0 | 4 / 6 | |
| 5.19.0 | 4 / 6 | |
| 5.18.0 | 4 / 6 | |
| 5.17.1 | 4 / 6 | |
| 5.17.0 | 4 / 6 | |
| 5.16.0 | 4 / 6 | |
| 5.15.0 | 4 / 6 | |
| 5.14.0 | 4 / 6 | |
| 5.13.0 | 4 / 6 | |
| 5.12.0 | 4 / 6 | |
| 5.11.0 | 4 / 6 | |
| 5.10.2 | 4 / 6 | |
| 5.10.1 | 4 / 6 | |
| 5.10.0 | 4 / 6 | |
| 5.9.1 | 4 / 6 | |
| 5.9.0 | 4 / 6 | |
| 5.8.1 | 4 / 6 | |
| 5.8.0 | 4 / 6 | |
| 5.7.0 | 4 / 6 | |
| 5.6.1 | 4 / 6 | |
| 5.6.0 | 4 / 6 | |
| 5.5.3 | 4 / 6 | |
| 5.5.2 | 4 / 6 | |
| 5.5.1 | 4 / 6 | |
| 5.5.0 | 4 / 6 | |
| 5.4.3 | 4 / 6 | |
| 5.4.1 | 4 / 6 | |
| 5.4.0 | 4 / 6 | |
| 5.3.2 | 3 / 6 | |
| 5.3.1 | 3 / 6 | |
| 5.3.0 | 3 / 6 | |
| 5.2.5 | 3 / 6 | |
| 5.2.4 | 3 / 3 | |
| 5.2.3 | 3 / 3 | |
| 5.2.2 | 3 / 3 | |
| 5.2.1 | 3 / 3 | |
| 5.1.1 | 3 / 3 | |
| 5.1.0 | 3 / 3 | |
| 5.0.2 | 3 / 3 | |
| 5.0.0 | 3 / 3 | |
| 4.25.3 | 3 / 0 | |
| 4.24.0 | 3 / 0 | |
| 4.23.3 | 3 / 0 | |
| 4.23.2 | 3 / 0 | |
| 4.23.1 | 3 / 0 | |
| 4.23.0 | 3 / 0 | |
| 4.22.1 | 3 / 0 | |
| 4.22.0 | 3 / 0 | |
| 4.21.1 | 3 / 0 | |
| 4.21.0 | 3 / 0 | |
| 4.20.0 | 3 / 0 | |
| 4.19.1 | 3 / 0 |
v5.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.52.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.50.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.50.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.49.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.49.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.48.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.48.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.