@algolia/autocomplete-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Algolia's publish pipeline does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 1.19.9 | 2 / 3 | |
| 1.19.8 | 2 / 3 | |
| 1.19.7 | 2 / 3 | |
| 1.19.6 | 2 / 3 | |
| 1.19.5 | 2 / 3 | |
| 1.19.4 | 2 / 3 | |
| 1.19.3 | 2 / 3 | |
| 1.19.2 | 2 / 3 | |
| 1.19.1 | 2 / 3 | |
| 1.19.0 | 2 / 3 | |
| 1.18.1 | 2 / 3 | |
| 1.18.0 | 2 / 3 | |
| 1.17.9 | 2 / 3 | |
| 1.17.8 | 2 / 3 | |
| 1.17.7 | 2 / 3 | |
| 1.17.6 | 2 / 3 | |
| 1.17.5 | 2 / 3 | |
| 1.17.4 | 2 / 3 | |
| 1.17.3 | 2 / 3 | |
| 1.17.2 | 2 / 3 | |
| 1.17.1 | 2 / 3 | |
| 1.17.0 | 2 / 3 | |
| 1.16.0 | 2 / 3 | |
| 1.15.1 | 2 / 3 | |
| 1.15.0 | 2 / 3 | |
| 1.14.0 | 2 / 3 | |
| 1.13.0 | 2 / 3 | |
| 1.12.2 | 2 / 3 | |
| 1.12.1 | 2 / 3 | |
| 1.12.0 | 2 / 3 | |
| 1.11.1 | 2 / 3 | |
| 1.11.0 | 2 / 3 | |
| 1.10.0 | 2 / 3 | |
| 1.9.4 | 2 / 3 | |
| 1.9.3 | 2 / 3 | |
| 1.9.2 | 2 / 3 | |
| 1.9.1 | 2 / 3 | |
| 1.9.0 | 2 / 3 | |
| 1.8.3 | 1 / 3 | |
| 1.8.2 | 1 / 3 | |
| 1.8.1 | 1 / 3 | |
| 1.8.0 | 1 / 3 | |
| 1.7.4 | 1 / 3 | |
| 1.7.3 | 1 / 3 | |
| 1.7.2 | 1 / 3 | |
| 1.7.1 | 1 / 3 | |
| 1.7.0 | 1 / 3 | |
| 1.6.3 | 1 / 3 | |
| 1.6.2 | 1 / 3 | |
| 1.6.1 | 1 / 3 | |
| 1.6.0 | 1 / 3 |
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
2 findingsThis version was published by a different npm account (instantsearch-bot) than the most recent previously approved version (dhaya.b) on 2023-03-02. It has since remained available on npm for 1240 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dhaya.b) than the most recent previously approved version (francoischalifour) on 2023-02-09, but dhaya.b is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.