Corporate GitHub Activity
Most Active Corporations on GitHub, 05 2023
Ranking companies with employees who, during 05 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 39% 39% (n=224) of all SUSE engineers (n=5751) were active on GitHub. | 9% 9% (n=224) of all SUSE employees (n=2,4002) were active on GitHub. | 224 224 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Grafana Labs | 38% 38% (n=194) of all Grafana Labs engineers (n=5163) were active on GitHub. | 16% 16% (n=194) of all Grafana Labs employees (n=1,2174) were active on GitHub. | 194 194 Grafana Labs employees were active on GitHub. | 
| 3. Automattic | 33% 33% (n=284) of all Automattic engineers (n=8665) were active on GitHub. | 15% 15% (n=284) of all Automattic employees (n=1,9306) were active on GitHub. | 284 284 Automattic employees were active on GitHub. | 
| 4. Mozilla | 27% 27% (n=158) of all Mozilla engineers (n=5857) were active on GitHub. | 9% 9% (n=158) of all Mozilla employees (n=1,7458) were active on GitHub. | 158 158 Mozilla employees were active on GitHub. | 
| 5. HashiCorp | 26% 26% (n=180) of all HashiCorp engineers (n=6809) were active on GitHub. | 8% 8% (n=180) of all HashiCorp employees (n=2,20010) were active on GitHub. | 180 180 HashiCorp employees were active on GitHub. | 
| 6. Elastic | 25% 25% (n=257) of all Elastic engineers (n=1,02211) were active on GitHub. | 8% 8% (n=257) of all Elastic employees (n=3,18712) were active on GitHub. | 257 257 Elastic employees were active on GitHub. | 
| 7. The Guardian | 22% 22% (n=31) of all The Guardian engineers (n=14413) were active on GitHub. | 1% 1% (n=31) of all The Guardian employees (n=2,50114) were active on GitHub. | 31 31 The Guardian employees were active on GitHub. | 
| 8. Odoo | 19% 19% (n=122) of all Odoo engineers (n=64515) were active on GitHub. | 7% 7% (n=122) of all Odoo employees (n=1,70016) were active on GitHub. | 122 122 Odoo employees were active on GitHub. | 
| 9. Docker | 19% 19% (n=31) of all Docker engineers (n=16717) were active on GitHub. | 4% 4% (n=31) of all Docker employees (n=76718) were active on GitHub. | 31 31 Docker employees were active on GitHub. | 
| 10. Vercel | 17% 17% (n=26) of all Vercel engineers (n=15419) were active on GitHub. | 5% 5% (n=26) of all Vercel employees (n=47320) were active on GitHub. | 26 26 Vercel employees were active on GitHub. | 
| 11. JetBrains | 16% 16% (n=153) of all JetBrains engineers (n=97221) were active on GitHub. | 9% 9% (n=153) of all JetBrains employees (n=1,80022) were active on GitHub. | 153 153 JetBrains employees were active on GitHub. | 
| 12. WikiMedia Foundation | 12% 12% (n=24) of all WikiMedia Foundation engineers (n=20423) were active on GitHub. | 3% 3% (n=24) of all WikiMedia Foundation employees (n=70024) were active on GitHub. | 24 24 WikiMedia Foundation employees were active on GitHub. | 
| 13. MongoDB | 10% 10% (n=119) of all MongoDB engineers (n=1,22625) were active on GitHub. | 2% 2% (n=119) of all MongoDB employees (n=5,03726) were active on GitHub. | 119 119 MongoDB employees were active on GitHub. | 
| 14. DataDog | 9% 9% (n=222) of all DataDog engineers (n=2,40027) were active on GitHub. | 4% 4% (n=222) of all DataDog employees (n=5,20028) were active on GitHub. | 222 222 DataDog employees were active on GitHub. | 
| 15. Cloudflare | 9% 9% (n=73) of all Cloudflare engineers (n=83029) were active on GitHub. | 2% 2% (n=73) of all Cloudflare employees (n=3,68230) were active on GitHub. | 73 73 Cloudflare employees were active on GitHub. | 
| 16. WSO2 | 9% 9% (n=58) of all WSO2 engineers (n=66431) were active on GitHub. | 6% 6% (n=58) of all WSO2 employees (n=1,02032) were active on GitHub. | 58 58 WSO2 employees were active on GitHub. | 
| 17. New Relic | 7% 7% (n=65) of all New Relic engineers (n=88433) were active on GitHub. | 3% 3% (n=65) of all New Relic employees (n=2,58434) were active on GitHub. | 65 65 New Relic employees were active on GitHub. | 
| 18. Liferay | 6% 6% (n=29) of all Liferay engineers (n=46035) were active on GitHub. | 2% 2% (n=29) of all Liferay employees (n=1,37536) were active on GitHub. | 29 29 Liferay employees were active on GitHub. | 
| 19. Twitter | 6% 6% (n=31) of all Twitter engineers (n=54937) were active on GitHub. | 1% 1% (n=31) of all Twitter employees (n=2,14038) were active on GitHub. | 31 31 Twitter employees were active on GitHub. | 
| 20. Shopify | 5% 5% (n=165) of all Shopify engineers (n=3,56439) were active on GitHub. | 2% 2% (n=165) of all Shopify employees (n=8,30040) were active on GitHub. | 165 165 Shopify employees were active on GitHub. | 
| 21. Confluent | 4% 4% (n=44) of all Confluent engineers (n=1,03441) were active on GitHub. | 2% 2% (n=44) of all Confluent employees (n=2,74442) were active on GitHub. | 44 44 Confluent employees were active on GitHub. | 
| 22. Microsoft | 4% 4% (n=2,812) of all Microsoft engineers (n=72,00043) were active on GitHub. | 1% 1% (n=2,812) of all Microsoft employees (n=221,00044) were active on GitHub. | 2,812 2,812 Microsoft employees were active on GitHub. | 
| 23. GitLab | 3% 3% (n=22) of all GitLab engineers (n=64145) were active on GitHub. | 1% 1% (n=22) of all GitLab employees (n=2,13046) were active on GitHub. | 22 22 GitLab employees were active on GitHub. | 
| 24. Progress Software | 3% 3% (n=30) of all Progress Software engineers (n=88647) were active on GitHub. | 1% 1% (n=30) of all Progress Software employees (n=2,28448) were active on GitHub. | 30 30 Progress Software employees were active on GitHub. | 
| 25. Square, Inc. | 3% 3% (n=69) of all Square, Inc. engineers (n=2,06049) were active on GitHub. | 1% 1% (n=69) of all Square, Inc. employees (n=12,98550) were active on GitHub. | 69 69 Square, Inc. employees were active on GitHub. | 
| 26. Alibaba | 3% 3% (n=286) of all Alibaba engineers (n=10,02551) were active on GitHub. | 0% 0% (n=286) of all Alibaba employees (n=224,95552) were active on GitHub. | 286 286 Alibaba employees were active on GitHub. | 
| 27. ESRI | 3% 3% (n=59) of all ESRI engineers (n=2,07453) were active on GitHub. | 1% 1% (n=59) of all ESRI employees (n=6,44754) were active on GitHub. | 59 59 ESRI employees were active on GitHub. | 
| 28. Snowflake, Inc. | 3% 3% (n=55) of all Snowflake, Inc. engineers (n=2,00255) were active on GitHub. | 1% 1% (n=55) of all Snowflake, Inc. employees (n=7,00456) were active on GitHub. | 55 55 Snowflake, Inc. employees were active on GitHub. | 
| 29. VMWare | 3% 3% (n=335) of all VMWare engineers (n=12,94457) were active on GitHub. | 1% 1% (n=335) of all VMWare employees (n=38,30058) were active on GitHub. | 335 335 VMWare employees were active on GitHub. | 
| 30. Okta | 2% 2% (n=39) of all Okta engineers (n=1,57059) were active on GitHub. | 1% 1% (n=39) of all Okta employees (n=5,90860) were active on GitHub. | 39 39 Okta employees were active on GitHub. | 
| 31. ThoughtWorks | 2% 2% (n=86) of all ThoughtWorks engineers (n=3,76561) were active on GitHub. | 1% 1% (n=86) of all ThoughtWorks employees (n=10,50062) were active on GitHub. | 86 86 ThoughtWorks employees were active on GitHub. | 
| 32. Amazon | 2% 2% (n=954) of all Amazon engineers (n=43,60563) were active on GitHub. | 1% 1% (n=954) of all Amazon employees (n=125,34564) were active on GitHub. | 954 954 Amazon employees were active on GitHub. | 
| 33. Netflix | 2% 2% (n=49) of all Netflix engineers (n=2,40965) were active on GitHub. | 0% 0% (n=49) of all Netflix employees (n=13,00066) were active on GitHub. | 49 49 Netflix employees were active on GitHub. | 
| 34. Unity Technologies | 2% 2% (n=77) of all Unity Technologies engineers (n=3,84467) were active on GitHub. | 1% 1% (n=77) of all Unity Technologies employees (n=6,74868) were active on GitHub. | 77 77 Unity Technologies employees were active on GitHub. | 
| 35. Adobe | 2% 2% (n=205) of all Adobe engineers (n=10,24769) were active on GitHub. | 1% 1% (n=205) of all Adobe employees (n=29,94570) were active on GitHub. | 205 205 Adobe employees were active on GitHub. | 
| 36. Twilio | 2% 2% (n=50) of all Twilio engineers (n=2,56371) were active on GitHub. | 1% 1% (n=50) of all Twilio employees (n=5,86772) were active on GitHub. | 50 50 Twilio employees were active on GitHub. | 
| 37. Arm Ltd | 2% 2% (n=89) of all Arm Ltd engineers (n=4,75373) were active on GitHub. | 1% 1% (n=89) of all Arm Ltd employees (n=5,96374) were active on GitHub. | 89 89 Arm Ltd employees were active on GitHub. | 
| 38. Zendesk | 2% 2% (n=26) of all Zendesk engineers (n=1,48175) were active on GitHub. | 0% 0% (n=26) of all Zendesk employees (n=6,17976) were active on GitHub. | 26 26 Zendesk employees were active on GitHub. | 
| 39. Stripe | 2% 2% (n=51) of all Stripe engineers (n=2,95277) were active on GitHub. | 1% 1% (n=51) of all Stripe employees (n=8,40978) were active on GitHub. | 51 51 Stripe employees were active on GitHub. | 
| 40. Google | 2% 2% (n=1,300) of all Google engineers (n=75,57179) were active on GitHub. | 1% 1% (n=1,300) of all Google employees (n=182,50280) were active on GitHub. | 1,300 1,300 Google employees were active on GitHub. | 
| 41. WIX | 2% 2% (n=38) of all WIX engineers (n=2,30181) were active on GitHub. | 1% 1% (n=38) of all WIX employees (n=4,60082) were active on GitHub. | 38 38 WIX employees were active on GitHub. | 
| 42. Tencent | 2% 2% (n=222) of all Tencent engineers (n=13,64283) were active on GitHub. | 0% 0% (n=222) of all Tencent employees (n=105,41784) were active on GitHub. | 222 222 Tencent employees were active on GitHub. | 
| 43. Zalando DE | 2% 2% (n=28) of all Zalando DE engineers (n=1,72285) were active on GitHub. | 0% 0% (n=28) of all Zalando DE employees (n=15,79386) were active on GitHub. | 28 28 Zalando DE employees were active on GitHub. | 
| 44. NVIDIA | 1% 1% (n=257) of all NVIDIA engineers (n=22,20087) were active on GitHub. | 1% 1% (n=257) of all NVIDIA employees (n=29,60088) were active on GitHub. | 257 257 NVIDIA employees were active on GitHub. | 
| 45. Splunk | 1% 1% (n=27) of all Splunk engineers (n=2,38789) were active on GitHub. | 0% 0% (n=27) of all Splunk employees (n=8,00090) were active on GitHub. | 27 27 Splunk employees were active on GitHub. | 
| 46. Spotify | 1% 1% (n=48) of all Spotify engineers (n=4,71991) were active on GitHub. | 1% 1% (n=48) of all Spotify employees (n=9,12392) were active on GitHub. | 48 48 Spotify employees were active on GitHub. | 
| 47. Indeed | 1% 1% (n=26) of all Indeed engineers (n=2,81393) were active on GitHub. | 0% 0% (n=26) of all Indeed employees (n=18,03894) were active on GitHub. | 26 26 Indeed employees were active on GitHub. | 
| 48. Atlassian | 1% 1% (n=46) of all Atlassian engineers (n=5,36395) were active on GitHub. | 0% 0% (n=46) of all Atlassian employees (n=10,72696) were active on GitHub. | 46 46 Atlassian employees were active on GitHub. | 
| 49. Autodesk | 1% 1% (n=34) of all Autodesk engineers (n=4,20997) were active on GitHub. | 0% 0% (n=34) of all Autodesk employees (n=14,10098) were active on GitHub. | 34 34 Autodesk employees were active on GitHub. | 
| 50. Meta | 1% 1% (n=250) of all Meta engineers (n=31,33899) were active on GitHub. | 0% 0% (n=250) of all Meta employees (n=67,317100) were active on GitHub. | 250 250 Meta employees were active on GitHub. | 
| 51. Intel | 1% 1% (n=439) of all Intel engineers (n=57,201101) were active on GitHub. | 0% 0% (n=439) of all Intel employees (n=124,800102) were active on GitHub. | 439 439 Intel employees were active on GitHub. | 
| 52. SAP SE | 1% 1% (n=256) of all SAP SE engineers (n=33,377103) were active on GitHub. | 0% 0% (n=256) of all SAP SE employees (n=107,602104) were active on GitHub. | 256 256 SAP SE employees were active on GitHub. | 
| 53. Uber | 1% 1% (n=49) of all Uber engineers (n=6,426105) were active on GitHub. | 0% 0% (n=49) of all Uber employees (n=30,400106) were active on GitHub. | 49 49 Uber employees were active on GitHub. | 
| 54. Salesforce | 1% 1% (n=140) of all Salesforce engineers (n=19,483107) were active on GitHub. | 0% 0% (n=140) of all Salesforce employees (n=72,682108) were active on GitHub. | 140 140 Salesforce employees were active on GitHub. | 
| 55. AMD | 1% 1% (n=101) of all AMD engineers (n=15,606109) were active on GitHub. | 0% 0% (n=101) of all AMD employees (n=26,000110) were active on GitHub. | 101 101 AMD employees were active on GitHub. | 
| 56. Yandex | 1% 1% (n=70) of all Yandex engineers (n=13,003111) were active on GitHub. | 0% 0% (n=70) of all Yandex employees (n=26,361112) were active on GitHub. | 70 70 Yandex employees were active on GitHub. | 
| 57. Bloomberg | 1% 1% (n=38) of all Bloomberg engineers (n=7,328113) were active on GitHub. | 0% 0% (n=38) of all Bloomberg employees (n=25,923114) were active on GitHub. | 38 38 Bloomberg employees were active on GitHub. | 
| 58. Cisco Systems | 0% 0% (n=103) of all Cisco Systems engineers (n=23,772115) were active on GitHub. | 0% 0% (n=103) of all Cisco Systems employees (n=84,900116) were active on GitHub. | 103 103 Cisco Systems employees were active on GitHub. | 
| 59. Baidu | 0% 0% (n=92) of all Baidu engineers (n=21,800117) were active on GitHub. | 0% 0% (n=92) of all Baidu employees (n=39,800118) were active on GitHub. | 92 92 Baidu employees were active on GitHub. | 
| 60. NetEase | 0% 0% (n=53) of all NetEase engineers (n=14,855119) were active on GitHub. | 0% 0% (n=53) of all NetEase employees (n=29,128120) were active on GitHub. | 53 53 NetEase employees were active on GitHub. | 
| 61. PayPal | 0% 0% (n=29) of all PayPal engineers (n=8,658121) were active on GitHub. | 0% 0% (n=29) of all PayPal employees (n=27,200122) were active on GitHub. | 29 29 PayPal employees were active on GitHub. | 
| 62. Apple | 0% 0% (n=151) of all Apple engineers (n=46,752123) were active on GitHub. | 0% 0% (n=151) of all Apple employees (n=161,000124) were active on GitHub. | 151 151 Apple employees were active on GitHub. | 
| 63. Oracle | 0% 0% (n=150) of all Oracle engineers (n=47,000125) were active on GitHub. | 0% 0% (n=150) of all Oracle employees (n=164,000126) were active on GitHub. | 150 150 Oracle employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=83) of all EPAM Systems engineers (n=47,350127) were active on GitHub. | 0% 0% (n=83) of all EPAM Systems employees (n=53,150128) were active on GitHub. | 83 83 EPAM Systems employees were active on GitHub. | 
| 65. Nokia | 0% 0% (n=30) of all Nokia engineers (n=26,395129) were active on GitHub. | 0% 0% (n=30) of all Nokia employees (n=86,689130) were active on GitHub. | 30 30 Nokia employees were active on GitHub. | 
| 66. Ericsson | 0% 0% (n=29) of all Ericsson engineers (n=28,219131) were active on GitHub. | 0% 0% (n=29) of all Ericsson employees (n=99,952132) were active on GitHub. | 29 29 Ericsson employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=67) of all Samsung engineers (n=83,729133) were active on GitHub. | 0% 0% (n=67) of all Samsung employees (n=267,860134) were active on GitHub. | 67 67 Samsung employees were active on GitHub. | 
| 68. Capgemini | 0% 0% (n=48) of all Capgemini engineers (n=69,796135) were active on GitHub. | 0% 0% (n=48) of all Capgemini employees (n=340,400136) were active on GitHub. | 48 48 Capgemini employees were active on GitHub. | 
| 69. Huawei | 0% 0% (n=66) of all Huawei engineers (n=114,000137) were active on GitHub. | 0% 0% (n=66) of all Huawei employees (n=207,000138) were active on GitHub. | 66 66 Huawei employees were active on GitHub. | 
| 70. IBM | (n=1,625) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,625) of all IBM employees (n=282,200139) were active on GitHub. | 1,625 1,625 IBM employees were active on GitHub. | 
| 71. ByteDance | (n=121) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=121) of all ByteDance employees (n=NaN0) were active on GitHub. | 121 121 ByteDance employees were active on GitHub. | 
| 72. Canonical | (n=106) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=106) of all Canonical employees (n=NaN0) were active on GitHub. | 106 106 Canonical employees were active on GitHub. | 
| 73. Accenture | (n=77) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=77) of all Accenture employees (n=733,000140) were active on GitHub. | 77 77 Accenture employees were active on GitHub. | 
| 74. Databricks | (n=66) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=66) of all Databricks employees (n=7,211141) were active on GitHub. | 66 66 Databricks employees were active on GitHub. | 
| 75. Sentry.io | (n=61) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 16% 16% (n=61) of all Sentry.io employees (n=378142) were active on GitHub. | 61 61 Sentry.io employees were active on GitHub. | 
| 76. Software Mansion | (n=52) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=52) of all Software Mansion employees (n=NaN0) were active on GitHub. | 52 52 Software Mansion employees were active on GitHub. | 
| 77. Yahoo! | (n=45) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=45) of all Yahoo! employees (n=NaN0) were active on GitHub. | 45 45 Yahoo! employees were active on GitHub. | 
| 78. Qlik | (n=41) of all Qlik engineers (n=NaN0) were active on GitHub. | (n=41) of all Qlik employees (n=NaN0) were active on GitHub. | 41 41 Qlik employees were active on GitHub. | 
| 79. 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. | 
| 80. Harness | (n=33) of all Harness engineers (n=NaN0) were active on GitHub. | (n=33) of all Harness employees (n=NaN0) were active on GitHub. | 33 33 Harness employees were active on GitHub. | 
| 81. Posit | (n=33) of all Posit engineers (n=NaN0) were active on GitHub. | (n=33) of all Posit employees (n=NaN0) were active on GitHub. | 33 33 Posit employees were active on GitHub. | 
| 82. @vercel | (n=30) of all @vercel engineers (n=NaN0) were active on GitHub. | (n=30) of all @vercel employees (n=NaN0) were active on GitHub. | 30 30 @vercel employees were active on GitHub. | 
| 83. Cloudera | (n=30) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=30) of all Cloudera employees (n=NaN0) were active on GitHub. | 30 30 Cloudera employees were active on GitHub. | 
| 84. PingCAP | (n=29) of all PingCAP engineers (n=NaN0) were active on GitHub. | 7% 7% (n=29) of all PingCAP employees (n=410143) were active on GitHub. | 29 29 PingCAP employees were active on GitHub. | 
| 85. UCL | (n=28) of all UCL engineers (n=NaN0) were active on GitHub. | (n=28) of all UCL employees (n=NaN0) were active on GitHub. | 28 28 UCL employees were active on GitHub. | 
| 86. Palo Alto Networks | (n=28) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=28) of all Palo Alto Networks employees (n=13,948144) were active on GitHub. | 28 28 Palo Alto Networks employees were active on GitHub. | 
| 87. Snyk | (n=28) of all Snyk engineers (n=NaN0) were active on GitHub. | 2% 2% (n=28) of all Snyk employees (n=1,171145) were active on GitHub. | 28 28 Snyk employees were active on GitHub. | 
| 88. TU Delft | (n=27) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=27) of all TU Delft employees (n=NaN0) were active on GitHub. | 27 27 TU Delft employees were active on GitHub. | 
| 89. Protocol Labs | (n=26) of all Protocol Labs engineers (n=NaN0) were active on GitHub. | (n=26) of all Protocol Labs employees (n=NaN0) were active on GitHub. | 26 26 Protocol Labs employees were active on GitHub. | 
| 90. Kitware | (n=25) of all Kitware engineers (n=NaN0) were active on GitHub. | 15% 15% (n=25) of all Kitware employees (n=171146) were active on GitHub. | 25 25 Kitware employees were active on GitHub. | 
| 91. @MathWorks | (n=25) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=25) of all @MathWorks employees (n=NaN0) were active on GitHub. | 25 25 @MathWorks employees were active on GitHub. | 
| 92. @bytedance | (n=25) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=25) of all @bytedance employees (n=NaN0) were active on GitHub. | 25 25 @bytedance employees were active on GitHub. | 
| 93. Intuit | (n=24) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=24) of all Intuit employees (n=18,200147) were active on GitHub. | 24 24 Intuit employees were active on GitHub. | 
| 94. @apache | (n=24) of all @apache engineers (n=NaN0) were active on GitHub. | (n=24) of all @apache employees (n=NaN0) were active on GitHub. | 24 24 @apache employees were active on GitHub. | 
| 95. Orange S.A. | (n=23) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=23) of all Orange S.A. employees (n=127,109148) were active on GitHub. | 23 23 Orange S.A. employees were active on GitHub. | 
| 96. Ascensio System SIA | (n=23) of all Ascensio System SIA engineers (n=NaN0) were active on GitHub. | (n=23) of all Ascensio System SIA employees (n=NaN0) were active on GitHub. | 23 23 Ascensio System SIA employees were active on GitHub. | 
| 97. @SSWConsulting | (n=23) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=23) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 23 23 @SSWConsulting employees were active on GitHub. | 
| 98. The Alan Turing Institute | (n=22) of all The Alan Turing Institute engineers (n=NaN0) were active on GitHub. | (n=22) of all The Alan Turing Institute employees (n=NaN0) were active on GitHub. | 22 22 The Alan Turing Institute employees were active on GitHub. | 
| 99. UIUC | (n=21) of all UIUC engineers (n=NaN0) were active on GitHub. | (n=21) of all UIUC employees (n=NaN0) were active on GitHub. | 21 21 UIUC employees were active on GitHub. | 
| 100. @paritytech | (n=21) of all @paritytech engineers (n=NaN0) were active on GitHub. | (n=21) of all @paritytech employees (n=NaN0) were active on GitHub. | 21 21 @paritytech employees were active on GitHub. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: links.imagerelay.com (page 10)
- 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)
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- Vercel engineer count: linkedin.com
- Vercel 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
- MongoDB engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 9)
- 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)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- New Relic engineer count: linkedin.com (Retrieved December 2023)
- New Relic employee count: linkedin.com (Retrieved December 2023)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- Shopify engineer count: linkedin.com (retrieved Dec 2023)
- Shopify employee count: s27.q4cdn.com (page 22)
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- GitLab engineer count: linkedin.com (retrieved December 2023)
- GitLab employee count: sec.gov (page 12)
- Progress Software engineer count: sec.gov (page 7, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 7)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 20)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Interim Report, page 15)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 17)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 14)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 18)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 10)
- WIX engineer count: sec.gov (page 89, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 149)
- Tencent engineer count: linkedin.com (retrieved Dec 2023)
- Tencent employee count: static.tencent.com (page 56)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Spotify engineer count: sec.gov (page 68, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 68)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- 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)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 60)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- 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)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- Salesforce engineer count: linkedin.com (retrieved Dec 2023)
- Salesforce employee count: sec.gov (page 10)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 12)
- Yandex engineer count: sec.gov (page 54, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 54)
- 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)
- Baidu engineer count: sec.gov (page 196, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 196)
- NetEase engineer count: sec.gov (page 156, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 156)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- EPAM Systems engineer count: sec.gov (page 5, referred to as 'delivery professionals')
- EPAM Systems employee count: sec.gov (page 5)
- Nokia engineer count: linkedin.com (retrieved Dec 2023)
- Nokia employee count: sec.gov (page 105)
- Ericsson engineer count: sec.gov (page 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- 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)
- 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
- PingCAP employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- Snyk employee count: linkedin.com
- Kitware employee count: linkedin.com
- Intuit employee count: sec.gov (page 12)
- Orange S.A. employee count: gallery.orange.com (page 58)