@algolia/recommend
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Algolia official package; lack of Sigstore provenance is a minor gap but not a risk signal for this well-known vendor package. | ai | |
| dependencies | unvetted-dep:@algolia/client-common | AI (dependencies): Sibling package in the same Algolia monorepo, released in lockstep at the same version. SLSA provenance covers the release pipeline. | ai | |
| dependencies | unvetted-dep:@algolia/requester-fetch | AI (dependencies): Sibling package in the same Algolia monorepo, released in lockstep at the same version. SLSA provenance covers the release pipeline. | ai | |
| dependencies | unvetted-dep:@algolia/requester-node-http | AI (dependencies): Sibling package in the same Algolia monorepo, released in lockstep at the same version. SLSA provenance covers the release pipeline. | ai | |
| dependencies | unvetted-dep:@algolia/requester-browser-xhr | AI (dependencies): Sibling package in the same Algolia monorepo, released in lockstep at the same version. SLSA provenance covers the release pipeline. | ai |
Versions (showing 22 of 122)
| Version | Deps | Published |
|---|---|---|
| 4.18.0 | 11 / 0 | |
| 4.17.2 | 11 / 0 | |
| 4.17.1 | 11 / 0 | |
| 4.17.0 | 11 / 0 | |
| 4.16.0 | 11 / 0 | |
| 4.15.0 | 11 / 0 | |
| 4.14.3 | 11 / 0 | |
| 4.14.2 | 11 / 0 | |
| 4.14.1 | 11 / 0 | |
| 4.14.0 | 11 / 0 | |
| 4.13.1 | 11 / 0 | |
| 4.13.0 | 11 / 0 | |
| 4.12.2 | 11 / 0 | |
| 4.12.1 | 11 / 0 | |
| 4.12.0 | 11 / 0 | |
| 4.11.0 | 11 / 0 | |
| 4.10.5 | 11 / 0 | |
| 4.10.4 | 11 / 0 | |
| 4.10.3 | 11 / 0 | |
| 4.10.2 | 11 / 0 | |
| 4.10.1 | 11 / 0 | |
| 4.10.0 | 11 / 0 |
v4.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.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.
v4.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.
v4.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.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.
v4.14.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.
v4.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.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.
v4.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.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.
v4.12.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.
v4.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.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.
v4.10.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.
v4.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.