Is Client Config Safe?

Client Config — Nerq Trust Score 84.5/100 (A- grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-20

Client Config is a npm package with a Nerq Trust Score of 84.5/100 (A-), based on 3 independent data dimensions. Last analyzed: 2026-03-20 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.

Measured Signals

Client Config has a Nerq Trust Score of 84/100 (A-). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

• Client Config has a Trust Score of 84/100 (A-).
• The score is a measured composite — it is not a suitability judgment. Evaluate the individual signals against your own requirements.
• Query the current measured values via the Nerq API.

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.