npmpackage.info

Gathering detailed insights and metrics for @wdio/lighthouse-service

@wdio/lighthouse-service - 9.17.0 | npmpackage.info

@wdio/lighthouse-service

Next-gen browser and mobile automation test framework for Node.js

9.17.0

9,540

MIT

TypeScript

88.74 kB

Installations

npm install @wdio/lighthouse-service

Developer Guide

BETA

Typescript

Yes

Module System

ESM

Min. Node Version

>=18.20.0

Node Version

20.11.1

NPM Version

lerna/8.2.3/node@v20.11.1+x64 (linux)

Pull Requests

Open

13

Total

8,140

Closed

1,467

Merged

6,660

Issues

Open

223

Total

5,766

Closed

5,543

Releases

568

v9.17.1

Updated on Jul 09, 2025

v9.17.0

Updated on Jul 09, 2025

v9.16.2

Updated on Jun 23, 2025

v9.16.1

Updated on Jun 23, 2025

v9.16.0

Updated on Jun 23, 2025

v8.45.0

Updated on Jun 12, 2025

View All 568 releases

Languages

TypeScript

JavaScript

EJS

CSS

Gherkin

Dockerfile

Vue

Svelte

HTML

TypeScript (94.25%)

JavaScript (3.6%)

EJS (1.37%)

CSS (0.67%)

Gherkin (0.07%)

Dockerfile (0.03%)

Vue (0.01%)

Developer

webdriverio

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

9,540 Stars

8,054 Commits

2,599 Forks

213 Watchers

32 Branches

652 Contributors

Updated on Jul 12, 2025

Maintainers

View All 652 Contributors

Package Meta Information

Latest Version

9.17.0

Package Id

@wdio/lighthouse-service@9.17.0

Unpacked Size

88.74 kB

Size

24.72 kB

File Count

NPM Version

lerna/8.2.3/node@v20.11.1+x64 (linux)

Node Version

20.11.1

Published on

Jul 09, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@babel/core @tracerbench/trace-event @types/node @wdio/logger @wdio/types babel-plugin-istanbul devtools-protocol istanbul-lib-coverage istanbul-lib-report istanbul-reports lighthouse puppeteer-core webdriverio

Dev Dependencies

@types/babel__core @types/istanbul-lib-coverage @types/istanbul-lib-report @types/istanbul-reports @wdio/globals

Next-gen browser and mobile automation test framework for Node.js.

WebdriverIO is a test automation framework, for e2e as well as unit and component testing in the browser, that allows you to run tests based on the WebDriver and WebDriver BiDi as well as Appium automation technology. It provides support for your favorite BDD/TDD test framework and will run your tests locally or in the cloud using Sauce Labs, BrowserStack, TestingBot or LambdaTest.

:woman_technologist: :man_technologist: Contributing

Do you like WebdriverIO and want to help make it better? Awesome! Have a look into our Contributor Documentation to get started and find out what contributions can be and how to make them.

Getting started with GitHub Codespaces

To get started, create a codespace for this repository by clicking this 👇

A codespace will open in a web-based version of Visual Studio Code. The dev container is fully configured with the software needed for this project.

Note: Dev containers are an open spec that is supported by GitHub Codespaces and other tools.

Getting started with Gitpod

You can also just click on:

to get a ready-to-use development environment for you to start working on this code base.

If you're looking for issues to help out with, check out the issues labeled "good first pick". You can also reach out to our Matrix Channel if you have questions on where to start contributing.

:office: WebdriverIO for Enterprise

Available as part of the Tidelift Subscription.

The maintainers of WebdriverIO and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open-source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.

:package: Packages

This repository contains some of the core packages of the WebdriverIO project. There are many wonderful curated resources the WebdriverIO community has put together.

Did you build a WebdriverIO service or reporter? That's awesome! Please add it to our configuration wizard and docs (e.g. like in this example commit) as well as to our awesome-webdriverio list. Thank you! 🙏 ❤️

