yihong0618/running_page

Make your own running home page

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 21 minutes ago
Added to GitGenius on September 15th, 2026
Created on September 17th, 2020
Open Issues & Pull Requests: 53 (+0)
GitHub issues: Enabled
Number of forks: 1,424
Total Stargazers: 4,525 (+0)
Total Subscribers: 44 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.6 hours
Mean response time: 15.7 days
90th percentile: 10.1 days
Tracked items: 149

Most active contributors

Sign in to see contributor activity.

How this project is maintained

70% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 71% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 32
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 679 days
Stale 30+ days: 31
Stale 90+ days: 30

Recent activity

Opened in 7 days: 0
Closed in 7 days: 2
Comments in 7 days: 3
Events in 7 days: 6

Top labels

  • documentation (3)
  • enhancement (3)
  • good first issue (2)
  • bug (1)
  • help wanted (1)
  • user-demo (1)

Detailed Description

Running Page is a static site generator that creates a personal running home page displaying activity data and visualizations.

The project solves the problem of aggregating running data from fitness platforms into a single personalized webpage. It works by syncing activity data from sources like Strava, Garmin, and Nike Club through GitHub Actions, storing the data in a local database, and rendering an interactive dashboard with maps, statistics, and elevation gain information. The tool uses MapCN for mapping by default but supports Mapbox as an alternative. Data synchronization runs automatically via GitHub workflows, pulling new activities and updating the site without manual intervention.

This tool suits runners who want a centralized, self-hosted view of their training data without relying on a single platform's interface. It works well for those comfortable with GitHub-based deployment through Vercel and who want to customize their running statistics display. The project integrates with multiple data sources, allowing users to pull from Strava, Garmin watches, Adidas, and Nike Club simultaneously. Anyone adopting the tool should be aware that schema updates occasionally require database migrations, particularly when new fields like elevation gain are added; the README provides specific instructions for handling these updates. Users choosing Mapbox over the default MapCN should obtain their own token rather than reusing shared credentials.

Development activity shows consistent maintenance with schema updates being documented and communicated to users through the README. The project addresses platform-specific requirements, such as Garmin's need for secret string configuration in GitHub Actions. Migration guidance is provided when database changes occur, indicating attention to backward compatibility for existing users. The tool receives updates that add new data fields and improve accuracy, with notes on limitations where applicable, such as elevation gain potentially requiring manual correction through platform-specific features.