KAS: Developer Commits
Kaspa Developer Commits was 0 commits on 9 Nov 2026 (latest daily value).
Commits each day in the public repositories of Kaspa that we mirror: new work by its developers, each change counted once.
Why use it. Steady commits show a project that is being built and maintained; a lasting fall can mean its developers have moved on. How to read it. Daily counts are noisy: compare weeks or months, or read the 30-day active developers. History shows work on the days it was written; since 19 October 2026 work counts on the day it lands, so a large merge makes a one-day spike, and commits written before then but merged later count when they land. Projects that squash each contribution into one commit show fewer commits for the same work, so counts compare best within one project over time.
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. Source: CryptoKeyhole's own mirrors of 1 public repository of Kaspa on GitHub, fetched every 30 minutes. kaspanet/rusty-kaspa: the reference node. History starts at the first counted commit, on 14 July 2022. Only public repositories are covered: work in private repositories, on other hosts or on branches not yet merged is not seen.