Core

webdriver - A Node.js bindings implementation for the W3C WebDriver and Mobile JSONWire Protocol
webdriverio - Next-gen browser and mobile automation test framework for Node.js
@wdio/cli - A WebdriverIO testrunner command line interface

Helper

@wdio/config - A helper utility to parse and validate WebdriverIO options
@wdio/logger - A helper utility for logging WebdriverIO packages
@wdio/protocols - Utility package providing information about automation protocols
@wdio/repl - A WDIO helper utility to provide a repl interface for WebdriverIO
@wdio/reporter - A WebdriverIO utility to help report all events
@wdio/runner - A WebdriverIO service that runs tests in arbitrary environments
@wdio/utils - A WDIO helper utility to provide several utility functions used across the project
@wdio/globals - A WDIO helper utility for importing global variables directly

Reporter

@wdio/allure-reporter - A WebdriverIO reporter plugin to create Allure Test Reports
@wdio/concise-reporter - A WebdriverIO reporter plugin to create concise test reports
@wdio/dot-reporter - A WebdriverIO plugin to report in dot style
@wdio/junit-reporter - A WebdriverIO reporter that creates test results in XML format
@wdio/spec-reporter - A WebdriverIO plugin to report in spec style
@wdio/sumologic-reporter - A WebdriverIO reporter that sends test results to Sumologic for data analyses

Services

@wdio/appium-service - A WebdriverIO service to start & stop Appium Server
@wdio/browserstack-service - A WebdriverIO service that can be used to use BrowserStack Test Observability which is a reporting, debugging, and test suite quality tracking tool for any test running anywhere. The service also helps for a better integration with the BrowserStack grid if you're running tests on the grid.
@wdio/lighthouse-service - A WebdriverIO service that integrates Google Lighthouse commands to use it for automate tests
@wdio/firefox-profile-service - A WebdriverIO service that lets you define your Firefox profile in your wdio.conf.js
@wdio/sauce-service - A WebdriverIO service that provides a better integration into Sauce Labs
@wdio/shared-store-service - A WebdriverIO service to exchange data across processes
@wdio/testingbot-service - A WebdriverIO service that provides a better integration into TestingBot

Runner

@wdio/local-runner - A WebdriverIO runner to run tests locally
@wdio/browser-runner - A WebdriverIO runner to run unit or component tests in the browser

Framework Adapters

@wdio/cucumber-framework - Adapter for Cucumber testing framework
@wdio/jasmine-framework - Adapter for Jasmine testing framework
@wdio/mocha-framework - Adapter for Mocha testing framework.

Others

create-wdio - A CLI and utility to install and setup a WebdriverIO
eslint-plugin-wdio - Eslint rules for WebdriverIO
@wdio/smoke-test-reporter - A WebdriverIO utility to smoke test reporters for internal testing purposes
@wdio/smoke-test-service - A WebdriverIO utility to smoke test services for internal testing purposes
@wdio/webdriver-mock-service - A WebdriverIO service to stub all endpoints for internal testing purposes

Infrastructure Packages

These packages are not released to NPM and used to work on this codebase.

@wdio/compiler - Esbuild script to compile the source code all of all packages
@wdio/lerna-patch - This sub-package is being used to patch Lerna to not run pnpm install after it prepared all packages for release

:handshake: Project Governance

This project is maintained by awesome people following a common set of rules and treating each other with respect and appreciation.

:man_cook: :woman_cook: Backers

Become a backer and show your support for our open-source project.

:money_with_wings: Sponsors

Does your company use WebdriverIO? Ask your manager or marketing team if your company would be interested in supporting our project. Support will allow the maintainers to dedicate more time to maintenance and new features for everyone. Also, your company's logo will show on GitHub - who doesn't want a little extra exposure? Here's the info.

💎 Premium Sponsor

We are immensely grateful to our exclusive Premium Sponsor for their invaluable support in the development of this project:

