pkg.soopen package index

brew / 排名 6719

使用 Homebrew, Nix 安装 api-linter

查看 api-linter 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install api-linter

local Homebrew formula metadata

Linux

Nix已验证 · 92%
nix profile install nixpkgs#api-linter

nixpkgs package indexes · pkgs/by-name/ap/api-linter/package.nix · 来源: api.github.com

概览

软件包摘要

Linter for APIs defined in protocol buffers

命令和别名

  • api-linter

历史

项目历史与用法

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.

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • 未记录 Homebrew bottle 元数据。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

可执行文件

已安装的可执行文件

命令类型暴露范围备注
api-linter可执行文件已索引可执行文件从本地可执行文件索引发现。

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-08-03
管理器版本2.3.1
管理器更新时间2026-07-25
本地数据未知
上游不可用
检测到的最新版本未检测到
  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:api-linter
版本2.3.1
软件包管理器Homebrew
主页https://linter.aip.dev/
仓库https://github.com/googleapis/api-linter
最后更新2026-07-25T14:18:26-04:00
Pulseupdated
Bottle未记录
服务未声明

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix95%

api-linter

nix profile install nixpkgs#api-linter
  • normalized package name match
  • 匹配方式:API Linter
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ap/api-linter/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation