envoyproxy/envoy

Cloud-native high-performance edge/middle/service proxy

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on October 15th, 2022
Created on August 8th, 2016
Open Issues & Pull Requests: 1,838 (+0)
Number of forks: 5,556
Total Stargazers: 28,778 (+0)
Total Subscribers: 562 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.6 hours
Mean response time: 150.5 days
90th percentile: 538.5 days
Tracked items: 2,950

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 76% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "tech debt" is answered fastest, typically in under an hour, while "dependencies" waits about 7 days. 47% of tracked open issues have had no activity in three months. Only 5% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 960
New in 7 days: 23
Closed in 7 days: 17
Avg open age: 1,080 days
Stale 30+ days: 859
Stale 90+ days: 800

Recent activity

Opened in 7 days: 21
Closed in 7 days: 13
Comments in 7 days: 27
Events in 7 days: 143

Top labels

  • stale (2,226)
  • no stalebot (2,106)
  • area/build (1,585)
  • enhancement (1,584)
  • dependencies (1,292)
  • question (1,273)
  • bug (1,242)
  • help wanted (1,158)

Detailed Description

Envoy is a cloud-native, high-performance proxy written in C++ that operates at the edge, middle, and service tiers of distributed systems. Hosted by the Cloud Native Computing Foundation, it serves as a critical infrastructure component for container-packaged, dynamically-scheduled, and microservices-oriented architectures. The project is classified across multiple networking and infrastructure domains including API gateway functionality, service mesh integration, load balancing, network traffic management, inter-service communication, traffic management, observability, network proxy capabilities, performance optimization, security features, TLS termination, reverse proxy functionality, microservices support, dynamic routing, and general networking proxy operations.

The repository demonstrates substantial and sustained activity.

The project maintains overlapping contributor relationships with several other significant repositories including github/gh-aw, solo-io/gloo, and microsoft/vscode, suggesting cross-pollination of development practices and shared architectural concerns across these ecosystems. Documentation is comprehensive, including official project documentation, FAQ materials, example implementations, and technical blog posts covering threading models, hot restart capabilities, statistics architecture, the universal data plane API, and operational dashboards.

Envoy provides multiple related projects and resources for users and developers. The data-plane-api repository contains v2 API definitions, envoy-perf offers a performance testing framework, and envoy-filter-example demonstrates how to extend Envoy with custom filters. The project maintains active community engagement through multiple mailing lists including envoy-announce for low-frequency announcements, envoy-security-announce for security updates, envoy-users for general discussion, envoy-dev for technical design discussions, and envoy-maintainers for core team communication. Community meetings are held twice monthly on Tuesdays at 9am PT with public calendar and meeting minutes available.

Security is treated as a priority concern. The project has undergone third-party security audits, including a 2018 engagement with Cure53 and a 2021 fuzzing infrastructure audit by Ada Logics, with full reports publicly available. Vulnerability reporting is handled through GitHub Security Advisories as the preferred channel, with an alternative email address for security concerns. The project maintains a documented security release process and participates in OSS fuzzing initiatives. The contribution process is designed to be accessible, with beginner-friendly issues, Docker-based build and test quick starts, a developer guide, and a development support toolchain to assist with code review workflows.