0xplaygrounds/rig

⚙️🦀 Build modular and scalable LLM Applications in Rust

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 7th, 2026
Created on June 5th, 2024
Open Issues & Pull Requests: 118 (+0)
GitHub issues: Enabled
Number of forks: 958
Total Stargazers: 8,584 (+0)
Total Subscribers: 57 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.4 hours
Mean response time: 10.2 days
90th percentile: 17.7 days
Tracked items: 801

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 65
New in 7 days: 7
Closed in 7 days: 3
Avg open age: 166 days
Stale 30+ days: 48
Stale 90+ days: 25

Recent activity

Opened in 7 days: 5
Closed in 7 days: 0
Comments in 7 days: 31
Events in 7 days: 32

Top labels

  • feat (252)
  • bug (230)
  • non-breaking (59)
  • accepted (40)
  • model (31)
  • breaking (26)
  • feature request (19)
  • good first issue (18)

Detailed Description

Rig is a Rust library for building modular and scalable LLM-powered applications.

Rig addresses the challenge of constructing production-grade applications that integrate large language models by providing a framework designed specifically for Rust environments. The library emphasizes modularity and ergonomics, allowing developers to compose LLM capabilities into larger systems without tight coupling. It supports multiple runtime choices and integrations with various LLM providers and services, enabling flexible architecture decisions based on project requirements.

Rig suits teams building LLM applications in Rust who prioritize type safety, performance, and maintainability. The project is particularly appropriate for scalable systems where modularity matters, as the framework is structured around composable components rather than monolithic abstractions. Developers should be aware that the project is actively evolving with planned feature additions, and breaking changes are expected as the library matures.

The project maintains active development with regular updates and ongoing feature work. The maintainers provide comprehensive documentation including API references, guides, and blog content to support adoption. Community engagement is facilitated through a Discord channel, and the team actively solicits contributions through the issue tracker.