Is Client Config Safe?

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

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

Safety Guide: Client Config

What is Client Config?

Client Config is a Node.js package — Responsible for translating stack outputs and metadata (read via the [deployed-backend-client](../deployed-backend-client/README.md)) into client config that can be consumed by the Amplify frontend li.

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=@aws-amplify/client-config

Key Safety Concerns for Node.js package

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

Trust Assessment

Client Config 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

• Client Config has a Trust Score of 84/100 (A-).
• Recommended for use — passes trust threshold.
• Always verify independently using the Nerq API.

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