Tool integration

ktlint Integration Guide

Anti-bikeshedding Kotlin linter with native SARIF output

Get a Free API Key

Integrate ktlint with Vulnetix. Lint Kotlin code for style violations and formatting issues, then upload SARIF results for centralised tracking.

KotlinCLI toolSARIF

Install & scan

$ # Download the latest standalone binary
curl -sSLO https://github.com/pinterest/ktlint/releases/latest/download/ktlint
chmod +x ktlint && sudo mv ktlint /usr/local/bin/

# Or via Homebrew on macOS
brew install ktlint
$ ktlint --reporter=sarif,output=ktlint.sarif "src/**/*.kt" "**/*.kts"

Run ktlint in CI

Scan on every push and upload the report as a workflow artifact:

- name: Download ktlint
  run: |
    curl -sSLO https://github.com/pinterest/ktlint/releases/latest/download/ktlint
    chmod +x ktlint && sudo mv ktlint /usr/local/bin/

- name: Run ktlint
  run: ktlint --reporter=sarif,output=ktlint.sarif

- name: Upload report
  uses: actions/upload-artifact@v6
  with:
    name: ktlint
    path: ktlint.sarif
    if-no-files-found: warn

Then one publish job hands every artifact in the run to Vulnetix, recorded under ktlint's own name and version. Written once per workflow, however many scanners you run:

publish:
  name: Publish to Vulnetix
  runs-on: ubuntu-latest
  needs: [scan]        # every scanner job, or its report is never published
  if: always()         # or one failing scanner suppresses all the others
  permissions:
    contents: read
    actions: read      # required to list the run's artifacts
  env:
    VULNETIX_ORG_ID: ${{ secrets.VULNETIX_ORG_ID }}
    VULNETIX_API_KEY: ${{ secrets.VULNETIX_API_KEY }}
  steps:
    - uses: actions/checkout@v5
    - name: Install Vulnetix CLI
      run: |
        curl -fsSL https://cli.vulnetix.com/install.sh | sh -s -- --install-dir "$HOME/.local/bin"
        echo "$HOME/.local/bin" >> "$GITHUB_PATH"
    - name: Publish scanner reports
      env:
        GITHUB_TOKEN: ${{ github.token }}
      run: vulnetix gha upload --org-id "$VULNETIX_ORG_ID" --json

After the run, vulnetix gha status reports what was actually recorded.

How Vulnetix compares: better together

Vulnetix does not replace ktlint. Keep running it. Vulnetix sits on top of ktlint (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.

CapabilityVulnetixktlint
Security coverage
SAST (static code analysis)Built-in rules + Semgrep augmentation~ Static Kotlin analysis for formatting plus some bug-class rules (wildcard/unused imports); style-focused, not security. Source: pinterest.github.io/ktlint, github.com/ktlint/ktlint
SCA / dependencies40+ ecosystems, transitive graph
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine
Container & imageImage CVEs, base image, Dockerfile
IaC / misconfigurationTerraform, k8s, CloudFormation
Secret scanning1,000+ rules, source + binary + git history
Cloud / CSPMCloud-posture findings, compliance tab
Mobile (MAST)~ Ingests mobile scanner output; no native mobile engine
License complianceSPDX, copyleft/AGPL/SSPL policy
SBOM generationCycloneDX 1.7 + SPDX 2.3, cosign-signable
Malware / supply-chainDe-duplicated corpus + install-time firewall (25+ registries)
Network / infra vuln~ Ingests network scanner output; no native network scanner
FuzzingIngests fuzzing crashes; no native fuzzer
Pentest / bug bountyIngests pentest/bug-bounty findings; not a testing service
The Vulnetix orchestration layer
Cross-scanner dedup & one queue (ASPM)Correlates every scanner into one prioritised queue with ownership routing
Exploit-intel prioritisationEPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix LEV
Reachability analysisTree-sitter + CVEAffected; direct/transitive/semantic
Versioned VEX + audit trailImmutable OpenVEX/CycloneDX, cosign-signable
Safe Harbour autofixResolves + applies the nearest safe version~ format/-F auto-corrects formatting and some lint issues; style remediation, not vulnerability fixing. Source: github.com/ktlint/ktlint
End-of-life policyFlags/blocks past-EOL runtimes & packages
SSVC / risk-based policySSVC v2 + CISA/FedRAMP/Essential-8 presets

✓ full · ~ partial · ✗ not covered

What ktlint does well

Where Vulnetix adds to it: Vulnetix ingests ktlint's native SARIF output into its consolidated, deduplicated findings queue and does not run Kotlin style linting itself; Vulnetix's SAST engine (built-in rules + Semgrep) addresses code-security defects, not Kotlin formatting. Together, ktlint enforces Kotlin style while Vulnetix layers cross-scanner dedup, exploit-intel prioritisation, reachability and VEX.

No migration, no rip-and-replace. ktlint keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.

Centralise ktlint results in Vulnetix

Upload ktlint SARIF output to the Vulnetix platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.

ktlint documentation ↗  ·  Source repository ↗

Wire ktlint into your CI/CD pipeline →