GitHub Repository Health & Activity Report avatar

GitHub Repository Health & Activity Report

Pricing

from $1.20 / 1,000 results

Go to Apify Store
GitHub Repository Health & Activity Report

GitHub Repository Health & Activity Report

GitHub Repository Health & Activity Report returns stars, commit activity, contributors, latest release and community-health files for any repo list or org:<name> — one scored row per repo.

Pricing

from $1.20 / 1,000 results

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

What is GitHub Repository Health Checker?

GitHub Repository Health Checker is an Apify Actor that reads stars, commit activity, contributor count, latest release and community-health files for any list of GitHub repositories — or an entire organisation via org:<name> — and returns one scored row per repository. Every lookup goes through the public GitHub REST API (api.github.com): no HTML scraping, no browser, no proxy. Each repo also gets a healthScore (0-100), a letter grade (A-F) and a riskFlags array — "archived", "stale-2-years", "single-contributor", "no-license", "fork" — that drops straight into a due-diligence or vendor-risk report.

What data does GitHub Repository Health Checker extract?

GitHub Repository Health Checker extracts 30+ fields per repository:

FieldTypeDescription
repo, url, description, language, topics, licensestring, arrayIdentity, primary language, GitHub topics and SPDX license
stars, forks, watchers, openIssuesnumberPopularity and open-issue counts
archived, disabled, isFork, defaultBranchboolean, stringRepository status flags
createdAt, pushedAt, updatedAt, daysSinceLastPushstring, numberLifecycle dates and freshness
commitCount, latestCommitAtnumber, stringEstimated total commits (from pagination) and the newest commit's date
contributorCountnumberEstimated contributor count, including anonymous commits
latestRelease, releaseCountobject, number{tag, publishedAt, daysAgo} of the newest release, and how many of the 5 most recent were found
communityHealthPercent, hasReadme, hasLicense, hasCodeOfConduct, hasContributing, hasSecurityPolicynumber, booleanGitHub's community-profile checklist
healthScore, healthGrade, riskFlagsnumber, string, array0-100 score, A-F grade and plain-English risk flags
query, error, scrapedAtstringThe input entry that produced the row, per-row failure notes, and check timestamp

How to use GitHub Repository Health Checker

  1. Paste repositories into Repositories or organisations: bare owner/repo (apify/crawlee), full URLs (https://github.com/expressjs/express), or org:<name> (org:apify) to pull that organisation's most recently updated public repos.
  2. Optionally paste a free GitHub personal access token (no scopes needed) to raise the API limit from 60 to 5000 requests/hour — each repo costs up to 5 requests, so anything past ~10 repos per run needs one.
  3. Click Start, then export the results as JSON, CSV, Excel or HTML from the Output tab.

Example input

{
"repos": ["apify/crawlee", "https://github.com/expressjs/express", "org:apify"],
"orgRepoLimit": 5,
"maxConcurrency": 3
}

Example output

{
"repo": "expressjs/express",
"url": "https://github.com/expressjs/express",
"language": "JavaScript",
"license": "MIT",
"stars": 67000,
"forks": 8100,
"openIssues": 130,
"archived": false,
"daysSinceLastPush": 3,
"commitCount": 6200,
"contributorCount": 292,
"latestRelease": { "tag": "5.1.0", "publishedAt": "2026-03-31T00:00:00.000Z", "daysAgo": 165 },
"communityHealthPercent": 87,
"hasReadme": true,
"hasLicense": true,
"healthScore": 99,
"healthGrade": "A",
"riskFlags": [],
"query": "https://github.com/expressjs/express",
"scrapedAt": "2026-09-12T18:05:00.000Z"
}

Input parameters

ParameterTypeDefaultDescription
reposarray["apify/crawlee"]owner/repo, GitHub URLs, or org:<name>, one row per repo
githubTokenstringnone (secret)Raises the API limit from 60 to 5000 requests/hour
includeContributorsbooleantrueFetch an estimated contributor count (1 extra request/repo)
includeReleasesbooleantrueFetch the 5 most recent releases (1 extra request/repo)
orgRepoLimitinteger30Max repos pulled per org:<name> entry (1-100)
maxConcurrencyinteger3Repositories checked in parallel (1-20)

Pricing

GitHub Repository Health Checker uses pay-per-event pricing: $0.002 per repository result, i.e. $2 per 1,000 repos, plus a negligible actor-start fee. Each repo costs at most 5 small GitHub API requests, so a run stays in the cents even for a few hundred repositories — provided you add a free GitHub token, since the unauthenticated 60/hour limit otherwise caps a token-less run at about 10-12 repos. Set Maximum cost per run and the Actor trims the list to what the budget covers.

GitHub Repository Health Checker vs. manually checking GitHub

Clicking through a repo's Insights tab, its Releases page and its Community Standards checklist one at a time doesn't scale past a handful of dependencies. This Actor takes a whole list — or a whole GitHub organisation — and returns one flat, scored dataset row per repo in seconds, ready to sort by grade, filter by risk flag, or feed into a spreadsheet for an open-source due-diligence review.

Using GitHub Repository Health Checker with AI agents and MCP

GitHub Repository Health Checker is pay-per-event with limited permissions — the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes a list of repositories (or org:<name>) and gets back a structured, scored row per repo — ready for a "should we depend on this?" answer without the agent needing to parse GitHub's HTML or manage pagination itself.

FAQ

How is the score calculated? Pushed within 30 days +25 (within 180 days +15), more than one contributor +15, has a license +10, has a README +5, not archived +15, open-issues/stars ratio under 0.1 +10, a release in the last year +10, plus up to +10 from GitHub's own community-profile percentage. Grades: A ≥ 85, B ≥ 70, C ≥ 50, D ≥ 30, else F.

Why is hasSecurityPolicy always null? GitHub's community/profile endpoint, the only source for this field, no longer reports whether a SECURITY.md file exists. The field is kept in the schema for forward compatibility and always returns null today.

What happens if GitHub rate-limits the run? As soon as a response comes back 403/429 with a zeroed-out quota, the run stops making further requests and every remaining repo gets a row with error: "GitHub rate limit exceeded – add githubToken" instead of failing the whole run.

Is this legal to run? Yes. All data comes from GitHub's public REST API for public repositories, the same data anyone sees by visiting the repo on github.com.

Can I export to CSV or Excel? Yes, from the Output tab or the API, with ready-made Overview and Activity & community views.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, reads public data without a login, and returns one clean row per entity:

Browse the whole suite at webdatatools, or call ten of these Actors straight from Claude, Cursor or Cline with the webdatatools MCP server.

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data

Support and feedback

Found a repo where the score feels off, or a community-health field GitHub has started reporting again? Open an issue on the Issues tab.