Automic VaultAutomic Vault

brew

linkerd mit Homebrew, Nix, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install linkerd

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install extras/linkerd

Scoop official bucket manifest trees · bucket/linkerd.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Command-line utility to interact with linkerd

Verlauf

Projektgeschichte und Nutzung

Linkerd is a Kubernetes-focused service mesh and CLI for adding observability, reliability, and security features to service-to-service traffic without changing application code. The Homebrew package supplies the linkerd command used to install, inspect, and operate the mesh.

Projektgeschichte

Linkerd came from Buoyant's work on production microservice reliability. Linkerd's 2017 CNCF announcement says it was created by Buoyant founders William Morgan and Oliver Gould in 2015 and built on ideas from Twitter's Finagle library; CNCF's 2021 graduation announcement describes the project as created by Buoyant in 2016.

The first CNCF donation was Linkerd 1. Linkerd's own historical note distinguishes that donated project from Linkerd 2, the later Kubernetes-oriented line with a Rust-based data plane proxy. The Linkerd architecture documentation describes Linkerd2-proxy as an ultralight transparent micro-proxy written in Rust and designed specifically for service-mesh sidecar use.

Adoptionsgeschichte

Linkerd joined CNCF on January 24, 2017 as the foundation's fifth hosted project, alongside early cloud-native infrastructure projects such as Kubernetes and Prometheus. CNCF announced Linkerd graduation on July 28, 2021, calling it the first service mesh project to reach graduated status and naming production adopters including Microsoft, Nordstrom, Expedia, JPMC, Clover Health, Entain, and H-E-B.

The service mesh category grew quickly around Kubernetes operations. Linkerd's position was shaped by a deliberately small operational surface, a service-mesh-specific proxy rather than a general-purpose proxy, and CLI-first workflows for checking cluster health, injecting workloads, and inspecting traffic.

Wie es verwendet wird

The package is used by cluster operators and platform engineers to install Linkerd components, validate a cluster, inject workloads, inspect routes and metrics, and manage mesh extensions. It is usually paired with kubectl and Kubernetes manifests rather than used as a standalone network daemon.

Warum Paket-Nerds sich dafür interessieren

Linkerd is significant because it packages a whole distributed control-plane workflow behind a single CLI. For package managers, that means the local binary is only the front door: the installed command coordinates CRDs, proxies, mTLS identity, metrics, and Kubernetes resources that live elsewhere.

Zeitleiste

  • 2015-2016: Buoyant created Linkerd for cloud-native service communication and reliability.
  • 2017-01-24: CNCF accepted Linkerd as its fifth hosted project.
  • 2018-04-06: CNCF moved Linkerd to the Incubating maturity level.
  • 2021-07-28: CNCF announced Linkerd graduation.
  • Linkerd 2 era: the project centered on Kubernetes and the Rust Linkerd2-proxy data plane.

Related projects

  • Related projects include Kubernetes, Finagle, Linkerd2-proxy, Prometheus, OpenTracing, Fluentd, Envoy, and other service-mesh projects such as Istio.

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
linkerdcliglobales 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-25
Manager-Version2.20
Manager aktualisiert2026-06-23
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/linkerd/linkerd2

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:linkerd
Version2.20
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/linkerd
Homepagehttps://linkerd.io
Repositoryhttps://github.com/linkerd/linkerd2
Upstream-Dokumentationhttps://linkerd.io/2/reference/cli
LizenzApache-2.0
Quellarchivhttps://github.com/linkerd/linkerd2.git
Zuletzt aktualisiert2026-06-23T00:33:51Z
Pulseupdated
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 Namelinkerd
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%

linkerd

nix profile install nixpkgs#linkerd
  • normalized package name match
  • Abgeglichen nach: Linkerd
nixpkgs package indexes · raw.githubusercontent.com · nixpkgs package indexes: linkerd from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix
Scoop95%

extras/linkerd

scoop install extras/linkerd
  • normalized package name match
  • Abgeglichen nach: Linkerd
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/linkerd.json from https://api.github.com/repos/ScoopInstaller/Extras/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