Integrate Bearer CLI with Vulnetix. Scan source code for data flow security risks including sensitive data exposure, with SARIF output.
Install & scan
$ curl -sfL https://raw.githubusercontent.com/Bearer/bearer/main/contrib/install.sh | sh -s -- -b /usr/local/bin $ bearer scan --format sarif . > bearer.sarif
Run Bearer CLI in CI
Scan on every push and upload the report as a workflow artifact:
- name: Install Bearer
run: |
curl -sfL https://raw.githubusercontent.com/Bearer/bearer/main/contrib/install.sh | sh -s -- -b /usr/local/bin
- name: Run Bearer scan
run: bearer scan --format sarif . > bearer.sarif
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: bearer
path: bearer.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnetix, recorded under Bearer CLI'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" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnetix compares: better together
Vulnetix does not replace Bearer CLI. Keep running it. Vulnetix sits on top of Bearer CLI (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Bearer CLI is strongest at its core category and also carries features in Secret Scanning, just as Vulnetix spans categories.
| Capability | Vulnetix | Bearer CLI |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✓ Open-source SAST with data-flow analysis; OWASP Top 10 / CWE Top 25 rules across 7 languages (Go, Python, PHP, JS, TS, Ruby, Java) |
| 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 | ~ Data-flow rules can flag credentials/tokens moving through code, but not a dedicated secrets scanner |
| 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 Vulnetix 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, Vulnetix 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 Bearer CLI does well
- Data-flow analysis that traces sensitive data (PII/PHI) from source to sink, a privacy-risk lens most SAST tools lack
- Built-in rules mapped to OWASP Top 10 and CWE Top 25 (SQL injection, XSS, path traversal, crypto failures, insecure deserialization)
- Broad language coverage for an OSS SAST tool: Go, Python, PHP, JavaScript, TypeScript, Ruby, Java
- Native SARIF and gitlab-sast output plus HTML reports for easy CI/platform integration
Where Vulnetix adds to it: Bearer is the privacy/data-flow SAST core; Vulnetix ingests its SARIF into one deduplicated cross-scanner queue and adds what Bearer omits (SCA, container, IaC, cloud, license, SBOM, malware/package-firewall) plus exploit-intel prioritisation (EPSS/KEV/ESS), versioned VEX, EOL/SSVC policy, and Safe Harbour autofix.
No migration, no rip-and-replace. Bearer CLI keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise Bearer CLI results in Vulnetix
Upload Bearer CLI 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.