linkerd/website

Source code for the linkerd.io website

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

linkerd/website has 60+ stars and 200+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 33 minutes ago
Added to GitGenius on October 15th, 2026
Created on August 16th, 2018
Open Issues & Pull Requests: 149 (+0)
GitHub issues: Enabled
Number of forks: 221
Total Stargazers: 60 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.1 days
Mean response time: 176.0 days
90th percentile: 509.4 days
Tracked items: 31

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 1,033 days
Stale 30+ days: 7
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • docs (4)
  • good first issue (4)
  • help wanted (3)
  • bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The linkerd website is a static site repository that hosts multiple web properties for the Linkerd service mesh project.

The repository serves as the source code for several interconnected web properties. linkerd.io is the main website, run.linkerd.io provides installation scripts and demo applications, versioncheck.linkerd.io allows existing installations to check for updates, and api.linkerd.io hosts API documentation for Linkerd1. The project uses JavaScript as its primary language and is built and deployed using standard web publishing tooling with cloud storage backends.

This repository is relevant primarily to contributors and maintainers of the Linkerd project rather than end users adopting Linkerd itself. It suits teams responsible for maintaining project documentation, installation tooling, and version checking infrastructure. The codebase handles multiple distinct services with different deployment and caching requirements: the main linkerd.io site uses caching for non-HTML pages through a CDN, while run.linkerd.io and versioncheck.linkerd.io operate without caching to ensure immediate updates. API documentation requires separate release management and does not deploy automatically with the main publishing process.

Development activity on the project shows consistent maintenance of documentation and tooling infrastructure. The repository receives regular updates to keep website content and installation scripts current with Linkerd releases. Publishing workflows are documented and tested before production deployment, with specific procedures for cache management and version releases. The project maintains clear separation between different web properties, each with distinct deployment and update characteristics.