EIGEN: Active Developers by Repository
Shown as its Apr–Jun 2023 sample; the latest readings and full history are included with Plus.
Distinct developers with at least one counted commit in each repository in the 30 days up to each day.
Why use it. Shows where the project's developers work. How to read it. A developer working in several repositories counts in each, so the lines add up to more than the asset's active developers.
Calculation. Non-merge commits on each repository's default branch (and the branches named below). The history found when we began mirroring a repository (19 October 2026 for every current one) is dated by each commit's author timestamp in UTC: when the change was written, which rebases, cherry-picks and copies into other repositories keep. Since then a new commit is dated when it reached the branch: the time of the merge that brought it in, or its own time when added directly, held between our previous fetch and the fetch that found it, so a day already observed is never revised. A change counts once for the asset: copies in several of its repositories (forks, mirrors, cherry-picks, rewritten histories) are recognised by the same commit or the same author at the same second and count on the earliest date. Commits by automation accounts are left out: GitHub Apps (names ending in "[bot]"), known accounts such as Dependabot, Renovate and GitHub Actions, and names or GitHub accounts that contain the word "bot" or end in "Bot". The open day is partial; a closed day is final once our next fetch has run. Developers are told apart by a keyed hash of their e-mail address as the repository's .mailmap resolves it (GitHub's private addresses reduced to the account); no name or address is stored or published. A person using several addresses counts more than once, and people sharing one address count once. Source: CryptoKeyhole's own mirrors of 2 public repositories of EigenCloud on GitHub, fetched every 30 minutes. Layr-Labs/eigenlayer-contracts: EigenLayer, the restaking protocol contracts. Layr-Labs/eigenda: EigenDA, the data-availability service built on EigenLayer. History starts at the first counted commit, on 27 March 2023. Only public repositories are covered: work in private repositories, on other hosts or on branches not yet merged is not seen.