Is Credential Provider Login Safe?

Credential Provider Login — Nerq Trust Score 84.2/100 (A- grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-06-19.

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

Is Credential Provider Login safe?

YES — Credential Provider Login has a Nerq Trust Score of 84.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 → Credential Provider Login Privacy Report →

What is Credential Provider Login's trust score?

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

Security
90
Popularity
100

What are the key security findings for Credential Provider Login?

Credential Provider Login's strongest signal is popularity at 100/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

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

What is Credential Provider Login 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

Credential Provider Login vs @supabase/storage-jsCredential Provider Login vs @supabase/realtime-jsCredential Provider Login vs @supabase/functions-js

Safety Guide: Credential Provider Login

What is Credential Provider Login?

Credential Provider Login is a Node.js package — AWS credential provider that sources credentials from aws login cached tokens.

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/credential-provider-login

Key Safety Concerns for Node.js package

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

Trust Assessment

Credential Provider Login 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
Maintenance96/100
Popularity100/100
Quality80/100
Community45/100

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

What data does Credential Provider Login collect?

Credential Provider Login is a Node.js package maintained by amzn-oss. It receives approximately 21,547,838 weekly downloads. Licensed under Apache-2.0.

As a development package, Credential Provider Login 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: Credential Provider Login Privacy Report · Privacy review

Is Credential Provider Login secure?

Security score: 90/100. Credential Provider Login 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: Credential Provider Login Security Report

How we calculated this score

Credential Provider Login's trust score of 84.2/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 (96/100), popularity (100/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 19, 2026. Data version: 1.0.

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

Frequently Asked Questions

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