Google API Linter
linter.aip.dev
- Free plan
- Self-hosted
What Google API Linter is
Google API Linter is a self-hosted command-line tool for checking protocol buffer API surfaces against standards in Google API Improvement Proposals. It groups rules by AIP block, with core and client library rules enabled by default and Cloud rules disabled by default. Developers can configure checks with command-line flags, a configuration file, or comments in proto files. The CLI reports findings as YAML, JSON, GitHub output, or a summary table, using YAML by default, and suggests corrections when it can. Installation uses Go install into the local Go binary directory. The project is free, open-source software under the Apache 2.0 license, with CI/CD integration and GitHub issue support. Coverage is incomplete: some AIP guidance cannot become lint rules, and some possible rules have not yet been written. Rule changes can also make previously clean files report problems because the project does not use semantic versioning.
Who it suits
This tool suits developers maintaining Protocol Buffer APIs who need configurable checks against AIP requirements. It is appropriate for teams wanting self-hosted linting in development or CI/CD workflows.
Good to know, and what to watch
- Free Apache 2.0 open-source software
- Configurable through flags, files, or proto comments
- Multiple CLI output formats
- Suggests fixes for some mistakes
- Core and client rules enabled by default
- Some AIP guidance lacks lint rules
- Some expressible rules may be missing
- Cloud rules are disabled by default
- No semantic versioning
Plans
Every plan and priceApache 2.0 open-source software
Open source
The verdict
Google API Linter gives Protocol Buffer API teams a focused, configurable standards checker with several output formats. Its incomplete rule coverage and changing findings require teams to understand what the linter does not represent.
What the maker publishes
- Configuration
- Rules can be configured with CLI flags, a configuration file, or comments in proto files. source
- Contributions
- The project accepts contributions, and its contributing guide identifies writing a new lint rule as a common contribution. source
- Corrections
- When able, the linter suggests fixes for common mistakes and inconsistencies. source
- Coverage limit
- The documentation says some AIP guidance cannot be expressed as lint rules, and some expressible rules may not yet be written. source
- Installation
- The documentation instructs users to install the CLI with Go install into the local Go binary directory. source
- Intended users
- The tool is for developers working with APIs defined in protocol buffers and API standards. source
- License
- The software and its documentation are licensed under Apache 2.0. source
- Output formats
- The CLI supports YAML, JSON, GitHub, and summary table output, with YAML as the default. source
- Purpose
- The linter checks protocol buffer API surfaces for compliance with Google API standards documented in API Improvement Proposals. source
- Rule groups
- Rules are grouped by AIP block, with core and client library rules enabled by default and Cloud rules disabled by default. source
- Rule requirements
- Each linter rule must correspond to an AIP that mandates the behavior. source
- Support
- The project documentation links to GitHub to file an issue and view the source repository. source
- Versioning
- The project says it does not follow semantic versioning because adding or correcting rules can make previously clean files report problems. source
Checked against the maker's pages on 4 Oct 2026.