@algolia/autocomplete-plugin-recent-searches
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@algolia/autocomplete-preset-algolia | AI (phantom-deps): Same-org sibling package; declared as runtime dep, stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.19.9 | 4 / 1 | |
| 1.19.8 | 4 / 1 | |
| 1.19.7 | 4 / 1 | |
| 1.19.6 | 4 / 1 | |
| 1.19.5 | 4 / 1 | |
| 1.19.4 | 4 / 1 | |
| 1.19.3 | 4 / 1 | |
| 1.19.2 | 4 / 1 | |
| 1.19.1 | 4 / 1 | |
| 1.19.0 | 4 / 1 | |
| 1.18.1 | 4 / 1 | |
| 1.18.0 | 4 / 1 | |
| 1.17.9 | 4 / 1 | |
| 1.17.8 | 4 / 1 | |
| 1.17.7 | 4 / 1 | |
| 1.17.6 | 4 / 1 | |
| 1.17.5 | 4 / 1 | |
| 1.17.4 | 4 / 1 | |
| 1.17.3 | 4 / 1 | |
| 1.17.2 | 4 / 1 | |
| 1.17.1 | 4 / 1 |
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.