xgrep vs Cycode Bearer
How xgrep compares to Cycode Bearer. A single local binary that runs Semgrep-compatible rules with analysis on your machine, versus Bearer's SAST engine and Cycode's cloud ASPM platform.
Bearer is an open-source SAST engine, known for tracing sensitive-data (PII/PHI) flows through code, now part of Cycode, a cloud application-security posture management (ASPM) platform. This page compares xgrep to the code-scanning capability. Cycode the platform is broader, covering ASPM and pipeline security among other things, and xgrep does not try to replace all of it.
At a glance
| xgrep | Cycode Bearer | |
|---|---|---|
| Install | single static binary | Bearer CLI / container |
| Where your code is analyzed | always local | Bearer CLI runs locally; the Cycode platform is cloud-hosted |
| Account required to scan | no for SAST and secrets; dependency vulnerability matching needs a Mondoo account | no for the Bearer CLI; yes for the Cycode platform |
| Rule format | Semgrep-compatible + built-in corpus | Bearer's own rules |
| Taint / dataflow | yes | yes (data-flow focused) |
| Sensitive-data (PII/PHI/PCI) flow | yes, xgrep dspm classifies the data a codebase holds and reports where it leaks | yes, Bearer's core focus |
| Secrets | built in | via the Cycode platform |
| Dependency (SCA) + vuln matching | built in | via the Cycode platform |
| SBOM / CBOM from source | built in | via the Cycode platform |
| AIBOM (AI/ML inventory) from source | built in, 20 languages, fully offline | via the Cycode platform (early access) |
Local, and rule-compatible
xgrep runs entirely from one local binary and reads Semgrep rule syntax, so
existing rules run without translation (see
Semgrep compatibility). The Bearer
CLI also runs locally, but its broader capabilities live in the Cycode cloud
platform: secrets, dependencies, posture. xgrep keeps SAST, secrets and dependency
scanning in the one local binary, and pairs with Mondoo Platform for
organization-wide
software supply chain security
across source code, dependencies, build integrity and signed SBOMs. The analysis still
finishes locally and only the findings publish, with --incognito to opt out.
Dependency vulnerability matching is the step that needs an account, and it sends your
SBOM rather than your source.
Accuracy
Both tools are scored on the same suite: deliberately vulnerable applications with hand-triaged ground truth, on pinned versions. xgrep comes out ahead on every application where both run.
| application | language | xgrep recall | Bearer recall | xgrep F1 | Bearer F1 |
|---|---|---|---|---|---|
| railsgoat | Ruby | 94% | 50% | 89% | 55% |
| java-sec-code | Java | 100% | 20% | 87% | 33% |
| webgoat | Java | 90% | 60% | 78% | 67% |
| juice-shop | JavaScript | 96% | 25% | 61% | 24% |
| shopizer | Java | 100% | 0% | 38% | — |
A dash means Bearer found none of that application's vulnerabilities, which leaves F1 undefined.
Recall is how much of what is really there a tool finds. Precision is how much of what it reports is real. Either is easy to win alone, so F1 combines them and only rises when both do.
Bearer has no C#, Kotlin, PowerShell or C/C++ support, so it does not run at all on seven more of the suite's applications. Those include three C# apps where xgrep scores 100%, 92% and 84% F1, and a Kotlin one where it finds all 16 planted vulnerabilities with no false alarms.
When Cycode is the better fit
If you want Cycode's managed ASPM and its pipeline-security coverage specifically, that is what it sells, with the cloud account and platform footprint it entails. The organization-wide posture and supply-chain dashboards are not the deciding factor they look like, because Mondoo Platform provides those too (below). xgrep is the choice when you want accurate, Semgrep-compatible SAST plus secrets and dependency scanning from a single local binary whose analysis never uploads your code.
Bearer's privacy focus is less of a deciding factor than it used to be, though, because
xgrep dspm covers the same ground. It classifies the entities and fields a codebase
holds as PII, PHI, PCI, secrets, customer content or AI context, then reports where a
classified value reaches a log, a third party, an AI prompt, an API response or
storage. All of it from source alone, with no datastore access. See
code DSPM.
When Mondoo is the better fit
Cycode's pitch is one platform for application security posture. Mondoo's is the same shape with the analysis kept local and the reach extended: xgrep puts SAST, SCA, secrets and malware findings for every repository on Mondoo Platform, risk-scored and org-wide, and cnspec adds infrastructure as code, cloud accounts, containers, Kubernetes and running hosts. Both land on the same asset, so code, build and runtime sit in one view, which an application-security platform on its own does not reach.
If you are comparing ASPM platforms, that is the comparison worth running, and Mondoo gets you there without your source leaving your machine. For sovereign requirements the platform's deployment options include a self-managed install in your own cloud account, and the scanning side needs no connection at all.
Try it
xgrep scan . # local SAST + secrets + dependency vulns
xgrep scan -f ./my-rules/ . # run your existing Semgrep-format rulesSee Getting started.
Last updated on