Is Selenium Driver With Chrome Config Safe?

Selenium Driver With Chrome Config — Nerq Trust Score 48.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Selenium Driver With Chrome Config is a npm package (node_env= dev will run selenium locally) with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Last analyzed: 2026-03-25 Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-25. Machine-readable data (JSON).

Is Selenium Driver With Chrome Config safe?

Trust Score Breakdown — Selenium Driver With Chrome Config has a Nerq Trust Score of 48.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Selenium Driver With Chrome Config Privacy Report →

What is Selenium Driver With Chrome Config's trust score?

Selenium Driver With Chrome Config has a Nerq Trust Score of 48.2/100, earning a D grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Selenium Driver With Chrome Config?

Selenium Driver With Chrome Config's strongest signal is security at 90/100. No known vulnerabilities have been detected.

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

What is Selenium Driver With Chrome Config and who maintains it?

Authormadvinking
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

react-library-boilerplate-for-npm (58)bindler (58)@yassidev/nuxt-directus (58)spectro-kubernetes-client (58)pocketto-svelte (58)
See all safest Npm →

Compare

Selenium Driver With Chrome Config vs react-library-boilerplate-for-npmSelenium Driver With Chrome Config vs bindlerSelenium Driver With Chrome Config vs @yassidev/nuxt-directus

Safety Guide: Selenium Driver With Chrome Config

What is Selenium Driver With Chrome Config?

Selenium Driver With Chrome Config is a Node.js package — node_env= dev will run selenium locally.

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=selenium_driver_with_chrome_config

Key Safety Concerns for Node.js package

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

Measured Signals

Selenium Driver With Chrome Config has a Nerq Trust Score of 48/100 (D). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Selenium Driver With Chrome Config Safe?
selenium_driver_with_chrome_config with a Nerq Trust Score of 48.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Selenium Driver With Chrome Config's trust score?
selenium_driver_with_chrome_config: 48.2/100 (D). Score based on Security (90/100), Popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=selenium_driver_with_chrome_config
What are safer alternatives to Selenium Driver With Chrome Config?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. selenium_driver_with_chrome_config scores 48.2/100.
Does Selenium Driver With Chrome Config have known vulnerabilities?
Nerq checks Selenium Driver With Chrome Config 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.
Is Selenium Driver With Chrome Config actively maintained?
Selenium Driver With Chrome Config maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy