Monitor GitHub Repository Growth Over Time

The GitHub Repositories Scraper helps open-source maintainers, investors, and competitive-intelligence teams measure repository momentum over time. It collects public records into a bounded Apify dataset while preserving the query or category that produced each result. That provenance matters when a spreadsheet becomes a recurring workflow rather than a one-off browse.

This guide uses a deliberately narrow starting point: topic:ai-agents stars:>250. Small inputs make field coverage, duplicate behavior, source changes, and cost visible. A large first run can hide all four.

Separate growth from a one-day spike

Imagine tracking fifty agent-framework repositories every Monday. Store each repository's star, fork, watcher, open-issue, and update values in a dated snapshot. Calculate absolute and percentage deltas, but suppress alerts for tiny bases where one new star creates a dramatic percentage. A useful weekly digest can show the five largest star gains, newly archived projects, and repositories that stopped receiving pushes.

Add context before calling any project "fast growing." A launch post, conference talk, or migration can cause a short surge. Fork growth may tell a different story from stars. Issue counts can rise because adoption increased or because maintenance slowed. The monitor should surface changes for investigation. It should not manufacture a single momentum score whose assumptions are impossible to defend later.

Define the question before collecting data

Write down the decision the dataset is meant to support. Name the records that qualify, the freshness window, the minimum fields required, and who reviews exceptions. For this workflow, star, fork, and issue deltas should be examined alongside stable identifiers and current source URLs. Avoid a score that quietly combines unrelated signals.

Set a maximum result count that is cheap to inspect by hand. Ten to fifty records is usually enough for the first pass. Open several ordinary rows, at least one sparse row, and one surprising result. If those examples do not support the intended question, adjust the input before scheduling anything.

Run a bounded Apify Task

Use the Actor input form to encode topic:ai-agents stars:>250. Keep each saved Task focused on one question, geography, topic, category, or counterparty set. Focused Tasks are easier to name, retry, audit, and retire.

After the run finishes, save the Actor build number, run ID, dataset ID, input, and collection time with the export. The Actor returns repository ID, owner, stars, forks, topics, primary language, license, issue counts, archive state, and activity timestamps. Preserve raw values. Put classifications, scores, and business rules in a separate reviewed transformation so source evidence is never overwritten.

Check the evidence at the source

Store first-seen and last-seen values, then calculate deltas only between successful snapshots. Sample more records after a source-layout or API change. Check identifiers, canonical URLs, dates, numeric fields, arrays, and null rates. A result should be reproducible from its input and source link.

A publicity spike can move stars quickly while adoption and maintenance remain unchanged. That limitation belongs in the workflow documentation, not in a footnote added after someone questions the output. Missing fields should remain null rather than becoming zero, false, or an invented label.

Turn snapshots into reliable monitoring

Choose a cadence that matches the decision. Daily collection suits fast-moving operational queues. Weekly snapshots are often enough for market or catalog monitoring. Monthly runs can support slower benchmarks. Store the previous successful dataset and compare stable IDs plus named material fields.

Do not advance the baseline after a failed, partial, or unexpectedly empty run. Separate additions, updates, and removals. An empty dataset is an incident to investigate, not proof that the market disappeared. Alerts should include changed fields, collection time, the source URL, and a link to the Apify run.

Model the dataset without erasing history

Use the source identifier as the primary upsert key. Keep first-seen, last-seen, source-updated, and collected-at timestamps separate because they answer different questions. Retain the original text beside any normalized value. If entity resolution is needed, store the mapping with a confidence note and reviewer rather than silently merging names.

For trend analysis, compare like with like. The same queries, categories, page limits, sort order, and Actor version should be used across snapshots. If an input changes, begin a new series or annotate the break. Otherwise a collection change can be mistaken for a market change.

Export the result and control access

Apify datasets can be downloaded as JSON, CSV, or Excel or consumed through the API, webhooks, Make, Zapier, n8n, and MCP workflows. Keep credentials outside Actor inputs. Restrict downstream access to the use case and define retention for raw snapshots, derived tables, and alerts.

The GitHub Repositories Scraper on Apify charges per saved result and exposes an explicit result limit. Start with a small verified run. Scale only when the extra records change a real decision and the review process can absorb them.

Operational checklist

Before scheduling, confirm that the input is allowed, bounded, and documented. Verify representative output against the source. Record expected row count and acceptable null rates. Assign an owner for failed runs and source changes. Finally, write a stop condition: retire or revise the Task when its data no longer supports the original decision.

Distinguish audience growth from development activity

Track star and fork deltas beside pushed-at time, open issues, archive status, and default branch, but do not blend them into one unexplained score. A launch can produce rapid stars without sustained maintenance; a mature library may add few stars while shipping dependable releases. Use stable repository IDs so renames do not create false entrants. A useful weekly digest highlights acceleration, inactivity, archive transitions, and identity changes in separate sections. Analysts can then investigate causes using releases, commits, discussions, and project communication.