# 使用 Homebrew, Nix 安装 api-linter
查看 api-linter 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。
## 安装
```sh
sudo av install brew:api-linter
```
其他安装命令:
### macOS
- Homebrew (100%):
```sh
brew install api-linter
```
证据: local Homebrew formula metadata
### Linux
- Nix (92%):
```sh
nix profile install nixpkgs#api-linter
```
证据: nixpkgs package indexes: pkgs/by-name/ap/api-linter/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
## 软件包事实
- **软件包键:** brew:api-linter
- **软件包管理器:** Homebrew
- **版本:** 2.3.1
- **来源摘要:** Linter for APIs defined in protocol buffers
- **主页:**
- **仓库:**
- **最后更新:** 2026-07-25T14:18:26-04:00
- **已生成:** 2026-08-03T19:37:03+00:00
## 可执行文件
- api-linter (别名)
## 安装行为
- Bottle: 不可用
## 版本和新鲜度
- 页面生成时间: 2026-08-03
- 管理器版本: 2.3.1
## 项目历史与用法
Google API Linter is a Go command-line linter for APIs defined in protocol buffers. It checks protobuf API surfaces against Google's API Improvement Proposals, making Google's API design guidance enforceable in local development and CI.
### 项目历史
The public GitHub repository was created in 2019 under googleapis. The README and official documentation frame the tool as a companion to Google's AIP guidance: it can identify common mistakes in API surfaces, offer fixes where possible, and document individual lint rules.
The project explicitly does not follow strict semantic versioning. Its README explains that new or corrected lint rules can be breaking for users because previously clean files may begin reporting findings, so release numbers reflect the linter's core interface rather than a pure compatibility promise.
### 采用历史
api-linter is most naturally adopted by teams designing protobuf APIs in the Google style. The README documents installation with Go and notes a Google-internal released binary for internal source control users, while the batch input shows Homebrew and Nix packaging for external command-line installation.
### 使用方式
The basic invocation is api-linter followed by one or more proto files. It supports proto import paths, descriptor sets, rule listing, structured output formats such as YAML, JSON, GitHub, and summary, and a set-exit-status flag for CI enforcement.
Configuration is supplied explicitly through the --config flag or inline proto comments. The official configuration docs show JSON and YAML config examples that enable or disable rules by included or excluded path, but they do not document a default config-file path, so no config-file-location is recorded here.
### 为什么软件包爱好者会关心
For package-manager users, api-linter is a compact example of policy-as-CLI: it packages a large body of API-design convention into a reproducible binary. It matters to protobuf-heavy shops because it can be pinned, run in presubmit checks, and upgraded deliberately when new lint rules land.
### 时间线
- 2019: Public googleapis/api-linter repository created.
- 2025: Version 2.0.0 released, marking a major core-interface version.
- 2026: Versions 2.1, 2.2, and 2.3 continued rule and interface evolution.
### Related projects
- The linter is tied to API Improvement Proposals at aip.dev and to Protocol Buffers API definitions. It is adjacent to protobuf compilers, buf-based linting workflows, and API governance tooling.
### 来源
-
-
-
-
- input source_facts.package-manager
## 安全说明
narrow executable package without higher-risk signals.
- **Geiger 风险:** 绿色 / 低
- narrow executable package without higher-risk signals
## 其他软件包管理器记录
- Nix - api-linter: normalized package name match | nixpkgs package indexes: pkgs/by-name/ap/api-linter/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
## Combined YAML source
View the package source record on GitHub. [combined/api-linter.yml](https://github.com/mxcl/pkgdb/blob/main/combined/api-linter.yml)
## 来源
- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph