encode/uvicorn · Security & risks
Authoritative risk signals for encode/uvicorn — 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
4
Deps scanned
4 direct
OpenSSF Scorecard · 7.0/10
- Signed-Releases—
- CII-Best-Practices0/10
- Fuzzing0/10
- Code-Review1/10
- Branch-Protection3/10
- Security-Policy4/10
- Token-Permissions9/10
- Maintained10/10
Ask AI about encode/uvicorn
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.