go-gitea/gitea · Security & risks
Authoritative risk signals for go-gitea/gitea — 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
75
Deps scanned
25 direct
OpenSSF Scorecard · 7.0/10
- Dangerous-Workflow0/10
- SAST0/10
- Branch-Protection3/10
- CII-Best-Practices5/10
- Code-Review8/10
- Pinned-Dependencies8/10
- Signed-Releases8/10
- Security-Policy10/10
Ask AI about go-gitea/gitea
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.