Codecov Code Coverage Stats Scraper

Codecov Code Coverage Stats Scraper

Scrape code coverage stats from any Codecov account by owner, provider, or single repository. Pull repo summaries, commit histories, pull request coverage diffs, or per-file line coverage. Export to CSV, JSON, Excel, or XML.

Codecov dashboards show coverage trends, but pulling that data into your own reports or CI checks means clicking through pages or stitching together API calls. This actor reads the public stats pages directly, so you get coverage percentages, patch coverage, and change counts for every repo, commit, PR, or file in one flat dataset. No token setup, no pagination code.

Who uses it	What they scrape Codecov for
Engineering managers	Monitor coverage trends across every team repo in one spreadsheet.
DevOps engineers	Feed per-commit coverage into a CI quality gate or internal dashboard.
Open source maintainers	Audit coverage across hundreds of repos under a large GitHub org.
QA analysts	Identify files with the lowest coverage for targeted test planning.

What it does

This Actor collects Codecov coverage statistics by owner account and returns each repo, commit, pull request, or file as a single row.

• 📦 Four scrape modes: repos (one row per tracked repo), commits (one row per commit), pulls (one row per PR with base and head coverage), and files (one row per file with line-level coverage).
• 🔍 Single-repo focus: set a repository name to fetch exactly that one repo and skip pagination entirely.
• 🏷️ Provider filter: choose GitHub, GitLab, or Bitbucket to match the git host backing the Codecov account.
• ✅ Active-only toggle: return only repos currently sending coverage uploads, dropping stale entries from the result set.
• 📊 Flat row output: every record lands in your dataset with the same schema, ready for CSV, JSON, Excel, or XML export.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Codecov data

📈 Monitor org-wide coverage trends.

An engineering director scrapes all repos under a company GitHub org weekly to track the average line coverage and spot teams that are slipping.

🔬 Audit per-commit coverage deltas.

A DevOps engineer pulls every commit from the last sprint to find which changes introduced uncovered code before the release branch is cut.

🔍 Compare PR head vs. base coverage.

A platform team scrapes pull request stats to enforce a policy that no PR merges when the head branch coverage drops below the base branch.

📁 Find the least-covered files.

A QA lead scrapes per-file coverage for a critical service and sorts by line coverage to prioritize test-writing effort for the riskiest modules.

Why choose this scraper

	What you get
No API token required	Reads public Codecov stats pages directly.
Four granularity levels	Repos, commits, pull requests, or individual files.
Multi-provider support	Works with GitHub, GitLab, and Bitbucket-backed accounts.
Active-only filtering	Excludes repos that stopped sending coverage uploads.

How it compares

No other Store actor targets Codecov the same way, so the honest comparison is with the alternatives teams actually weigh.

	Codecov Code Coverage Stats Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When Codecov changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor from an owner slug and a provider, then narrow results with an optional single-repo name and an active-only toggle. The Input tab lists every parameter.

A first run with the defaults:

{
 "mode": "repos",
 "owner": "vercel",
 "maxItems": 10
}

A larger pull:

{
 "mode": "repos",
 "owner": "vercel",
 "maxItems": 200
}

Pricing

Pay-per-result: $0.0363 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$3.63
1,000 results	$36.30
10,000 results	$363.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Codecov Code Coverage Stats Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Codecov through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/codecov-stats-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that the owner slug and provider are correct. If active-only is checked, the org may have no repos currently sending coverage. Try unchecking it to see all historically tracked repos.

The actor returns far fewer repos than I expected.

The active-only toggle filters out repos that have stopped sending coverage uploads. Large orgs often have hundreds of stale repos. Uncheck active-only to get the full list.

I set a repo name but the actor still seems slow.

When a single repo is specified, the actor skips pagination and fetches only that repo. If you are in commits or pulls mode, a busy repo can still have thousands of records. Lower the max items value to speed up the run.

The actor fails with a timeout or error.

Codecov pages can be slow for very large orgs. Try reducing max items, or switch to a single repo with the optional repository field. If the issue persists, the Codecov public pages may be rate-limiting; wait and retry.

Can I get coverage for a specific branch?

The actor scrapes the default branch coverage shown on Codecov's public pages. Branch-specific stats are not exposed in the current scrape modes.

FAQ

Question	Answer
Do I need a Codecov API token?	No. This actor reads the public stats pages that Codecov serves for every tracked repository. You only need the owner slug and provider.
Which git providers does this support?	GitHub, GitLab, and Bitbucket. Set the provider input to match the host backing the Codecov account you want to scrape.
Can I scrape a single repository instead of the whole org?	Yes. Fill in the optional repository name field and the actor fetches only that one repo, ignoring pagination and the max items limit for other repos.
What does the active-only toggle do?	When checked, the actor returns only repositories that are currently sending coverage uploads to Codecov. Unchecked, it returns every repo Codecov has ever tracked for that owner.
How many records can I get in one run?	You set the maximum records field. The actor stops after collecting that many rows, whether you are scraping repos, commits, pulls, or files.
What is the difference between the four scrape modes?	Repos mode returns one row per tracked repository with its overall coverage. Commits mode returns one row per commit with its coverage delta. Pulls mode returns one row per PR with base and head coverage. Files mode returns one row per file in the latest report with line-level coverage.
Can I export the data to Google Sheets?	Yes. Apify supports CSV, JSON, Excel, and XML exports. You can download the dataset and import it into Google Sheets, or use an Apify integration to push it directly.
Does this work for private repositories?	This actor reads public Codecov pages. If a repository's coverage stats are publicly visible on Codecov, the actor can scrape them. Private repos that require authentication are not supported.
How do I find the owner slug for a Codecov account?	Look at the Codecov URL for any tracked repo. The owner is the segment after the provider and before the repo name, for example 'vercel' in codecov.io/github/vercel/next.js.
What happens if an org has thousands of repos?	Set the max items field to control how many records you collect. With the active-only toggle on, large orgs often drop from thousands of tracked repos to a few dozen active ones.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Codecov, Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.