← Home

@ghostery/adblocker-content

npm Repository Homepage

Ghostery adblocker library (content-scripts helpers)

60
Versions
MPL-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

chrmodsmalluban

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with org-level automation adoption. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; README links are to related packages/docs, not a phishing farm. ai

Versions (showing 60 of 60)

Version Deps Published
2.18.1 1 / 7
2.18.0 1 / 7
2.17.3 1 / 7
2.17.2 1 / 7
2.17.1 1 / 7
2.17.0 1 / 7
2.16.0 1 / 7
2.15.0 1 / 7
2.14.5 1 / 7
2.14.4 1 / 7
2.14.3 1 / 7
2.14.2 1 / 7
2.14.1 1 / 7
2.14.0 1 / 7
2.13.4 1 / 7
2.13.3 1 / 7
2.13.2 1 / 7
2.13.1 1 / 7
2.13.0 1 / 7
2.12.5 1 / 7
2.12.4 1 / 7
2.12.3 1 / 7
2.12.2 1 / 7
2.12.1 1 / 7
2.12.0 1 / 7
2.11.6 1 / 7
2.11.5 1 / 7
2.11.4 1 / 7
2.11.3 1 / 7
2.11.2 1 / 7
2.11.1 1 / 7
2.11.0 1 / 7
2.10.1 1 / 7
2.10.0 1 / 7
2.9.5 1 / 7
2.9.4 1 / 7
2.9.3 1 / 7
2.9.2 1 / 7
2.9.1 1 / 7
2.9.0 1 / 7
2.8.0 1 / 7
2.7.0 1 / 7
2.6.1 1 / 7
2.6.0 1 / 7
2.5.2 1 / 7
2.5.1 1 / 7
2.5.0 1 / 7
2.4.0 1 / 7
2.3.2 1 / 7
2.3.1 1 / 7
2.3.0 1 / 7
2.2.0 1 / 7
2.1.2 1 / 7
2.1.1 1 / 7
2.1.0 1 / 7
2.0.4 1 / 7
2.0.3 1 / 7
2.0.2 1 / 7
2.0.1 1 / 7
2.0.0 1 / 7

v2.18.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.