How Pulse counts
Every number on Pulse comes from public GitHub activity. This page says what is counted, what is left out and where the numbers can mislead.
Where the numbers come from
The public activity of the organisations and projects Pulse follows, read from GitHub: pushes, pull requests, issues, reviews, comments, releases, new repositories, stars and forks. It is not on-chain data. GitHub lists events a few minutes late, and a private repository shows nothing.
What an update is
One thing someone did on GitHub: a push, a pull request opened or merged, an issue, a review, a comment, a release. A push is one update, and its commits are counted apart as commits. A merged pull request is credited to its author, unless the author is a bot or an AI account: then to whoever merged it. A star or a fork also counts as an update, and whoever gave it as a person.
The time windows
Day is the last 24 hours, week the last 7 days and month the last 30 days, always counted back from now. The current month in a chart is still counting. People and projects are counted once in each window.
Rankings and medals
Medals are for volume (most updates, commits, pushes) and for kinds of work (most reviews, most pull requests accepted). Medals and top lists count at most 10 updates per person, project and hour, and never count opening a branch, so one script cannot take a medal. The lists on a project card and the tools that answer questions count every update, so their numbers can be higher.
Bots and agents
Accounts marked as bots on GitHub (dependabot, github-actions and the like) and branches that agents open are shown in grey and never ranked. Accounts that say they are an AI in their own bio have a category of their own, marked AI: out of the people counts and the medals, listed apart. Pulse cannot tell who is behind a normal account, so an agent that works through one is counted as that account.
Who builds on what
The page of who builds on what reads the package.json (or the Cargo.toml for Rust) at the root of each public project Pulse follows, about twice a day, and says which ones use CCC, Lumos, Spore SDK or ckb-std. It counts a project that depends on a library, not how much it uses it, and it misses a dependency kept in a sub-folder.
Which projects
Organisations and people with public CKB work, found by topics, names and dependencies such as CCC, Spore and ckb-std, plus the ones suggested on the page. An owner with no human activity for 30 days leaves the page and comes back with its next update.
Our own work
LusoCryptoLabs builds Pulse and also builds on CKB. Its work is counted in the totals, but it is not ranked and wins no medals: it is listed apart, with the mark Operator.
What the numbers do not say
Activity is not value: a large change and a typo fix are one update each. Work outside GitHub (forum, translation, audits, moderation) is not seen. History before today covers only the projects Pulse follows now.
Privacy
Something looks wrong
Open an issue with the page and the number you expected. Corrections are welcome.