[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-11473":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":9,"totalLinesOfCode":9,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":9,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":21,"hasPages":21,"topics":23,"createdAt":9,"pushedAt":9,"updatedAt":32,"readmeContent":33,"aiSummary":34,"trendingCount":16,"starSnapshotCount":16,"syncStatus":35,"lastSyncTime":36,"discoverSource":37},11473,"envoy","envoyproxy\u002Fenvoy","envoyproxy","Cloud-native high-performance edge\u002Fmiddle\u002Fservice proxy",null,"https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy","C++",28379,5423,562,1656,0,82,439,37,97,false,"main",[24,25,26,27,28,29,30,31],"cats","rocket-ships","cars","more-cats","cats-over-dogs","nanoservices","corgis","cncf","2026-06-13 04:00:52","![Envoy Logo](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fartwork\u002Fblob\u002Fmain\u002FPNG\u002FEnvoy_Logo_Final_PANTONE.png)\n\n[Cloud-native high-performance edge\u002Fmiddle\u002Fservice proxy](https:\u002F\u002Fwww.envoyproxy.io\u002F)\n\nEnvoy is hosted by the [Cloud Native Computing Foundation](https:\u002F\u002Fcncf.io) (CNCF). If you are a\ncompany that wants to help shape the evolution of technologies that are container-packaged,\ndynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's\ninvolved and how Envoy plays a role, read the CNCF\n[announcement](https:\u002F\u002Fwww.cncf.io\u002Fblog\u002F2017\u002F09\u002F13\u002Fcncf-hosts-envoy\u002F).\n\n[![CII Best Practices](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F1266\u002Fbadge)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F1266)\n[![OpenSSF Scorecard](https:\u002F\u002Fapi.securityscorecards.dev\u002Fprojects\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy\u002Fbadge)](https:\u002F\u002Fsecurityscorecards.dev\u002Fviewer\u002F?uri=github.com\u002Fenvoyproxy\u002Fenvoy)\n[![CLOMonitor](https:\u002F\u002Fimg.shields.io\u002Fendpoint?url=https:\u002F\u002Fclomonitor.io\u002Fapi\u002Fprojects\u002Fcncf\u002Fenvoy\u002Fbadge)](https:\u002F\u002Fclomonitor.io\u002Fprojects\u002Fcncf\u002Fenvoy)\n\n## Documentation\n\n* [Official documentation](https:\u002F\u002Fwww.envoyproxy.io\u002F)\n* [FAQ](https:\u002F\u002Fwww.envoyproxy.io\u002Fdocs\u002Fenvoy\u002Flatest\u002Ffaq\u002Foverview)\n* [Example documentation](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fexamples\u002F)\n* [Blog](https:\u002F\u002Fmedium.com\u002F@mattklein123\u002Fenvoy-threading-model-a8d44b922310) about the threading model\n* [Blog](https:\u002F\u002Fmedium.com\u002F@mattklein123\u002Fenvoy-hot-restart-1d16b14555b5) about hot restart\n* [Blog](https:\u002F\u002Fmedium.com\u002F@mattklein123\u002Fenvoy-stats-b65c7f363342) about stats architecture\n* [Blog](https:\u002F\u002Fmedium.com\u002F@mattklein123\u002Fthe-universal-data-plane-api-d15cec7a) about universal data plane API\n* [Blog](https:\u002F\u002Fmedium.com\u002F@mattklein123\u002Flyfts-envoy-dashboards-5c91738816b1) on Lyft's Envoy dashboards\n\n## Related\n\n* [data-plane-api](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fdata-plane-api): v2 API definitions as a standalone\n  repository. This is a read-only mirror of [api](api\u002F).\n* [envoy-perf](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy-perf): Performance testing framework.\n* [envoy-filter-example](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy-filter-example): Example of how to add new filters\n  and link to the main repository.\n\n## Contact\n\n* [envoy-announce](https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!forum\u002Fenvoy-announce): Low frequency mailing\n  list where we will email announcements only.\n* [envoy-security-announce](https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!forum\u002Fenvoy-security-announce): Low frequency mailing\n  list where we will email security related announcements only.\n* [envoy-users](https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!forum\u002Fenvoy-users): General user discussion.\n* [envoy-dev](https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!forum\u002Fenvoy-dev): Envoy developer discussion (APIs,\n  feature design, etc.).\n* [envoy-maintainers](https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!forum\u002Fenvoy-maintainers): Use this list\n  to reach all core Envoy maintainers.\n* [Twitter](https:\u002F\u002Ftwitter.com\u002FEnvoyProxy\u002F): Follow along on Twitter!\n* [Slack](https:\u002F\u002Fenvoyproxy.slack.com\u002F): Slack, to get invited go [here](https:\u002F\u002Fcommunityinviter.com\u002Fapps\u002Fenvoyproxy\u002Fenvoy).\n  * NOTE: Response to user questions is best effort on Slack. For a \"guaranteed\" response please email\n    envoy-users@ per the guidance in the following linked thread.\n\nPlease see [this](https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!topic\u002Fenvoy-announce\u002Fl9zjYsnS3TY) email thread\nfor information on email list usage.\n\n## Contributing\n\nContributing to Envoy is fun and modern C++ is a lot less scary than you might think if you don't\nhave prior experience. To get started:\n\n* [Contributing guide](CONTRIBUTING.md)\n* [Beginner issues](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy\u002Fissues?q=is%3Aopen+is%3Aissue+label%3Abeginner)\n* [Build\u002Ftest quick start using docker](ci#building-and-running-tests-as-a-developer)\n* [Developer guide](DEVELOPER.md)\n* Consider installing the Envoy [development support toolchain](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy\u002Fblob\u002Fmain\u002Fsupport\u002FREADME.md), which helps automate parts of the development process, particularly those involving code review.\n* Please make sure that you let us know if you are working on an issue so we don't duplicate work!\n\n## Community Meeting\n\nThe Envoy team has a scheduled meeting time twice per month on Tuesday at 9am PT. The public\nGoogle calendar is [here](https:\u002F\u002Fgoo.gl\u002FPkDijT).  The meeting will only be held\nif there are agenda items listed in the [meeting\nminutes](https:\u002F\u002Fgoo.gl\u002F5Cergb).  Any member of the community should be able to\npropose agenda items by adding to the minutes.  The maintainers will either confirm\nthe additions to the agenda, or will cancel the meeting within 24 hours of the scheduled\ndate if there is no confirmed agenda.\n\n## Security\n\n### Security Audit\n\nThere has been several third party engagements focused on Envoy security:\n* In 2018 Cure53 performed a security audit, [full report](docs\u002Fsecurity\u002Faudit_cure53_2018.pdf).\n* In 2021 Ada Logics performed an audit on our fuzzing infrastructure with recommendations for improvements, [full report](docs\u002Fsecurity\u002Faudit_fuzzer_adalogics_2021.pdf).\n\n### Reporting security vulnerabilities\n\nIf you've found a vulnerability or a potential vulnerability in Envoy, please\n[open a GitHub Security Advisory](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy\u002Fsecurity\u002Fadvisories\u002Fnew).\nThis is the preferred reporting channel, as the reports can be triaged directly on GitHub.\n\nAlternatively, you may email [envoy-security@googlegroups.com](mailto:envoy-security@googlegroups.com).\n\nFor further details please see our complete [security release process](SECURITY.md).\n\n### OSS fuzzing\n\n[![Fuzzing Status](https:\u002F\u002Foss-fuzz-build-logs.storage.googleapis.com\u002Fbadges\u002Fenvoy.svg)](https:\u002F\u002Fbugs.chromium.org\u002Fp\u002Foss-fuzz\u002Fissues\u002Flist?sort=-opened&can=1&q=proj:envoy)\n\n### ppc64le builds\n\nBuilds for the ppc64le architecture or using aws-lc are not covered by the envoy security policy. The ppc64le architecture is currently best-effort and not maintained by the Envoy maintainers.\n\n[![Jenkins](https:\u002F\u002Fpowerci.osuosl.org\u002FbuildStatus\u002Ficon?job=build-envoy-static-master&subject=ppc64le%20build)](https:\u002F\u002Fpowerci.osuosl.org\u002Fjob\u002Fbuild-envoy-static-master\u002F)\n\n### Other builds\n\n[![Jenkins](https:\u002F\u002Fibmz-ci.osuosl.org\u002FbuildStatus\u002Ficon?job=Envoy_IBMZ_CI&subject=s390x%20build)](https:\u002F\u002Fibmz-ci.osuosl.org\u002Fjob\u002FEnvoy_IBMZ_CI\u002F)\n\n## Releases\n\nFor further details please see our [release process](https:\u002F\u002Fgithub.com\u002Fenvoyproxy\u002Fenvoy\u002Fblob\u002Fmain\u002FRELEASES.md).\n","Envoy 是一个云原生的高性能边缘\u002F中间\u002F服务代理。它使用 C++ 编写，支持动态调度和微服务架构，具备强大的流量管理、负载均衡和服务发现功能。Envoy 的核心特点包括高效的多线程模型、热重启能力以及丰富的统计和监控接口，这些特性使其能够在不中断服务的情况下进行配置更新和性能优化。适用于需要在复杂的微服务环境中提供可靠网络通信的场景，如容器化应用部署、API 网关或作为服务网格的一部分。",2,"2026-06-11 03:31:57","trending"]