linkerd/linkerd2 · Security & risks
Authoritative risk signals for linkerd/linkerd2 — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.
Dependency CVEs (deps.dev)
0
Critical
0 direct
0
High
0 direct
0
Moderate
50
Deps scanned
0 direct
OpenSSF Scorecard · 8.2/10
- Packaging—
- Branch-Protection—
- Signed-Releases0/10
- CII-Best-Practices5/10
- Pinned-Dependencies5/10
- SAST7/10
- Code-Review10/10
- Security-Policy10/10
Ask AI about linkerd/linkerd2
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 questionInformational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.