Is Browserslist Safe?

Browserslist — Nerq Trust Score 84.5/100 (A- grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-04-01.

Yes, Browserslist is safe to use. Browserslist is a Node.js package with a Nerq Trust Score of 84.5/100 (A-), based on 3 independent data dimensions. It is recommended for production use. Security: 90/100. Popularity: 100/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Machine-readable data (JSON).

Is Browserslist safe?

YES — Browserslist has a Nerq Trust Score of 84.5/100 (A-). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → {name} Privacy Report →

What is Browserslist's trust score?

Browserslist has a Nerq Trust Score of 84.5/100, earning a A- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
100

What are the key security findings for Browserslist?

Browserslist's strongest signal is popularity at 100/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 100/100 — community adoption

What is Browserslist and who maintains it?

Authorai
Categorynpm
SourceN/A

Similar Npm by Trust Score

@testing-library/react (90)@supabase/supabase-js (90)@supabase/storage-js (90)@supabase/realtime-js (90)@supabase/functions-js (90)
See all safest Npm →

Safety Guide: Browserslist

What is Browserslist?

Browserslist is a Node.js package — Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=browserslist

Key Safety Concerns for Node.js packages

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Browserslist has a Nerq Trust Score of 84/100 (A-) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Privacy80/100
Reliability90/100
Transparency85/100
Maintenance60/100

Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Browserslist collect?

Browserslist is a Node.js package maintained by ai. It receives approximately 63,883,073 weekly downloads. Licensed under MIT.

As a development package, Browserslist does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Browserslist Privacy Report · Privacy review

Is Browserslist secure?

Security score: 90/100. Browserslist has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

Licensed under MIT, allowing code inspection. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Browserslist Security Report

How we calculated this score

Browserslist's trust score of 84.5/100 (A-) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), privacy (80/100), reliability (90/100), transparency (85/100), maintenance (60/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on April 01, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Browserslist safe to use?
Yes, it is safe to use. browserslist has a Nerq Trust Score of 84.5/100 (A-). Strongest signal: popularity (100/100). Score based on security (90/100), popularity (100/100).
What is Browserslist's trust score?
browserslist: 84.5/100 (A-). Score based on: security (90/100), popularity (100/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=browserslist
What are safer alternatives to Browserslist?
In the npm category, more Node.js packages are being analyzed — check back soon. browserslist scores 84.5/100.
Does Browserslist have known vulnerabilities?
Nerq checks Browserslist against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
How actively maintained is Browserslist?
Browserslist has a trust score of 84.5/100 (A-). Meets Nerq Verified threshold.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy Policy