GitScout 🛡️

Know before you clone. Change github.com/owner/repo → gitscout.meadityazzzz.in/owner/repo — instant pre-clone security verdict.

What It Does

GitScout scans any public GitHub repository before you clone or install — detecting 63 attack patterns across 9 threat categories in under 30 seconds.

Tech Stack

• Backend: Go (Chi router) — goroutine-based concurrent scanning engine
• Frontend: SvelteKit — real-time SSE streaming results UI
• AST Parsing: tree-sitter — multi-language static analysis

Attack Categories Detected

Category	Threat Level	Examples
PostInstall Scripts	🔴 CRITICAL	curl | bash in lifecycle hooks
Credential Harvesting	🔴 CRITICAL	Reading ~/.ssh, ~/.aws, process.env
Typosquatting	🔴 HIGH	crossenv instead of cross-env
Dependency Confusion	🔴 HIGH	Public package overriding private scope
Code Obfuscation	🔴 HIGH	Base64 eval chains, hex strings
Unicode/Trojan Source	🔴 HIGH	Bidirectional override characters
Logic Bombs	🟠 HIGH	Geo-triggered, time-triggered payloads
Supply Chain Hijacking	🟠 HIGH	Maintainer account takeover
CI/CD Workflow Attacks	🟡 MEDIUM	Malicious GitHub Actions
Network Exfiltration	🟡 MEDIUM	DNS tunneling, webhook beacons
Crypto Mining	🟡 MEDIUM	Embedded XMRig miners
Fake Metadata	🟢 LOW	Inflated stars, fake downloads

Project Structure

GitScout/
├── backend/           # Go backend (Chi + goroutines)
│   ├── cmd/server/    # Entry point
│   ├── internal/
│   │   ├── api/       # HTTP handlers + SSE
│   │   ├── scanner/   # Scan orchestrator
│   │   ├── checks/    # One file per attack category
│   │   ├── ast/       # tree-sitter wrapper
│   │   └── models/    # Data types
│   └── go.mod
├── frontend/          # SvelteKit
└── docs/              # Implementation plan + attack taxonomy

Running Locally

# Backend
cd backend
go run ./cmd/server

# Frontend
cd frontend
npm install
npm run dev

License

MIT