Automic VaultAutomic Vault

brew

api-linter mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für api-linter in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install api-linter

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#api-linter

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

Überblick

Paketzusammenfassung

Linter for APIs defined in protocol buffers

Befehle und Aliase

  • api-linter

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
api-lintercliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version2.3.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.3.1

https://github.com/googleapis/api-linter

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:api-linter
Version2.3.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/api-linter
Homepagehttps://linter.aip.dev/
Repositoryhttps://github.com/googleapis/api-linter
Upstream-Dokumentationhttps://github.com/googleapis/api-linter#readme
LizenzApache-2.0
Quellarchivhttps://github.com/googleapis/api-linter/archive/refs/tags/v2.3.1.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameapi-linter
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

api-linter

nix profile install nixpkgs#api-linter
  • normalized package name match
  • Abgeglichen nach: 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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment