Corporate GitHub Activity
Most Active Corporations on GitHub, Q4 2023
Ranking companies with employees who, during Q4 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 52% 52% (n=298) of all SUSE engineers (n=5751) were active on GitHub. | 12% 12% (n=298) of all SUSE employees (n=2,4002) were active on GitHub. | 298 298 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Vercel | 50% 50% (n=77) of all Vercel engineers (n=1543) were active on GitHub. | 16% 16% (n=77) of all Vercel employees (n=4734) were active on GitHub. | 77 77 Vercel employees were active on GitHub. | 
| 3. Grafana Labs | 46% 46% (n=237) of all Grafana Labs engineers (n=5165) were active on GitHub. | 19% 19% (n=237) of all Grafana Labs employees (n=1,2176) were active on GitHub. | 237 237 Grafana Labs employees were active on GitHub. | 
| 4. Automattic | 41% 41% (n=357) of all Automattic engineers (n=8667) were active on GitHub. | 18% 18% (n=357) of all Automattic employees (n=1,9308) were active on GitHub. | 357 357 Automattic employees were active on GitHub. | 
| 5. Mozilla | 37% 37% (n=215) of all Mozilla engineers (n=5859) were active on GitHub. | 12% 12% (n=215) of all Mozilla employees (n=1,74510) were active on GitHub. | 215 215 Mozilla employees were active on GitHub. | 
| 6. HashiCorp | 34% 34% (n=229) of all HashiCorp engineers (n=68011) were active on GitHub. | 10% 10% (n=229) of all HashiCorp employees (n=2,20012) were active on GitHub. | 229 229 HashiCorp employees were active on GitHub. | 
| 7. Elastic | 33% 33% (n=340) of all Elastic engineers (n=1,02213) were active on GitHub. | 11% 11% (n=340) of all Elastic employees (n=3,18714) were active on GitHub. | 340 340 Elastic employees were active on GitHub. | 
| 8. The Guardian | 29% 29% (n=42) of all The Guardian engineers (n=14415) were active on GitHub. | 2% 2% (n=42) of all The Guardian employees (n=2,50116) were active on GitHub. | 42 42 The Guardian employees were active on GitHub. | 
| 9. Docker | 28% 28% (n=46) of all Docker engineers (n=16717) were active on GitHub. | 6% 6% (n=46) of all Docker employees (n=76718) were active on GitHub. | 46 46 Docker employees were active on GitHub. | 
| 10. JetBrains | 22% 22% (n=217) of all JetBrains engineers (n=97219) were active on GitHub. | 12% 12% (n=217) of all JetBrains employees (n=1,80020) were active on GitHub. | 217 217 JetBrains employees were active on GitHub. | 
| 11. WikiMedia Foundation | 22% 22% (n=44) of all WikiMedia Foundation engineers (n=20421) were active on GitHub. | 6% 6% (n=44) of all WikiMedia Foundation employees (n=70022) were active on GitHub. | 44 44 WikiMedia Foundation employees were active on GitHub. | 
| 12. WSO2 | 20% 20% (n=134) of all WSO2 engineers (n=66423) were active on GitHub. | 13% 13% (n=134) of all WSO2 employees (n=1,02024) were active on GitHub. | 134 134 WSO2 employees were active on GitHub. | 
| 13. DataDog | 15% 15% (n=350) of all DataDog engineers (n=2,40025) were active on GitHub. | 7% 7% (n=350) of all DataDog employees (n=5,20026) were active on GitHub. | 350 350 DataDog employees were active on GitHub. | 
| 14. Cloudflare | 13% 13% (n=110) of all Cloudflare engineers (n=83027) were active on GitHub. | 3% 3% (n=110) of all Cloudflare employees (n=3,68228) were active on GitHub. | 110 110 Cloudflare employees were active on GitHub. | 
| 15. MongoDB | 13% 13% (n=158) of all MongoDB engineers (n=1,22629) were active on GitHub. | 3% 3% (n=158) of all MongoDB employees (n=5,03730) were active on GitHub. | 158 158 MongoDB employees were active on GitHub. | 
| 16. Liferay | 12% 12% (n=56) of all Liferay engineers (n=46031) were active on GitHub. | 4% 4% (n=56) of all Liferay employees (n=1,37532) were active on GitHub. | 56 56 Liferay employees were active on GitHub. | 
| 17. New Relic | 10% 10% (n=90) of all New Relic engineers (n=88433) were active on GitHub. | 3% 3% (n=90) of all New Relic employees (n=2,58434) were active on GitHub. | 90 90 New Relic employees were active on GitHub. | 
| 18. ESRI | 7% 7% (n=155) of all ESRI engineers (n=2,07435) were active on GitHub. | 2% 2% (n=155) of all ESRI employees (n=6,44736) were active on GitHub. | 155 155 ESRI employees were active on GitHub. | 
| 19. Odoo | 7% 7% (n=47) of all Odoo engineers (n=64537) were active on GitHub. | 3% 3% (n=47) of all Odoo employees (n=1,70038) were active on GitHub. | 47 47 Odoo employees were active on GitHub. | 
| 20. Confluent | 7% 7% (n=73) of all Confluent engineers (n=1,03439) were active on GitHub. | 3% 3% (n=73) of all Confluent employees (n=2,74440) were active on GitHub. | 73 73 Confluent employees were active on GitHub. | 
| 21. Shopify | 7% 7% (n=250) of all Shopify engineers (n=3,56441) were active on GitHub. | 3% 3% (n=250) of all Shopify employees (n=8,30042) were active on GitHub. | 250 250 Shopify employees were active on GitHub. | 
| 22. Progress Software | 6% 6% (n=55) of all Progress Software engineers (n=88643) were active on GitHub. | 2% 2% (n=55) of all Progress Software employees (n=2,28444) were active on GitHub. | 55 55 Progress Software employees were active on GitHub. | 
| 23. Microsoft | 6% 6% (n=4,189) of all Microsoft engineers (n=72,00045) were active on GitHub. | 2% 2% (n=4,189) of all Microsoft employees (n=221,00046) were active on GitHub. | 4,189 4,189 Microsoft employees were active on GitHub. | 
| 24. Okta | 5% 5% (n=72) of all Okta engineers (n=1,57047) were active on GitHub. | 1% 1% (n=72) of all Okta employees (n=5,90848) were active on GitHub. | 72 72 Okta employees were active on GitHub. | 
| 25. Square, Inc. | 4% 4% (n=92) of all Square, Inc. engineers (n=2,06049) were active on GitHub. | 1% 1% (n=92) of all Square, Inc. employees (n=12,98550) were active on GitHub. | 92 92 Square, Inc. employees were active on GitHub. | 
| 26. ThoughtWorks | 4% 4% (n=152) of all ThoughtWorks engineers (n=3,76551) were active on GitHub. | 1% 1% (n=152) of all ThoughtWorks employees (n=10,50052) were active on GitHub. | 152 152 ThoughtWorks employees were active on GitHub. | 
| 27. Alibaba | 4% 4% (n=401) of all Alibaba engineers (n=10,02553) were active on GitHub. | 0% 0% (n=401) of all Alibaba employees (n=224,95554) were active on GitHub. | 401 401 Alibaba employees were active on GitHub. | 
| 28. Adobe | 4% 4% (n=406) of all Adobe engineers (n=10,24755) were active on GitHub. | 1% 1% (n=406) of all Adobe employees (n=29,94556) were active on GitHub. | 406 406 Adobe employees were active on GitHub. | 
| 29. Broadcom | 4% 4% (n=490) of all Broadcom engineers (n=12,60057) were active on GitHub. | 2% 2% (n=490) of all Broadcom employees (n=20,00058) were active on GitHub. | 490 490 Broadcom employees were active on GitHub. | 
| 30. Amazon | 4% 4% (n=1,592) of all Amazon engineers (n=43,60559) were active on GitHub. | 1% 1% (n=1,592) of all Amazon employees (n=125,34560) were active on GitHub. | 1,592 1,592 Amazon employees were active on GitHub. | 
| 31. Netflix | 4% 4% (n=86) of all Netflix engineers (n=2,40961) were active on GitHub. | 1% 1% (n=86) of all Netflix employees (n=13,00062) were active on GitHub. | 86 86 Netflix employees were active on GitHub. | 
| 32. Snowflake, Inc. | 4% 4% (n=71) of all Snowflake, Inc. engineers (n=2,00263) were active on GitHub. | 1% 1% (n=71) of all Snowflake, Inc. employees (n=7,00464) were active on GitHub. | 71 71 Snowflake, Inc. employees were active on GitHub. | 
| 33. Twilio | 3% 3% (n=88) of all Twilio engineers (n=2,56365) were active on GitHub. | 1% 1% (n=88) of all Twilio employees (n=5,86766) were active on GitHub. | 88 88 Twilio employees were active on GitHub. | 
| 34. Zendesk | 3% 3% (n=47) of all Zendesk engineers (n=1,48167) were active on GitHub. | 1% 1% (n=47) of all Zendesk employees (n=6,17968) were active on GitHub. | 47 47 Zendesk employees were active on GitHub. | 
| 35. Arm Ltd | 3% 3% (n=147) of all Arm Ltd engineers (n=4,75369) were active on GitHub. | 2% 2% (n=147) of all Arm Ltd employees (n=5,96370) were active on GitHub. | 147 147 Arm Ltd employees were active on GitHub. | 
| 36. Unity Technologies | 3% 3% (n=116) of all Unity Technologies engineers (n=3,84471) were active on GitHub. | 2% 2% (n=116) of all Unity Technologies employees (n=6,74872) were active on GitHub. | 116 116 Unity Technologies employees were active on GitHub. | 
| 37. Splunk | 3% 3% (n=70) of all Splunk engineers (n=2,38773) were active on GitHub. | 1% 1% (n=70) of all Splunk employees (n=8,00074) were active on GitHub. | 70 70 Splunk employees were active on GitHub. | 
| 38. Tencent | 3% 3% (n=385) of all Tencent engineers (n=13,64275) were active on GitHub. | 0% 0% (n=385) of all Tencent employees (n=105,41776) were active on GitHub. | 385 385 Tencent employees were active on GitHub. | 
| 39. CyberAgent | 3% 3% (n=46) of all CyberAgent engineers (n=1,66077) were active on GitHub. | 1% 1% (n=46) of all CyberAgent employees (n=7,25178) were active on GitHub. | 46 46 CyberAgent employees were active on GitHub. | 
| 40. WIX | 3% 3% (n=58) of all WIX engineers (n=2,30179) were active on GitHub. | 1% 1% (n=58) of all WIX employees (n=4,60080) were active on GitHub. | 58 58 WIX employees were active on GitHub. | 
| 41. Google | 3% 3% (n=1,899) of all Google engineers (n=75,57181) were active on GitHub. | 1% 1% (n=1,899) of all Google employees (n=182,50282) were active on GitHub. | 1,899 1,899 Google employees were active on GitHub. | 
| 42. Zalando DE | 2% 2% (n=41) of all Zalando DE engineers (n=1,72283) were active on GitHub. | 0% 0% (n=41) of all Zalando DE employees (n=15,79384) were active on GitHub. | 41 41 Zalando DE employees were active on GitHub. | 
| 43. Stripe | 2% 2% (n=70) of all Stripe engineers (n=2,95285) were active on GitHub. | 1% 1% (n=70) of all Stripe employees (n=8,40986) were active on GitHub. | 70 70 Stripe employees were active on GitHub. | 
| 44. BBC | 2% 2% (n=41) of all BBC engineers (n=1,82287) were active on GitHub. | 0% 0% (n=41) of all BBC employees (n=21,63188) were active on GitHub. | 41 41 BBC employees were active on GitHub. | 
| 45. Spotify | 2% 2% (n=92) of all Spotify engineers (n=4,71989) were active on GitHub. | 1% 1% (n=92) of all Spotify employees (n=9,12390) were active on GitHub. | 92 92 Spotify employees were active on GitHub. | 
| 46. NVIDIA | 2% 2% (n=424) of all NVIDIA engineers (n=22,20091) were active on GitHub. | 1% 1% (n=424) of all NVIDIA employees (n=29,60092) were active on GitHub. | 424 424 NVIDIA employees were active on GitHub. | 
| 47. Atlassian | 2% 2% (n=92) of all Atlassian engineers (n=5,36393) were active on GitHub. | 1% 1% (n=92) of all Atlassian employees (n=10,72694) were active on GitHub. | 92 92 Atlassian employees were active on GitHub. | 
| 48. Autodesk | 1% 1% (n=62) of all Autodesk engineers (n=4,20995) were active on GitHub. | 0% 0% (n=62) of all Autodesk employees (n=14,10096) were active on GitHub. | 62 62 Autodesk employees were active on GitHub. | 
| 49. Uber | 1% 1% (n=90) of all Uber engineers (n=6,42697) were active on GitHub. | 0% 0% (n=90) of all Uber employees (n=30,40098) were active on GitHub. | 90 90 Uber employees were active on GitHub. | 
| 50. Meta | 1% 1% (n=428) of all Meta engineers (n=31,33899) were active on GitHub. | 1% 1% (n=428) of all Meta employees (n=67,317100) were active on GitHub. | 428 428 Meta employees were active on GitHub. | 
| 51. SAP SE | 1% 1% (n=451) of all SAP SE engineers (n=33,377101) were active on GitHub. | 0% 0% (n=451) of all SAP SE employees (n=107,602102) were active on GitHub. | 451 451 SAP SE employees were active on GitHub. | 
| 52. Indeed | 1% 1% (n=38) of all Indeed engineers (n=2,813103) were active on GitHub. | 0% 0% (n=38) of all Indeed employees (n=18,038104) were active on GitHub. | 38 38 Indeed employees were active on GitHub. | 
| 53. AMD | 1% 1% (n=203) of all AMD engineers (n=15,606105) were active on GitHub. | 1% 1% (n=203) of all AMD employees (n=26,000106) were active on GitHub. | 203 203 AMD employees were active on GitHub. | 
| 54. Booking.com | 1% 1% (n=35) of all Booking.com engineers (n=2,844107) were active on GitHub. | 0% 0% (n=35) of all Booking.com employees (n=23,600108) were active on GitHub. | 35 35 Booking.com employees were active on GitHub. | 
| 55. Yandex | 1% 1% (n=158) of all Yandex engineers (n=13,003109) were active on GitHub. | 1% 1% (n=158) of all Yandex employees (n=26,361110) were active on GitHub. | 158 158 Yandex employees were active on GitHub. | 
| 56. Intel | 1% 1% (n=693) of all Intel engineers (n=57,201111) were active on GitHub. | 1% 1% (n=693) of all Intel employees (n=124,800112) were active on GitHub. | 693 693 Intel employees were active on GitHub. | 
| 57. Salesforce | 1% 1% (n=235) of all Salesforce engineers (n=19,483113) were active on GitHub. | 0% 0% (n=235) of all Salesforce employees (n=72,682114) were active on GitHub. | 235 235 Salesforce employees were active on GitHub. | 
| 58. Bloomberg | 1% 1% (n=86) of all Bloomberg engineers (n=7,328115) were active on GitHub. | 0% 0% (n=86) of all Bloomberg employees (n=25,923116) were active on GitHub. | 86 86 Bloomberg employees were active on GitHub. | 
| 59. Cisco Systems | 1% 1% (n=201) of all Cisco Systems engineers (n=23,772117) were active on GitHub. | 0% 0% (n=201) of all Cisco Systems employees (n=84,900118) were active on GitHub. | 201 201 Cisco Systems employees were active on GitHub. | 
| 60. PayPal | 1% 1% (n=60) of all PayPal engineers (n=8,658119) were active on GitHub. | 0% 0% (n=60) of all PayPal employees (n=27,200120) were active on GitHub. | 60 60 PayPal employees were active on GitHub. | 
| 61. Oracle | 1% 1% (n=282) of all Oracle engineers (n=47,000121) were active on GitHub. | 0% 0% (n=282) of all Oracle employees (n=164,000122) were active on GitHub. | 282 282 Oracle employees were active on GitHub. | 
| 62. Baidu | 1% 1% (n=124) of all Baidu engineers (n=21,800123) were active on GitHub. | 0% 0% (n=124) of all Baidu employees (n=39,800124) were active on GitHub. | 124 124 Baidu employees were active on GitHub. | 
| 63. Apple | 0% 0% (n=233) of all Apple engineers (n=46,752125) were active on GitHub. | 0% 0% (n=233) of all Apple employees (n=161,000126) were active on GitHub. | 233 233 Apple employees were active on GitHub. | 
| 64. NetEase | 0% 0% (n=73) of all NetEase engineers (n=14,855127) were active on GitHub. | 0% 0% (n=73) of all NetEase employees (n=29,128128) were active on GitHub. | 73 73 NetEase employees were active on GitHub. | 
| 65. EPAM Systems | 0% 0% (n=198) of all EPAM Systems engineers (n=47,350129) were active on GitHub. | 0% 0% (n=198) of all EPAM Systems employees (n=53,150130) were active on GitHub. | 198 198 EPAM Systems employees were active on GitHub. | 
| 66. Ericsson | 0% 0% (n=82) of all Ericsson engineers (n=28,219131) were active on GitHub. | 0% 0% (n=82) of all Ericsson employees (n=99,952132) were active on GitHub. | 82 82 Ericsson employees were active on GitHub. | 
| 67. Capital One | 0% 0% (n=36) of all Capital One engineers (n=12,962133) were active on GitHub. | 0% 0% (n=36) of all Capital One employees (n=51,987134) were active on GitHub. | 36 36 Capital One employees were active on GitHub. | 
| 68. Nokia | 0% 0% (n=60) of all Nokia engineers (n=26,395135) were active on GitHub. | 0% 0% (n=60) of all Nokia employees (n=86,689136) were active on GitHub. | 60 60 Nokia employees were active on GitHub. | 
| 69. Samsung | 0% 0% (n=132) of all Samsung engineers (n=83,729137) were active on GitHub. | 0% 0% (n=132) of all Samsung employees (n=267,860138) were active on GitHub. | 132 132 Samsung employees were active on GitHub. | 
| 70. Capgemini | 0% 0% (n=110) of all Capgemini engineers (n=69,796139) were active on GitHub. | 0% 0% (n=110) of all Capgemini employees (n=340,400140) were active on GitHub. | 110 110 Capgemini employees were active on GitHub. | 
| 71. Globant | 0% 0% (n=36) of all Globant engineers (n=24,968141) were active on GitHub. | 0% 0% (n=36) of all Globant employees (n=29,150142) were active on GitHub. | 36 36 Globant employees were active on GitHub. | 
| 72. Huawei | 0% 0% (n=125) of all Huawei engineers (n=114,000143) were active on GitHub. | 0% 0% (n=125) of all Huawei employees (n=207,000144) were active on GitHub. | 125 125 Huawei employees were active on GitHub. | 
| 73. IBM | (n=2,623) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=2,623) of all IBM employees (n=282,200145) were active on GitHub. | 2,623 2,623 IBM employees were active on GitHub. | 
| 74. ByteDance | (n=279) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=279) of all ByteDance employees (n=NaN0) were active on GitHub. | 279 279 ByteDance employees were active on GitHub. | 
| 75. Canonical | (n=178) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=178) of all Canonical employees (n=NaN0) were active on GitHub. | 178 178 Canonical employees were active on GitHub. | 
| 76. Accenture | (n=160) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=160) of all Accenture employees (n=733,000146) were active on GitHub. | 160 160 Accenture employees were active on GitHub. | 
| 77. Databricks | (n=95) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=95) of all Databricks employees (n=7,211147) were active on GitHub. | 95 95 Databricks employees were active on GitHub. | 
| 78. Sentry.io | (n=81) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 21% 21% (n=81) of all Sentry.io employees (n=378148) were active on GitHub. | 81 81 Sentry.io employees were active on GitHub. | 
| 79. Software Mansion | (n=75) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=75) of all Software Mansion employees (n=NaN0) were active on GitHub. | 75 75 Software Mansion employees were active on GitHub. | 
| 80. Posit | (n=62) of all Posit engineers (n=NaN0) were active on GitHub. | (n=62) of all Posit employees (n=NaN0) were active on GitHub. | 62 62 Posit employees were active on GitHub. | 
| 81. Yahoo! | (n=61) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=61) of all Yahoo! employees (n=NaN0) were active on GitHub. | 61 61 Yahoo! employees were active on GitHub. | 
| 82. Intuit | (n=59) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=59) of all Intuit employees (n=18,200149) were active on GitHub. | 59 59 Intuit employees were active on GitHub. | 
| 83. TU Delft | (n=54) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=54) of all TU Delft employees (n=NaN0) were active on GitHub. | 54 54 TU Delft employees were active on GitHub. | 
| 84. @SSWConsulting | (n=54) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=54) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 54 54 @SSWConsulting employees were active on GitHub. | 
| 85. PingCAP | (n=50) of all PingCAP engineers (n=NaN0) were active on GitHub. | 12% 12% (n=50) of all PingCAP employees (n=410150) were active on GitHub. | 50 50 PingCAP employees were active on GitHub. | 
| 86. @MathWorks | (n=50) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=50) of all @MathWorks employees (n=NaN0) were active on GitHub. | 50 50 @MathWorks employees were active on GitHub. | 
| 87. UCL | (n=48) of all UCL engineers (n=NaN0) were active on GitHub. | (n=48) of all UCL employees (n=NaN0) were active on GitHub. | 48 48 UCL employees were active on GitHub. | 
| 88. Qlik | (n=47) of all Qlik engineers (n=NaN0) were active on GitHub. | (n=47) of all Qlik employees (n=NaN0) were active on GitHub. | 47 47 Qlik employees were active on GitHub. | 
| 89. Snyk | (n=47) of all Snyk engineers (n=NaN0) were active on GitHub. | 4% 4% (n=47) of all Snyk employees (n=1,171151) were active on GitHub. | 47 47 Snyk employees were active on GitHub. | 
| 90. Tata Consultancy Services | (n=45) of all Tata Consultancy Services engineers (n=NaN0) were active on GitHub. | (n=45) of all Tata Consultancy Services employees (n=NaN0) were active on GitHub. | 45 45 Tata Consultancy Services employees were active on GitHub. | 
| 91. Epitech | (n=44) of all Epitech engineers (n=NaN0) were active on GitHub. | (n=44) of all Epitech employees (n=NaN0) were active on GitHub. | 44 44 Epitech employees were active on GitHub. | 
| 92. Orange S.A. | (n=43) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=43) of all Orange S.A. employees (n=127,109152) were active on GitHub. | 43 43 Orange S.A. employees were active on GitHub. | 
| 93. Kitware | (n=43) of all Kitware engineers (n=NaN0) were active on GitHub. | 25% 25% (n=43) of all Kitware employees (n=171153) were active on GitHub. | 43 43 Kitware employees were active on GitHub. | 
| 94. Dynatrace | (n=42) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=42) of all Dynatrace employees (n=NaN0) were active on GitHub. | 42 42 Dynatrace employees were active on GitHub. | 
| 95. Palo Alto Networks | (n=41) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=41) of all Palo Alto Networks employees (n=13,948154) were active on GitHub. | 41 41 Palo Alto Networks employees were active on GitHub. | 
| 96. Harness | (n=39) of all Harness engineers (n=NaN0) were active on GitHub. | (n=39) of all Harness employees (n=NaN0) were active on GitHub. | 39 39 Harness employees were active on GitHub. | 
| 97. MIPT | (n=38) of all MIPT engineers (n=NaN0) were active on GitHub. | (n=38) of all MIPT employees (n=NaN0) were active on GitHub. | 38 38 MIPT employees were active on GitHub. | 
| 98. R3 | (n=36) of all R3 engineers (n=NaN0) were active on GitHub. | (n=36) of all R3 employees (n=NaN0) were active on GitHub. | 36 36 R3 employees were active on GitHub. | 
| 99. NTNU | (n=35) of all NTNU engineers (n=NaN0) were active on GitHub. | (n=35) of all NTNU employees (n=NaN0) were active on GitHub. | 35 35 NTNU employees were active on GitHub. | 
| 100. Ant Group | (n=35) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=35) of all Ant Group employees (n=NaN0) were active on GitHub. | 35 35 Ant Group employees were active on GitHub. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: links.imagerelay.com (page 10)
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved December 2023)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 13)
- Elastic engineer count: linkedin.com (retrieved Dec 2023)
- Elastic employee count: sec.gov (page 15)
- The Guardian engineer count: linkedin.com (retrieved Dec 2023)
- The Guardian employee count: linkedin.com (retrieved Dec 2023)
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- WikiMedia Foundation engineer count: linkedin.com
- WikiMedia Foundation employee count: wikimediafoundation.org
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- DataDog engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 11)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- MongoDB engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 9)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- New Relic engineer count: linkedin.com (Retrieved December 2023)
- New Relic employee count: linkedin.com (Retrieved December 2023)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- Shopify engineer count: linkedin.com (retrieved Dec 2023)
- Shopify employee count: s27.q4cdn.com (page 22)
- Progress Software engineer count: sec.gov (page 7, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 7)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 14)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 20)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Interim Report, page 15)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 18)
- Broadcom engineer count: sec.gov (page 11, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 11)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 17)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Tencent engineer count: linkedin.com (retrieved Dec 2023)
- Tencent employee count: static.tencent.com (page 56)
- CyberAgent engineer count: cyberagent.co.jp (page 8)
- CyberAgent employee count: cyberagent.co.jp (page 8)
- WIX engineer count: sec.gov (page 89, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 149)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 10)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- BBC engineer count: linkedin.com
- BBC employee count: bbc.co.uk (page 59)
- Spotify engineer count: sec.gov (page 68, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 68)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Atlassian engineer count: sec.gov (page 9, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 12)
- Autodesk engineer count: linkedin.com (retrieved Dec 2023)
- Autodesk employee count: sec.gov (page 13)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 60)
- SAP SE engineer count: sec.gov (page F-23, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 102)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 12)
- Booking.com engineer count: linkedin.com
- Booking.com employee count: sec.gov (page 6)
- Yandex engineer count: sec.gov (page 54, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 54)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- Salesforce engineer count: linkedin.com (retrieved Dec 2023)
- Salesforce employee count: sec.gov (page 10)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Cisco Systems engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 10)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- Baidu engineer count: sec.gov (page 196, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 196)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- NetEase engineer count: sec.gov (page 156, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 156)
- EPAM Systems engineer count: sec.gov (page 5, referred to as 'delivery professionals')
- EPAM Systems employee count: sec.gov (page 5)
- Ericsson engineer count: sec.gov (page 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- Capital One engineer count: linkedin.com
- Capital One employee count: sec.gov (page 18)
- Nokia engineer count: linkedin.com (retrieved Dec 2023)
- Nokia employee count: sec.gov (page 105)
- Samsung engineer count: samsung.com (page 58, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 58)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 4)
- Globant engineer count: sec.gov (page 79, referred to as employees in 'technology')
- Globant employee count: sec.gov (page 78)
- Huawei engineer count: www-file.huawei.com (page 67, referred to as employees in 'R&D')
- Huawei employee count: www-file.huawei.com (page 1)
- IBM employee count: sec.gov (page 16)
- Accenture employee count: sec.gov (page 25)
- Databricks employee count: linkedin.com
- Sentry.io employee count: linkedin.com
- Intuit employee count: sec.gov (page 12)
- PingCAP employee count: linkedin.com
- Snyk employee count: linkedin.com
- Orange S.A. employee count: gallery.orange.com (page 58)
- Kitware employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)