Their contributions, not ours.
Merged upstream contributions by verified node.uk Developer Network members, counted from the forge account each member authenticated with. Contributions by node.uk itself are not included.
That boundary matters. Our open source position says we do not currently sponsor the projects we host and are not significant code contributors to them. This page is a separate claim: the verified members of the Developer Network who do contribute upstream, counted per application we host.
By application
No verified Developer Network members have countable merged upstream contributions yet. The network is open — if you contribute to any of the applications we host, join with GitHub or GitLab and verified work will appear here. Until then we show an empty list rather than an aspiration.
Related
- Our open source position — what node.uk itself does and does not claim
- Developer Network — verified members and how engagements work
- Product pages carry a provenance block naming the upstream project and licence for each Hosting for X offer
Frequently asked questions
Does this page mean Node contributes code upstream?
No. Our open source position page states plainly that we are not significant code contributors today. This page counts merged contributions by independent Developer Network members, from the forge account each member authenticated with. The basis text on this page and in the API payload both say so.
What does a verified contributor badge mean here?
Only that a network member's GitHub or GitLab account has merged contributions in that application's upstream repository, checked against public forge data. It is our own designation. It does not mean the upstream project endorses the developer, or us.
Why is the list empty or small?
Because the bar is real: verified membership and merged upstream work. We would rather show nothing than invent a record. When the first verified members land, their apps appear here with active and past contributor counts.