GitHub Repo Health Check

GitHub repo health check before you depend on a library: each repository gets a 0–100 score, a verdict and a list of concrete risks ranked by severity, each with the data behind it.

What it checks

Every check below maps to a field in the output.

Check	Output field(s)
Days since the last push (over 120 = low maintenance, over 365 = abandoned)	lastCommitAt, daysSinceLastCommit, risk low-maintenance / abandoned
Archived repository	archived, risk archived
License	license, hasLicense, risk no-license
Tests: test folder or config in the root, or a real test script / test framework in package.json	hasTests, testEvidence, risk no-tests
CI config in the root (.github, GitLab CI, CircleCI, Jenkins, Azure)	hasCI, risk no-ci
README	hasReadme, risk no-readme
Single contributor (first 10 contributors sampled)	contributorsSample, risk single-maintainer
Published releases	releases (0 or 1, first page only), risk no-releases
Open issues vs stars (over 100 open and over 10% of stars)	openIssues, stars, risk neglected-issues
Issues disabled	risk issues-disabled
Repo stats	stars, forks, watchers, language, createdAt, url
Score and verdict	score, verdict, riskCount

Risks are sorted by weight, highest first. Each risk has code and detail in English, plus codigo and detalle (the original Spanish fields, kept for backward compatibility). verdict and testEvidence are currently in Spanish (Se puede usar = safe to use, Usar con cuidado = use with care, Riesgoso = risky, No depender de esto = do not depend on it).

A repository that cannot be read is reported as { "repo", "error", "score": null } and the run continues.

Input

Field	Type	Required	Default	Description
repos	array	yes	["https://github.com/apify/crawlee"]	One per row: owner/name or a full GitHub URL.
githubToken	string	no	—	Optional read-only token. Without it GitHub allows 60 requests/hour (about 10 repos); with it, 5,000. Not stored.

Example input (runs as is)

{
  "repos": [
    "facebook/react",
    "https://github.com/apify/crawlee"
  ]
}

Output

One dataset item per repository. Example from a real run on 2026-10-14 (code and detail are added in this version next to the original fields):

{
  "repo": "django/django",
  "url": "https://github.com/django/django",
  "score": 90,
  "verdict": "Se puede usar",
  "riskCount": 2,
  "risks": [
    {
      "codigo": "sin-releases",
      "detalle": "Sin releases publicados: no hay versiones estables marcadas.",
      "code": "no-releases",
      "detail": "No published releases: no stable versions are tagged.",
      "peso": 6
    },
    {
      "codigo": "issues-cerrados",
      "detalle": "Los issues están deshabilitados: no hay dónde reportar un bug.",
      "code": "issues-disabled",
      "detail": "Issues are disabled: there is nowhere to report a bug.",
      "peso": 4
    }
  ],
  "stars": 91327,
  "forks": 37274,
  "openIssues": 540,
  "watchers": 2282,
  "language": "Python",
  "license": "BSD-3-Clause",
  "hasLicense": true,
  "hasTests": true,
  "testEvidence": "carpeta o config en la raíz",
  "hasCI": true,
  "hasReadme": true,
  "contributorsSample": 10,
  "releases": 0,
  "archived": false,
  "createdAt": "2012-04-28T02:47:18Z",
  "lastCommitAt": "2026-10-14T12:29:10Z",
  "daysSinceLastCommit": 0,
  "checkedAt": "2026-10-14T22:32:04.747Z"
}

Pricing

Pay per event: USD 0.01 per checked repo. Checking 10 repos costs USD 0.10, plus Apify's small per-run start and per-dataset-item events. Repos that fail are not charged as checked repos.

Export results as JSON, CSV, Excel or HTML, or use them via the Apify API.

---

© 2026 Ranuk IT Solutions · ranuk.dev