Datahogo

io.github.datahogoPublished by GitHub account datahogov0.1.3Updated Oct 24, 2026

Scan a project for security issues locally with the open-source Data Hogo engine.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Runs the open-source Data Hogo security scanner locally so an assistant can scan a project, inspect findings, check a deployed URL, and audit database rules.

What you can do
Exposes the Data Hogo scan engine as MCP tools over stdio: scan_project scans a project directory, get_finding retrieves a specific finding, scan_url checks a deployed URL for headers, SSL and CORS issues, and check_db_rules reviews Supabase or Firebase rules. It auto-detects the stack and runs matching analyzers, with deepest coverage for JavaScript/TypeScript, plus secret detection and dependency scanning across languages. The agent writes the explanation and fix itself, so no AI key is needed for that.
When to use it
Useful when you want an assistant to run local security checks on a codebase, pull up a particular vulnerability, review deployed-site configuration, or audit database security rules without sending code to a hosted scanner.
Requirements
Local process started with npx -y @datahogo/mcp over stdio; Node.js and npm are needed. No account, API key or environment variable is declared for the MCP server itself. Optional external tools Semgrep and Gitleaks add extra rules if installed; the CLI's --explain option uses ANTHROPIC_API_KEY, but the MCP server is described as not needing it.
Before you install
The scanner reads project files on your machine and reports findings, including leaked secrets, to the assistant. The optional CLI --explain flag sends code context to Anthropic using your own ANTHROPIC_API_KEY and is billed to you; the MCP server is described as not requiring that key. Findings and any secrets detected may appear in the agent conversation, so review before sharing output.

Installation

In SourceWeft

  1. Open Datahogo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

保護 · Data Hogo

Open-source security scanner that runs on your machine. Your code never leaves your laptop.

[License: AGPL-3.0] [npm] [Node]

English · Español · datahogo.com

Why Data Hogo

Most security scanners ask you to hand over access to your repositories. Data Hogo doesn't. It's a CLI that runs entirely on your machine — it reads your files locally, finds vulnerabilities, and prints them to your terminal. Nothing is uploaded. There's no account, no sign-up, and no server to trust. The source is here for you to read.

It's built for developers and vibecoders who ship real projects but aren't security experts: it explains findings in plain language and, if you want, generates fixes using your own AI key.

bash
npx datahogo

That's it. Point it at a project and it scans the current directory.

Quick start

bash
# Scan the current directorynpx datahogo
# Scan a specific pathnpx datahogo scan ./my-app
# Fail CI if there are high-severity findingsnpx datahogo scan --fail-on high
# Output SARIF for GitHub Code Scanningnpx datahogo scan --sarif > results.sarif

Install it globally if you'd rather not use npx every time:

bash
npm install -g datahogodatahogo scan

What it checks

Data Hogo auto-detects your stack and runs the matching analyzers. Coverage is deepest for the JavaScript/TypeScript ecosystem; other languages have a focused set of high-signal checks.

StackExamples of what's detected
JavaScript / TypeScriptNode, Next.js, React, Express, Fastify, NestJS — injection, XSS, eval, insecure config, vulnerable dependencies, leaked secrets
PythonDjango DEBUG, hardcoded SECRET_KEY, wildcard ALLOWED_HOSTS, Flask/FastAPI missing auth, vulnerable packages
GoSQL injection, command injection, weak crypto, hardcoded credentials
Java / KotlinSpring endpoints without authorization, unsafe deserialization, XXE, SQL injection
PHP / LaravelMass assignment, SQL injection, unsafe file handling
C# / .NETMissing [Authorize], BinaryFormatter deserialization, XXE, weak hashing
MobileReact Native, Expo, Flutter/Dart — insecure storage, hardcoded secrets
SupabaseRow Level Security gaps, exposed service keys, insecure policies

Secrets detection and dependency scanning run across every project regardless of language.

Optional: deeper analysis

Two industry-standard tools add extra depth when installed. Data Hogo works fine without them — it just uses its built-in checks and tells you what you're missing.

bash
datahogo doctor   # shows what's installed and how to add the rest
  • Semgrep — ~250 additional AST-based rules for JS/TS
  • Gitleaks — comprehensive secret-detection ruleset

AI explanations & fixes (bring your own key)

Every finding comes with a plain-language explanation and a suggested fix out of the box. If you want richer, context-aware fixes generated by Claude, set your own Anthropic API key — the calls go directly from your machine to Anthropic, billed to you. We never see them.

bash
export ANTHROPIC_API_KEY=sk-ant-...datahogo scan --explain

Use it in CI

GitHub Action

yaml
# .github/workflows/security.ymlname: Securityon: [push, pull_request]permissions:  contents: read  security-events: writejobs:  scan:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - uses: datahogo/datahogo@main        with:          fail-on: high

