Skip to content

Provider Execution

Nightward has built-in offline heuristics and optional explicit providers.

Local Providers

These run only when selected with --with:

  • Gitleaks: secret scanning.
  • TruffleHog: secret scanning with verification disabled by Nightward’s default runner.
  • Semgrep: static analysis using explicit local config.
sh
nw providers doctor --with gitleaks,trufflehog,semgrep
nw analyze --workspace . --with gitleaks,trufflehog,semgrep --json

Nightward does not install tools. It discovers them on PATH, runs bounded commands, parses supported JSON shapes, and redacts provider-derived evidence before emitting JSON, SARIF, TUI, Raycast, MCP, policy, or badge output.

Online-Capable Providers

These require both provider selection and an online gate:

sh
nw analyze --workspace . --with trivy,osv-scanner,socket --online --json
ProviderBehavior
trivyRuns a filesystem scan with JSON output. Vulnerability database behavior can contact upstream services.
osv-scannerRuns source scanning against vulnerability data.
socketCreates a remote Socket scan artifact and uploads dependency manifest metadata. Nightward does not fetch remote Socket reports in v1.

Use allow_online_providers: true only in policy files where that network behavior is intended.

Raycast Provider Doctor

The Raycast Provider Doctor mirrors this model:

  • enable or disable selected providers for Raycast Analysis;
  • keep online-capable providers blocked until the extension preference allows them;
  • show install commands and upstream docs when a provider is missing.

Raycast does not run package managers for you. That keeps provider installation explicit and avoids surprising writes from a status UI.

Local-first. No telemetry. No default network calls. No live config mutation.