explaingit

kubeek-sec/deep-scan

Analysis updated 2026-05-18

5PythonAudience · ops devopsComplexity · 4/5Setup · moderate

TLDR

A modular security scanner with 20+ tools exposed as a CLI, MCP server, REST API, and continuous scanning fleet.

Mindmap

mindmap
  root((Deep Scan))
    What it does
      Runs 20+ security scanners
      Normalizes findings
      Filters reachable issues
    Tech stack
      Python
      Docker
      Kubernetes
      MCP server
    Use cases
      CI security gate
      Agent-driven remediation
      Continuous scanning fleet
    Audience
      Security teams
      DevOps engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Run a security scan against a codebase from the command line as part of a CI pipeline.

USE CASE 2

Let an AI agent drive the MCP server to find, confirm, and fix real vulnerabilities automatically.

USE CASE 3

Filter dependency vulnerabilities down to only the ones actually reachable from the code.

USE CASE 4

Deploy a continuous scanning fleet with a dashboard to track security posture across many projects.

What is it built with?

PythonDockerKubernetesMCPPostgreSQL

How does it compare?

kubeek-sec/deep-scan1ncendium/aibusteraaronmayeux/ha-hurricane-tracker
Stars555
LanguagePythonPythonPython
Setup difficultymoderatemoderateeasy
Complexity4/53/52/5
Audienceops devopsops devopsgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires Python 3.13 with uv, and Docker Compose for the full server stack with the dashboard.

The README does not state a license.

In plain English

Deep Scan is a security scanning project made up of several connected pieces that all share one underlying scanning engine. That same engine is exposed in four ways: as an MCP server for AI agents and code editors, as a command line tool for local use and continuous integration pipelines, as a REST API with a web app for running many scans at once, and as a continuous scanning fleet with a dashboard for tracking security posture across many projects over time. It bundles more than 20 individual scanning tools covering static code analysis, dependency vulnerabilities, exposed secrets, infrastructure configuration issues, license checks, malware detection, and dynamic application testing. Every scanner's results are normalized into one shared finding format, deduplicated, and rendered into JSON, Markdown, HTML, or the SARIF format used by many code review tools. A separate, non AI code graph analysis engine can trace which vulnerable dependencies are actually reachable from a program's entry points, cutting down on findings that do not matter in practice. An optional AI powered triage step can also prioritize findings and suggest fixes, and it can run against a local model to avoid sending code externally. A key feature is that an AI agent can drive the MCP server through an entire remediation loop: scanning a project, confirming which findings are truly reachable, then opening a separate review branch for each group of fixes with a minimal patch and a test proving the issue is resolved. The project also includes a deliberately vulnerable sample application for trying out the scanner safely. For running the full stack, including the database, the scanning worker fleet, the web app, and the MCP server, Docker Compose brings everything up with one command. On Kubernetes, the scanning workers can be hardened further and even run inside gVisor, a sandboxing technology, since scanning unfamiliar code is inherently risky. The project is written in Python using the uv tool for dependency management.

Copy-paste prompts

Prompt 1
Set up deep-scan as an MCP server and have an agent scan this project for reachable vulnerabilities.
Prompt 2
Run deep-scan's CLI against this repository and fail the build if a high severity issue is found.
Prompt 3
Explain how deep-scan's reachability analysis reduces false positive dependency findings.
Prompt 4
Bring up the full deep-scan stack with Docker Compose and open the ASPM dashboard.

Frequently asked questions

What is deep-scan?

A modular security scanner with 20+ tools exposed as a CLI, MCP server, REST API, and continuous scanning fleet.

What language is deep-scan written in?

Mainly Python. The stack also includes Python, Docker, Kubernetes.

What license does deep-scan use?

The README does not state a license.

How hard is deep-scan to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is deep-scan for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.