Findings show up in your repository's Security tab automatically. See action.yml for every input (path, url, upload-sarif).

Any other CI

Data Hogo exits with a non-zero code when it finds issues at or above the severity you choose, so it drops straight into any pipeline:

yaml
- run: npx datahogo scan --fail-on high --sarif > results.sarif- uses: github/codeql-action/upload-sarif@v3  if: always()  with:    sarif_file: results.sarif

The SARIF output shows up in your repository's Security tab.

Commands & options

datahogo [scan] [path]        Scan a directory (default: current directory)datahogo doctor               Check optional external tools
  --json                      Machine-readable JSON output  --sarif                     SARIF 2.1.0 (GitHub Code Scanning)  --fail-on <severity>        Exit 1 if findings >= critical|high|medium|low  --url <url>                 Also scan a deployed URL (headers, SSL, CORS)  --explain                   AI explanations (requires ANTHROPIC_API_KEY)  --all                       Include informational / non-production findings  --help, --version

Use it from Claude Code, Cursor, or Claude Desktop (MCP)

@datahogo/mcp exposes the same scan engine as MCP tools, so your agent can scan a project, pull a specific finding, check a deployed URL, or review Supabase/Firebase rules — and write the explanation and fix itself, at no AI cost to you.

bash
claude mcp add datahogo -- npx -y @datahogo/mcp

For Cursor or another MCP client, point it at the same command: npx -y @datahogo/mcp, stdio transport.

Tools: scan_project, get_finding, scan_url, check_db_rules.

Prefer a lighter footprint in Claude Code specifically? Install the Claude Code skill instead — it just teaches the agent to run npx datahogo scan --json and interpret the output, no MCP server process required:

bash
npx skills add datahogo/datahogo/skills/datahogo

Data Hogo Cloud

The CLI is free and always will be. If you want scan history, findings tracked across commits, automatic fix pull requests, scheduled scans, and team dashboards, Data Hogo Cloud builds those on top of the same engine. Using the CLI never requires it.

Contributing

Issues and pull requests are welcome — new detection rules for any language are especially valuable. The scan engine lives in packages/core and the CLI in packages/cli.

bash
git clone https://github.com/datahogo/datahogo.gitcd datahogonpm installnpm run buildnpm test

Support the project

Data Hogo is free and open source. If it saved you from shipping a vulnerability, consider sponsoring the project — it funds new detection rules and keeps the lights on.

License

AGPL-3.0 © Data Hogo. You're free to use, read, run, and modify it. If you offer a modified version as a network service, you must share your source under the same license.

Por qué Data Hogo

La mayoría de los escáneres de seguridad te piden acceso a tus repositorios. Data Hogo no. Es una herramienta de línea de comandos que corre completamente en tu máquina: lee tus archivos localmente, encuentra vulnerabilidades y las muestra en tu terminal. No se sube nada. No hay cuenta, no hay registro, no hay servidor en quien confiar. El código está aquí para que lo leas.

Está hecho para developers y vibecoders que lanzan proyectos reales pero no son expertos en seguridad: explica los hallazgos en lenguaje simple y, si quieres, genera arreglos usando tu propia llave de AI.

bash
npx datahogo

Eso es todo. Apúntalo a un proyecto y escanea el directorio actual.

Inicio rápido

bash
# Escanear el directorio actualnpx datahogo
# Escanear una ruta específicanpx datahogo scan ./mi-app
# Romper el CI si hay hallazgos de severidad altanpx datahogo scan --fail-on high
# Generar SARIF para GitHub Code Scanningnpx datahogo scan --sarif > results.sarif

Instálalo de forma global si prefieres no usar npx cada vez:

bash
npm install -g datahogodatahogo scan

Qué revisa

Data Hogo detecta tu stack automáticamente y corre los analizadores que correspondan. La cobertura es más profunda en el ecosistema JavaScript/TypeScript; los demás lenguajes tienen un conjunto enfocado de checks de alta señal.

StackEjemplos de lo que detecta
JavaScript / TypeScriptNode, Next.js, React, Express, Fastify, NestJS — inyección, XSS, eval, config insegura, dependencias vulnerables, secretos filtrados
PythonDEBUG de Django, SECRET_KEY hardcodeado, ALLOWED_HOSTS con comodín, Flask/FastAPI sin auth, paquetes vulnerables
GoInyección SQL, inyección de comandos, criptografía débil, credenciales hardcodeadas
Java / KotlinEndpoints de Spring sin autorización, deserialización insegura, XXE, inyección SQL
PHP / LaravelMass assignment, inyección SQL, manejo de archivos inseguro
C# / .NETFalta de [Authorize], deserialización con BinaryFormatter, XXE, hashing débil
MóvilReact Native, Expo, Flutter/Dart — almacenamiento inseguro, secretos hardcodeados
SupabaseFallas de Row Level Security, service keys expuestas, políticas inseguras

