istio/proxy

The Istio proxy components.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

istio/proxy has 900+ stars and 1k+ forks on GitHub, is written in Go, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on December 1st, 2016
Open Issues & Pull Requests: 8 (+1)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 1,461
Total Stargazers: 915 (+0)
Total Subscribers: 117 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Istio Proxy is a microservice proxy that extends Envoy with policy and telemetry capabilities for service mesh deployments.

The tool addresses the need for intelligent traffic management and observability in microservice architectures by building on Envoy's proven proxy foundation and adding extensions specific to service mesh requirements. It operates as both client-side and server-side sidecar proxies, intercepting and managing traffic between services while enforcing policies and collecting telemetry data about that traffic.

Adoption suits organizations running Kubernetes-based microservices that need centralized control over inter-service communication, traffic policies, and observability without modifying application code. The project works best for teams already committed to the Istio service mesh ecosystem, as the proxy is tightly integrated with Istio's control plane for configuration and policy distribution. Those evaluating it should understand that it extends rather than replaces Envoy, so familiarity with Envoy concepts and configuration patterns is valuable. The project has established a boundary around scope: new extensions are added only when they represent core APIs, which means the tool maintains focus on essential mesh functionality rather than accumulating specialized features.

Development activity shows a mature, deliberately scoped project. The codebase receives regular updates and maintenance focused on stability and core functionality. Pull requests are reviewed and merged with attention to quality standards. The project maintains clear architectural boundaries and resists feature expansion outside its defined scope, indicating disciplined stewardship of the codebase.