Skip to main content
This page lists the formats check and the scanners can produce, and the languages and file types MergeGuide checks.

Check output formats

mergeguide check supports these formats via --format:
FormatUse it for
textHuman-readable terminal output. The default.
jsonProgrammatic consumption and custom tooling.
sarifCode-scanning dashboards and security platforms (GitHub code scanning, etc.).
markdownPasting a report into a PR comment or document.
mergeguide check src/ --format sarif --output results.sarif

Scanner output formats

mergeguide scan vuln and mergeguide scan iac support text, json, and sarif:
mergeguide scan vuln --format json
mergeguide scan iac main.tf --format sarif

SBOM formats

mergeguide sbom generate produces these SBOM formats:
FormatStandard
cyclonedx-jsonCycloneDX 1.5
cyclonedx-xmlCycloneDX 1.5
spdx-jsonSPDX 2.3
spdx-tag-valueSPDX 2.3
See SBOM export.

Supported languages

MergeGuide checks source files in a range of common languages, including:
LanguageExample extensions
Python.py, .pyw, .pyi
JavaScript.js, .jsx, .mjs, .cjs
TypeScript.ts, .tsx
Java.java
Go.go
Rust.rs
Ruby.rb
PHP.php
C#.cs
C / C++.c, .h, .cpp, .hpp, .cc
Swift.swift
Kotlin.kt, .kts
Scala.scala
Shell.sh, .bash, .zsh

Infrastructure-as-code

The IaC scanner (scan iac) supports Terraform, CloudFormation, Kubernetes, and Helm. See Running scans.
Language and IaC support evolves. If a language you need isn’t listed, confirm current coverage against the running CLI before relying on it.

Next steps

Running scans

Produce these outputs.

CI/CD patterns

Feed SARIF into your pipeline.