Developer activity

GitHub activity snapshots per coin: commits, contributors, issues, stars, forks. One row per repo per week.

3,800+repo snapshots

One row per repository per week. commits_last_4_weeks can be 0 on a repo with 38 contributors — detecting the dormant ones is the point.

What's in a record

Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.

id
repo_url
repo_name
commits_last_4_weeks
contributors_count
open_issues
stars
forks
date

{
  "id": 3905,
  "repo_url": "https://github.com/Near-One/rainbow-bridge",
  "repo_name": "Near-One/rainbow-bridge",
  "commits_last_4_weeks": 0,
  "contributors_count": 38,
  "open_issues": 133,
  "stars": 328,
  "forks": 100,
  "date": "2026-09-15"
}

Get it

A curl that runs against the live API right now, plus the MCP tool names for the same data.

curl https://api.alphaday.com/coins/developer-activity/?limit=1

MCP tools

get_developer_activityget_developer_activity_detail

What it's for

Three concrete questions this capability answers that a general crypto API does not.

A 'is this project still being built' check that does not depend on Twitter announcements. Sort by commits_last_4_weeks ascending and the dormant repos surface themselves — the example record above carries 38 contributors and 0 commits in the last four weeks.
A comparative snapshot for a research brief: every coin gets the same nine fields, so a side-by-side over a watchlist is a single shape to render.
Projecting an open-issue backlog rather than scraping the GitHub API repo by repo: open_issues is the live count from each snapshot.

Known limits

Required, not optional. Coverage gaps, staleness and parameter traps that were observed by running the curl above against the live server on 2026-09-18.

There is no working managed filter.

Verified corpus-wide on 18 Sep 2026: ?managed=true returns the full 3,822 records, ?managed=false returns 0, ?managed=banana (junk value) returns the full 3,822. An invalid value returns the unfiltered corpus, so a working-looking boolean filter is indistinguishable from no filter at all. Filter client-side on repo_name or contributors_count instead.

Zero commits does not mean zero activity.

A repo with 38 contributors can carry commits_last_4_weeks: 0 — pull requests, reviews and issue triage are not counted. Treat 0 as 'no merges in the window', not 'the repo is dead', and look at contributors_count alongside.

One snapshot per repo per week, not per push.

Granularity is weekly. The date is the snapshot date, not the most recent commit. Real-time activity requires the GitHub API directly.

Figures and payloads verified against the live API on 2026-09-18. The API needs no key and no signup — see the full endpoint reference and the MCP server.

All 22 capabilities Cookbook: worked use cases

The crypto data layer for humans, apps, and AI agents.

Product

Launch app Dashboards API & MCP Docs Pulse Recipes

Company

Blog Contact Give Feedback Terms of Use Privacy Policy

Crypto 101

What is Bitcoin?What Is Ethereum?What is Wrapped Crypto?What is Arbitrum?What is zkSync?

Learn

Making Money with Cryptocurrency How to Build a Cryptocurrency Dashboard What Is Crypto Halving: A Bitcoin Story How To Set Up Ethereum Wallet How to Read Crypto Charts Crypto Asset Management Guide Staking vs. Liquidity Mining (Yield Farming)