← Home

lighthouse

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

paulirishhotenlusayaa

Keywords

googlechromedevtools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Decodes CDP IO.read responses in fetcher.js; legitimate protocol handling, not obfuscation. ai
phantom-deps phantom-dep:ws AI (phantom-deps): ws is a declared runtime dependency used by the CDP WebSocket layer; phantom-dep heuristic false positive. ai

Versions (showing 7 of 7)

Version Deps Published
13.4.1 26 / 79
13.4.0 26 / 79
13.3.0 26 / 79
13.2.0 26 / 79
13.1.0 26 / 79
13.0.3 25 / 79
12.8.2 27 / 80

v13.4.1

2 findings
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.

INFO Publisher changed: hoten → GitHub Actions (on 2026-07-20, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (hoten) on 2026-07-20, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v13.1.0

2 findings
HIGH Publisher changed: paulirish → lusayaa (on 2026-04-06) provenance

This version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v13.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: hoten → paulirish (on 2026-02-11, known maintainer) provenance

This version was published by a different npm account (paulirish) than the most recent previously approved version (hoten) on 2026-02-11, but paulirish is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.