@algolia/autocomplete-shared
Shared utils for Autocomplete packages.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Algolia-affiliated; consistent with internal team rotation, not a hostile takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former Algolia employees; paired with new Algolia-affiliated additions, this is a routine handoff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by Algolia-bot publish with no code changes; consistent with a delayed maintenance release, not takeover. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.19.8 | 0 / 2 | |
| 1.19.7 | 0 / 2 | |
| 1.19.6 | 0 / 2 | |
| 1.19.5 | 0 / 2 | |
| 1.19.4 | 0 / 2 | |
| 1.19.3 | 0 / 2 | |
| 1.19.2 | 0 / 2 | |
| 1.19.1 | 0 / 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.