Is Chrome Cmd Safe?

Chrome Cmd — Nerq Trust Score 68.8/100 (B- grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-08-02.

Use Chrome Cmd with some caution. Chrome Cmd is a npm package with a Nerq Trust Score of 68.8/100 (B-), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 15/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-21. Machine-readable data (JSON).

Is Chrome Cmd safe?

CAUTION — Chrome Cmd has a Nerq Trust Score of 68.8/100 (B-). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → Chrome Cmd Privacy Report →

What is Chrome Cmd's trust score?

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

Security
90
Popularity
15

What are the key security findings for Chrome Cmd?

Chrome Cmd's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

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

What is Chrome Cmd and who maintains it?

Authorlucasvtiradentes
Categorynpm Packages
SourceN/A

Chrome Cmd Across Platforms

Same developer/company in other registries:

branch-ctx
57/100 · pypi

Similar Npm by Trust Score

@vue-macros/setup-block (78)vite-plugin-symfony (78)@actions/languageservice (78)@marko/webpack (78)@vue-macros/setup-component (78)
See all safest Npm →

Compare

Chrome Cmd vs @vue-macros/setup-blockChrome Cmd vs vite-plugin-symfonyChrome Cmd vs @actions/languageservice

Safety Guide: Chrome Cmd

What is Chrome Cmd?

Chrome Cmd is a Node.js package — Control Chrome from the command line - List tabs, execute JavaScript, and more.

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=chrome-cmd

Key Safety Concerns for Node.js package

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

Trust Assessment

Chrome Cmd has a Nerq Trust Score of 69/100 (B-) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Chrome Cmd Safe?
Use with some caution. chrome-cmd with a Nerq Trust Score of 68.8/100 (B-). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (15/100).
What is Chrome Cmd's trust score?
chrome-cmd: 68.8/100 (B-). Score based on Security (90/100), Popularity (15/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=chrome-cmd
What are safer alternatives to Chrome Cmd?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. chrome-cmd scores 68.8/100.
Does Chrome Cmd have known vulnerabilities?
Nerq checks Chrome Cmd 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 Chrome Cmd actively maintained?
Chrome Cmd 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 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