Introducing Vulnascan

Vulnascan is a deterministic, non-LLM static security scanner for your application’s local project directory. Provide it the directory containing your application code and get a detailed vulnerability report with remediation advice. No model, no randomness — identical report for identical input in every run.

What it does

The pipeline runs in fixed order — discover files → SAST rules → confidence gate → dependency scan (OSV) → CVE enrichment (NVD). A network or parse failure never aborts the scan; it marks the report PARTIAL and lists what was skipped, and the code findings are still complete. --offline skips all network and still runs the full SAST pass. OSV/NVD responses are cached on disk for 24 h.

Three shapes, one engine

Vulnascan is free and open source, and ships in three shapes over one shared engine. All three call the same scan(path, ScanConfig) -> ScanResult — there are no divergent code paths.

Desktop app

Double-click, choose a folder, read a rendered report. No Python, no terminal.

Read the desktop guide →

CLI

security-preview scan <path> — for terminals and CI, with --format, --offline, --min-confidence, and exit-code gating.

Read the CLI guide →

Coding-agent skill

Claude Code or Cursor run the scan on request and summarise the findings from the JSON report.

Read the skill guide →
Supported languages

Pattern rules match 14 languages and config formats (17 file extensions). Coverage is deep for the first six and targeted for the rest; dependency (CVE) scanning is separate and language-agnostic.

LanguageExtensionsRule checks
Python.py24
JavaScript.js .jsx24
TypeScript.ts .tsx24
Java.java24
PHP.php23
Ruby.rb17
Go.go14
C#.cs7
YAML.yml .yaml3
JSON.json3
C.c1
C++.cpp1
HTML.html1
Shell.sh1

Dependency scanning reads lockfiles for Python, npm, Go, Ruby and Maven (requirements.txt, poetry.lock, Pipfile.lock, package-lock.json, yarn.lock, go.mod, Gemfile.lock, pom.xml) and matches every pinned package against the OSV database.