We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money
Codecov’s appeal is clear: PR coverage feedback, unlimited public uploads for open-source projects, and coverage and bundle-size tracking. The reasons to reconsider are concrete, too: Reddit threads discuss the compromised Bash uploader and GitHub Action, while other users report missed coverage, inconsistent results and upload failures. The tools below are mostly adjacent QA options, not proven drop-in coverage replacements. Choose based on whether you need code checks, test traceability, visual review or device testing—and verify coverage reporting before migrating.
01Why people leave Codecov
Supply-chain security concerns
Reddit discussions of the compromised Bash uploader and GitHub Action raised concerns about CI pipeline access, exposed secrets and the work of rotating keys.
Coverage and upload reliability
One Reddit thread reports missed or inconsistent coverage on main and EPIPE upload failures; another commenter says reliability issues led their project to stop using Codecov.
Coverage can mislead
A Reddit commenter notes that deleting covered code can make reported coverage fall. Coverage is a blunt signal, not proof that tests are good.
02The alternatives, ranked by fit
- Code quality gates
SonarQubeSonarQubeSonarQube is the closest listed option if you want code checks around a repository rather than a replacement for Codecov’s coverage workflow. Its listed use cases include code quality gates, smaller private projects and public open-source repositories. It has a free plan and is listed from $34; check the LOC caps and add-on costs before comparing its price with Codecov.
Trade-off: The pricing page does not describe it as a coverage-upload replacement; LOC caps and add-on costs need checking.
6.5/10from
$34/mofree plan - Jira test tracking
XrayXrayIf Jira is central to your QA workflow, Xray shifts the focus to test traceability and automating tests from Jira. That can suit teams whose main frustration is organizing and connecting tests, rather than collecting PR coverage feedback. It is listed from $8.33, but the published description does not present it as a drop-in coverage reporter.
Trade-off: It centers on Jira test workflows, not Codecov-style coverage feedback.
6.0/10from
$8.33/mo - Visual UI review
ChromaticChromaticChromatic fits teams reviewing UI changes together or running browser-based visual checks. That is a different job from measuring code coverage, but it may address a broader need to catch regressions during review. It has a free plan and is listed from $179. The pricing page warns that snapshot costs can rise as testing grows.
Trade-off: It focuses on visual checks; snapshot costs can rise as testing grows.
7.5/10from
$179/mofree plan - Real-device testing
BrowserStackBrowserStackBrowserStack is worth considering when the gap is testing across real devices, browsers or manual and automated QA—not replacing Codecov’s coverage reporting. The pricing page describes broad device coverage and a starting price of $29. It also warns that costs can rise quickly for teams, so compare the testing scope you need before switching.
Trade-off: Device and browser testing is a different job, and costs can rise quickly.
7.6/10from
$29/mo - Browser and device QA
Sauce LabsSauce LabsSauce Labs is listed for browser and device testing, real-device testing, and distributing beta app builds. It may suit a team trying to consolidate broader QA work, but the published description does not identify coverage reporting as a replacement use case. The listing starts at $39 and notes that automation plans cost more than manual testing.
Trade-off: Automation plans cost more than manual testing; coverage replacement is not listed.
6.7/10from
$39/mo - Local cloud testing
LocalStackLocalStackLocalStack makes sense if your reason for reassessing Codecov is part of a wider testing-stack change and you need to test AWS applications locally. Its listed use cases also include validating fixes before cloud deployment and local Snowflake workflows. It has a free plan and is listed from $39, but it is not described as a coverage reporter.
Trade-off: It emulates cloud workflows locally; it is not described as a coverage-reporting alternative.
6.4/10from
$39/mofree plan
03Side by side
| Tool | Score | From | Free plan | Best for |
|---|---|---|---|---|
| Codecov Codecov (current) | 6.5 | $4/mo | Yes | Teams adding coverage feedback to pull requests |
| 6.5 | $34/mo | Yes | Teams adding code quality gates | |
| 6.0 | $8.33/mo | No | Teams already working in Jira | |
| 7.5 | $179/mo | Yes | Teams reviewing UI changes together | |
| 7.6 | $29/mo | No | Teams testing across real devices | |
| 6.7 | $39/mo | No | Teams testing across browsers and devices | |
| 6.4 | $39/mo | Yes | Teams testing AWS applications locally |
Questions people ask
Are these direct replacements for Codecov?
The published descriptions do not identify any of these six as a drop-in replacement for Codecov’s coverage uploads and PR feedback. SonarQube is the closest code-focused option, while Xray, Chromatic, BrowserStack, Sauce Labs and LocalStack target other QA workflows. Confirm coverage reporting and integrations before migrating.
Why are teams leaving Codecov?
Reddit threads discuss the compromised Bash uploader and GitHub Action, with commenters raising concerns about CI access and secrets. Other users report missed or inconsistent coverage and upload failures. One commenter also questions how useful coverage changes are when code is removed. These are user reports, not a guarantee that every team will see the same problems.
Which Codecov alternative is closest for code checks?
SonarQube is the closest fit in this list for code quality gates. Its the pricing page includes a free plan and a starting price of $34, but warns about LOC caps and add-on costs. That does not establish it as a Codecov coverage replacement, so check the exact reporting and CI needs you rely on.