How often the XDC node software changes
0
XDPoSChain commits per week
GitHub REST API, weekly commit counts of XinFinOrg/XDPoSChain · updated 15 min ago
Weekly commit counts of XinFinOrg/XDPoSChain ↗ from GitHub's own statistics. Weeks run from Sunday to Saturday, UTC; the week in progress is left out so the last point is not a partial count.
The most active XDC repositories
| # | |||||||
|---|---|---|---|---|---|---|---|
| 1 | XinFinOrg/XDPoSChain ↗ | 60 | 22 days ago | 228 | ≥ 5 | v2.7.1 (4 Jun 2026) | 145 |
| 2 | XinFinOrg/Official-XinFinOrg ↗ | 5 | 20 hours ago | 31 | 1 | None | 7 |
| 3 | goplugin/datafeed_jobs ↗ | 0 | 84 days ago | 11 | 1 | None | 0 |
| 4 | XinFinOrg/XinFin-Node ↗ | 66 | 33 hours ago | 10 | 4 | 1.4.4 (14 May 2022) | 24 |
| 5 | PrimeNumbersLabs/primestaking-gitbook ↗ | 0 | 10 days ago | 9 | 2 | None | 0 |
| 6 | XinFinOrg/MasterNode-App ↗ | 1 | 33 days ago | 8 | 2 | None | 6 |
| 7 | PrimeNumbersLabs/primefi-gitbook ↗ | 0 | 12 days ago | 5 | 1 | None | 0 |
| 8 | XinFinOrg/XDC-CSC ↗ | 0 | 22 days ago | 3 | 2 | v0.3.0 (24 Apr 2025) | 6 |
| 9 | XinFinOrg/Docs ↗ | 2 | 28 days ago | 2 | 2 | None | 4 |
| 10 | PrimeNumbersLabs/intiero-liquidator-example ↗ | 0 | 82 days ago | 2 | 1 | None | 0 |
| 11 | PrimeNumbersLabs/primeport-gitbook ↗ | 0 | 20 days ago | 1 | 1 | None | 0 |
| 12 | XinFinOrg/Subnet-Deployment ↗ | 0 | 421 days ago | 0 | 0 | v2.1.0 (23 Sep 2025) | 1 |
| 13 | XinFinOrg/subnet-stats-service ↗ | 0 | 737 days ago | 0 | 0 | v0.1.11 (4 Oct 2024) | 2 |
| 14 | XinFinOrg/XDC-Relayer ↗ | 1 | 208 days ago | 0 | 0 | v0.3.3 (24 Apr 2026) | 1 |
| 15 | XinFinOrg/XIP ↗ | 0 | 90 days ago | — | — | None | 0 |
Repositories are public, not archived, pushed in the last year and not forks, except XinFinOrg/XDPoSChain, which GitHub marks as a fork of go-ethereum although it is the XDC node software. Owners: XinFinOrg, XDC-Community, PrimeNumbersLabs, goplugin. The 15 most recently pushed are read in detail. Commits are counted over full weeks. People are distinct authors among the latest 100 commits that fall in the last 90 days ("≥" when all 100 do). Open issues is the count GitHub reports for the repository and includes open pull requests. A dash means the repository has not been read in detail yet.
GitHub REST API (api.github.com), read from our server · updated 15 min ago
What this page measures
It counts changes to published source code. It does not rate the code, the team or the project, and it says nothing about price.
Where the repositories come from
The XDC documentation links to its source repository in the XinFinOrg organisation on GitHub, which also holds the node software, masternode tools and improvement proposals, and the footer of xdc.org links to the XDC-Community organisation. We also read the GitHub owner of every project in our projects directory whose own site or docs link to a repository. A repository is on the board when it is public, not archived, not a fork and has been pushed to in the last year. The one exception is XinFinOrg/XDPoSChain: GitHub marks it as a fork of go-ethereum, but it is the XDC node software, so it is always included.
What each column means
Last commit is the newest commit on the default branch. Commits, 12 weeks adds up GitHub's own weekly counts for the last 12 full weeks, Sunday to Saturday in UTC, without the week in progress (GitHub statistics API). People, 90 days is the number of different authors among the latest 100 commits that were made in the last 90 days; when all 100 commits fall in that period the figure is shown as a minimum, with "≥". Latest release is the newest published release that is not a draft or a pre-release (GitHub releases). Open issues is the count GitHub reports for the repository and includes open pull requests (GitHub repositories API).
How we read GitHub
Our server asks the public GitHub API once a day for each repository. No account, token or visitor data is involved, and nothing is read in your browser.
Schedule and limits
GitHub allows 60 unauthenticated requests per hour (GitHub rate limits). Our server never makes more than six requests in one run and about 36 an hour, reads each owner's repository list and each ranked repository once a day, and pauses for an hour if GitHub answers that a limit is reached. The first complete fill after a restart takes a few hours. The line under the table says when the data was last updated.
Statistics GitHub is still computing
GitHub builds weekly statistics on demand and answers "still computing" the first time (GitHub statistics API). A repository whose weekly count is not ready shows a dash for the commits column and is asked again 15 minutes later.
History
The chart is GitHub's own 52-week series, which GitHub keeps, so the history is there from the first day. Weeks run from Sunday to Saturday (UTC) and the week in progress is left out. GitHub caches the numbers, so the newest full week can lag by a few hours.
What GitHub activity does not tell you
More commits do not mean a better project, and fewer do not mean a worse one. We do not score, grade or rank repositories by quality.
Commits are not value
A commit can be a one-character fix, a merged pull request, an automated dependency update or a large feature. The count says how often the code changed, not how much each change matters.
A quiet repository can be finished
A stable library or a documentation repository may change rarely because it is complete. A repository with no push for a year drops out of the board rather than being labelled abandoned.
Private work and other branches
Only public repositories can be read, and the weekly counts are for the default branch. A team can work in private repositories or on branches that never reach this count. Some XDC projects keep their code elsewhere, and those are not covered.
A release is not a deployment
A new release means the maintainers published a version. It does not mean the XDC mainnet runs it: masternode operators upgrade on their own schedule. Upgrade announcements are in the XDC documentation and, for this site, in our developer guide.
Not advice
This page is not financial advice and not an audit. Read a project's code, audits and documentation yourself before you rely on it. See the safety center for how to check a project.
XDC GitHub FAQ
The XDC node software is in XinFinOrg/XDPoSChain, in the XinFinOrg organisation, which the XDC documentation links to. Community repositories are under XDC-Community. The board above lists the most active ones.
The node software, the masternode tools and the documentation are public repositories on GitHub. Each repository has its own licence, shown on its GitHub page, so check it before you reuse any code.
The chart shows the weekly commit count of the node software for the last 12, 26 or 52 weeks, and the board shows the last commit of each repository. Activity says how much code changes, not how good or safe it is.
The XDC node software. GitHub marks it as a fork of go-ethereum, which is why it is the one fork on the board; its name refers to XDPoS, the consensus mechanism of the XDC Network.
The board shows how many different people made commits in the last 90 days for each repository we read in detail. That counts commit authors in public repositories only and is not the size of any team.
The board lists the latest published release of each repository with its date, for example the newest tag of XDPoSChain. A release is a published version, not a statement that mainnet already runs it.
Our server reads GitHub once a day for each repository, spread over several runs, and the line under the table shows when. The statistics GitHub keeps can lag by a few hours.
Our server has not read it in detail yet, or GitHub is still computing its weekly statistics. Both fix themselves within a few hours.
The board only lists public repositories that are not archived, not forks and were pushed to in the last year, from the owners we read.
No. Activity is not an audit and not a measure of quality. Check audits, documentation and the contract addresses on XDCScan, and read our safety center.