ZAMA: Active Repositories
Shown as its Jan–Mar 2023 sample; the latest readings and full history are included with Plus.
How many of the mirrored repositories had at least one counted commit in the 30 days up to each day.
Why use it. Shows how broad the development is: one busy repository or work across the whole project. How to read it. The maximum is the 2 repositories we mirror for Zama; repositories that are finished or archived drop out.
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 2 public repositories of Zama on GitHub, fetched every 30 minutes. zama-ai/fhevm: fhEVM, the confidential smart-contract protocol. zama-ai/tfhe-rs: TFHE-rs, the homomorphic-encryption library the protocol is built on, maintained by Zama. History starts at the first counted commit, on 21 October 2022. Only public repositories are covered: work in private repositories, on other hosts or on branches not yet merged is not seen.