browserslist

v4.24.3

Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset For more information about how to use this package see README

Latest version published 8 days ago

License: MIT

NPM

GitHub

Package Health Score

91 / 100

security
No known security issues
popularity
Key ecosystem project
maintenance
Healthy
community
Active

Explore Similar Packages

Security

No known security issues

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
4.24.3	\|	12/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.24.2	\|	10/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.23.3	\|	08/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.2.8	\|	05/2018		0 C 0 H 1 M 0 L	0 H 0 M 0 L
2.11.3	\|	01/2018		0 C 0 H 1 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

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

Get started free

Popularity

Key ecosystem project

Weekly Downloads (44,752,566)

GitHub Stars: 13.06K
Forks: 720
Contributors: 180

Direct Usage Popularity

The npm package browserslist receives a total of 44,752,566 downloads a week. As such, we scored browserslist popularity level to be Key ecosystem project.

Based on project statistics from the GitHub repository for the npm package browserslist, we found that it has been starred 13,065 times.

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: No
Code of Conduct: No
Contributors: 180
Funding: Yes

A good and healthy external contribution signal for browserslist project, which invites more than one hundred open source maintainers to collaborate on the repository.

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

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 39
Open PR: 5
Last Release: 8 days ago
Last Commit: 8 days ago

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

We found that browserslist 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.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7

Age: 10 years
Dependencies: 4 Direct
Versions: 196
Install Size: 64.2 kB
Dist-tags: 1
# of Files: 11
Maintainers: 1
TS Typings: Yes

browserslist 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.

Not sure how to use browserslist?

To help you get started, we've collected the most common ways that browserslist is being used within popular public projects.

DestinyItemManager / DIM / src / browsercheck.js View on Github

function getBrowserVersionFromUserAgent(agent) {
  var browserName = getBrowserName(agent);
  var version = (browserName === 'ios_saf'
    ? agent.os.version
    : agent.browser.version || agent.os.version || ''
  ).split('.');
  while (version.length > 0) {
    try {
      return browserslist(browserName + ' ' + version.join('.'))[0];
    } catch (e) {
      // Ignore unknown browser query error
    }
    version.pop();
  }
  return 'unknown';
}

View more ways to use browserslist

Browserslist

The config to share target browsers and Node.js versions between different front-end tools. It is used in:

All tools will find target browsers automatically, when you add the following to package.json:

  "browserslist": [
    "defaults and fully supports es6-module",
    "maintained node versions"
  ]

Or in .browserslistrc config:

# Browsers that we support

defaults and fully supports es6-module
maintained node versions

Developers set their version lists using queries like last 2 versions to be free from updating versions manually. Browserslist will use caniuse-lite with Can I Use data for this queries.

You can check how config works at our playground: browsersl.ist

Docs

Read full docs here.

browserslist dependencies

caniuse-lite electron-to-chromium node-releases update-browserslist-db

FAQs

What is browserslist?

Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset. Visit Snyk Advisor to see a full health score report for browserslist, including popularity, security, maintenance & community analysis.

Is browserslist popular?

The npm package browserslist receives a total of 44,752,566 weekly downloads. As such, browserslist popularity was classified as a key ecosystem project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is browserslist well maintained?

We found that browserslist demonstrated a healthy version release cadence and project activity. It has a community of 180 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is browserslist safe to use?

The npm package browserslist was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 December-2024, at 01:57 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP