Is Client Common Safe?

Client Common — Nerq Trust Score 88.2/100 (A grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-07-30.

Yes, Client Common is safe to use. Client Common is a npm package with a Nerq Trust Score of 88.2/100 (A), based on 3 independent data dimensions. Recommended for production use. Security: 90/100. Popularity: 90/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-20. Machine-readable data (JSON).

Is Client Common safe?

YES — Client Common has a Nerq Trust Score of 88.2/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 → Client Common Privacy Report →

What is Client Common's trust score?

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

Security
90
Popularity
90

What are the key security findings for Client Common?

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

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

What is Client Common and who maintains it?

Authorserdec
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@supabase/functions-js (90)workbox-webpack-plugin (89)expo-router (89)@auth0/auth0-spa-js (89)@react-native-community/datetimepicker (89)
See all safest Npm →

Compare

Client Common vs @supabase/functions-jsClient Common vs workbox-webpack-pluginClient Common vs expo-router

Safety Guide: Client Common

What is Client Common?

Client Common is a Node.js package — Official JS client for ClickHouse DB - common types.

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=@clickhouse/client-common

Key Safety Concerns for Node.js package

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

Trust Assessment

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

Key Takeaways

Frequently Asked Questions

Is Client Common Safe?
Yes, it is safe to use. @clickhouse/client-common with a Nerq Trust Score of 88.2/100 (A). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (90/100).
What is Client Common's trust score?
@clickhouse/client-common: 88.2/100 (A). Score based on Security (90/100), Popularity (90/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@clickhouse/client-common
What are safer alternatives to Client Common?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @clickhouse/client-common scores 88.2/100.
Does Client Common have known vulnerabilities?
Nerq checks Client Common 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 Client Common actively maintained?
Client Common 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