Integrate ktlint with Vulnesis. Lint Kotlin code for style violations and formatting issues, then upload SARIF results for centralised tracking.
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: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under ktlint's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnesis
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 Vulnesis CLI
run: |
curl -fsSL https://cli.vulnes.is/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" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnesis compares: better together
Vulnesis does not replace ktlint. Keep running it. Vulnesis sits on top of ktlint (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
| Capability | Vulnesis | ktlint |
|---|---|---|
| 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 / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✗ |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25 registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + 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 policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What ktlint does well
- Opinionated, zero-config "anti-bikeshedding" enforcement of the Kotlin Coding Conventions and Android Kotlin Style Guide
- Built-in formatter (-F / format) that auto-fixes most violations, eliminating separate formatter setup
- Native SARIF reporter (alongside plain, JSON, Checkstyle, HTML) that plugs directly into GitHub code scanning and CI/CD
- Created at Pinterest and now community-maintained under the ktlint org, with a mature Gradle plugin ecosystem for painless integration
Where Vulnesis adds to it: Vulnesis ingests ktlint's native SARIF output into its consolidated, deduplicated findings queue and does not run Kotlin style linting itself; Vulnesis's SAST engine (built-in rules + Semgrep) addresses code-security defects, not Kotlin formatting. Together, ktlint enforces Kotlin style while Vulnesis layers cross-scanner dedup, exploit-intel prioritisation, reachability and VEX.
No migration, no rip-and-replace. ktlint keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise ktlint results in Vulnesis
Upload ktlint SARIF output to the Vulnesis 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.