cargo-llvm-cov

At a glance

• Editor score
  6.3 / 10
• Pricing
  Open source
• Best for
  Rust teams needing CI-ready coverage gates
• Paid from
  None
• Coverage types
  line, region, function, branch, MC/DC
• Facts checked
  20 Sep 2026

• Where it wins

  • Supports line, region, function, optional branch, and MC/DC coverage types
  • Exports HTML, text, JSON, LCOV, Cobertura, and Codecov formats
  • Works with GitHub Actions, GitLab CI, Codecov, and cargo-nextest

• Where it doesn't

  • Branch coverage and MC/DC are documented as unstable features
  • C and C++ coverage is limited to code linked through Rust FFI
  • Its workflow is centered on Cargo-based Rust projects

Our verdict on cargo-llvm-cov

cargo-llvm-cov is an open-source Cargo subcommand for measuring code coverage in Rust projects. It uses LLVM source-based instrumentation and can run cargo test, cargo run, or cargo-nextest workflows. The tool suits Rust teams that want coverage reporting during local development and continuous integration, especially when coverage thresholds and uncovered-item limits need to be part of a repeatable CI workflow. It also supports C and C++ coverage when that code is linked through Rust libraries or binaries via FFI.

Coverage depth and reporting breadth are major strengths. The published capabilities include line, region, function, optional branch, and MC/DC coverage types, along with merging coverage collected under different test conditions. Reports can be exported as HTML, text, JSON, LCOV, Cobertura, or Codecov Custom Coverage. That range supports both readable local reports and downstream CI or coverage-service workflows. GitHub Actions, GitLab CI, Codecov, cargo-nextest, and VS Code are part of its surrounding integration fit, while Windows, macOS, and Linux support makes it suitable for varied development environments.

For teams adopting coverage gates, thresholds and uncovered-item limits provide direct control over pass or fail criteria. The open-source model keeps the tool available without commercial plan distinctions, and self-hosted use fits teams that want coverage processing within their own development or CI setup. The main boundary is scope: its workflow is built around Cargo and Rust, with C and C++ coverage tied to Rust FFI. Branch coverage and MC/DC are also documented as unstable features. Choose cargo-llvm-cov when Rust coverage depth, report flexibility, and CI controls matter; consider another tool when the primary need is broader language coverage outside Rust-linked C or C++.

cargo-llvm-cov pricing

cargo-llvm-cov fact sheet

cargo-llvm-cov integrations

cargo-llvm-cov lists 5 integrations on its own site.

• GitHub Actions
• GitLab CI
• Codecov
• cargo-nextest
• VS Code

Alternatives to cargo-llvm-cov

• CodecovA broad CI coverage platform with strong pull-request checks, analytics, and integrations.10.0
• CoverallsA mature coverage service for multi-language teams needing CI and pull-request visibility.9.2
• ReportGeneratorA flexible command-line coverage reporter with strong aggregation and history features.7.7

See all cargo-llvm-cov alternatives →

Featured on iTechGuides

cargo-llvm-cov is listed in our Test Coverage Tools directory. Add the badge to your site — it links back to this page.

<a href="https://www.itechguides.com/products/cargo-llvm-cov/"><img src="https://www.itechguides.com/best/badge/cargo-llvm-cov.svg" alt="Featured on iTechGuides" width="230" height="46"></a>

Reviewed by iTechGuides Editors · Editorial team · Updated Sep 2026

Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. It never changes a score or a verdict. How we rank.

Last updated 28 Sep 2026 · How we research and update