Is Google Auth Library Safe?

Google Auth Library — Nerq Trust Score 84.5/100 (A- grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-04-24.

Yes, Google Auth Library is safe to use. Google Auth Library 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: 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 Google Auth Library safe?

YES — Google Auth Library has a Nerq Trust Score of 84.5/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 → Google Auth Library Privacy Report →

What is Google Auth Library's trust score?

Google Auth Library has a Nerq Trust Score of 84.5/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 Google Auth Library?

Google Auth Library'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 Google Auth Library and who maintains it?

Authorgoogle-wombot
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

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

Compare

Google Auth Library vs @supabase/storage-jsGoogle Auth Library vs @supabase/realtime-jsGoogle Auth Library vs @supabase/functions-js

Safety Guide: Google Auth Library

What is Google Auth Library?

Google Auth Library is a Node.js package — Google APIs Authentication Client Library for Node.js.

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=google-auth-library

Key Safety Concerns for Node.js package

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

Trust Assessment

Google Auth Library 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
Popularity100/100
Quality80/100
Community40/100

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

What data does Google Auth Library collect?

Google Auth Library is a Node.js package maintained by google-wombot. It receives approximately 35,985,995 weekly downloads. Licensed under Apache-2.0.

As a development package, Google Auth Library 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: Google Auth Library Privacy Report · Privacy review

Is Google Auth Library secure?

Security score: 90/100. Google Auth Library 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: Google Auth Library Security Report

How we calculated this score

Google Auth Library's trust score of 84.5/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 (100/100), quality (80/100), community (40/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 April 24, 2026. Data version: 1.0.

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

Frequently Asked Questions

Is Google Auth Library Safe?
Yes, it is safe to use. google-auth-library with a Nerq Trust Score of 84.5/100 (A-). Strongest signal: popularity (100/100). Score based on Security (90/100), Popularity (100/100).
What is Google Auth Library's trust score?
google-auth-library: 84.5/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=google-auth-library
What are safer alternatives to Google Auth Library?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. google-auth-library scores 84.5/100.
Does Google Auth Library have known vulnerabilities?
Nerq checks Google Auth Library 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 Google Auth Library actively maintained?
Google Auth Library 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