syncthing/syncthing

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.

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

Scan timing: clone 2.9s · analysis 9.38s · 10.1 MB · GitHub API rate-limit (preflight)

https://github.com/syncthing/syncthing · scanned 2026-06-05 07:18 UTC (6 days ago) · 10 languages

317 raw signals (191 security + 126 graph) 30th percentile · Go · large (100-500K LoC) System graph score 74 (lower by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 6 days ago · v2 · 133 actionable findings from 2 signal sources. 121 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 · 42 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	21.6	0.25	5.40
`testing_score`	90.0	0.20	18.00
`documentation_score`	76.0	0.15	11.40
`practices_score`	100.0	0.15	15.00
`code_quality`	61.2	0.10	6.12
Overall		1.00	68.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 60 Medium 9 Low 37 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 91 System graph 42 Crowd 0 Layer: Quality 38 Software 73 Cicd 7 Security 7 Api 1 Frontend 4 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 3 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/`.

3 matching findings on this repo

info Commented-code block (5 lines) in gui/default/syncthing/app.js:227
info Commented-code block (5 lines) in gui/default/syncthing/core/eventService.js:11
info Commented-code block (5 lines) in gui/default/syncthing/core/syncthingControlle…

View all commented-out code findings →

Config drift 3 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.

3 matching findings on this repo

high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… cmd/syncthing/cli/client.go:60
high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… cmd/strelaysrv/main.go:178
low Very large file: lib/config/mocks/mocked_wrapper.go (1831 lines)

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/e2d7c0f7-b692-4ec4-b108-3322fb43d091/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e2d7c0f7-b692-4ec4-b108-3322fb43d091/

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.