Codecov threshold enforcement limits on free tier

Question

Codecov provides a free tier designed for low-traffic repositories, offering basic coverage reporting and pull-request annotations. While the v2 API supports coverage threshold configurations, the documentation does not explicitly confirm if enforcement logic is active for non-paid accounts.
There is uncertainty regarding whether the status check will successfully trigger a CI build failure when the reported coverage falls below a defined threshold on a free plan. This behavior is critical for small projects seeking to maintain code quality standards without upgrading to the Starter plan immediately.
Please clarify the following:Does the free tier enforce and return a failure status when a coverage threshold is not met?Is the POST /projects/{id}/thresholds endpoint functional for free-tier accounts?

Tasadduq Burney · Answer

Direct answer
On Codecov's free tier, the POST /projects/{id}/thresholds endpoint is functional and accepts threshold configurations. However, the platform does not guarantee that a coverage miss will produce a failing CI status check. The check may remain neutral or successful. If you need a hard quality gate, implement it outside Codecov's free-tier enforcement.

Confirmed behavior vs. likely limits
Confirmed: Free-tier accounts can create and read threshold settings through the v2 API. The endpoint response structure is consistent across plans.
Uncertain: Whether the enforced flag or downstream CI integration actually blocks a merge on free tier. Public documentation does not explicitly confirm enforcement for non-paid accounts, and behavior may depend on repository settings, the Codecov uploader version, and your Git provider's status-check configuration.

Practical verification steps

Set a threshold above your repository's current coverage.
Push a commit that leaves coverage unchanged or lower.
Check the pull-request status: does it fail, report unstable, or pass?
Review the CI job logs for the Codecov step's exit code.

Recommendation
Until you have verified the status-check result on your own free-tier repository, do not treat Codecov threshold enforcement as a reliable CI gate. Use a separate CI step—such as a coverage tool's built-in threshold flag—to fail the build deterministically.

One detail that changes the advice
Are you currently seeing a failure status on a free-tier repository when coverage is below the threshold? If yes, the tier policy may have changed and you should document the observed behavior rather than assume it is paid-only.

Codecov threshold enforcement limits on free tier

1 answer

Direct answer

Confirmed behavior vs. likely limits

Practical verification steps

Recommendation

One detail that changes the advice

Your perspective belongs here.

0 question comments