Security Hub

Scan for hard-coded secrets, risky containers, dependencies and live endpoints.

  1. Run DevSnip Pro: Security Hub (or a single scan command from the table below).
  2. Pick a scan and start it. Workspace scans read your files locally and skip dependency, build and cache folders.
  3. Open a finding to see its file and line, evidence (secrets are masked), severity and fix.
  4. Export the results as Markdown or JSON to share them or attach them to a pull request.
ScanWhat it checks
Workspace Security AuditHard-coded API keys, tokens and passwords, injection risks, weak cryptography
Cloud & Container AuditTerraform, Kubernetes, Docker Compose, Dockerfiles and GitHub Actions
Dependency & Config CheckLockfiles, unbounded ranges, compromised packages, registry credentials, .env hygiene
Endpoint Security ScanTLS, HSTS, security headers, CSP, CORS, cookies, auth behaviour and rate limiting

Heads upOnly scan endpoints you are authorised to test. Its two active checks (a reflected-input probe and well-known sensitive paths) are off by default; enable them per scan or with devsnip.security.activeChecks.

TipFound a real secret? Rotate it โ€” removing it from the code does not remove it from git history.

Guide: Find hard-coded secrets in VS Code โ†’