google/styleguide

Style guides for Google-originated open-source projects

Owned by Google

View on GitHub ↗Jump to charts ↓Open shareable report →

google/styleguide has 39k+ stars and 12k+ forks on GitHub, is written in HTML, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 29 minutes ago
Type:Documentation / SpecificationCategory(s):Cheatsheets, Checklists & Best PracticesLearning & Resources
Added to GitGenius on August 31st, 2026
Created on May 20th, 2015
Open Issues & Pull Requests: 90 (+0)
GitHub issues: Enabled
Number of forks: 12,927
Total Stargazers: 39,682 (+0)
Total Subscribers: 1,245 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 359.2 days
Mean response time: 1209.7 days
90th percentile: 3529.9 days
Tracked items: 146

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "lang:python" is answered fastest, typically in about 3 hours, while "auto-migrated" waits about 118 months. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 1
Closed in 7 days: 41
Avg open age: 1,038 days
Stale 30+ days: 20
Stale 90+ days: 17

Recent activity

Opened in 7 days: 1
Closed in 7 days: 41
Comments in 7 days: 37
Events in 7 days: 85

Top labels

  • cpplint (57)
  • lang:java (30)
  • auto-migrated (18)
  • lang:python (11)
  • question (10)
  • lang:js (9)
  • enhancement (8)
  • lang:cpp (8)

Most active issues this week

Sign in to see which issues are moving.
Sign in

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.