Automic VaultAutomic Vault

brew

Install linkerd with Homebrew, Nix, scoop

Command-line utility to interact with linkerd. Version 2.20 via Homebrew; verified 2026-06-23.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install linkerd

local Homebrew formula metadata

Windows

Scoopverified · 92%
scoop install extras/linkerd

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

overview

Package summary

Command-line utility to interact with linkerd

Commands and aliases

  • linkerd

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
linkerdcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version2.20
manager updated2026-06-23
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/linkerd/linkerd2

install metadata

Package metadata

Package keybrew:linkerd
Version2.20
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/linkerd
Homepagehttps://linkerd.io
Repositoryhttps://github.com/linkerd/linkerd2
Upstream docshttps://linkerd.io/2/reference/cli
LicenseApache-2.0
Source archivehttps://github.com/linkerd/linkerd2.git
Last updated2026-06-23T00:33:51Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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 database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

linkerd

nix profile install nixpkgs#linkerd
  • normalized package name match
  • Matched by: 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
  • Matched by: 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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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