GitHub Repo, Maintainer & Company Signal Extractor

Collect bounded public GitHub repository intelligence from repository URLs, owner/name values, or repository search queries. The Actor reads GitHub's public REST responses and uses a public repository-page fallback only when the API returns a not-found response. It normalizes repository metadata, releases, README details, languages, topics, public owner/contributor profiles, and transparent rule-based signals.

Public source behavior

Public GitHub repository pages expose the repository name, owner, description, language, stars, forks, issues, topics, README, releases, and public maintainer/contributor links. The Actor preserves those public fields with API/page attribution and bounded detail requests. It does not log in, access private repositories, bypass CAPTCHA or rate limits, follow external sites for enrichment, or claim that a commercialization signal proves revenue, employment, incorporation, or legal company status.

Input

{
  "repositories": "apify/crawlee",
  "maxResults": 1,
  "includeReadme": true,
  "includeLanguages": true,
  "includeTopics": true,
  "includeReleases": true,
  "maxReleases": 3,
  "includeMaintainer": true,
  "includeContributors": false,
  "includeCommercializationSignals": true
}

Use repositories for exact public targets, or searchQuery/searchQueries for bounded discovery. maxResults, maxPages, and perPage cap discovery; concurrency, delay, timeout, retries, and enrichment toggles control request cost. An optional read-only GitHub token may increase public API limits; it is never written to dataset rows or logs.

Dataset output

Normal rows contain public repository identity and stats, links, timestamps, optional README/language/topic/release enrichment, public maintainer and contributors, and explainable signal evidence. Internal record IDs/types, status/data flags, and source-website markers are not emitted in normal rows. Operational run duration, request controls, and counts are stored separately in the run-summary key-value record.

{
  "repositoryId": 123456789,
  "fullName": "apify/crawlee",
  "name": "crawlee",
  "sourceUrl": "https://api.github.com/repos/apify/crawlee",
  "url": "https://github.com/apify/crawlee",
  "stars": 1234,
  "forks": 120,
  "language": "TypeScript",
  "maintainer": {
    "login": "apify",
    "type": "Organization",
    "profileUrl": "https://github.com/apify"
  },
  "companySignals": {
    "score": 35,
    "labels": ["organization-owner", "developer-product"]
  },
  "scrapedAt": "2026-09-08T00:00:00.000Z"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Local run and validation

npm ci
npm test
npm run lint
apify validate-schema
apify run --purge --input-file test/inputs/live-smoke.json
npm run validate-datasets

Keep runs bounded and respectful of GitHub's public API limits and terms. If GitHub returns an access-control, login, or rate-limit boundary, the Actor skips the unavailable enrichment or target rather than bypassing it.