Tool integration

RuboCop integration guide

Ruby static analyzer and formatter with JSON output

Get a Free API Key

Integrate RuboCop with Vulnesis. Lint Ruby code for style violations, security issues, and performance anti-patterns, then upload JSON results.

RubyCLI toolJSON

Install & scan

$ gem install rubocop

# Or add to Gemfile
bundle add rubocop --dev
$ rubocop --format json --out rubocop.json

Run RuboCop in CI

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

- name: Run RuboCop
  run: |
    gem install rubocop
    rubocop --format json --out rubocop.json

- name: Upload to Vulnesis
  run: vulnetix upload --file rubocop.json

How Vulnesis compares: better together

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

CapabilityVulnesisRuboCop
Security coverage
SAST (static code analysis)✓ Built-in rules + Semgrep augmentation~ Lint + Security department cops catch unsafe Ruby patterns; primarily a style/quality analyzer, not a full SAST engine
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✗
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 RuboCop does well

Where Vulnesis adds to it: Vulnesis ingests RuboCop findings into its cross-scanner queue, dedups Ruby code issues against dependency and secret findings, and applies EPSS/KEV exploit-intel prioritisation, reachability, versioned VEX and SSVC policy that RuboCop does not model. Vulnesis's native SAST plus Semgrep adds security-rule depth while RuboCop remains the language-native Ruby linter/formatter it never replaces.

No migration, no rip-and-replace. RuboCop 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 RuboCop results in Vulnesis

Upload RuboCop JSON 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.

RuboCop documentation ↗  ·  Source repository ↗

Wire RuboCop into your CI/CD pipeline →