Corporate GitHub Activity
Most Active Corporations on GitHub, 12 2023
Ranking companies with employees who, during 12 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Vercel | 36% 36% (n=56) of all Vercel engineers (n=1541) were active on GitHub. | 12% 12% (n=56) of all Vercel employees (n=4732) were active on GitHub. | 56 56 Vercel employees were active on GitHub. | 
|---|---|---|---|
| 2. Grafana Labs | 34% 34% (n=175) of all Grafana Labs engineers (n=5163) were active on GitHub. | 14% 14% (n=175) of all Grafana Labs employees (n=1,2174) were active on GitHub. | 175 175 Grafana Labs employees were active on GitHub. | 
| 3. SUSE | 30% 30% (n=173) of all SUSE engineers (n=5755) were active on GitHub. | 7% 7% (n=173) of all SUSE employees (n=2,4006) were active on GitHub. | 173 173 SUSE employees were active on GitHub. | 
| 4. Automattic | 27% 27% (n=238) of all Automattic engineers (n=8667) were active on GitHub. | 12% 12% (n=238) of all Automattic employees (n=1,9308) were active on GitHub. | 238 238 Automattic employees were active on GitHub. | 
| 5. Elastic | 25% 25% (n=253) of all Elastic engineers (n=1,0229) were active on GitHub. | 8% 8% (n=253) of all Elastic employees (n=3,18710) were active on GitHub. | 253 253 Elastic employees were active on GitHub. | 
| 6. Mozilla | 23% 23% (n=134) of all Mozilla engineers (n=58511) were active on GitHub. | 8% 8% (n=134) of all Mozilla employees (n=1,74512) were active on GitHub. | 134 134 Mozilla employees were active on GitHub. | 
| 7. HashiCorp | 21% 21% (n=143) of all HashiCorp engineers (n=68013) were active on GitHub. | 7% 7% (n=143) of all HashiCorp employees (n=2,20014) were active on GitHub. | 143 143 HashiCorp employees were active on GitHub. | 
| 8. JetBrains | 15% 15% (n=141) of all JetBrains engineers (n=97215) were active on GitHub. | 8% 8% (n=141) of all JetBrains employees (n=1,80016) were active on GitHub. | 141 141 JetBrains employees were active on GitHub. | 
| 9. Docker | 14% 14% (n=24) of all Docker engineers (n=16717) were active on GitHub. | 3% 3% (n=24) of all Docker employees (n=76718) were active on GitHub. | 24 24 Docker employees were active on GitHub. | 
| 10. WikiMedia Foundation | 10% 10% (n=21) of all WikiMedia Foundation engineers (n=20419) were active on GitHub. | 3% 3% (n=21) of all WikiMedia Foundation employees (n=70020) were active on GitHub. | 21 21 WikiMedia Foundation employees were active on GitHub. | 
| 11. DataDog | 10% 10% (n=236) of all DataDog engineers (n=2,40021) were active on GitHub. | 5% 5% (n=236) of all DataDog employees (n=5,20022) were active on GitHub. | 236 236 DataDog employees were active on GitHub. | 
| 12. WSO2 | 8% 8% (n=56) of all WSO2 engineers (n=66423) were active on GitHub. | 5% 5% (n=56) of all WSO2 employees (n=1,02024) were active on GitHub. | 56 56 WSO2 employees were active on GitHub. | 
| 13. MongoDB | 8% 8% (n=100) of all MongoDB engineers (n=1,22625) were active on GitHub. | 2% 2% (n=100) of all MongoDB employees (n=5,03726) were active on GitHub. | 100 100 MongoDB employees were active on GitHub. | 
| 14. Cloudflare | 8% 8% (n=64) of all Cloudflare engineers (n=83027) were active on GitHub. | 2% 2% (n=64) of all Cloudflare employees (n=3,68228) were active on GitHub. | 64 64 Cloudflare employees were active on GitHub. | 
| 15. New Relic | 6% 6% (n=49) of all New Relic engineers (n=88429) were active on GitHub. | 2% 2% (n=49) of all New Relic employees (n=2,58430) were active on GitHub. | 49 49 New Relic employees were active on GitHub. | 
| 16. Odoo | 4% 4% (n=25) of all Odoo engineers (n=64531) were active on GitHub. | 1% 1% (n=25) of all Odoo employees (n=1,70032) were active on GitHub. | 25 25 Odoo employees were active on GitHub. | 
| 17. Shopify | 4% 4% (n=128) of all Shopify engineers (n=3,56433) were active on GitHub. | 2% 2% (n=128) of all Shopify employees (n=8,30034) were active on GitHub. | 128 128 Shopify employees were active on GitHub. | 
| 18. Confluent | 4% 4% (n=37) of all Confluent engineers (n=1,03435) were active on GitHub. | 1% 1% (n=37) of all Confluent employees (n=2,74436) were active on GitHub. | 37 37 Confluent employees were active on GitHub. | 
| 19. Microsoft | 3% 3% (n=2,360) of all Microsoft engineers (n=72,00037) were active on GitHub. | 1% 1% (n=2,360) of all Microsoft employees (n=221,00038) were active on GitHub. | 2,360 2,360 Microsoft employees were active on GitHub. | 
| 20. GitLab | 3% 3% (n=19) of all GitLab engineers (n=64139) were active on GitHub. | 1% 1% (n=19) of all GitLab employees (n=2,13040) were active on GitHub. | 19 19 GitLab employees were active on GitHub. | 
| 21. ESRI | 3% 3% (n=59) of all ESRI engineers (n=2,07441) were active on GitHub. | 1% 1% (n=59) of all ESRI employees (n=6,44742) were active on GitHub. | 59 59 ESRI employees were active on GitHub. | 
| 22. Progress Software | 3% 3% (n=25) of all Progress Software engineers (n=88643) were active on GitHub. | 1% 1% (n=25) of all Progress Software employees (n=2,28444) were active on GitHub. | 25 25 Progress Software employees were active on GitHub. | 
| 23. Okta | 3% 3% (n=41) of all Okta engineers (n=1,57045) were active on GitHub. | 1% 1% (n=41) of all Okta employees (n=5,90846) were active on GitHub. | 41 41 Okta employees were active on GitHub. | 
| 24. Alibaba | 2% 2% (n=247) of all Alibaba engineers (n=10,02547) were active on GitHub. | 0% 0% (n=247) of all Alibaba employees (n=224,95548) were active on GitHub. | 247 247 Alibaba employees were active on GitHub. | 
| 25. Broadcom | 2% 2% (n=266) of all Broadcom engineers (n=12,60049) were active on GitHub. | 1% 1% (n=266) of all Broadcom employees (n=20,00050) were active on GitHub. | 266 266 Broadcom employees were active on GitHub. | 
| 26. Square, Inc. | 2% 2% (n=40) of all Square, Inc. engineers (n=2,06051) were active on GitHub. | 0% 0% (n=40) of all Square, Inc. employees (n=12,98552) were active on GitHub. | 40 40 Square, Inc. employees were active on GitHub. | 
| 27. Splunk | 2% 2% (n=46) of all Splunk engineers (n=2,38753) were active on GitHub. | 1% 1% (n=46) of all Splunk employees (n=8,00054) were active on GitHub. | 46 46 Splunk employees were active on GitHub. | 
| 28. Netflix | 2% 2% (n=46) of all Netflix engineers (n=2,40955) were active on GitHub. | 0% 0% (n=46) of all Netflix employees (n=13,00056) were active on GitHub. | 46 46 Netflix employees were active on GitHub. | 
| 29. Amazon | 2% 2% (n=791) of all Amazon engineers (n=43,60557) were active on GitHub. | 1% 1% (n=791) of all Amazon employees (n=125,34558) were active on GitHub. | 791 791 Amazon employees were active on GitHub. | 
| 30. Snowflake, Inc. | 2% 2% (n=36) of all Snowflake, Inc. engineers (n=2,00259) were active on GitHub. | 1% 1% (n=36) of all Snowflake, Inc. employees (n=7,00460) were active on GitHub. | 36 36 Snowflake, Inc. employees were active on GitHub. | 
| 31. Arm Ltd | 2% 2% (n=83) of all Arm Ltd engineers (n=4,75361) were active on GitHub. | 1% 1% (n=83) of all Arm Ltd employees (n=5,96362) were active on GitHub. | 83 83 Arm Ltd employees were active on GitHub. | 
| 32. Hyland | 2% 2% (n=19) of all Hyland engineers (n=1,09263) were active on GitHub. | 0% 0% (n=19) of all Hyland employees (n=4,08564) were active on GitHub. | 19 19 Hyland employees were active on GitHub. | 
| 33. ThoughtWorks | 2% 2% (n=59) of all ThoughtWorks engineers (n=3,76565) were active on GitHub. | 1% 1% (n=59) of all ThoughtWorks employees (n=10,50066) were active on GitHub. | 59 59 ThoughtWorks employees were active on GitHub. | 
| 34. Stripe | 1% 1% (n=44) of all Stripe engineers (n=2,95267) were active on GitHub. | 1% 1% (n=44) of all Stripe employees (n=8,40968) were active on GitHub. | 44 44 Stripe employees were active on GitHub. | 
| 35. Google | 1% 1% (n=1,109) of all Google engineers (n=75,57169) were active on GitHub. | 1% 1% (n=1,109) of all Google employees (n=182,50270) were active on GitHub. | 1,109 1,109 Google employees were active on GitHub. | 
| 36. CyberAgent | 1% 1% (n=24) of all CyberAgent engineers (n=1,66071) were active on GitHub. | 0% 0% (n=24) of all CyberAgent employees (n=7,25172) were active on GitHub. | 24 24 CyberAgent employees were active on GitHub. | 
| 37. Twilio | 1% 1% (n=37) of all Twilio engineers (n=2,56373) were active on GitHub. | 1% 1% (n=37) of all Twilio employees (n=5,86774) were active on GitHub. | 37 37 Twilio employees were active on GitHub. | 
| 38. Adobe | 1% 1% (n=146) of all Adobe engineers (n=10,24775) were active on GitHub. | 0% 0% (n=146) of all Adobe employees (n=29,94576) were active on GitHub. | 146 146 Adobe employees were active on GitHub. | 
| 39. Unity Technologies | 1% 1% (n=54) of all Unity Technologies engineers (n=3,84477) were active on GitHub. | 1% 1% (n=54) of all Unity Technologies employees (n=6,74878) were active on GitHub. | 54 54 Unity Technologies employees were active on GitHub. | 
| 40. Tencent | 1% 1% (n=190) of all Tencent engineers (n=13,64279) were active on GitHub. | 0% 0% (n=190) of all Tencent employees (n=105,41780) were active on GitHub. | 190 190 Tencent employees were active on GitHub. | 
| 41. WIX | 1% 1% (n=30) of all WIX engineers (n=2,30181) were active on GitHub. | 1% 1% (n=30) of all WIX employees (n=4,60082) were active on GitHub. | 30 30 WIX employees were active on GitHub. | 
| 42. Zendesk | 1% 1% (n=19) of all Zendesk engineers (n=1,48183) were active on GitHub. | 0% 0% (n=19) of all Zendesk employees (n=6,17984) were active on GitHub. | 19 19 Zendesk employees were active on GitHub. | 
| 43. NVIDIA | 1% 1% (n=249) of all NVIDIA engineers (n=22,20085) were active on GitHub. | 1% 1% (n=249) of all NVIDIA employees (n=29,60086) were active on GitHub. | 249 249 NVIDIA employees were active on GitHub. | 
| 44. Zalando DE | 1% 1% (n=18) of all Zalando DE engineers (n=1,72287) were active on GitHub. | 0% 0% (n=18) of all Zalando DE employees (n=15,79388) were active on GitHub. | 18 18 Zalando DE employees were active on GitHub. | 
| 45. Spotify | 1% 1% (n=47) of all Spotify engineers (n=4,71989) were active on GitHub. | 1% 1% (n=47) of all Spotify employees (n=9,12390) were active on GitHub. | 47 47 Spotify employees were active on GitHub. | 
| 46. Atlassian | 1% 1% (n=53) of all Atlassian engineers (n=5,36391) were active on GitHub. | 0% 0% (n=53) of all Atlassian employees (n=10,72692) were active on GitHub. | 53 53 Atlassian employees were active on GitHub. | 
| 47. BBC | 1% 1% (n=18) of all BBC engineers (n=1,82293) were active on GitHub. | 0% 0% (n=18) of all BBC employees (n=21,63194) were active on GitHub. | 18 18 BBC employees were active on GitHub. | 
| 48. AMD | 1% 1% (n=125) of all AMD engineers (n=15,60695) were active on GitHub. | 0% 0% (n=125) of all AMD employees (n=26,00096) were active on GitHub. | 125 125 AMD employees were active on GitHub. | 
| 49. Autodesk | 1% 1% (n=32) of all Autodesk engineers (n=4,20997) were active on GitHub. | 0% 0% (n=32) of all Autodesk employees (n=14,10098) were active on GitHub. | 32 32 Autodesk employees were active on GitHub. | 
| 50. Meta | 1% 1% (n=238) of all Meta engineers (n=31,33899) were active on GitHub. | 0% 0% (n=238) of all Meta employees (n=67,317100) were active on GitHub. | 238 238 Meta employees were active on GitHub. | 
| 51. Intel | 1% 1% (n=422) of all Intel engineers (n=57,201101) were active on GitHub. | 0% 0% (n=422) of all Intel employees (n=124,800102) were active on GitHub. | 422 422 Intel employees were active on GitHub. | 
| 52. Uber | 1% 1% (n=47) of all Uber engineers (n=6,426103) were active on GitHub. | 0% 0% (n=47) of all Uber employees (n=30,400104) were active on GitHub. | 47 47 Uber employees were active on GitHub. | 
| 53. Indeed | 1% 1% (n=18) of all Indeed engineers (n=2,813105) were active on GitHub. | 0% 0% (n=18) of all Indeed employees (n=18,038106) were active on GitHub. | 18 18 Indeed employees were active on GitHub. | 
| 54. Booking.com | 1% 1% (n=18) of all Booking.com engineers (n=2,844107) were active on GitHub. | 0% 0% (n=18) of all Booking.com employees (n=23,600108) were active on GitHub. | 18 18 Booking.com employees were active on GitHub. | 
| 55. SAP SE | 1% 1% (n=209) of all SAP SE engineers (n=33,377109) were active on GitHub. | 0% 0% (n=209) of all SAP SE employees (n=107,602110) were active on GitHub. | 209 209 SAP SE employees were active on GitHub. | 
| 56. Bloomberg | 1% 1% (n=45) of all Bloomberg engineers (n=7,328111) were active on GitHub. | 0% 0% (n=45) of all Bloomberg employees (n=25,923112) were active on GitHub. | 45 45 Bloomberg employees were active on GitHub. | 
| 57. Salesforce | 1% 1% (n=110) of all Salesforce engineers (n=19,483113) were active on GitHub. | 0% 0% (n=110) of all Salesforce employees (n=72,682114) were active on GitHub. | 110 110 Salesforce employees were active on GitHub. | 
| 58. Yandex | 1% 1% (n=72) of all Yandex engineers (n=13,003115) were active on GitHub. | 0% 0% (n=72) of all Yandex employees (n=26,361116) were active on GitHub. | 72 72 Yandex employees were active on GitHub. | 
| 59. Baidu | 0% 0% (n=78) of all Baidu engineers (n=21,800117) were active on GitHub. | 0% 0% (n=78) of all Baidu employees (n=39,800118) were active on GitHub. | 78 78 Baidu employees were active on GitHub. | 
| 60. Apple | 0% 0% (n=144) of all Apple engineers (n=46,752119) were active on GitHub. | 0% 0% (n=144) of all Apple employees (n=161,000120) were active on GitHub. | 144 144 Apple employees were active on GitHub. | 
| 61. NetEase | 0% 0% (n=45) of all NetEase engineers (n=14,855121) were active on GitHub. | 0% 0% (n=45) of all NetEase employees (n=29,128122) were active on GitHub. | 45 45 NetEase employees were active on GitHub. | 
| 62. PayPal | 0% 0% (n=25) of all PayPal engineers (n=8,658123) were active on GitHub. | 0% 0% (n=25) of all PayPal employees (n=27,200124) were active on GitHub. | 25 25 PayPal employees were active on GitHub. | 
| 63. Cisco Systems | 0% 0% (n=67) of all Cisco Systems engineers (n=23,772125) were active on GitHub. | 0% 0% (n=67) of all Cisco Systems employees (n=84,900126) were active on GitHub. | 67 67 Cisco Systems employees were active on GitHub. | 
| 64. Oracle | 0% 0% (n=110) of all Oracle engineers (n=47,000127) were active on GitHub. | 0% 0% (n=110) of all Oracle employees (n=164,000128) were active on GitHub. | 110 110 Oracle employees were active on GitHub. | 
| 65. EPAM Systems | 0% 0% (n=98) of all EPAM Systems engineers (n=47,350129) were active on GitHub. | 0% 0% (n=98) of all EPAM Systems employees (n=53,150130) were active on GitHub. | 98 98 EPAM Systems employees were active on GitHub. | 
| 66. Ericsson | 0% 0% (n=35) of all Ericsson engineers (n=28,219131) were active on GitHub. | 0% 0% (n=35) of all Ericsson employees (n=99,952132) were active on GitHub. | 35 35 Ericsson employees were active on GitHub. | 
| 67. Nokia | 0% 0% (n=26) of all Nokia engineers (n=26,395133) were active on GitHub. | 0% 0% (n=26) of all Nokia employees (n=86,689134) were active on GitHub. | 26 26 Nokia employees were active on GitHub. | 
| 68. Samsung | 0% 0% (n=58) of all Samsung engineers (n=83,729135) were active on GitHub. | 0% 0% (n=58) of all Samsung employees (n=267,860136) were active on GitHub. | 58 58 Samsung employees were active on GitHub. | 
| 69. Capgemini | 0% 0% (n=42) of all Capgemini engineers (n=69,796137) were active on GitHub. | 0% 0% (n=42) of all Capgemini employees (n=340,400138) were active on GitHub. | 42 42 Capgemini employees were active on GitHub. | 
| 70. Huawei | 0% 0% (n=58) of all Huawei engineers (n=114,000139) were active on GitHub. | 0% 0% (n=58) of all Huawei employees (n=207,000140) were active on GitHub. | 58 58 Huawei employees were active on GitHub. | 
| 71. IBM | (n=1,288) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=1,288) of all IBM employees (n=282,200141) were active on GitHub. | 1,288 1,288 IBM employees were active on GitHub. | 
| 72. ByteDance | (n=159) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=159) of all ByteDance employees (n=NaN0) were active on GitHub. | 159 159 ByteDance employees were active on GitHub. | 
| 73. Canonical | (n=87) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=87) of all Canonical employees (n=NaN0) were active on GitHub. | 87 87 Canonical employees were active on GitHub. | 
| 74. Sentry.io | (n=64) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 17% 17% (n=64) of all Sentry.io employees (n=378142) were active on GitHub. | 64 64 Sentry.io employees were active on GitHub. | 
| 75. Databricks | (n=62) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=62) of all Databricks employees (n=7,211143) were active on GitHub. | 62 62 Databricks employees were active on GitHub. | 
| 76. Software Mansion | (n=58) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=58) of all Software Mansion employees (n=NaN0) were active on GitHub. | 58 58 Software Mansion employees were active on GitHub. | 
| 77. Accenture | (n=52) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=52) of all Accenture employees (n=733,000144) were active on GitHub. | 52 52 Accenture employees were active on GitHub. | 
| 78. Posit | (n=39) of all Posit engineers (n=NaN0) were active on GitHub. | (n=39) of all Posit employees (n=NaN0) were active on GitHub. | 39 39 Posit employees were active on GitHub. | 
| 79. Yahoo! | (n=39) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=39) of all Yahoo! employees (n=NaN0) were active on GitHub. | 39 39 Yahoo! employees were active on GitHub. | 
| 80. Harness | (n=31) of all Harness engineers (n=NaN0) were active on GitHub. | (n=31) of all Harness employees (n=NaN0) were active on GitHub. | 31 31 Harness employees were active on GitHub. | 
| 81. Kitware | (n=30) of all Kitware engineers (n=NaN0) were active on GitHub. | 18% 18% (n=30) of all Kitware employees (n=171145) were active on GitHub. | 30 30 Kitware employees were active on GitHub. | 
| 82. Intuit | (n=30) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=30) of all Intuit employees (n=18,200146) were active on GitHub. | 30 30 Intuit employees were active on GitHub. | 
| 83. R3 | (n=26) of all R3 engineers (n=NaN0) were active on GitHub. | (n=26) of all R3 employees (n=NaN0) were active on GitHub. | 26 26 R3 employees were active on GitHub. | 
| 84. PingCAP | (n=26) of all PingCAP engineers (n=NaN0) were active on GitHub. | 6% 6% (n=26) of all PingCAP employees (n=410147) were active on GitHub. | 26 26 PingCAP employees were active on GitHub. | 
| 85. Ascensio System SIA | (n=26) of all Ascensio System SIA engineers (n=NaN0) were active on GitHub. | (n=26) of all Ascensio System SIA employees (n=NaN0) were active on GitHub. | 26 26 Ascensio System SIA employees were active on GitHub. | 
| 86. Ant Group | (n=25) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=25) of all Ant Group employees (n=NaN0) were active on GitHub. | 25 25 Ant Group employees were active on GitHub. | 
| 87. Palo Alto Networks | (n=25) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=25) of all Palo Alto Networks employees (n=13,948148) were active on GitHub. | 25 25 Palo Alto Networks employees were active on GitHub. | 
| 88. Qlik | (n=25) of all Qlik engineers (n=NaN0) were active on GitHub. | (n=25) of all Qlik employees (n=NaN0) were active on GitHub. | 25 25 Qlik employees were active on GitHub. | 
| 89. OpenAI | (n=25) of all OpenAI engineers (n=NaN0) were active on GitHub. | 2% 2% (n=25) of all OpenAI employees (n=1,604149) were active on GitHub. | 25 25 OpenAI employees were active on GitHub. | 
| 90. TU Delft | (n=24) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=24) of all TU Delft employees (n=NaN0) were active on GitHub. | 24 24 TU Delft employees were active on GitHub. | 
| 91. 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,109150) were active on GitHub. | 23 23 Orange S.A. employees were active on GitHub. | 
| 92. Dynatrace | (n=23) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=23) of all Dynatrace employees (n=NaN0) were active on GitHub. | 23 23 Dynatrace employees were active on GitHub. | 
| 93. @Kong | (n=23) of all @Kong engineers (n=NaN0) were active on GitHub. | (n=23) of all @Kong employees (n=NaN0) were active on GitHub. | 23 23 @Kong employees were active on GitHub. | 
| 94. @apache | (n=21) of all @apache engineers (n=NaN0) were active on GitHub. | (n=21) of all @apache employees (n=NaN0) were active on GitHub. | 21 21 @apache employees were active on GitHub. | 
| 95. Tata Consultancy Services | (n=20) of all Tata Consultancy Services engineers (n=NaN0) were active on GitHub. | (n=20) of all Tata Consultancy Services employees (n=NaN0) were active on GitHub. | 20 20 Tata Consultancy Services employees were active on GitHub. | 
| 96. @paritytech | (n=20) of all @paritytech engineers (n=NaN0) were active on GitHub. | (n=20) of all @paritytech employees (n=NaN0) were active on GitHub. | 20 20 @paritytech employees were active on GitHub. | 
| 97. Sanity | (n=20) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=20) of all Sanity employees (n=NaN0) were active on GitHub. | 20 20 Sanity employees were active on GitHub. | 
| 98. UCL | (n=19) of all UCL engineers (n=NaN0) were active on GitHub. | (n=19) of all UCL employees (n=NaN0) were active on GitHub. | 19 19 UCL employees were active on GitHub. | 
| 99. Snyk | (n=19) of all Snyk engineers (n=NaN0) were active on GitHub. | 2% 2% (n=19) of all Snyk employees (n=1,171151) were active on GitHub. | 19 19 Snyk employees were active on GitHub. | 
| 100. @MathWorks | (n=18) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=18) of all @MathWorks employees (n=NaN0) were active on GitHub. | 18 18 @MathWorks employees were active on GitHub. | 
References
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- SUSE engineer count: linkedin.com
- SUSE employee count: links.imagerelay.com (page 10)
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved December 2023)
- Elastic engineer count: linkedin.com (retrieved Dec 2023)
- Elastic employee count: sec.gov (page 15)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 13)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- WikiMedia Foundation employee count: wikimediafoundation.org
- DataDog engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 11)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- MongoDB engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 9)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- New Relic engineer count: linkedin.com (Retrieved December 2023)
- New Relic employee count: linkedin.com (Retrieved December 2023)
- Odoo engineer count: linkedin.com
- Odoo 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)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Progress Software engineer count: sec.gov (page 7, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 7)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 14)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Interim Report, page 15)
- Broadcom engineer count: sec.gov (page 11, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 11)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 20)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 17)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Hyland engineer count: linkedin.com
- Hyland employee count: linkedin.com
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 10)
- CyberAgent engineer count: cyberagent.co.jp (page 8)
- CyberAgent employee count: cyberagent.co.jp (page 8)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 18)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Tencent engineer count: linkedin.com (retrieved Dec 2023)
- Tencent employee count: static.tencent.com (page 56)
- WIX engineer count: sec.gov (page 89, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 149)
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- Spotify engineer count: sec.gov (page 68, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 68)
- 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)
- BBC engineer count: linkedin.com
- BBC employee count: bbc.co.uk (page 59)
- AMD engineer count: linkedin.com
- AMD 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)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- Booking.com engineer count: linkedin.com
- Booking.com employee count: sec.gov (page 6)
- 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)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Salesforce engineer count: linkedin.com (retrieved Dec 2023)
- Salesforce employee count: sec.gov (page 10)
- Yandex engineer count: sec.gov (page 54, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 54)
- 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)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- Cisco Systems engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 10)
- 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)
- Ericsson engineer count: sec.gov (page 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- 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)
- 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)
- Sentry.io employee count: linkedin.com
- Databricks employee count: linkedin.com
- Accenture employee count: sec.gov (page 25)
- Kitware employee count: linkedin.com
- Intuit employee count: sec.gov (page 12)
- PingCAP employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- OpenAI employee count: linkedin.com
- Orange S.A. employee count: gallery.orange.com (page 58)
- Snyk employee count: linkedin.com