@browserless/lighthouse
Run Google Lighthouse audits on websites using headless Chrome. Get performance, accessibility, and SEO metrics.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:lighthouse | AI (dependencies): lighthouse is a well-known Google-maintained package; stable false positive for this integration package. | ai | |
| provenance | no-provenance | AI (provenance): Established package from trusted publisher; absence of provenance is common and not a risk indicator here. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 13.6.9 | 2 / 2 | |
| 13.6.7 | 2 / 2 | |
| 13.6.5 | 2 / 2 | |
| 13.6.4 | 2 / 2 | |
| 13.6.3 | 2 / 2 | |
| 13.6.2 | 2 / 2 | |
| 13.1.8 | 2 / 2 | |
| 13.1.7 | 1 / 2 | |
| 13.1.5 | 1 / 2 | |
| 13.1.2 | 1 / 2 | |
| 13.1.1 | 1 / 2 | |
| 13.0.8 | 1 / 2 | |
| 13.0.0 | 1 / 2 | |
| 11.0.0 | 1 / 2 | |
| 10.12.15 | 1 / 2 | |
| 10.12.13 | 1 / 2 | |
| 10.12.10 | 1 / 2 | |
| 10.12.9 | 1 / 2 | |
| 10.12.6 | 1 / 2 | |
| 10.11.4 | 1 / 2 | |
| 10.11.3 | 1 / 2 | |
| 10.11.1 | 1 / 2 | |
| 10.9.18 | 1 / 2 | |
| 10.9.16 | 1 / 2 | |
| 10.9.15 | 1 / 2 | |
| 10.9.14 | 1 / 2 | |
| 10.9.11 | 1 / 2 | |
| 10.9.8 | 1 / 2 | |
| 10.9.7 | 1 / 2 | |
| 10.9.0 | 1 / 2 | |
| 10.7.13 | 1 / 2 | |
| 10.7.12 | 1 / 2 | |
| 10.7.10 | 1 / 2 | |
| 10.7.6 | 1 / 2 | |
| 10.7.3 | 1 / 2 | |
| 10.7.2 | 1 / 2 | |
| 10.7.0 | 1 / 2 | |
| 10.6.3 | 1 / 2 | |
| 10.6.0 | 1 / 2 | |
| 10.5.2 | 1 / 2 |
v13.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.