CodeInspectus is a local-first, privacy-preserving secure MCP server and CLI developed by Synvoya. It targets AI-generated "vibe coding" code and can be invoked by AI coding agents such as Claude Code, Cursor, and Codex to implement a scan → fix → rescan closed loop, entirely on the local machine, with no account required and zero network egress during scanning.
In terms of main capabilities, CodeInspectus unifies three industry open-source engines under a single normalized schema keyed by CWE: Opengrep handles SAST / OWASP Top 10 (SARIF); Gitleaks handles secret detection; Trivy handles dependency CVEs (SCA), IaC misconfigurations, secrets, licenses, and SBOM. At the same time, it adds AI code-specific checks that general-purpose scanners tend to miss, such as client-side secrets/bundle exposure, Supabase RLS / reverse authentication (CVE-2025-48757 class), prompt injection sinks, model-generated tool arguments reaching Node, Python, and, with limited support, Go, Java, C#, PHP, Rust, and Ruby shell sinks without guards, model output reaching JavaScript eval / Function, Next.js and Express admin API handlers lacking visible authentication or server-side authorization, Supabase Edge Functions deployed anonymously but lacking request authentication or authorization for privileged operations, client-writable user_metadata authorization, unsanitized model/user output rendered via dangerouslySetInnerHTML (XSS / LLM05), as well as API boundary leaks, raw requests written directly to the database, sensitive logging, and evidence-based security header/CSP/Referrer-Policy/Permissions-Policy/session cookie/Supabase CAPTCHA configuration checks. There are also dedicated rule packs for Flutter/Dart, Android/iOS, React Native, Expo, Python AI/API, Go, Java, C#, PHP, Rust, Ruby, Firebase configuration, and GitHub Actions workflows.
Included manifestIncludes 94 curated checks: 72 first-party native rule IDs, 18 Opengrep-owned SAST rules, and 4 custom Gitleaks rules. Opengrep, Gitleaks, and Trivy are optional, managed, incremental engines. CodeInspectus explains each engine's coverage, license, platform-specific size, and required actions before requesting permission; after approval, it downloads official SHA-pinned engine binaries, stores them outside the npm package, and invokes them as local subprocesses.
In terms of usage, the prerequisite is Node.js >= 22, with Node 24 LTS recommended. The first bare run of npx codeinspectus opens guided setup; MCP clients start it via piped stdio, exposing codeinspectus_setup, and agents must request a plan, present it and obtain permission, then call install with confirm_downloads=true. The setup phase downloads only missing, mismatched, or newly pinned binaries, verifies the immutable lockfile, and atomically installs them to ~/.codeinspectus/; the offline Trivy vulnerability database is refreshed only when it is missing, there is no rescan source, or it is more than seven days old. Every scan and codeinspectus_list_rules response includes structured engine_setup status: ready, repair_required, db_refresh_recommended, or unsupported_platform.
Supports CLI, CI, and local evidence workflows: Git range scans preserve full repository context, mark changes and supported context discovery, report the exact resolved revision and explicit integrity limitations, and never check out, reset, stage, or modify the repository; sealed packages preserve sanitized JSON, SARIF, Markdown, coverage, provenance, and attached canonical scan records with content hashes, and must be verified before export or comparison; CSV is a deterministic spreadsheet-safe projection of the canonical JSON model, always preserving explicit scan/coverage rows and neutralizing formula-triggering cells; the V2 TypeScript SDK is available from codeinspectus/sdk. Batch mode scans existing repositories, with controlled concurrency, per-repository isolation, and atomic resumable manifests; repository history mode requires separate opt-in and requires exact revisions, UTC dates, and commit count boundaries.
Applicable scenarios include pre-release security review of AI-generated applications, CI gates, comparison of local scan history, baseline enforcement, issue adapters generating sanitized GitHub, Jira, or Linear JSON payloads, etc. In terms of limitations, some upstream Opengrep assets require glibc on Linux, and Alpine/musl is not compatible with Opengrep; the official @contentauth/c2pa-node verifier is an optional peer dependency and must be installed explicitly; if the Trivy DB was installed before 0.3.2, setup must be run once to enable CVE rescan tracking; missing facts are not yet provided.
