google/styleguide

Style guides for Google-originated open-source projects

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 14 minutes ago
Added to GitGenius on August 31st, 2026
Created on May 20th, 2015
Open Issues & Pull Requests: 170 (+0)
GitHub issues: Enabled
Number of forks: 12,939
Total Stargazers: 39,554 (-1)
Total Subscribers: 1,248 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 138.4 days
Mean response time: 1053.5 days
90th percentile: 3314.8 days
Tracked items: 106

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. Only 5% of issues opened in the past year have been closed. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 31
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 894 days
Stale 30+ days: 25
Stale 90+ days: 24

Recent activity

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

Top labels

  • cpplint (57)
  • auto-migrated (13)
  • lang:java (10)
  • lang:python (9)
  • lang:go (7)
  • lang:cpp (6)
  • Type-Patch (4)
  • enhancement (4)

Detailed Description

Google Style Guides is a collection of style guides for multiple programming languages and formats used across Google-originated open-source projects.

The project addresses the problem of maintaining consistency across large codebases by documenting conventions for code style, naming, structure, and best practices. It covers ground ranging from naming conventions like camelCase to architectural decisions like avoiding global variables or exceptions. The guides are presented as reference documents that developers can consult when contributing to Google projects or when designing their own style standards.

Developers working on Google-originated open-source projects should use these guides as the authoritative reference for their contributions. The collection spans seventeen languages and formats including C++, Python, Java, Go, JavaScript, TypeScript, and others, making it useful for polyglot teams. The guides are also valuable as templates for organizations designing their own style standards, since they represent decisions made by experienced teams at scale. The project explicitly notes that external contributions are not accepted and that changes flow from Google's internal style guides outward, so these should be treated as read-only references rather than community-driven standards.

Development of the style guides is driven by Google's internal needs, with changes made to internal versions first before being copied into the public repository. The project does not actively solicit external pull requests, though issues that raise technical questions or point out mistakes may receive engagement. The guides themselves are stable reference documents rather than actively developed software, with updates reflecting shifts in Google's internal practices.