google/libphonenumber · Security & risks

Authoritative risk signals for google/libphonenumber — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.

Architecture Security & risks Dependencies License Maintenance Alternatives Vs Full analysis

Dependency CVEs (deps.dev)

Critical

0 direct

High

0 direct

Moderate

Deps scanned

0 direct

OpenSSF Scorecard · 9.2/10

Branch-Protection—
Packaging—
CII-Best-Practices2/10
Signed-Releases8/10
Vulnerabilities8/10
Binary-Artifacts9/10
Pinned-Dependencies9/10
Token-Permissions9/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about google/libphonenumber

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.