microg/gmscore

Free implementation of Play Services

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 4th, 2026
Created on April 23rd, 2014
Open Issues & Pull Requests: 1,409 (+1)
GitHub issues: Enabled
Number of forks: 3,133
Total Stargazers: 14,496 (+0)
Total Subscribers: 262 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.9 hours
Mean response time: 55.4 days
90th percentile: 83.1 days
Tracked items: 789

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "invalid / wontfix" is answered fastest, typically in about 4 hours, while "🗺 Maps" waits about 3 weeks. 64% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 526
New in 7 days: 13
Closed in 7 days: 6
Avg open age: 650 days
Stale 30+ days: 469
Stale 90+ days: 384

Recent activity

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

Top labels

  • bug (265)
  • enhancement (98)
  • invalid / wontfix (72)
  • question (66)
  • confirmed (20)
  • 🗺 Maps (11)
  • 👥 Google Accounts (7)
  • 📍 Location (7)

Detailed Description

microG Services is a free and open source framework that provides a replacement for Google Play Services on Android systems where the proprietary service is unavailable or undesired.

The problem it solves is that many Android applications depend on Google Play Services for core functionality including authentication, cloud messaging, push notifications, geolocation, and maps integration. microG implements these APIs as a compatible alternative, allowing such applications to function on devices running custom Android distributions, de-Googled systems, or environments where Play Services cannot be installed. The framework achieves this by providing FLOSS implementations of the Play Services interfaces that applications expect.

Developers should choose this tool if they are building or maintaining Android systems that cannot or should not include proprietary Google Play Services, or if they want to reduce dependency on Google infrastructure. It suits projects targeting privacy-conscious users, custom ROM distributions, or environments with restricted access to Google services. The project is particularly valuable for applications that would otherwise be unusable on such systems, as it enables broad app compatibility without requiring the proprietary framework.

The project maintains active engagement with its community through translation contributions, indicating ongoing localization efforts. Development activity shows consistent attention to the codebase with regular updates addressing the multiple service categories the framework supports. The project sustains a long-term commitment to compatibility, maintaining implementations across authentication, messaging, location services, and mapping APIs that evolve alongside changes in the Android ecosystem and Google's service offerings.