Configuration

Configure Falcn using a YAML file, environment variables, or CLI flags.

Configuration File

Create config.yaml in your project root or ~/.falcn/config.yaml:

# config.yaml
scanner:
  package_managers:
    - npm
    - pip
    - go
  check_vulnerabilities: true
  parallel_workers: 4

detection:
  runt:
    enabled: true
    threshold: 0.8
  dirt:
    enabled: true
    asset_criticality: INTERNAL
  gtr:
    enabled: true
    max_depth: 5

llm:
  enabled: true
  provider: ollama
  model: llama3
  endpoint: http://localhost:11434
  max_calls: 10

policy:
  mode: ALERT  # BLOCK, ALERT, or REVIEW
  fail_on:
    - malicious
    - critical

output:
  format: table  # json, sarif, table, spdx
  file: null

Environment Variables

All settings can be configured via environment variables:

Variable	Description	Default
`FALCN_LLM_ENABLED`	Enable AI explanations	false
`FALCN_LLM_PROVIDER`	LLM provider (ollama, openai)	ollama
`FALCN_LLM_MODEL`	Model name	llama3
`FALCN_POLICY_MODE`	Enforcement mode	ALERT
`FALCN_OUTPUT_FORMAT`	Output format	table

CLI Flags

CLI flags override config file and environment variables:

falcn scan . \
  --check-vulnerabilities \
  --no-llm \
  --output json \
  --fail-on malicious

Asset Criticality

Set asset criticality to adjust risk scoring:

PUBLIC (0.5x multiplier) – Public-facing, non-critical
INTERNAL (1.0x) – Internal tools and services
CRITICAL (2.0x) – Production, customer-facing

falcn scan . --asset-criticality CRITICAL