google/gts

☂️ TypeScript style guide, formatter, and linter.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 12th, 2026
Created on July 31st, 2017
Open Issues & Pull Requests: 60 (+0)
GitHub issues: Enabled
Number of forks: 212
Total Stargazers: 5,293 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 36.8 days
Mean response time: 141.5 days
90th percentile: 615.7 days
Tracked items: 18

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 500 days
Stale 30+ days: 13
Stale 90+ days: 13

Recent activity

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

Top labels

  • type: feature request (4)
  • semver: major (2)
  • type: bug (2)
  • priority: p2 (1)
  • type: process (1)
  • type: question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

gts is a TypeScript style guide, formatter, and linter that enforces Google's opinionated coding standards with zero configuration required.

The tool solves the problem of style inconsistency and code review friction by providing a pre-configured, opinionated approach to TypeScript formatting and linting. It combines ESLint for style enforcement with Prettier for code reformatting, eliminating the need for teams to debate syntax conventions or maintain custom lint configurations. Running `gts init` sets up a project with an opinionated tsconfig.json, adds necessary development dependencies, and installs npm scripts for linting, fixing, compiling, and cleaning code.

Teams should adopt gts if they value consistency and want to eliminate style discussions from code reviews without the overhead of configuration management. It suits any TypeScript project where enforcing a single, well-reasoned style guide is preferable to allowing customization. The tool allows dropping down to raw ESLint configuration if a project needs to extend the shared config with custom rules or integrate with the broader ESLint ecosystem, such as editor plugins. The README does not compare gts to alternative style tools.

The project maintains active development with regular updates to keep pace with TypeScript and ESLint ecosystem changes. The tool is designed to support all active and maintenance versions of Node.js according to the Node.js release schedule. Integration support extends to pre-commit frameworks, allowing teams to enforce style checks as part of their version control workflows.