@algolia/autocomplete-preset-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): instantsearch-bot is Algolia's org-wide CI publisher with 440 approved packages; change is org-level, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Algolia org-wide maintainer roster update; consistent with known Algolia publishing patterns. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removals are the other side of the same Algolia org-wide roster update; not indicative of takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Algolia monorepo release cadence; dormancy reflects upstream release timing, not account compromise. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.19.8 | 1 / 1 | |
| 1.19.7 | 1 / 1 | |
| 1.19.6 | 1 / 1 | |
| 1.19.5 | 1 / 1 | |
| 1.19.4 | 1 / 1 | |
| 1.19.3 | 1 / 1 | |
| 1.19.2 | 1 / 1 | |
| 1.19.1 | 1 / 1 | |
| 1.7.4 | 1 / 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
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.6
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.5
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
Package 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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-05-20. This could indicate a legitimate maintainer transition or an account compromise.
v1.19.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-04-29. This could indicate a legitimate maintainer transition or an account compromise.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.