{
  "product": "HefestoAI",
  "description": "Pre-commit code quality guardian for AI-generated code",
  "faq": [
    {
      "q": "What is HefestoAI?",
      "a": "HefestoAI is a pre-commit guardian that detects semantic drift and risky changes in AI-generated code before they reach production. It runs as a git hook and in CI."
    },
    {
      "q": "What is semantic drift?",
      "a": "Semantic drift is when code changes still compile and pass tests but silently alter behavior — authorization logic, invariants, contracts, or business rules. Traditional linters miss it."
    },
    {
      "q": "How is HefestoAI different from SonarQube or Snyk?",
      "a": "HefestoAI is pre-commit (prevents issues before they enter the repo). SonarQube and Snyk are post-commit scanners that detect issues after the fact. HefestoAI is also designed specifically for AI-generated code."
    },
    {
      "q": "How is HefestoAI different from Claude Code Security?",
      "a": "Claude Code Security scans entire repos post-commit for security vulnerabilities (Enterprise only). HefestoAI runs pre-commit and in CI for any developer: the CLI is free, PRO is $8/month per user and OMEGA is $19/month. It focuses on code quality and semantic drift."
    },
    {
      "q": "Why use HefestoAI if we already have GitHub Code Quality or Copilot Autofix?",
      "a": "GitHub's tools fit well if your team is on GitHub Team or Enterprise Cloud and wants findings in the pull request. On pull requests, Code Quality posts deterministic CodeQL findings for C#, Go, Java, JavaScript, Python, Ruby and TypeScript, and Copilot Autofix suggests fixes for code scanning alerts. HefestoAI checks one step earlier. hefesto install-hooks adds a pre-commit hook that analyzes the files you're committing and blocks the commit on HIGH findings, before anything is pushed. GitHub doesn't document a pre-commit mode for Code Quality. The hook runs with git on the developer's machine, so it also works for teams on GitHub Enterprise Server, where Code Quality isn't available. HefestoAI also has rules for COBOL, Terraform, Dockerfile, CloudFormation and Helm, which aren't among Code Quality's rule languages. Its findings come from rules, so the same code gets the same result on every run. GitHub describes Autofix as non-deterministic."
    },
    {
      "q": "How do I install HefestoAI?",
      "a": "pip install hefesto-ai — requires Python 3.10+. Then run: hefesto analyze . or hefesto install-hooks to auto-run on every commit."
    },
    {
      "q": "What languages does HefestoAI support?",
      "a": "The package ships analyzers for 22 formats: 7 code languages (Python, TypeScript, JavaScript, Java, Go, Rust, C#), 11 DevOps formats and 4 Cloud IaC formats. In v4.20.4, hefesto analyze runs all 22 of them. TypeScript, JavaScript, Java, Go, Rust and C# need the multilang extra: pip install \"hefesto-ai[multilang]\"."
    },
    {
      "q": "What does HefestoAI cost?",
      "a": "Free: CLI analysis with security rules, SARIF output for GitHub code scanning, the --fail-on CI gate, pre-commit hooks and the GitHub Action (artvepa80/Agents-Hefesto@v4). PRO, $8/month per user, adds the API server, enrichment, scope gating and the hefesto-swarm security pipeline. OMEGA, $19/month, adds IRIS."
    },
    {
      "q": "Can I use HefestoAI with Claude Code / Copilot / Cursor?",
      "a": "Yes — HefestoAI works as a pre-commit hook in any git workflow. It is specifically designed to validate code generated by Claude Code, GitHub Copilot, Cursor, and other AI assistants."
    },
    {
      "q": "Does HefestoAI send my code to any server?",
      "a": "The CLI and the GitHub Action analyze your code where they run and do not upload it. The MCP analyze tool is different: it runs on Narapa's server on the files you send and stores nothing. By default the CLI sends usage events to PostHog US Cloud: a random install ID, file and issue counts, duration, exit code, version, OS and Python; never code, file paths, findings or repository names. Our PostHog project discards the IP address, and the first run only prints a notice. Turn them off with hefesto telemetry disable, HEFESTO_TELEMETRY=0 or DO_NOT_TRACK=1. The GitHub Action sends no usage events unless you set telemetry: 1. hefesto analyze also asks pypi.org for the latest version (cached for 24 hours); from version 4.20.3, HEFESTO_NO_UPDATE_CHECK=1, HEFESTO_TELEMETRY=0 or DO_NOT_TRACK=1 skips that check (hefesto telemetry disable does not; version 4.20.2 and earlier have no setting to turn it off)."
    },
    {
      "q": "Is HefestoAI open source?",
      "a": "The core is open source (MIT). PRO and OMEGA add closed-source features: the API server, enrichment, scope gating and hefesto-swarm in PRO, and IRIS in OMEGA."
    },
    {
      "q": "How do I add HefestoAI as an MCP tool?",
      "a": "npx @smithery/cli@latest mcp add artvepa80/hefestoai — works with Claude Code, Cursor, and any MCP-compatible client. Connect to https://hefestoai.narapallc.com/api/mcp-protocol (Streamable HTTP)."
    },
    {
      "q": "Where is HefestoAI built?",
      "a": "Lima, Peru — by Arturo Velasquez via Narapa LLC (Miami). Independent founder, not VC-backed."
    }
  ],
  "endpoints": {
    "mcp": "https://hefestoai.narapallc.com/api/mcp-protocol",
    "ask": "https://hefestoai.narapallc.com/api/ask",
    "openapi": "https://hefestoai.narapallc.com/openapi.json"
  }
}