go-gitea/gitea

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

60 of your 143 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.37s · analysis 25.73s · 31.9 MB · GitHub API rate-limit (preflight)

https://github.com/go-gitea/gitea · scanned 2026-06-05 10:17 UTC (5 days, 15 hours ago) · 10 languages

445 raw signals (119 security + 326 graph) 11/13 scanners ran 91st percentile · Go · large (100-500K LoC) System graph score 74 (higher by 17)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 15 hours ago · v2 · 217 actionable findings from 2 signal sources. 65 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 158 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	90.0	0.15	13.50
`practices_score`	100.0	0.15	15.00
`code_quality`	80.0	0.10	8.00
Overall		1.00	90.5

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 15 Medium 37 Low 78 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 59 System graph 158 Crowd 0 Layer: Quality 71 Security 33 Cicd 6 Software 60 Api 1 Frontend 38 Network 5 Hardware 3

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 18 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (9 lines) in tailwind.config.ts:103
info Commented-code block (5 lines) in tests/e2e/events.test.ts:69
info Commented-code block (5 lines) in web_src/js/svg.ts:204
info Commented-code block (7 lines) in web_src/js/utils/dom.ts:114
info Commented-code block (10 lines) in web_src/js/utils/glob.ts:9
info Commented-code block (5 lines) in web_src/js/modules/observer.ts:22
info Commented-code block (8 lines) in web_src/js/modules/worker.ts:45
info Commented-code block (7 lines) in web_src/js/modules/fomantic/dropdown.ts:162
info Commented-code block (5 lines) in web_src/js/markup/content.ts:15
info Commented-code block (5 lines) in web_src/js/markup/mermaid.ts:60
info Commented-code block (6 lines) in web_src/js/render/plugin.ts:1
info Commented-code block (5 lines) in web_src/js/features/common-fetch-action.ts:382

View all commented-out code findings →

Config drift 10 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

10 matching findings on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… web_src/js/utils.ts:174
high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… modules/private/internal.go:60
low File has no detected symbols: playwright.config.ts
low File has no detected symbols: eslint.config.ts
low File has no detected symbols: eslint.json.config.ts
low File has no detected symbols: stylelint.config.ts
low File has no detected symbols: vitest.config.ts
info TODO/FIXME marker in shipping code — web_src/js/features/admin/config.ts:60
info TODO/FIXME marker in shipping code — web_src/js/features/admin/config.test.ts:45
info Commented-code block (9 lines) in tailwind.config.ts:103

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/9ddf74f5-e0e0-4f6b-a0b9-76c2b098dce1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9ddf74f5-e0e0-4f6b-a0b9-76c2b098dce1/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.