google/boringssl

Health v2 · maintenance only

Adoption not part of the score

2262 stars · 897 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

BoringSSL is Google's fork of OpenSSL, serving as the TLS/SSL library in Chrome, Chromium, and Android. It is open source but explicitly not intended for general third-party use, with no API or ABI stability guarantees.

Use cases

• implement TLS in a Chromium-based browser
• need an SSL library for an Android system component
• port OpenSSL-based code to Google's TLS stack
• fuzz and audit a TLS implementation for security research
• vendor a TLS library into a project that tracks upstream changes

When to choose

• you are Google or a project already integrated with BoringSSL
• you can vendor and update your own copy of the library
• you need the exact TLS stack used by Chrome/Android

When to avoid

• you want a general-purpose TLS library with stable APIs
• you are a third party starting a new project (use OpenSSL, LibreSSL, or rustls instead)
• you rely on ABI stability across versions

Facets

library · maturity active

cryptography security http-server security developer-tools web-development cpp c cross-platform tls ssl openssl-fork google chrome no-api-stability android

Member repositories

For agents

markdown · JSON · MCP: product_card(name="google/boringssl")