Offline
Your code stays on your machine. No cloud upload, no telemetry, no LLM. One signed CVE bundle is the only outbound call, and VULKRO_OFFLINE=1 refuses even that.
Built by a developer, for developers
A command-line security scanner that runs on your laptop. Catches broken access, leaked credentials, vulnerable dependencies, and risky infrastructure - locally, in seconds, with no account
Four things we picked, on purpose
Every SAST tool makes tradeoffs the vendor decided for you. Here are ours, on the front page, so you can decide before you install.
Your code stays on your machine. No cloud upload, no telemetry, no LLM. One signed CVE bundle is the only outbound call, and VULKRO_OFFLINE=1 refuses even that.
Public benchmark, reproducible scoring, documented misses. We tell you which detector packs ship off by default because they are noisy. File an issue on a misfire and one developer reads it.
104 seconds to scan a 13-repo benchmark corpus on a laptop. Seconds on a PR diff with vulkro scan --since main. Rust on tree-sitter, no JVM warmup.
Findings map to nine frameworks: ASVS, OWASP Top 10, PCI-DSS 4.0, SOC 2, HIPAA, GDPR Art. 30, NIST SSDF, ISO 27001, CIS v8. Outputs in SARIF, JUnit, CycloneDX, SPDX, CSV, JSON, HTML, PDF.
How it works
Local files, any supported language. Nothing leaves your machine.
You type vulkro scan in your terminal, or Claude / Cursor / Codex runs it for you via the MCP server. Same scanner, same results, same speed.
Taint flow, reachability, CVE matching, 120+ rules in Rust. Offline, deterministic, no JVM warmup.
Web UI, SARIF, JUnit, GitHub PR comment, executive HTML, PDF, terminal table, IDE diagnostics. Pick the format your reader speaks.
You read the finding and patch it yourself, or your AI agent reads the structured output and writes the patch for you. Re-run the scan to confirm. Same loop, same scanner.
What it covers
One command checks all eight in a single pass. Results go to the systems your team already uses: GitHub PR comments, Slack, Jira, SIEM, and your auditor, in the formats they already understand.
The bug classes responsible for most real-world breaches.
Hardcoded passwords, API keys, and tokens - including in git history.
Known CVEs in the third-party libraries you ship with.
CVE scan for the same dependencies inside your Docker images.
Cloud and Kubernetes settings that quietly create risk.
Per-control pass/fail across the frameworks auditors ask about.
Where customer PII and PHI travel through your code.
Optional: confirm static findings against a running service.
vulkro serve
How does it compare?
Built on the same scanner, tuned for Salesforce teams. One offline scan covers your Apex code and the org around it (security hardening, access, third-party Connected Apps, and Agentforce) and produces an AppExchange Security Review readiness report. Connect a live org through your own Salesforce login to check its posture too: nothing is uploaded and the access token never leaves your machine.
Apex SOQL injection, CRUD / FLS, LWC / Aura DOM XSS, Visualforce, Flow system-context DML
SecuritySettings hardening, sharing rules, login IP ranges, password policy
Profile and Permission-set over-privilege, ghost admins, SAML SSO signing
Connected App OAuth posture (Drift / Gainsight token-sprawl class)
ForcedLeak (CVSS 9.4) class-bypass detector for GenAiFunction Apex actions
Community
Three ways to follow what we ship and what we are working on. Pick whichever fits how you already work.
Subscribe once, get two things: the weekly CVE + release digest in your inbox, and access to the live chat where in-between things land (detector ideas, weird findings, release heads-ups).
Public community at r/vulkro. Bug reports, scan-result war stories, CVE chat, AppSec questions. No email required, indexed by Google so threads stay useful.
Bug reports, install help, billing questions. One human reads every message. No web form, no chatbot, no AI summariser.
Install in 60 seconds. 14 days of full Pro, then it drops to Free and keeps running. No card. Reports stay yours either way.