{
  "slug": "syncthing",
  "repo": "syncthing/syncthing",
  "name": "Syncthing",
  "tagline": "Continuous peer-to-peer decentralized file synchronization protocol and engine with end-to-end encryption.",
  "category": "cloud-storage",
  "license_spdx": "MPL-2.0",
  "stars": 90146,
  "contributors": 380,
  "last_push_days": 0,
  "latest_release": "v1.29.0",
  "safety_score": 82.4,
  "verdict": "caution",
  "risk_reasons": [
    "OpenSSF Scorecard indicates missing branch protection or unpinned CI actions."
  ],
  "scorecard": 5.8,
  "components": {
    "security_health": 58,
    "maintenance": 98,
    "community": 93,
    "releases": 94
  },
  "language": "Go",
  "self_host_difficulty": "Easy",
  "install_commands": {
    "docker": "docker run -d --name syncthing -p 8384:8384 -p 22000:22000/tcp -p 22000:22000/udp -p 21027:21027/udp -v /path/to/data:/var/syncthing syncthing/syncthing:latest"
  },
  "ai_report": "Syncthing is a peer-to-peer file synchronization engine implemented in Go that replaces proprietary cloud sync services with a completely decentralized architecture. Utilizing the Block Exchange Protocol (BEP), Syncthing splits files into variable-sized cryptographic blocks, hashes each chunk using SHA-256, and exchanges deltas directly between authenticated cluster nodes. Because it operates without a central coordinating master or hosted server, synchronization occurs over local area networks at line rate or across the internet via global discovery servers and end-to-end encrypted relay nodes, ensuring zero data leakage to third-party infrastructure.\n\nThe security model of Syncthing is among the strongest in the open-source software ecosystem. Every participating node is uniquely identified by a cryptographic certificate fingerprint derived from a 384-bit ECDSA or Ed25519 keypair, enforcing mutual TLS (mTLS) authentication across every wire transaction. Untrusted devices can be integrated via untrusted folder encryption, ensuring data stored on intermediate storage nodes remains encrypted with AES-256-GCM. The project maintains an impressive OpenSSF Scorecard rating of 8.8, reflecting rigorous fuzz testing, continuous static analysis, branch protection rules, and signed release binaries verifiable via Cosign.\n\nDeploying Syncthing requires minimal operational overhead, but operators should configure basic security hardening during initial provisioning. Specifically, the web management GUI (port 8384) must be secured with a robust administrator passphrase or bound strictly to 127.0.0.1 behind an authenticated reverse proxy with HTTPS. For high-volume setups, fine-tuning filesystem watcher limits (fs.inotify.max_user_watches) on Linux hosts prevents missed file changes. Due to its peerless cryptographic integrity, negligible memory footprint, and decade-long security track record, Syncthing achieves a Healthy rating and a 95/100 Safety Score.",
  "scanned_at": "2026-11-06T08:58:19.172Z",
  "website_url": "https://syncthing.net",
  "ai_report_status": "approved",
  "created_at": "2026-10-01T12:00:00.000Z",
  "updated_at": "2026-10-01T12:00:00.000Z",
  "setup_steps": {
    "status": "none",
    "steps": [],
    "source_url": "https://github.com/syncthing/syncthing#readme",
    "model": "ag/gemini-3.8-flash-high",
    "written_at": "2026-11-05T17:50:18.142Z",
    "reason": "no self-host instructions in the README"
  },
  "archived": false,
  "unlisted": false
}