~/.codegate/config.json (global) and <scan-target>/.codegate.json (project override), unless noted otherwise. See Configuration overview for precedence and merge rules.
Scan behavior
The minimum severity level at which a scan exits with code
2 (blocking). Findings at or above this level trigger blocking behavior in codegate run.Allowed values: critical, high, medium, low, infoWhen
true, codegate run proceeds to launch the selected tool without prompting if all findings are below severity_threshold. When false, any finding — even a non-blocking one — prompts for confirmation before launch.Default output format for
codegate scan. Can be overridden at runtime with --format.Allowed values: terminal, json, sarif, markdown, htmlPath to the file that stores MCP baseline state for rug-pull detection (
NEW_SERVER and CONFIG_CHANGE findings). Paths beginning with ~ resolve to the current user’s home directory.When
true, user-scope AI tool config paths (home directory tool configs) are included in Layer 1 discovery and Layer 3 resource discovery. Set to false to limit scans to the project directory only. Can be force-enabled per run with --include-user-scope.TUI
Controls the interactive terminal UI rendered during
codegate scan and codegate run.Tool discovery
Controls which AI tools CodeGate discovers and uses for Layer 3 deep scan.
Trust and blocking
List of directory paths that are treated as trusted for
codegate run confirmation purposes. When the current working directory is inside a configured trusted directory, warning-level launch confirmations are skipped.Paths are evaluated against resolved absolute paths.Command names that are flagged when found in MCP server
command arrays or hooks. This list is merged with the built-in defaults; the defaults are always retained regardless of what you configure.Domain names that are considered trusted for outbound API call checks. Findings involving these domains are not raised.
Known-safe allowlists
Package or server identifiers that are considered safe and will not produce
NEW_SERVER findings. Prefilled with a set of well-known servers:@anthropic/mcp-server-filesystem@modelcontextprotocol/server-github
Formatter names that are considered safe. Prefilled with common formatters:
prettier,black,gofmt,rustfmt,clang-format
LSP server names that are considered safe. Prefilled with common servers:
typescript-language-server,pyright,rust-analyzer,gopls
Relative hook file paths (relative to the repository root) that are considered safe and will not produce hook-related findings. Example:
.git/hooks/pre-commit.Analysis toggles
When
true, CodeGate checks for hidden or misleading Unicode characters in Layer 2 rule-file scanning and Layer 3 tool-description scanning.Setting this to false disables hidden-unicode findings only. All other rule-file heuristics remain enabled.When
false, IDE_SETTINGS findings are suppressed entirely.When
false, detection behavior is unchanged but owasp arrays in reports are emitted as empty arrays. Use this to reduce report noise if OWASP categorization is not relevant to your workflow.Suppression and rule policy
List of finding IDs or fingerprints to suppress. Matching findings are marked as suppressed and excluded from exit code calculation. Merged across global and project config.
Structured suppression rules. Each rule suppresses findings that match all specified criteria (AND semantics). Omitted criteria are ignored. Merged across global and project config.See Suppression and rule policy for full field reference and examples.
Per-rule policy configuration. Keys are rule IDs; values are policy objects with
disable, ignore, and config fields.See Suppression and rule policy for details.Rule pack loading
Paths to extra JSON rule pack files or directories of JSON rule packs to load in addition to the built-in rules. Merged across global and project config.
After all rule packs are loaded, only rule IDs in this list remain active. An empty list means all loaded rules are active. Merged across global and project config.
Rule IDs to drop after all rule packs are loaded. Applied after
allowed_rules. Merged across global and project config.Collection and persona (advanced)
Default collection scope modes for scans. Allowed values:
default, project, user, explicit, all. Can be overridden per run with --collect.Restrict collection to specific artifact kinds. Allowed values:
workflows, actions, dependabot. When unset, all kinds are collected. Can be overridden per run with --collect-kind.When
true, parse failures in collected inputs are treated as high-severity findings instead of being silently skipped.Audit sensitivity persona applied during scans. Allowed values:
regular, pedantic, auditor. Can be overridden per run with --persona.Runtime mode for optional online audits. Allowed values:
offline, online, online-no-audits. Can be overridden per run with --runtime-mode.Controls the GitHub Actions workflow audit pack.