flosse/rust-web-framework-comparison

A comparison of some web frameworks and libs written in Rust

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 11th, 2026
Created on August 16th, 2015
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 224
Total Stargazers: 5,758 (+0)
Total Subscribers: 166 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.7 hours
Mean response time: 28.5 days
90th percentile: 162.6 days
Tracked items: 6

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 834 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

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

Top labels

  • help wanted (3)
  • question (3)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

rust-web-framework-comparison is a comparison resource that catalogs web frameworks and libraries written in Rust.

The project addresses the challenge of navigating Rust's web ecosystem by organizing frameworks into categories covering frontend frameworks for WebAssembly, server frameworks at both high and low levels, client frameworks, templating engines, and WebSocket libraries. It distinguishes between current and outdated options, focusing exclusively on frameworks compatible with stable Rust. This structured approach helps developers understand what tools are available across different layers of web development rather than recommending a single solution.

The resource suits developers new to Rust web development who need an overview of the landscape, or those evaluating which framework might fit their specific use case. It covers both frontend development via WebAssembly and backend server development, making it useful for full-stack projects. The separation of high-level and low-level server frameworks helps developers choose based on their preference for abstraction versus control.

The project's issue tracker shows activity concentrated on questions and enhancement requests, indicating ongoing engagement with users seeking clarification about frameworks and suggestions for improving the comparison itself.