@freik/search
A small trie-based search index builder
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Consistent publisher with clean history; missing gitHead reflects env change, not a risk for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.3.10 | 0 / 9 | |
| 1.3.9 | 0 / 9 | |
| 1.3.7 | 0 / 9 | |
| 1.3.6 | 0 / 9 | |
| 1.3.5 | 0 / 9 | |
| 1.3.4 | 0 / 9 | |
| 1.3.3 | 0 / 9 | |
| 1.3.2 | 0 / 9 | |
| 1.3.1 | 0 / 9 | |
| 1.2.1 | 0 / 9 | |
| 1.2.0 | 0 / 9 | |
| 1.1.24 | 0 / 9 | |
| 1.1.23 | 0 / 9 | |
| 1.1.21 | 0 / 9 | |
| 1.1.20 | 0 / 9 | |
| 1.1.19 | 0 / 9 | |
| 1.1.18 | 0 / 9 | |
| 1.1.17 | 0 / 9 | |
| 1.1.16 | 0 / 9 | |
| 1.1.15 | 0 / 9 | |
| 1.1.14 | 0 / 9 | |
| 1.1.12 | 0 / 9 | |
| 1.1.11 | 0 / 15 |
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.