Is Client Secrets Manager Safe?

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

Yes, Client Secrets Manager is safe to use. Client Secrets Manager is a npm package with a Nerq Trust Score of 83.8/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-04-12. Machine-readable data (JSON).

Is Client Secrets Manager safe?

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

What is Client Secrets Manager's trust score?

Client Secrets Manager has a Nerq Trust Score of 83.8/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 Secrets Manager?

Client Secrets Manager'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 Secrets Manager and who maintains it?

Authoramzn-oss
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@supabase/storage-js (90)@supabase/realtime-js (90)@supabase/functions-js (90)@testing-library/react (90)@supabase/supabase-js (90)
See all safest Npm →

Compare

Client Secrets Manager vs @supabase/storage-jsClient Secrets Manager vs @supabase/realtime-jsClient Secrets Manager vs @supabase/functions-js

Safety Guide: Client Secrets Manager

What is Client Secrets Manager?

Client Secrets Manager is a Node.js package — AWS SDK for JavaScript Secrets Manager Client for Node.js, Browser and React Native.

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-sdk/client-secrets-manager

Key Safety Concerns for Node.js package

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

Trust Assessment

Client Secrets Manager 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

Detailed Score Analysis

DimensionScore
Security90/100
Maintenance100/100
Popularity90/100
Quality80/100
Community45/100

Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Client Secrets Manager collect?

Client Secrets Manager is a Node.js package maintained by amzn-oss. It receives approximately 5,182,215 weekly downloads. Licensed under Apache-2.0.

As a development package, Client Secrets Manager does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Client Secrets Manager Privacy Report · Privacy review

Is Client Secrets Manager secure?

Security score: 90/100. Client Secrets Manager has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

Licensed under Apache-2.0, allowing code inspection. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Client Secrets Manager Security Report

How we calculated this score

Client Secrets Manager's trust score of 83.8/100 (A-) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), maintenance (100/100), popularity (90/100), quality (80/100), community (45/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on June 14, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Client Secrets Manager Safe?
Yes, it is safe to use. @aws-sdk/client-secrets-manager with a Nerq Trust Score of 83.8/100 (A-). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (90/100).
What is Client Secrets Manager's trust score?
@aws-sdk/client-secrets-manager: 83.8/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=@aws-sdk/client-secrets-manager
What are safer alternatives to Client Secrets Manager?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @aws-sdk/client-secrets-manager scores 83.8/100.
Does Client Secrets Manager have known vulnerabilities?
Nerq checks Client Secrets Manager 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 Secrets Manager actively maintained?
Client Secrets Manager 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