This repository is a curated, version-controlled taxonomy of cryptocurrency and blockchain ecosystems and their associated GitHub repositories. It is the dataset behind Electric Capital's developer activity reports. The primary artifact is a large collection of timestamped migration files (a custom DSL using commands like `repadd`, `ecoadd`, `ecocon`) that incrementally build a graph mapping ecosystems to repositories with tags. The dataset spans over a decade (2014–2026) and includes hundreds of thousands of repository entries across dozens of ecosystems, from major chains (Ethereum, Bitcoin, Stellar) to niche projects and hackathon submissions. The repository also provides a Python CLI tool (`open-dev-data`) for validating migrations, exporting the taxonomy as JSON Lines or Parquet, downloading the full dataset with resumable transfers and integrity checks, and exploring it locally via DuckDB and an interactive TUI (Harlequin). The codebase is well-structured, with clean abstractions for the data model, timestamp handling, and shell-like command parsing. However, the dataset itself suffers from significant noise—many entries are student hackathon repos, boilerplate forks, or duplicate URLs—which dilutes its signal for research. The curation is manual and not automatically deduplicated. Despite this, the taxonomy and tooling are highly reusable for any domain needing a version-controlled, hierarchically categorized registry of external projects.
This repository generates static markdown pages ranking GitHub users by followers, public contributions, and total contributions for 138 countries. It uses a GitHub Action to fetch user data from the GitHub GraphQL API, caches it as JSON, and produces per-country markdown tables with social sharing buttons. A choropleth map visualization is also provided in the docs/ folder. The core data pipeline logic is not present in this repo; it relies on an external action (`gayanvoice/top-github-users-action`). The generated data contains many low-quality entries (spam, non-developer accounts, future timestamps), and the Node.js version used (14.17.0) is end-of-life. The repo is popular (4886 stars) but the actual data freshness and maintenance are questionable due to unrealistic timestamps and lack of visible validation logic.