🥇 Gold Sponsor

🥈 Silver Sponsor

🥉 Bronze Sponsor

:page_facing_up: License

MIT

:beginner: Badge

Show the world you're using webdriver.io →

GitHub markup

[![tested with webdriver.io](https://img.shields.io/badge/tested%20with-webdriver.io-%23ea5906)](https://webdriver.io/)

HTML

<a href="https://webdriver.io/">
    <img alt="WebdriverIO" src="https://img.shields.io/badge/tested%20with-webdriver.io-%23ea5906">
</a>

:clap: Supporters

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

9

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

6

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

5

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

4

SAST

Determines if the project uses static code analysis.

3

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

Reason

detected GitHub workflow tokens with excessive permissions

Details

Info: found token with 'none' permissions: .github/workflows/authorize.yml:1
Info: jobLevel 'contents' permission set to 'read': .github/workflows/build.yml:11
Info: jobLevel 'packages' permission set to 'read': .github/workflows/build.yml:12
Warn: jobLevel 'contents' permission set to 'write': .github/workflows/cr.yml:12
Info: jobLevel 'packages' permission set to 'read': .github/workflows/cr.yml:14
Warn: jobLevel 'contents' permission set to 'write': .github/workflows/expense.yml:45
Warn: jobLevel 'contents' permission set to 'write': .github/workflows/publish.yml:36
Info: jobLevel 'packages' permission set to 'read': .github/workflows/publish.yml:38
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-cloud.yml:12
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-component.yml:12
Warn: jobLevel 'actions' permission set to 'write': .github/workflows/test-component.yml:13
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-interop.yml:12
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-launch.yml:12
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-multiremote.yml:12
Warn: jobLevel 'actions' permission set to 'write': .github/workflows/test-smoke.yml:13
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-smoke.yml:12
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-standalone.yml:12
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-static.yml:13
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-testrunner.yml:12
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-typings.yml:12
Info: jobLevel 'contents' permission set to 'read': .github/workflows/test-unit.yml:12
Warn: jobLevel 'actions' permission set to 'write': .github/workflows/test-unit.yml:13
Warn: no topLevel permission defined: .github/workflows/authorize.yml:1
Warn: no topLevel permission defined: .github/workflows/build.yml:1
Warn: no topLevel permission defined: .github/workflows/cr.yml:1
Info: topLevel 'contents' permission set to 'read': .github/workflows/deploy.yml:8
Info: topLevel 'packages' permission set to 'read': .github/workflows/deploy.yml:9
Warn: no topLevel permission defined: .github/workflows/expense.yml:1
Warn: no topLevel permission defined: .github/workflows/labeler.yml:1
Warn: no topLevel permission defined: .github/workflows/publish.yml:1
Warn: no topLevel permission defined: .github/workflows/test-cloud.yml:1
Warn: no topLevel permission defined: .github/workflows/test-component.yml:1
Warn: no topLevel permission defined: .github/workflows/test-interop.yml:1
Warn: no topLevel permission defined: .github/workflows/test-launch.yml:1
Warn: no topLevel permission defined: .github/workflows/test-multiremote.yml:1
Warn: no topLevel permission defined: .github/workflows/test-smoke.yml:1
Warn: no topLevel permission defined: .github/workflows/test-standalone.yml:1
Warn: no topLevel permission defined: .github/workflows/test-static.yml:1
Warn: no topLevel permission defined: .github/workflows/test-testrunner.yml:1
Warn: no topLevel permission defined: .github/workflows/test-typings.yml:1
Warn: no topLevel permission defined: .github/workflows/test-unit.yml:1
Warn: no topLevel permission defined: .github/workflows/test.yml:1
Warn: topLevel 'contents' permission set to 'write': .github/workflows/update.yaml:11

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Fuzzing

Determines if the project uses fuzzing.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

5

/10

Last Scanned on 2025-06-30

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More