@algolia/autocomplete-plugin-query-suggestions
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@algolia/autocomplete-core | AI (phantom-deps): Same-org sibling dep; declared for type resolution, stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@algolia/autocomplete-preset-algolia | AI (phantom-deps): Same-org sibling dep; declared for type resolution, stable pattern across this monorepo. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.19.8 | 4 / 2 | |
| 1.19.7 | 4 / 2 | |
| 1.19.6 | 4 / 2 | |
| 1.19.5 | 4 / 2 | |
| 1.19.4 | 4 / 2 | |
| 1.19.3 | 4 / 2 | |
| 1.19.2 | 4 / 2 |
v1.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.