Is Googleauth Safe?
Googleauth — Nerq Trust Score 68.2/100 (B- grade). Score based on 2 independent trust signals. Last analyzed: 2026-04-12
Googleauth is a Ruby gem with a Nerq Trust Score of 68.2/100 (B-), based on 3 independent data dimensions. Last analyzed: 2026-04-12 Security: 90/100. Popularity: 100/100. Data sourced from rubygems.org, GitHub, and NVD. Last updated: 2026-04-12. Machine-readable data (JSON).
Is Googleauth safe?
Trust Score Breakdown — Googleauth has a Nerq Trust Score of 68.2/100 (B-). Measured across 2 independent trust signals (as of 2026-04-12).
What is Googleauth's trust score?
Googleauth has a Nerq Trust Score of 68.2/100, earning a B- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Googleauth?
Googleauth's strongest signal is popularity at 100/100. No known vulnerabilities have been detected.
What is Googleauth and who maintains it?
| Author | Google LLC |
| Category | Ruby Gems |
| Source | N/A |
Googleauth Across Platforms
Same developer/company in other registries:
Similar Gems by Trust Score
Safety Guide: Googleauth
What is Googleauth?
Googleauth is a Ruby gem — Implements simple authorization for accessing Google APIs, and provides support for Application Default Credentials..
How to Verify Safety
Run bundle audit. Review on rubygems.org.
You can also check the trust score via API: GET /v1/preflight?target=googleauth
Key Safety Concerns for Ruby gem
When evaluating any Ruby gem, watch for: dependency vulnerabilities, maintenance status.
Measured Signals
Googleauth has a Nerq Trust Score of 68/100 (B-). This score is a composite of automated measurements of security, maintenance, community, and quality signals.
Key Takeaways
- Googleauth has a Trust Score of 68/100 (B-).
- 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.
Detailed Score Analysis
| Dimension | Score |
|---|---|
| Security | 90/100 |
| Maintenance | 50/100 |
| Popularity | 100/100 |
| Quality | 65/100 |
| Community | 35/100 |
Based on 5 dimensions. Data from rubygems.org, GitHub, and NVD.
What data does Googleauth collect?
Googleauth is a Ruby gem maintained by Google LLC. It receives approximately 456,004,169 weekly downloads. Licensed under Apache-2.0.
As a development package, Googleauth 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: Googleauth Privacy Report · Privacy review
Is Googleauth secure?
Security score: 90/100 (0-100, higher = fewer measured security issues).
Nerq monitors this entity against NVD, OSV.dev, and registry-specific vulnerability databases for ongoing security assessment.
Full analysis: Googleauth Security Report
Googleauth Across Platforms
Same developer/company in other registries:
How we calculated this score
Googleauth's trust score of 68.2/100 (B-) is computed from rubygems.org, GitHub, and NVD. The score reflects 5 independent dimensions: security (90/100), maintenance (50/100), popularity (100/100), quality (65/100), community (35/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.
Signals last measured on April 12, 2026. Data version: 1.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Googleauth Safe?
What is Googleauth's trust score?
What are safer alternatives to Googleauth?
Does Googleauth have known vulnerabilities?
Is Googleauth actively maintained?
Popular in Ruby Gems
See Also
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.