La detección de secretos y el escaneo de dependencias corren en todos los proyectos sin importar el lenguaje.

Opcional: análisis más profundo

Dos herramientas estándar de la industria agregan profundidad extra si las tienes instaladas. Data Hogo funciona bien sin ellas: usa sus checks integrados y te dice qué te estás perdiendo.

bash
datahogo doctor   # muestra qué tienes instalado y cómo agregar lo demás
  • Semgrep — ~250 reglas adicionales basadas en AST para JS/TS
  • Gitleaks — conjunto completo de reglas de detección de secretos

Explicaciones y arreglos con AI (usa tu propia llave)

Cada hallazgo viene con una explicación en lenguaje simple y un arreglo sugerido de fábrica. Si quieres arreglos más ricos y con contexto generados por Claude, configura tu propia llave de API de Anthropic: las llamadas van directo de tu máquina a Anthropic, facturadas a ti. Nosotros nunca las vemos.

bash
export ANTHROPIC_API_KEY=sk-ant-...datahogo scan --explain

Úsalo en CI

GitHub Action

yaml
# .github/workflows/security.ymlname: Securityon: [push, pull_request]permissions:  contents: read  security-events: writejobs:  scan:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - uses: datahogo/datahogo@main        with:          fail-on: high

Los hallazgos aparecen automáticamente en la pestaña Security de tu repositorio. Ve action.yml para todas las opciones (path, url, upload-sarif).

Cualquier otro CI

Data Hogo termina con un código distinto de cero cuando encuentra problemas de la severidad que elijas, así que encaja en cualquier pipeline:

yaml
- run: npx datahogo scan --fail-on high --sarif > results.sarif- uses: github/codeql-action/upload-sarif@v3  if: always()  with:    sarif_file: results.sarif

El resultado SARIF aparece en la pestaña Security de tu repositorio.

Comandos y opciones

datahogo [scan] [ruta]        Escanea un directorio (por defecto: el actual)datahogo doctor               Revisa las herramientas externas opcionales
  --json                      Salida JSON legible por máquina  --sarif                     SARIF 2.1.0 (GitHub Code Scanning)  --fail-on <severidad>       Sale con 1 si hay hallazgos >= critical|high|medium|low  --url <url>                 Escanea también una URL desplegada (headers, SSL, CORS)  --explain                   Explicaciones con AI (requiere ANTHROPIC_API_KEY)  --all                       Incluye hallazgos informativos / no productivos  --help, --version

Úsalo desde Claude Code, Cursor o Claude Desktop (MCP)

@datahogo/mcp expone el mismo motor de escaneo como tools de MCP, así que tu agente puede escanear un proyecto, consultar un hallazgo específico, revisar una URL desplegada o auditar reglas de Supabase/Firebase — y escribir la explicación y el arreglo él mismo, sin costo de AI para ti.

bash
claude mcp add datahogo -- npx -y @datahogo/mcp

Para Cursor u otro cliente MCP, apúntalo al mismo comando: npx -y @datahogo/mcp, transporte stdio.

Tools: scan_project, get_finding, scan_url, check_db_rules.

¿Prefieres algo más ligero específicamente en Claude Code? Instala el skill de Claude Code en su lugar — solo le enseña al agente a correr npx datahogo scan --json e interpretar la salida, sin necesidad de un proceso de servidor MCP:

bash
npx skills add datahogo/datahogo/skills/datahogo

Data Hogo Cloud

La CLI es gratis y siempre lo será. Si quieres historial de escaneos, seguimiento de hallazgos entre commits, pull requests de arreglos automáticos, escaneos programados y dashboards de equipo, Data Hogo Cloud construye todo eso sobre el mismo motor. Usar la CLI nunca lo requiere.

Contribuir

Los issues y pull requests son bienvenidos — las nuevas reglas de detección para cualquier lenguaje son especialmente valiosas. El motor de escaneo vive en packages/core y la CLI en packages/cli.

bash
git clone https://github.com/datahogo/datahogo.gitcd datahogonpm installnpm run buildnpm test

Apoya el proyecto

Data Hogo es gratis y open source. Si te salvó de lanzar una vulnerabilidad, considera patrocinar el proyecto — financia nuevas reglas de detección y mantiene el proyecto vivo.

Licencia

AGPL-3.0 © Data Hogo. Eres libre de usarlo, leerlo, correrlo y modificarlo. Si ofreces una versión modificada como servicio en red, debes compartir tu código bajo la misma licencia.

Source: README.md at commit aeb2336

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts