react-instantsearch-core
⚡ Lightning-fast search for React, by Algolia
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep used transitively; phantom-dep fires because it's not directly imported in this package's source. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): zod-to-json-schema is a declared runtime dep used transitively; same pattern as zod phantom-dep false positive. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 7.33.1 | 4 / 2 | |
| 7.33.0 | 6 / 2 | |
| 7.32.3 | 6 / 2 | |
| 7.32.2 | 6 / 2 | |
| 7.32.1 | 6 / 2 | |
| 7.32.0 | 6 / 2 | |
| 7.31.0 | 6 / 2 | |
| 7.30.0 | 6 / 2 | |
| 7.29.0 | 6 / 2 | |
| 7.28.1 | 6 / 2 | |
| 7.28.0 | 6 / 2 | |
| 7.27.0 | 6 / 2 | |
| 7.26.1 | 6 / 2 | |
| 7.26.0 | 6 / 2 | |
| 7.25.0 | 6 / 2 | |
| 7.24.0 | 6 / 2 | |
| 7.23.2 | 6 / 2 | |
| 7.23.1 | 6 / 2 | |
| 7.23.0 | 7 / 2 | |
| 7.22.1 | 7 / 2 | |
| 7.22.0 | 7 / 2 | |
| 7.21.0 | 7 / 2 | |
| 7.20.2 | 7 / 2 | |
| 7.20.1 | 7 / 2 | |
| 7.20.0 | 7 / 2 | |
| 7.19.0 | 7 / 2 | |
| 7.18.0 | 7 / 2 | |
| 7.17.0 | 7 / 2 | |
| 7.16.3 | 4 / 2 | |
| 7.16.2 | 4 / 2 | |
| 7.16.1 | 4 / 2 | |
| 7.16.0 | 4 / 2 | |
| 7.15.8 | 4 / 2 | |
| 7.15.7 | 4 / 2 | |
| 7.15.6 | 4 / 2 |
v7.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.