@rcrsr/rill-ext-search-brave
rill extension for Brave search API integration
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; consistent with legitimate automation migration. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is a side-effect of the CI publishing migration; SLSA attestation provides stronger supply chain integrity. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.19.1 | 0 / 7 | |
| 0.19.0 | 0 / 7 | |
| 0.18.4 | 0 / 7 | |
| 0.18.2 | 0 / 7 |
v0.19.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.18.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-04-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.