Corporate GitHub Activity
Most Active Corporations on GitHub, 06 2022
Ranking companies with employees who, during 06 2022, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Grafana Labs | 45% 45% (n=156) of all Grafana Labs engineers (n=3431) were active on GitHub. | 26% 26% (n=156) of all Grafana Labs employees (n=6002) were active on GitHub. | 156 156 Grafana Labs employees were active on GitHub. | 
|---|---|---|---|
| 2. SUSE | 36% 36% (n=188) of all SUSE engineers (n=5223) were active on GitHub. | 8% 8% (n=188) of all SUSE employees (n=2,3984) were active on GitHub. | 188 188 SUSE employees were active on GitHub. | 
| 3. Mozilla | 29% 29% (n=138) of all Mozilla engineers (n=4725) were active on GitHub. | 9% 9% (n=138) of all Mozilla employees (n=1,5106) were active on GitHub. | 138 138 Mozilla employees were active on GitHub. | 
| 4. Automattic | 28% 28% (n=231) of all Automattic engineers (n=8307) were active on GitHub. | 12% 12% (n=231) of all Automattic employees (n=2,0028) were active on GitHub. | 231 231 Automattic employees were active on GitHub. | 
| 5. Elastic | 27% 27% (n=250) of all Elastic engineers (n=9149) were active on GitHub. | 9% 9% (n=250) of all Elastic employees (n=2,88610) were active on GitHub. | 250 250 Elastic employees were active on GitHub. | 
| 6. Docker | 25% 25% (n=25) of all Docker engineers (n=10111) were active on GitHub. | 6% 6% (n=25) of all Docker employees (n=43512) were active on GitHub. | 25 25 Docker employees were active on GitHub. | 
| 7. Odoo | 22% 22% (n=106) of all Odoo engineers (n=47413) were active on GitHub. | 8% 8% (n=106) of all Odoo employees (n=1,32714) were active on GitHub. | 106 106 Odoo employees were active on GitHub. | 
| 8. Vercel | 18% 18% (n=21) of all Vercel engineers (n=11815) were active on GitHub. | 5% 5% (n=21) of all Vercel employees (n=39816) were active on GitHub. | 21 21 Vercel employees were active on GitHub. | 
| 9. HashiCorp | 18% 18% (n=118) of all HashiCorp engineers (n=67017) were active on GitHub. | 5% 5% (n=118) of all HashiCorp employees (n=2,40018) were active on GitHub. | 118 118 HashiCorp employees were active on GitHub. | 
| 10. JetBrains | 18% 18% (n=126) of all JetBrains engineers (n=71919) were active on GitHub. | 7% 7% (n=126) of all JetBrains employees (n=1,90020) were active on GitHub. | 126 126 JetBrains employees were active on GitHub. | 
| 11. The Guardian | 17% 17% (n=22) of all The Guardian engineers (n=12721) were active on GitHub. | 1% 1% (n=22) of all The Guardian employees (n=2,30022) were active on GitHub. | 22 22 The Guardian employees were active on GitHub. | 
| 12. Mapbox | 14% 14% (n=36) of all Mapbox engineers (n=25823) were active on GitHub. | 5% 5% (n=36) of all Mapbox employees (n=67824) were active on GitHub. | 36 36 Mapbox employees were active on GitHub. | 
| 13. WikiMedia Foundation | 11% 11% (n=22) of all WikiMedia Foundation engineers (n=19425) were active on GitHub. | (n=22) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 22 22 WikiMedia Foundation employees were active on GitHub. | 
| 14. MongoDB | 10% 10% (n=108) of all MongoDB engineers (n=1,03026) were active on GitHub. | 2% 2% (n=108) of all MongoDB employees (n=4,61927) were active on GitHub. | 108 108 MongoDB employees were active on GitHub. | 
| 15. Cloudflare | 10% 10% (n=62) of all Cloudflare engineers (n=61028) were active on GitHub. | 2% 2% (n=62) of all Cloudflare employees (n=3,21729) were active on GitHub. | 62 62 Cloudflare employees were active on GitHub. | 
| 16. WSO2 | 9% 9% (n=73) of all WSO2 engineers (n=77530) were active on GitHub. | 6% 6% (n=73) of all WSO2 employees (n=1,16531) were active on GitHub. | 73 73 WSO2 employees were active on GitHub. | 
| 17. DataDog | 8% 8% (n=167) of all DataDog engineers (n=2,00032) were active on GitHub. | 3% 3% (n=167) of all DataDog employees (n=4,80033) were active on GitHub. | 167 167 DataDog employees were active on GitHub. | 
| 18. New Relic | 8% 8% (n=62) of all New Relic engineers (n=81934) were active on GitHub. | 2% 2% (n=62) of all New Relic employees (n=2,66335) were active on GitHub. | 62 62 New Relic employees were active on GitHub. | 
| 19. Confluent | 6% 6% (n=48) of all Confluent engineers (n=81836) were active on GitHub. | 2% 2% (n=48) of all Confluent employees (n=2,76137) were active on GitHub. | 48 48 Confluent employees were active on GitHub. | 
| 20. Liferay | 5% 5% (n=23) of all Liferay engineers (n=44438) were active on GitHub. | 2% 2% (n=23) of all Liferay employees (n=1,28939) were active on GitHub. | 23 23 Liferay employees were active on GitHub. | 
| 21. Shopify | 4% 4% (n=180) of all Shopify engineers (n=4,03740) were active on GitHub. | 2% 2% (n=180) of all Shopify employees (n=11,60041) were active on GitHub. | 180 180 Shopify employees were active on GitHub. | 
| 22. Microsoft | 4% 4% (n=2,744) of all Microsoft engineers (n=73,00042) were active on GitHub. | 1% 1% (n=2,744) of all Microsoft employees (n=221,00043) were active on GitHub. | 2,744 2,744 Microsoft employees were active on GitHub. | 
| 23. Progress Software | 4% 4% (n=31) of all Progress Software engineers (n=84244) were active on GitHub. | 1% 1% (n=31) of all Progress Software employees (n=2,07145) were active on GitHub. | 31 31 Progress Software employees were active on GitHub. | 
| 24. Square, Inc. | 4% 4% (n=66) of all Square, Inc. engineers (n=1,83146) were active on GitHub. | 1% 1% (n=66) of all Square, Inc. employees (n=12,42847) were active on GitHub. | 66 66 Square, Inc. employees were active on GitHub. | 
| 25. Alibaba | 3% 3% (n=323) of all Alibaba engineers (n=9,44048) were active on GitHub. | 0% 0% (n=323) of all Alibaba employees (n=254,94149) were active on GitHub. | 323 323 Alibaba employees were active on GitHub. | 
| 26. ESRI | 3% 3% (n=59) of all ESRI engineers (n=1,94750) were active on GitHub. | 1% 1% (n=59) of all ESRI employees (n=5,87351) were active on GitHub. | 59 59 ESRI employees were active on GitHub. | 
| 27. Okta | 3% 3% (n=42) of all Okta engineers (n=1,39252) were active on GitHub. | 1% 1% (n=42) of all Okta employees (n=6,01353) were active on GitHub. | 42 42 Okta employees were active on GitHub. | 
| 28. Snowflake, Inc. | 3% 3% (n=41) of all Snowflake, Inc. engineers (n=1,37854) were active on GitHub. | 1% 1% (n=41) of all Snowflake, Inc. employees (n=5,88455) were active on GitHub. | 41 41 Snowflake, Inc. employees were active on GitHub. | 
| 29. VMWare | 3% 3% (n=371) of all VMWare engineers (n=13,33256) were active on GitHub. | 1% 1% (n=371) of all VMWare employees (n=38,30057) were active on GitHub. | 371 371 VMWare employees were active on GitHub. | 
| 30. Twitter | 3% 3% (n=37) of all Twitter engineers (n=1,36958) were active on GitHub. | 0% 0% (n=37) of all Twitter employees (n=9,40059) were active on GitHub. | 37 37 Twitter employees were active on GitHub. | 
| 31. Stripe | 2% 2% (n=67) of all Stripe engineers (n=2,96160) were active on GitHub. | 1% 1% (n=67) of all Stripe employees (n=8,37261) were active on GitHub. | 67 67 Stripe employees were active on GitHub. | 
| 32. Amazon | 2% 2% (n=823) of all Amazon engineers (n=37,13462) were active on GitHub. | 1% 1% (n=823) of all Amazon employees (n=112,31563) were active on GitHub. | 823 823 Amazon employees were active on GitHub. | 
| 33. ThoughtWorks | 2% 2% (n=92) of all ThoughtWorks engineers (n=4,15264) were active on GitHub. | 1% 1% (n=92) of all ThoughtWorks employees (n=12,50065) were active on GitHub. | 92 92 ThoughtWorks employees were active on GitHub. | 
| 34. Tencent | 2% 2% (n=272) of all Tencent engineers (n=12,97966) were active on GitHub. | 0% 0% (n=272) of all Tencent employees (n=108,43667) were active on GitHub. | 272 272 Tencent employees were active on GitHub. | 
| 35. Netflix | 2% 2% (n=45) of all Netflix engineers (n=2,22768) were active on GitHub. | 0% 0% (n=45) of all Netflix employees (n=12,80069) were active on GitHub. | 45 45 Netflix employees were active on GitHub. | 
| 36. Twilio | 2% 2% (n=69) of all Twilio engineers (n=3,59070) were active on GitHub. | 1% 1% (n=69) of all Twilio employees (n=8,15671) were active on GitHub. | 69 69 Twilio employees were active on GitHub. | 
| 37. Arm Ltd | 2% 2% (n=89) of all Arm Ltd engineers (n=4,75872) were active on GitHub. | 1% 1% (n=89) of all Arm Ltd employees (n=6,32973) were active on GitHub. | 89 89 Arm Ltd employees were active on GitHub. | 
| 38. Unity Technologies | 2% 2% (n=69) of all Unity Technologies engineers (n=3,75374) were active on GitHub. | 1% 1% (n=69) of all Unity Technologies employees (n=7,70375) were active on GitHub. | 69 69 Unity Technologies employees were active on GitHub. | 
| 39. Splunk | 2% 2% (n=37) of all Splunk engineers (n=2,07676) were active on GitHub. | 0% 0% (n=37) of all Splunk employees (n=8,00077) were active on GitHub. | 37 37 Splunk employees were active on GitHub. | 
| 40. CyberAgent | 2% 2% (n=26) of all CyberAgent engineers (n=1,47078) were active on GitHub. | 0% 0% (n=26) of all CyberAgent employees (n=6,33779) were active on GitHub. | 26 26 CyberAgent employees were active on GitHub. | 
| 41. Zendesk | 2% 2% (n=28) of all Zendesk engineers (n=1,62080) were active on GitHub. | 0% 0% (n=28) of all Zendesk employees (n=6,44081) were active on GitHub. | 28 28 Zendesk employees were active on GitHub. | 
| 42. WIX | 2% 2% (n=37) of all WIX engineers (n=2,20682) were active on GitHub. | 1% 1% (n=37) of all WIX employees (n=4,74283) were active on GitHub. | 37 37 WIX employees were active on GitHub. | 
| 43. Google | 2% 2% (n=1,187) of all Google engineers (n=71,08484) were active on GitHub. | 1% 1% (n=1,187) of all Google employees (n=190,23485) were active on GitHub. | 1,187 1,187 Google employees were active on GitHub. | 
| 44. Adobe | 2% 2% (n=155) of all Adobe engineers (n=9,45086) were active on GitHub. | 1% 1% (n=155) of all Adobe employees (n=29,23987) were active on GitHub. | 155 155 Adobe employees were active on GitHub. | 
| 45. Zalando DE | 1% 1% (n=24) of all Zalando DE engineers (n=1,60888) were active on GitHub. | 0% 0% (n=24) of all Zalando DE employees (n=16,99989) were active on GitHub. | 24 24 Zalando DE employees were active on GitHub. | 
| 46. Spotify | 1% 1% (n=51) of all Spotify engineers (n=4,16990) were active on GitHub. | 1% 1% (n=51) of all Spotify employees (n=8,35991) were active on GitHub. | 51 51 Spotify employees were active on GitHub. | 
| 47. NVIDIA | 1% 1% (n=233) of all NVIDIA engineers (n=19,53292) were active on GitHub. | 1% 1% (n=233) of all NVIDIA employees (n=26,19693) were active on GitHub. | 233 233 NVIDIA employees were active on GitHub. | 
| 48. Uber | 1% 1% (n=61) of all Uber engineers (n=5,50294) were active on GitHub. | 0% 0% (n=61) of all Uber employees (n=32,80095) were active on GitHub. | 61 61 Uber employees were active on GitHub. | 
| 49. Atlassian | 1% 1% (n=42) of all Atlassian engineers (n=4,40696) were active on GitHub. | 0% 0% (n=42) of all Atlassian employees (n=8,81397) were active on GitHub. | 42 42 Atlassian employees were active on GitHub. | 
| 50. Autodesk | 1% 1% (n=32) of all Autodesk engineers (n=3,80098) were active on GitHub. | 0% 0% (n=32) of all Autodesk employees (n=13,70099) were active on GitHub. | 32 32 Autodesk employees were active on GitHub. | 
| 51. Meta | 1% 1% (n=269) of all Meta engineers (n=35,611100) were active on GitHub. | 0% 0% (n=269) of all Meta employees (n=86,482101) were active on GitHub. | 269 269 Meta employees were active on GitHub. | 
| 52. SAP SE | 1% 1% (n=227) of all SAP SE engineers (n=34,122102) were active on GitHub. | 0% 0% (n=227) of all SAP SE employees (n=111,961103) were active on GitHub. | 227 227 SAP SE employees were active on GitHub. | 
| 53. Salesforce | 1% 1% (n=132) of all Salesforce engineers (n=20,537104) were active on GitHub. | 0% 0% (n=132) of all Salesforce employees (n=79,390105) were active on GitHub. | 132 132 Salesforce employees were active on GitHub. | 
| 54. Intel | 1% 1% (n=329) of all Intel engineers (n=57,090106) were active on GitHub. | 0% 0% (n=329) of all Intel employees (n=131,900107) were active on GitHub. | 329 329 Intel employees were active on GitHub. | 
| 55. Bloomberg | 1% 1% (n=35) of all Bloomberg engineers (n=6,326108) were active on GitHub. | 0% 0% (n=35) of all Bloomberg employees (n=23,033109) were active on GitHub. | 35 35 Bloomberg employees were active on GitHub. | 
| 56. Baidu | 1% 1% (n=120) of all Baidu engineers (n=23,600110) were active on GitHub. | 0% 0% (n=120) of all Baidu employees (n=41,300111) were active on GitHub. | 120 120 Baidu employees were active on GitHub. | 
| 57. AMD | 1% 1% (n=61) of all AMD engineers (n=12,146112) were active on GitHub. | 0% 0% (n=61) of all AMD employees (n=25,000113) were active on GitHub. | 61 61 AMD employees were active on GitHub. | 
| 58. Yandex | 0% 0% (n=51) of all Yandex engineers (n=10,708114) were active on GitHub. | 0% 0% (n=51) of all Yandex employees (n=20,850115) were active on GitHub. | 51 51 Yandex employees were active on GitHub. | 
| 59. Cisco Systems | 0% 0% (n=108) of all Cisco Systems engineers (n=23,407116) were active on GitHub. | 0% 0% (n=108) of all Cisco Systems employees (n=83,300117) were active on GitHub. | 108 108 Cisco Systems employees were active on GitHub. | 
| 60. Oracle | 0% 0% (n=156) of all Oracle engineers (n=44,000118) were active on GitHub. | 0% 0% (n=156) of all Oracle employees (n=143,000119) were active on GitHub. | 156 156 Oracle employees were active on GitHub. | 
| 61. Apple | 0% 0% (n=138) of all Apple engineers (n=39,361120) were active on GitHub. | 0% 0% (n=138) of all Apple employees (n=164,000121) were active on GitHub. | 138 138 Apple employees were active on GitHub. | 
| 62. NetEase | 0% 0% (n=48) of all NetEase engineers (n=15,211122) were active on GitHub. | 0% 0% (n=48) of all NetEase employees (n=31,119123) were active on GitHub. | 48 48 NetEase employees were active on GitHub. | 
| 63. PayPal | 0% 0% (n=24) of all PayPal engineers (n=8,805124) were active on GitHub. | 0% 0% (n=24) of all PayPal employees (n=29,900125) were active on GitHub. | 24 24 PayPal employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=97) of all EPAM Systems engineers (n=52,850126) were active on GitHub. | 0% 0% (n=97) of all EPAM Systems employees (n=59,300127) were active on GitHub. | 97 97 EPAM Systems employees were active on GitHub. | 
| 65. Ericsson | 0% 0% (n=34) of all Ericsson engineers (n=29,304128) were active on GitHub. | 0% 0% (n=34) of all Ericsson employees (n=105,529129) were active on GitHub. | 34 34 Ericsson employees were active on GitHub. | 
| 66. Samsung | 0% 0% (n=73) of all Samsung engineers (n=80,496130) were active on GitHub. | 0% 0% (n=73) of all Samsung employees (n=270,372131) were active on GitHub. | 73 73 Samsung employees were active on GitHub. | 
| 67. Huawei | 0% 0% (n=66) of all Huawei engineers (n=114,000132) were active on GitHub. | 0% 0% (n=66) of all Huawei employees (n=207,000133) were active on GitHub. | 66 66 Huawei employees were active on GitHub. | 
| 68. Capgemini | 0% 0% (n=40) of all Capgemini engineers (n=69,803134) were active on GitHub. | 0% 0% (n=40) of all Capgemini employees (n=360,000135) were active on GitHub. | 40 40 Capgemini employees were active on GitHub. | 
| 69. IBM | (n=1,594) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,594) of all IBM employees (n=288,300136) were active on GitHub. | 1,594 1,594 IBM employees were active on GitHub. | 
| 70. ByteDance | (n=88) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=88) of all ByteDance employees (n=NaN0) were active on GitHub. | 88 88 ByteDance employees were active on GitHub. | 
| 71. Canonical | (n=69) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=69) of all Canonical employees (n=NaN0) were active on GitHub. | 69 69 Canonical employees were active on GitHub. | 
| 72. Accenture | (n=55) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=55) of all Accenture employees (n=721,000137) were active on GitHub. | 55 55 Accenture employees were active on GitHub. | 
| 73. Sentry.io | (n=51) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=51) of all Sentry.io employees (n=NaN0) were active on GitHub. | 51 51 Sentry.io employees were active on GitHub. | 
| 74. PingCAP | (n=51) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=51) of all PingCAP employees (n=NaN0) were active on GitHub. | 51 51 PingCAP employees were active on GitHub. | 
| 75. Yahoo! | (n=50) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=50) of all Yahoo! employees (n=NaN0) were active on GitHub. | 50 50 Yahoo! employees were active on GitHub. | 
| 76. Databricks | (n=48) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=48) of all Databricks employees (n=NaN0) were active on GitHub. | 48 48 Databricks employees were active on GitHub. | 
| 77. Software Mansion | (n=41) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=41) of all Software Mansion employees (n=NaN0) were active on GitHub. | 41 41 Software Mansion employees were active on GitHub. | 
| 78. @bytedance | (n=38) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=38) of all @bytedance employees (n=NaN0) were active on GitHub. | 38 38 @bytedance employees were active on GitHub. | 
| 79. RStudio | (n=36) of all RStudio engineers (n=NaN0) were active on GitHub. | (n=36) of all RStudio employees (n=NaN0) were active on GitHub. | 36 36 RStudio employees were active on GitHub. | 
| 80. Snyk | (n=34) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=34) of all Snyk employees (n=NaN0) were active on GitHub. | 34 34 Snyk employees were active on GitHub. | 
| 81. 100Devs | (n=33) of all 100Devs engineers (n=NaN0) were active on GitHub. | (n=33) of all 100Devs employees (n=NaN0) were active on GitHub. | 33 33 100Devs employees were active on GitHub. | 
| 82. Kitware | (n=31) of all Kitware engineers (n=NaN0) were active on GitHub. | 18% 18% (n=31) of all Kitware employees (n=174138) were active on GitHub. | 31 31 Kitware employees were active on GitHub. | 
| 83. Apple Developer Academy @ POSTECH | (n=30) of all Apple Developer Academy @ POSTECH engineers (n=NaN0) were active on GitHub. | (n=30) of all Apple Developer Academy @ POSTECH employees (n=NaN0) were active on GitHub. | 30 30 Apple Developer Academy @ POSTECH employees were active on GitHub. | 
| 84. Harness | (n=29) of all Harness engineers (n=NaN0) were active on GitHub. | (n=29) of all Harness employees (n=NaN0) were active on GitHub. | 29 29 Harness employees were active on GitHub. | 
| 85. Palo Alto Networks | (n=29) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=29) of all Palo Alto Networks employees (n=12,561139) were active on GitHub. | 29 29 Palo Alto Networks employees were active on GitHub. | 
| 86. Cloudera | (n=27) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=27) of all Cloudera employees (n=NaN0) were active on GitHub. | 27 27 Cloudera employees were active on GitHub. | 
| 87. CircleCI | (n=26) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=26) of all CircleCI employees (n=NaN0) were active on GitHub. | 26 26 CircleCI employees were active on GitHub. | 
| 88. DigitalOcean | (n=25) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 2% 2% (n=25) of all DigitalOcean employees (n=1,204140) were active on GitHub. | 25 25 DigitalOcean employees were active on GitHub. | 
| 89. Broad Institute | (n=23) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=23) of all Broad Institute employees (n=NaN0) were active on GitHub. | 23 23 Broad Institute employees were active on GitHub. | 
| 90. UCL | (n=22) of all UCL engineers (n=NaN0) were active on GitHub. | (n=22) of all UCL employees (n=NaN0) were active on GitHub. | 22 22 UCL employees were active on GitHub. | 
| 91. TU Delft | (n=22) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=22) of all TU Delft employees (n=NaN0) were active on GitHub. | 22 22 TU Delft employees were active on GitHub. | 
| 92. ZJU | (n=22) of all ZJU engineers (n=NaN0) were active on GitHub. | (n=22) of all ZJU employees (n=NaN0) were active on GitHub. | 22 22 ZJU employees were active on GitHub. | 
| 93. Ubisoft | (n=21) of all Ubisoft engineers (n=NaN0) were active on GitHub. | (n=21) of all Ubisoft employees (n=NaN0) were active on GitHub. | 21 21 Ubisoft employees were active on GitHub. | 
| 94. Sourcegraph | (n=21) of all Sourcegraph engineers (n=NaN0) were active on GitHub. | (n=21) of all Sourcegraph employees (n=NaN0) were active on GitHub. | 21 21 Sourcegraph employees were active on GitHub. | 
| 95. R3 | (n=21) of all R3 engineers (n=NaN0) were active on GitHub. | (n=21) of all R3 employees (n=NaN0) were active on GitHub. | 21 21 R3 employees were active on GitHub. | 
| 96. @sourcegraph | (n=21) of all @sourcegraph engineers (n=NaN0) were active on GitHub. | (n=21) of all @sourcegraph employees (n=NaN0) were active on GitHub. | 21 21 @sourcegraph employees were active on GitHub. | 
| 97. Intuit | (n=21) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=21) of all Intuit employees (n=17,300141) were active on GitHub. | 21 21 Intuit employees were active on GitHub. | 
| 98. @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. | 
| 99. @sourcegraph | (n=20) of all @sourcegraph engineers (n=NaN0) were active on GitHub. | (n=20) of all @sourcegraph employees (n=NaN0) were active on GitHub. | 20 20 @sourcegraph employees were active on GitHub. | 
| 100. Protocol Labs | (n=20) of all Protocol Labs engineers (n=NaN0) were active on GitHub. | (n=20) of all Protocol Labs employees (n=NaN0) were active on GitHub. | 20 20 Protocol Labs employees were active on GitHub. | 
References
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- SUSE engineer count: linkedin.com
- SUSE employee count: ir.suse.com (Annual Report FY22, page 249)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved March 2023)
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- HashiCorp engineer count: sec.gov (page 13)
- HashiCorp employee count: sec.gov (page 14)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- MongoDB engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 8)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- 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)
- New Relic engineer count: linkedin.com
- New Relic employee count: sec.gov (page 9)
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Shopify engineer count: linkedin.com
- Shopify employee count: s27.q4cdn.com (page 23)
- Microsoft engineer count: sec.gov (page 8, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 8)
- Progress Software engineer count: sec.gov (page 8, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 8)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 21)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Annual Report, page 168)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 87)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Twilio engineer count: sec.gov (page 7, 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)
- Unity Technologies engineer count: sec.gov (page 4, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 4)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- CyberAgent engineer count: d2utiq8et4vl56.cloudfront.net (page 80)
- CyberAgent employee count: d2utiq8et4vl56.cloudfront.net (page 80)
- Zendesk engineer count: linkedin.com
- Zendesk employee count: sec.gov (page 54)
- WIX engineer count: sec.gov (page 142, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 142)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 8)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 16)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- Spotify engineer count: sec.gov (page 69, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 69)
- NVIDIA engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 12)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- Atlassian engineer count: sec.gov (page 65, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 43)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 12)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 55)
- SAP SE engineer count: sec.gov (page F-22, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 101)
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 10)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Baidu engineer count: sec.gov (page 197, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 197)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Yandex engineer count: sec.gov (page 48, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 48)
- Cisco Systems engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 11)
- Oracle engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 14)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- NetEase engineer count: sec.gov (page 159, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 159)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 14)
- 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 9, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 11)
- Samsung engineer count: samsung.com (page 103, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 103)
- Huawei engineer count: www-file.huawei.com (page 70, referred to as employees in 'R&D')
- Huawei employee count: www-file.huawei.com (page 2)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 17)
- IBM employee count: ibm.com (page 15)
- Accenture employee count: sec.gov (page 24)
- Kitware employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- DigitalOcean employee count: sec.gov (page 13)
- Intuit employee count: sec.gov (page 12)