Polyscan measures your whole codebase every week, tracks structural decay, and reports what to fix first. It also catches new problems on pull requests, powered by the open-source analyzers pyscn (Python) and polyscan (JavaScript/TypeScript, Go, Rust, C++).
The official home of Polyscan App: the issue tracker for bug reports and feature requests about the App, and the source of the site served at codescan.dev (a static Next.js app — no database, no accounts, no API).
The analysis engines are fully open source; the App's orchestration backend is closed:
| Project | Repository |
|---|---|
polyscan monorepo (core, polyscan CLI) |
ludo-technologies/polyscan |
| pyscn (Python analyzer) | ludo-technologies/pyscn |
| Polyscan App backend | ludo-technologies/polyscan-backend (private) |
Add .github/polyscan.yml to a repository where the App is installed:
language: en # report language: en, ja, zh, ko, es, fr, de, pt
target_directories: # directories to analyze (default: all)
- src/
audit_interval: weekly # daily (Pro), weekly, or monthlyReference documentation for the analyzers is published separately from pyscn/website (MkDocs) and served at docs.codescan.dev.
This repository previously hosted codescan.dev, a hosted security scanner built on Semgrep, Gitleaks, and Trivy. That product was retired; its frontend and Go scan engine remain in the git history up to the
feat/polyscan-sitebranch point.
bun install
bun run dev # http://localhost:3000| Command | Description |
|---|---|
bun run dev |
Start the dev server |
bun run build |
Production build |
bun run lint |
Biome check |
bun run format |
Biome format |
bun run test |
Vitest |
All optional — see .env.example.
| Variable | Purpose |
|---|---|
SITE_URL / NEXT_PUBLIC_SITE_URL |
Canonical origin for metadata, sitemap, and robots. Falls back to the Vercel URL, then https://codescan.dev. |
NEXT_PUBLIC_GA_MEASUREMENT_ID |
Google Analytics measurement ID. Analytics are disabled when unset. |
Deployed to Vercel manually: bunx vercel --prod from the repo root (there is no Git-integration auto-deploy).
See CONTRIBUTING.md.