Is Client Sdk Safe?

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

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

Is Client Sdk safe?

YES — Client Sdk has a Nerq Trust Score of 80.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 Sdk Privacy Report →

What is Client Sdk's trust score?

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

Security
90
Popularity
45

What are the key security findings for Client Sdk?

Client Sdk'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: 45/100 — community adoption

What is Client Sdk and who maintains it?

Authorben.yael
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

webpack-dev-middleware (90)webpack (90)@cloudflare/workers-types (89)expo-constants (89)expo-asset (89)
See all safest Npm →

Compare

Client Sdk vs webpack-dev-middlewareClient Sdk vs webpackClient Sdk vs @cloudflare/workers-types

Safety Guide: Client Sdk

What is Client Sdk?

Client Sdk is a Node.js package — d-id client sdk.

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=@d-id/client-sdk

Key Safety Concerns for Node.js package

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

Trust Assessment

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