@ghostery/adblocker-electron
Ghostery adblocker Electron wrapper
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 | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI/CD with SLSA attestation; consistent with legitimate automation migration for this org. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 3 / 13 | |
| 2.17.3 | 3 / 13 | |
| 2.17.2 | 3 / 13 | |
| 2.17.1 | 3 / 13 | |
| 2.17.0 | 3 / 13 | |
| 2.16.0 | 3 / 13 | |
| 2.15.0 | 3 / 13 | |
| 2.14.5 | 3 / 13 | |
| 2.14.4 | 3 / 13 | |
| 2.14.3 | 3 / 13 | |
| 2.14.2 | 3 / 13 | |
| 2.14.1 | 3 / 13 | |
| 2.14.0 | 3 / 13 | |
| 2.13.4 | 3 / 13 | |
| 2.13.3 | 3 / 13 | |
| 2.13.2 | 3 / 13 | |
| 2.13.1 | 3 / 13 | |
| 2.13.0 | 3 / 13 | |
| 2.12.5 | 3 / 13 | |
| 2.12.4 | 3 / 13 | |
| 2.12.3 | 3 / 13 | |
| 2.12.2 | 3 / 13 | |
| 2.12.1 | 3 / 13 | |
| 2.12.0 | 3 / 13 | |
| 2.11.6 | 3 / 13 | |
| 2.11.5 | 3 / 13 | |
| 2.11.4 | 3 / 13 | |
| 2.11.3 | 3 / 13 | |
| 2.11.2 | 3 / 13 | |
| 2.11.1 | 3 / 13 | |
| 2.11.0 | 3 / 13 | |
| 2.10.1 | 3 / 13 | |
| 2.10.0 | 3 / 13 | |
| 2.9.5 | 3 / 13 | |
| 2.9.4 | 3 / 13 | |
| 2.9.3 | 3 / 13 | |
| 2.9.2 | 3 / 13 | |
| 2.9.1 | 3 / 13 | |
| 2.9.0 | 3 / 13 | |
| 2.8.0 | 3 / 13 | |
| 2.7.0 | 3 / 13 | |
| 2.6.1 | 3 / 13 | |
| 2.6.0 | 3 / 13 | |
| 2.5.2 | 3 / 13 | |
| 2.5.1 | 3 / 13 | |
| 2.5.0 | 3 / 13 | |
| 2.4.0 | 3 / 13 | |
| 2.3.2 | 3 / 13 | |
| 2.3.1 | 3 / 13 | |
| 2.3.0 | 3 / 13 | |
| 2.2.0 | 3 / 13 | |
| 2.1.2 | 3 / 13 | |
| 2.1.1 | 3 / 13 | |
| 2.1.0 | 3 / 13 | |
| 2.0.4 | 3 / 13 | |
| 2.0.3 | 3 / 13 | |
| 2.0.2 | 3 / 13 | |
| 2.0.1 | 3 / 13 | |
| 2.0.0 | 3 / 13 |
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.