wger-project/wger

Self hosted FLOSS fitness/workout, nutrition and weight tracker

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 9th, 2026
Created on January 19th, 2013
Open Issues & Pull Requests: 249 (+1)
GitHub issues: Enabled
Number of forks: 1,014
Total Stargazers: 6,904 (+0)
Total Subscribers: 81 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.2 days
Mean response time: 288.6 days
90th percentile: 251.8 days
Tracked items: 32

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 1,127 days
Stale 30+ days: 10
Stale 90+ days: 10

Recent activity

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

Top labels

  • bug (1)
  • effort: medium (1)
  • good first issue (1)

Detailed Description

wger is a self-hosted fitness and workout tracker that combines workout planning, nutrition logging, and progress tracking in a single application.

The tool addresses the need for a privacy-respecting, customizable fitness management system. It lets users create workout routines with automatic weight progression, log meals against a food database sourced from Open Food Facts, track body weight and custom measurements, and maintain a photo gallery of fitness progress. The application includes a built-in exercise wiki that users can contribute to, and it exposes a REST API for third-party integrations. Multi-user support enables basic gym management workflows.

wger suits individuals and small gyms seeking self-hosted alternatives to commercial fitness apps. The project is deployable via Docker, making it accessible to users without deep infrastructure expertise. The cross-platform availability through Android, iOS, F-Droid, and Flathub means users can access their data from multiple devices. The tool's strength lies in combining workout, nutrition, and progress tracking in one system rather than requiring separate applications. Community translation via Weblate ensures multilingual support.

The project maintains active continuous integration with automated testing. Code coverage is tracked and publicly reported. The exercise wiki and translation infrastructure indicate ongoing community contribution beyond core development. Development activity spans multiple functional areas including API endpoints, mobile app support, and localization workflows.