chrome-launcher

v0.15.1

Launch latest Chrome with the Devtools Protocol port open

Apache-2.0
Latest version published 28 days ago
    npm install chrome-launcher
  

Package Health Score

92 / 100

Security

No known security issues
Powered by Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
0.15.1 | 05/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.14.2 | 11/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.13.4 | 07/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.12.0 | 10/2019
  • 0
    H
  • 0
    M
  • 0
    L
0.11.2 | 07/2019
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test chrome-launcher
Get started free

Popularity

Influential project

Weekly Downloads (1,400,042)

Download trend
Dependents
452
GitHub Stars
929
Forks
160
Contributors
60

Direct Usage Popularity

TOP 5%

The npm package chrome-launcher receives a total of 1,400,042 downloads a week. As such, we scored chrome-launcher popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package chrome-launcher, we found that it has been starred 929 times, and that 452 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
60
Funding
No

With more than 10 contributors for the chrome-launcher repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like chrome-launcher is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 92/100 package health 92/100

Maintenance

Healthy

Commit Frequency

Open Issues
58
Open PR
5
Last Release
28 days ago
Last Commit
20 days ago

Further analysis of the maintenance status of chrome-launcher based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that chrome-launcher demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=12.13.0

Age
5 years
Dependencies
4 Direct
Versions
39
Install Size
184 kB
Dist-tags
1
# of Files
44
Maintainers
5
TS Typings
Yes

chrome-launcher has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.