RepoPilot

envoyproxy/envoy · Security & risks

Authoritative risk signals for envoyproxy/envoy — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.

ArchitectureSecurity & risksDependenciesLicenseMaintenanceAlternativesVsFull analysis

Dependency CVEs (deps.dev)

0
Critical
0 direct
0
High
0 direct
0
Moderate
2
Deps scanned
2 direct

OpenSSF Scorecard · 8.5/10

  • Vulnerabilities1/10
  • Branch-Protection4/10
  • CII-Best-Practices5/10
  • Signed-Releases8/10
  • Code-Review9/10
  • Pinned-Dependencies9/10
  • SAST9/10
  • Maintained10/10

Ask AI about envoyproxy/envoy

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.