NEO: Code Changes
Shown as its 2019–2022 sample; the latest readings and full history are included with Plus.
Lines added and lines removed by the counted commits of each day.
Why use it. The size of the changes behind the commit count: large additions mark new code, large removals clean-ups. How to read it. Single large commits (imports, generated code, reorganisations) make spikes; read the trend over weeks.
Calculation. Each commit compared with its parent, as git counts lines. Dependency lock files and vendored third-party code (vendor, node_modules and third_party directories, and other projects' code copied in with git subtree) are left out; moved or renamed files count only the lines that changed; binary files have no lines. 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 Neo on GitHub, fetched every 30 minutes. neo-project/neo: the core of the protocol. History starts at the first counted commit, on 31 May 2015. Only public repositories are covered: work in private repositories, on other hosts or on branches not yet merged is not seen.