briansmith/ring
An experiment. observed · 2026-08-28
Health v2 · maintenance only
75/100
- Activity 94
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4060
- days_rel: n/a
- days_push: 41
- n_releases_24m: 0
Adoption not part of the score
4104 stars · 799 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
ring is a Rust library providing safe, fast cryptographic primitives (hashing, AEAD, signatures, key agreement) built largely on BoringSSL's C and assembly code. The author explicitly describes it as an experiment and discourages general-purpose dependence.
Use cases
- encrypt and decrypt data with AES-GCM or ChaCha20-Poly1305 in Rust
- generate and verify Ed25519 or RSA signatures
- compute SHA-256 digests and HMACs
- perform ECDH key agreement for TLS-like protocols
- generate cryptographically secure random values
When to choose
- you need a Rust crypto library with a misuse-resistant API and BoringSSL-derived primitives
- you are already using Rust TLS stacks like rustls that depend on it
- you want constant-time, assembly-optimized crypto on common platforms
When to avoid
- you need a formally supported, general-purpose crypto library with long-term stability guarantees
- you need a broad feature set like certificates, TLS protocol handling, or X.509 parsing
- you require side-channel guarantees beyond what the project documents in SIDE-CHANNELS.md
Facets
library · maturity maintenance
cryptography security security developer-tools rust cross-platform crypto-primitives boringssl-derived tls-crypto safe-api
1 source
- readme: https://github.com/briansmith/ring · fetched 2026-08-28 · e006fc2ae791
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| briansmith/ring | main | 75 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem