# linkerd/linkerd

Old repo for Linkerd 1.x. See the linkerd2 repo for Linkerd   2.x.

Repository: https://github.com/linkerd/linkerd
Canonical: https://ross.abutalabs.com/products/linkerd-linkerd
Homepage: https://linkerd.io
Language: Scala
License: Apache-2.0
License Family: permissive
Topics: cloud-native, service-mesh, linkerd, service-discovery
Last push: 2023-03-04T18:59:40+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3885, "days_push": 1278, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 5309, forks 494 (observed 2026-08-28T04:09:15.415437+00:00)

## What it is
Linkerd 1.x is a transparent service mesh proxy for HTTP, gRPC, and Thrift traffic, built on Netty and Finagle, that provides load balancing, service discovery integration, and observability with minimal configuration. This repository is now legacy: feature development has moved to the linkerd2 repo, and this repo only receives periodic maintenance releases of the 1.x line.

## Use cases
- add a transparent proxy layer to existing services without code changes
- load balance gRPC or HTTP/2 traffic across service endpoints
- integrate service discovery with Kubernetes, Nomad, or Mesos
- route and observe RPC traffic in a microservices deployment
- run a legacy Linkerd 1.x service mesh in production
- get per-service latency and success rate metrics for meshed traffic

## When to choose
- you are already running Linkerd 1.x and need maintenance releases
- you need a Finagle-based transparent proxy for non-Kubernetes schedulers like Nomad or Mesos
- you must support legacy Linkerd 1.x configurations

## When to avoid
- you are starting a new service mesh project - use Linkerd 2.x (linkerd2) instead
- you need modern Kubernetes-native features like zero-config mTLS or authorization policy
- you want an actively developed service mesh with current security support

## Facets
- artifact type: service
- maturity: maintenance
- function: proxy, service-discovery, rpc, monitoring, tracing, load-testing
- domain: microservices, cloud-computing, networking
- platform: jvm, self-hosted
- tags: service-mesh, linkerd-1x, finagle, netty, grpc, http-proxy, cncf, legacy, namerd, scala, devops, containers, docker, kubernetes, linux, macos

## Member repositories
- linkerd/linkerd (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:15.415437+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:58:59.412318+00:00, confidence not recorded.
  - readme: https://github.com/linkerd/linkerd (fetched 2026-08-28T04:09:15.415437+00:00, sha a91187fe4463)
  - homepage: https://linkerd.io (fetched 2026-08-29T08:53:54.295731+00:00, sha 81f0270ad4b7)
  - site_page: https://linkerd.io/docs (fetched 2026-08-29T08:53:54.327577+00:00, sha e06faf41467f)
  - site_page: https://linkerd.io/docs/getting-started (fetched 2026-08-29T08:53:54.402908+00:00, sha 825ac4e925a9)
  - site_page: https://linkerd.io/docs/features/telemetry (fetched 2026-08-29T08:53:54.432935+00:00, sha e7e922b81cbb)
  - site_page: https://linkerd.io/docs/features/server-policy (fetched 2026-08-29T08:53:54.435731+00:00, sha 881f2eb1cc0a)
  - site_page: https://linkerd.io/docs/tasks/debugging-502s (fetched 2026-08-29T08:53:54.437753+00:00, sha aee666695640)
  - site_page: https://linkerd.io/docs/features/load-balancing (fetched 2026-08-29T08:53:54.439508+00:00, sha 4306fbf7eec8)
  - site_page: https://linkerd.io/faq (fetched 2026-08-29T08:53:54.365251+00:00, sha 338fb9facc5a)
- Data as of 2026-08-30T08:39:29.467469+00:00.