dimforge/rapier

2D and 3D physics engines focused on performance.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 28 minutes ago
Added to GitGenius on September 11th, 2026
Created on August 25th, 2020
Open Issues & Pull Requests: 57 (+0)
GitHub issues: Enabled
Number of forks: 386
Total Stargazers: 5,737 (+0)
Total Subscribers: 55 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.8 days
Mean response time: 273.7 days
90th percentile: 841.0 days
Tracked items: 179

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "D-Medium" is answered fastest, typically in about 3 weeks, while "D-Difficult" waits about 10 months. Only 7% of issues opened in the past year have been closed. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 599 days
Stale 30+ days: 21
Stale 90+ days: 17

Recent activity

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

Top labels

  • C-Bug (39)
  • A-Dynamics (36)
  • D-Medium (29)
  • P-High (27)
  • C-Enhancement (24)
  • D-Difficult (23)
  • P-Medium (21)
  • A-Geometry (13)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Rapier is a set of 2D and 3D physics engines for the Rust programming language focused on performance.

Rapier addresses the need for efficient physics simulation in games, animation, and robotics by providing separate crates for 2D and 3D scenarios, each available in both single-precision and double-precision floating-point variants. The engine prioritizes performance through SIMD-batched constraint solving and contact processing that runs by default, with an optional parallel feature enabling multithreading of the entire physics step across broad phase, narrow phase, and solver stages via rayon. On heterogeneous-core processors, the tool supports pinning work to performance cores to avoid bottlenecks from efficiency cores.

Rapier suits projects requiring physics simulation in Rust where performance matters. The tool is particularly relevant for game developers and robotics applications needing both 2D and 3D capabilities. Python bindings are available for projects that need to integrate physics simulation into Python codebases. The README does not compare Rapier to alternative physics engines, so no comparative guidance can be offered.

The project maintains a substantial base of adopters who report issues from real-world use rather than the core team driving the issue agenda. However, responses to issues and pull requests often wait weeks or longer for initial attention. Work in the issue tracker concentrates on bug fixes and dynamics-related features, with most issues classified as medium difficulty.