briansmith/ring

An experiment.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Type:Library / SDKCategory(s):Privacy & CryptographySecurity & Privacy
Added to GitGenius on September 16th, 2026
Created on July 22nd, 2015
Open Issues & Pull Requests: 51 (+0)
GitHub issues: Enabled
Number of forks: 804
Total Stargazers: 4,107 (+0)
Total Subscribers: 46 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.7 days
Mean response time: 340.2 days
90th percentile: 1489.7 days
Tracked items: 261

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Work labelled "usability" is answered fastest, typically in about 10 days, while "test-coverage" waits about 17 months. Three people close 95% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,036 days
Stale 30+ days: 14
Stale 90+ days: 11

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • good-first-bug (27)
  • test-coverage (16)
  • usability (15)
  • static-analysis-and-type-safety (9)
  • rsa (7)
  • performance (5)
  • duplicate (4)
  • semver-breaking-change (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Ring is a cryptography library written in Rust that provides safe, fast implementations of common cryptographic operations.

The library addresses the need for cryptographic primitives that are both performant and resistant to side-channel attacks. Ring achieves this by implementing core algorithms in assembly language where necessary to ensure constant-time execution and prevent timing-based vulnerabilities. The library wraps these low-level implementations with a Rust interface that enforces safe usage patterns at compile time, preventing common cryptographic mistakes like key reuse or algorithm misuse.

Ring is suited for Rust applications that require cryptographic operations without the overhead of larger frameworks or the complexity of binding to C libraries. It works well for projects where performance matters and where developers want cryptographic guarantees enforced by the type system rather than relying on runtime checks or documentation. The library is particularly valuable for systems programming, embedded applications, and scenarios where side-channel resistance is a concern.

The project maintains a focused scope and does not appear to be under active feature expansion. Development activity is minimal, with infrequent updates and a narrow maintenance posture that prioritizes stability over adding new capabilities. The codebase shows signs of being treated as a stable, mature implementation rather than an actively evolving platform.