Corporate GitHub Activity
Most Active Corporations on GitHub, 08 2022
Ranking companies with employees who, during 08 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=153) of all Grafana Labs engineers (n=3431) were active on GitHub. | 26% 26% (n=153) of all Grafana Labs employees (n=6002) were active on GitHub. | 153 153 Grafana Labs employees were active on GitHub. | 
|---|---|---|---|
| 2. SUSE | 34% 34% (n=175) of all SUSE engineers (n=5223) were active on GitHub. | 7% 7% (n=175) of all SUSE employees (n=2,3984) were active on GitHub. | 175 175 SUSE employees were active on GitHub. | 
| 3. Mozilla | 33% 33% (n=154) of all Mozilla engineers (n=4725) were active on GitHub. | 10% 10% (n=154) of all Mozilla employees (n=1,5106) were active on GitHub. | 154 154 Mozilla employees were active on GitHub. | 
| 4. Automattic | 31% 31% (n=255) of all Automattic engineers (n=8307) were active on GitHub. | 13% 13% (n=255) of all Automattic employees (n=2,0028) were active on GitHub. | 255 255 Automattic employees were active on GitHub. | 
| 5. The Guardian | 30% 30% (n=38) of all The Guardian engineers (n=1279) were active on GitHub. | 2% 2% (n=38) of all The Guardian employees (n=2,30010) were active on GitHub. | 38 38 The Guardian employees were active on GitHub. | 
| 6. Docker | 30% 30% (n=30) of all Docker engineers (n=10111) were active on GitHub. | 7% 7% (n=30) of all Docker employees (n=43512) were active on GitHub. | 30 30 Docker employees were active on GitHub. | 
| 7. Elastic | 26% 26% (n=241) of all Elastic engineers (n=91413) were active on GitHub. | 8% 8% (n=241) of all Elastic employees (n=2,88614) were active on GitHub. | 241 241 Elastic employees were active on GitHub. | 
| 8. Vercel | 21% 21% (n=25) of all Vercel engineers (n=11815) were active on GitHub. | 6% 6% (n=25) of all Vercel employees (n=39816) were active on GitHub. | 25 25 Vercel employees were active on GitHub. | 
| 9. JetBrains | 20% 20% (n=144) of all JetBrains engineers (n=71917) were active on GitHub. | 8% 8% (n=144) of all JetBrains employees (n=1,90018) were active on GitHub. | 144 144 JetBrains employees were active on GitHub. | 
| 10. HashiCorp | 17% 17% (n=114) of all HashiCorp engineers (n=67019) were active on GitHub. | 5% 5% (n=114) of all HashiCorp employees (n=2,40020) were active on GitHub. | 114 114 HashiCorp employees were active on GitHub. | 
| 11. Mapbox | 14% 14% (n=36) of all Mapbox engineers (n=25821) were active on GitHub. | 5% 5% (n=36) of all Mapbox employees (n=67822) were active on GitHub. | 36 36 Mapbox employees were active on GitHub. | 
| 12. WikiMedia Foundation | 12% 12% (n=24) of all WikiMedia Foundation engineers (n=19423) were active on GitHub. | (n=24) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 24 24 WikiMedia Foundation employees were active on GitHub. | 
| 13. Cloudflare | 11% 11% (n=66) of all Cloudflare engineers (n=61024) were active on GitHub. | 2% 2% (n=66) of all Cloudflare employees (n=3,21725) were active on GitHub. | 66 66 Cloudflare employees were active on GitHub. | 
| 14. DataDog | 9% 9% (n=185) of all DataDog engineers (n=2,00026) were active on GitHub. | 4% 4% (n=185) of all DataDog employees (n=4,80027) were active on GitHub. | 185 185 DataDog employees were active on GitHub. | 
| 15. MongoDB | 9% 9% (n=94) of all MongoDB engineers (n=1,03028) were active on GitHub. | 2% 2% (n=94) of all MongoDB employees (n=4,61929) were active on GitHub. | 94 94 MongoDB employees were active on GitHub. | 
| 16. WSO2 | 9% 9% (n=66) of all WSO2 engineers (n=77530) were active on GitHub. | 6% 6% (n=66) of all WSO2 employees (n=1,16531) were active on GitHub. | 66 66 WSO2 employees were active on GitHub. | 
| 17. New Relic | 7% 7% (n=59) of all New Relic engineers (n=81932) were active on GitHub. | 2% 2% (n=59) of all New Relic employees (n=2,66333) were active on GitHub. | 59 59 New Relic employees were active on GitHub. | 
| 18. Confluent | 7% 7% (n=57) of all Confluent engineers (n=81834) were active on GitHub. | 2% 2% (n=57) of all Confluent employees (n=2,76135) were active on GitHub. | 57 57 Confluent employees were active on GitHub. | 
| 19. Liferay | 7% 7% (n=30) of all Liferay engineers (n=44436) were active on GitHub. | 2% 2% (n=30) of all Liferay employees (n=1,28937) were active on GitHub. | 30 30 Liferay employees were active on GitHub. | 
| 20. GitLab | 5% 5% (n=24) of all GitLab engineers (n=49438) were active on GitHub. | 1% 1% (n=24) of all GitLab employees (n=2,17039) were active on GitHub. | 24 24 GitLab employees were active on GitHub. | 
| 21. ESRI | 5% 5% (n=88) of all ESRI engineers (n=1,94740) were active on GitHub. | 1% 1% (n=88) of all ESRI employees (n=5,87341) were active on GitHub. | 88 88 ESRI employees were active on GitHub. | 
| 22. Odoo | 4% 4% (n=21) of all Odoo engineers (n=47442) were active on GitHub. | 2% 2% (n=21) of all Odoo employees (n=1,32743) were active on GitHub. | 21 21 Odoo employees were active on GitHub. | 
| 23. Shopify | 4% 4% (n=176) of all Shopify engineers (n=4,03744) were active on GitHub. | 2% 2% (n=176) of all Shopify employees (n=11,60045) were active on GitHub. | 176 176 Shopify employees were active on GitHub. | 
| 24. Microsoft | 4% 4% (n=2,946) of all Microsoft engineers (n=73,00046) were active on GitHub. | 1% 1% (n=2,946) of all Microsoft employees (n=221,00047) were active on GitHub. | 2,946 2,946 Microsoft employees were active on GitHub. | 
| 25. Progress Software | 4% 4% (n=33) of all Progress Software engineers (n=84248) were active on GitHub. | 2% 2% (n=33) of all Progress Software employees (n=2,07149) were active on GitHub. | 33 33 Progress Software employees were active on GitHub. | 
| 26. Okta | 4% 4% (n=52) of all Okta engineers (n=1,39250) were active on GitHub. | 1% 1% (n=52) of all Okta employees (n=6,01351) were active on GitHub. | 52 52 Okta employees were active on GitHub. | 
| 27. Alibaba | 3% 3% (n=320) of all Alibaba engineers (n=9,44052) were active on GitHub. | 0% 0% (n=320) of all Alibaba employees (n=254,94153) were active on GitHub. | 320 320 Alibaba employees were active on GitHub. | 
| 28. Square, Inc. | 3% 3% (n=61) of all Square, Inc. engineers (n=1,83154) were active on GitHub. | 0% 0% (n=61) of all Square, Inc. employees (n=12,42855) were active on GitHub. | 61 61 Square, Inc. employees were active on GitHub. | 
| 29. Snowflake, Inc. | 3% 3% (n=42) of all Snowflake, Inc. engineers (n=1,37856) were active on GitHub. | 1% 1% (n=42) of all Snowflake, Inc. employees (n=5,88457) were active on GitHub. | 42 42 Snowflake, Inc. employees were active on GitHub. | 
| 30. VMWare | 3% 3% (n=364) of all VMWare engineers (n=13,33258) were active on GitHub. | 1% 1% (n=364) of all VMWare employees (n=38,30059) were active on GitHub. | 364 364 VMWare employees were active on GitHub. | 
| 31. ThoughtWorks | 3% 3% (n=106) of all ThoughtWorks engineers (n=4,15260) were active on GitHub. | 1% 1% (n=106) of all ThoughtWorks employees (n=12,50061) were active on GitHub. | 106 106 ThoughtWorks employees were active on GitHub. | 
| 32. Amazon | 2% 2% (n=928) of all Amazon engineers (n=37,13462) were active on GitHub. | 1% 1% (n=928) of all Amazon employees (n=112,31563) were active on GitHub. | 928 928 Amazon employees were active on GitHub. | 
| 33. Twitter | 2% 2% (n=30) of all Twitter engineers (n=1,36964) were active on GitHub. | 0% 0% (n=30) of all Twitter employees (n=9,40065) were active on GitHub. | 30 30 Twitter employees were active on GitHub. | 
| 34. Netflix | 2% 2% (n=47) of all Netflix engineers (n=2,22766) were active on GitHub. | 0% 0% (n=47) of all Netflix employees (n=12,80067) were active on GitHub. | 47 47 Netflix employees were active on GitHub. | 
| 35. Tencent | 2% 2% (n=251) of all Tencent engineers (n=12,97968) were active on GitHub. | 0% 0% (n=251) of all Tencent employees (n=108,43669) were active on GitHub. | 251 251 Tencent employees were active on GitHub. | 
| 36. WIX | 2% 2% (n=41) of all WIX engineers (n=2,20670) were active on GitHub. | 1% 1% (n=41) of all WIX employees (n=4,74271) were active on GitHub. | 41 41 WIX employees were active on GitHub. | 
| 37. Stripe | 2% 2% (n=53) of all Stripe engineers (n=2,96172) were active on GitHub. | 1% 1% (n=53) of all Stripe employees (n=8,37273) were active on GitHub. | 53 53 Stripe employees were active on GitHub. | 
| 38. Arm Ltd | 2% 2% (n=85) of all Arm Ltd engineers (n=4,75874) were active on GitHub. | 1% 1% (n=85) of all Arm Ltd employees (n=6,32975) were active on GitHub. | 85 85 Arm Ltd employees were active on GitHub. | 
| 39. Google | 2% 2% (n=1,269) of all Google engineers (n=71,08476) were active on GitHub. | 1% 1% (n=1,269) of all Google employees (n=190,23477) were active on GitHub. | 1,269 1,269 Google employees were active on GitHub. | 
| 40. Unity Technologies | 2% 2% (n=64) of all Unity Technologies engineers (n=3,75378) were active on GitHub. | 1% 1% (n=64) of all Unity Technologies employees (n=7,70379) were active on GitHub. | 64 64 Unity Technologies employees were active on GitHub. | 
| 41. Twilio | 2% 2% (n=61) of all Twilio engineers (n=3,59080) were active on GitHub. | 1% 1% (n=61) of all Twilio employees (n=8,15681) were active on GitHub. | 61 61 Twilio employees were active on GitHub. | 
| 42. Adobe | 2% 2% (n=154) of all Adobe engineers (n=9,45082) were active on GitHub. | 1% 1% (n=154) of all Adobe employees (n=29,23983) were active on GitHub. | 154 154 Adobe employees were active on GitHub. | 
| 43. Splunk | 2% 2% (n=33) of all Splunk engineers (n=2,07684) were active on GitHub. | 0% 0% (n=33) of all Splunk employees (n=8,00085) were active on GitHub. | 33 33 Splunk employees were active on GitHub. | 
| 44. Yelp | 2% 2% (n=21) of all Yelp engineers (n=1,37286) were active on GitHub. | 0% 0% (n=21) of all Yelp employees (n=4,90087) were active on GitHub. | 21 21 Yelp employees were active on GitHub. | 
| 45. BBC | 2% 2% (n=23) of all BBC engineers (n=1,52188) were active on GitHub. | 0% 0% (n=23) of all BBC employees (n=21,28189) were active on GitHub. | 23 23 BBC employees were active on GitHub. | 
| 46. Lyft | 1% 1% (n=27) of all Lyft engineers (n=1,81190) were active on GitHub. | 1% 1% (n=27) of all Lyft employees (n=4,41991) were active on GitHub. | 27 27 Lyft employees were active on GitHub. | 
| 47. Zendesk | 1% 1% (n=24) of all Zendesk engineers (n=1,62092) were active on GitHub. | 0% 0% (n=24) of all Zendesk employees (n=6,44093) were active on GitHub. | 24 24 Zendesk employees were active on GitHub. | 
| 48. NVIDIA | 1% 1% (n=246) of all NVIDIA engineers (n=19,53294) were active on GitHub. | 1% 1% (n=246) of all NVIDIA employees (n=26,19695) were active on GitHub. | 246 246 NVIDIA employees were active on GitHub. | 
| 49. Atlassian | 1% 1% (n=54) of all Atlassian engineers (n=4,40696) were active on GitHub. | 1% 1% (n=54) of all Atlassian employees (n=8,81397) were active on GitHub. | 54 54 Atlassian employees were active on GitHub. | 
| 50. Spotify | 1% 1% (n=45) of all Spotify engineers (n=4,16998) were active on GitHub. | 1% 1% (n=45) of all Spotify employees (n=8,35999) were active on GitHub. | 45 45 Spotify employees were active on GitHub. | 
| 51. Uber | 1% 1% (n=49) of all Uber engineers (n=5,502100) were active on GitHub. | 0% 0% (n=49) of all Uber employees (n=32,800101) were active on GitHub. | 49 49 Uber employees were active on GitHub. | 
| 52. Autodesk | 1% 1% (n=33) of all Autodesk engineers (n=3,800102) were active on GitHub. | 0% 0% (n=33) of all Autodesk employees (n=13,700103) were active on GitHub. | 33 33 Autodesk employees were active on GitHub. | 
| 53. Meta | 1% 1% (n=272) of all Meta engineers (n=35,611104) were active on GitHub. | 0% 0% (n=272) of all Meta employees (n=86,482105) were active on GitHub. | 272 272 Meta employees were active on GitHub. | 
| 54. SAP SE | 1% 1% (n=251) of all SAP SE engineers (n=34,122106) were active on GitHub. | 0% 0% (n=251) of all SAP SE employees (n=111,961107) were active on GitHub. | 251 251 SAP SE employees were active on GitHub. | 
| 55. Salesforce | 1% 1% (n=144) of all Salesforce engineers (n=20,537108) were active on GitHub. | 0% 0% (n=144) of all Salesforce employees (n=79,390109) were active on GitHub. | 144 144 Salesforce employees were active on GitHub. | 
| 56. Intel | 1% 1% (n=395) of all Intel engineers (n=57,090110) were active on GitHub. | 0% 0% (n=395) of all Intel employees (n=131,900111) were active on GitHub. | 395 395 Intel employees were active on GitHub. | 
| 57. AMD | 1% 1% (n=70) of all AMD engineers (n=12,146112) were active on GitHub. | 0% 0% (n=70) of all AMD employees (n=25,000113) were active on GitHub. | 70 70 AMD employees were active on GitHub. | 
| 58. Bloomberg | 1% 1% (n=36) of all Bloomberg engineers (n=6,326114) were active on GitHub. | 0% 0% (n=36) of all Bloomberg employees (n=23,033115) were active on GitHub. | 36 36 Bloomberg employees were active on GitHub. | 
| 59. Baidu | 0% 0% (n=113) of all Baidu engineers (n=23,600116) were active on GitHub. | 0% 0% (n=113) of all Baidu employees (n=41,300117) were active on GitHub. | 113 113 Baidu employees were active on GitHub. | 
| 60. Yandex | 0% 0% (n=48) of all Yandex engineers (n=10,708118) were active on GitHub. | 0% 0% (n=48) of all Yandex employees (n=20,850119) were active on GitHub. | 48 48 Yandex employees were active on GitHub. | 
| 61. Cisco Systems | 0% 0% (n=104) of all Cisco Systems engineers (n=23,407120) were active on GitHub. | 0% 0% (n=104) of all Cisco Systems employees (n=83,300121) were active on GitHub. | 104 104 Cisco Systems employees were active on GitHub. | 
| 62. NetEase | 0% 0% (n=64) of all NetEase engineers (n=15,211122) were active on GitHub. | 0% 0% (n=64) of all NetEase employees (n=31,119123) were active on GitHub. | 64 64 NetEase employees were active on GitHub. | 
| 63. Oracle | 0% 0% (n=168) of all Oracle engineers (n=44,000124) were active on GitHub. | 0% 0% (n=168) of all Oracle employees (n=143,000125) were active on GitHub. | 168 168 Oracle employees were active on GitHub. | 
| 64. Apple | 0% 0% (n=139) of all Apple engineers (n=39,361126) were active on GitHub. | 0% 0% (n=139) of all Apple employees (n=164,000127) were active on GitHub. | 139 139 Apple employees were active on GitHub. | 
| 65. PayPal | 0% 0% (n=23) of all PayPal engineers (n=8,805128) were active on GitHub. | 0% 0% (n=23) of all PayPal employees (n=29,900129) were active on GitHub. | 23 23 PayPal employees were active on GitHub. | 
| 66. EPAM Systems | 0% 0% (n=107) of all EPAM Systems engineers (n=52,850130) were active on GitHub. | 0% 0% (n=107) of all EPAM Systems employees (n=59,300131) were active on GitHub. | 107 107 EPAM Systems employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=78) of all Samsung engineers (n=80,496132) were active on GitHub. | 0% 0% (n=78) of all Samsung employees (n=270,372133) were active on GitHub. | 78 78 Samsung employees were active on GitHub. | 
| 68. Ericsson | 0% 0% (n=28) of all Ericsson engineers (n=29,304134) were active on GitHub. | 0% 0% (n=28) of all Ericsson employees (n=105,529135) were active on GitHub. | 28 28 Ericsson employees were active on GitHub. | 
| 69. Huawei | 0% 0% (n=69) of all Huawei engineers (n=114,000136) were active on GitHub. | 0% 0% (n=69) of all Huawei employees (n=207,000137) were active on GitHub. | 69 69 Huawei employees were active on GitHub. | 
| 70. Capgemini | 0% 0% (n=42) of all Capgemini engineers (n=69,803138) were active on GitHub. | 0% 0% (n=42) of all Capgemini employees (n=360,000139) were active on GitHub. | 42 42 Capgemini employees were active on GitHub. | 
| 71. IBM | (n=1,656) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,656) of all IBM employees (n=288,300140) were active on GitHub. | 1,656 1,656 IBM employees were active on GitHub. | 
| 72. ByteDance | (n=102) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=102) of all ByteDance employees (n=NaN0) were active on GitHub. | 102 102 ByteDance employees were active on GitHub. | 
| 73. Canonical | (n=91) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=91) of all Canonical employees (n=NaN0) were active on GitHub. | 91 91 Canonical employees were active on GitHub. | 
| 74. Accenture | (n=74) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=74) of all Accenture employees (n=721,000141) were active on GitHub. | 74 74 Accenture employees were active on GitHub. | 
| 75. Sentry.io | (n=58) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=58) of all Sentry.io employees (n=NaN0) were active on GitHub. | 58 58 Sentry.io employees were active on GitHub. | 
| 76. Yahoo! | (n=53) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=53) of all Yahoo! employees (n=NaN0) were active on GitHub. | 53 53 Yahoo! employees were active on GitHub. | 
| 77. PingCAP | (n=47) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=47) of all PingCAP employees (n=NaN0) were active on GitHub. | 47 47 PingCAP employees were active on GitHub. | 
| 78. Databricks | (n=45) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=45) of all Databricks employees (n=NaN0) were active on GitHub. | 45 45 Databricks employees were active on GitHub. | 
| 79. Software Mansion | (n=45) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=45) of all Software Mansion employees (n=NaN0) were active on GitHub. | 45 45 Software Mansion employees were active on GitHub. | 
| 80. Snyk | (n=38) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=38) of all Snyk employees (n=NaN0) were active on GitHub. | 38 38 Snyk employees were active on GitHub. | 
| 81. @bytedance | (n=37) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=37) of all @bytedance employees (n=NaN0) were active on GitHub. | 37 37 @bytedance employees were active on GitHub. | 
| 82. Posit | (n=36) of all Posit engineers (n=NaN0) were active on GitHub. | (n=36) of all Posit employees (n=NaN0) were active on GitHub. | 36 36 Posit employees were active on GitHub. | 
| 83. Palo Alto Networks | (n=33) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=33) of all Palo Alto Networks employees (n=12,561142) were active on GitHub. | 33 33 Palo Alto Networks employees were active on GitHub. | 
| 84. @hashicorp | (n=31) of all @hashicorp engineers (n=NaN0) were active on GitHub. | (n=31) of all @hashicorp employees (n=NaN0) were active on GitHub. | 31 31 @hashicorp employees were active on GitHub. | 
| 85. R3 | (n=30) of all R3 engineers (n=NaN0) were active on GitHub. | (n=30) of all R3 employees (n=NaN0) were active on GitHub. | 30 30 R3 employees were active on GitHub. | 
| 86. Kitware | (n=30) of all Kitware engineers (n=NaN0) were active on GitHub. | 17% 17% (n=30) of all Kitware employees (n=174143) were active on GitHub. | 30 30 Kitware employees were active on GitHub. | 
| 87. 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. | 
| 88. CircleCI | (n=29) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=29) of all CircleCI employees (n=NaN0) were active on GitHub. | 29 29 CircleCI employees were active on GitHub. | 
| 89. 100Devs | (n=27) of all 100Devs engineers (n=NaN0) were active on GitHub. | (n=27) of all 100Devs employees (n=NaN0) were active on GitHub. | 27 27 100Devs employees were active on GitHub. | 
| 90. Harness | (n=26) of all Harness engineers (n=NaN0) were active on GitHub. | (n=26) of all Harness employees (n=NaN0) were active on GitHub. | 26 26 Harness employees were active on GitHub. | 
| 91. Broad Institute | (n=25) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=25) of all Broad Institute employees (n=NaN0) were active on GitHub. | 25 25 Broad Institute employees were active on GitHub. | 
| 92. 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. | 
| 93. @Kong | (n=24) of all @Kong engineers (n=NaN0) were active on GitHub. | (n=24) of all @Kong employees (n=NaN0) were active on GitHub. | 24 24 @Kong employees were active on GitHub. | 
| 94. UCL | (n=23) of all UCL engineers (n=NaN0) were active on GitHub. | (n=23) of all UCL employees (n=NaN0) were active on GitHub. | 23 23 UCL employees were active on GitHub. | 
| 95. @sourcegraph | (n=22) of all @sourcegraph engineers (n=NaN0) were active on GitHub. | (n=22) of all @sourcegraph employees (n=NaN0) were active on GitHub. | 22 22 @sourcegraph 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. Apple Developer Academy @ POSTECH | (n=21) of all Apple Developer Academy @ POSTECH engineers (n=NaN0) were active on GitHub. | (n=21) of all Apple Developer Academy @ POSTECH employees (n=NaN0) were active on GitHub. | 21 21 Apple Developer Academy @ POSTECH employees were active on GitHub. | 
| 98. DigitalOcean | (n=21) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 2% 2% (n=21) of all DigitalOcean employees (n=1,204144) were active on GitHub. | 21 21 DigitalOcean employees were active on GitHub. | 
| 99. Trybe | (n=20) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=20) of all Trybe employees (n=NaN0) were active on GitHub. | 20 20 Trybe employees were active on GitHub. | 
| 100. @MathWorks | (n=20) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=20) of all @MathWorks employees (n=NaN0) were active on GitHub. | 20 20 @MathWorks 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)
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- HashiCorp engineer count: sec.gov (page 13)
- HashiCorp employee count: sec.gov (page 14)
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- DataDog engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 11)
- MongoDB engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 8)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- 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
- GitLab engineer count: linkedin.com
- GitLab employee count: sec.gov (page 13)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Odoo engineer count: linkedin.com
- Odoo 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)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Annual Report, page 168)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 21)
- 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)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 87)
- WIX engineer count: sec.gov (page 142, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 142)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 8)
- Unity Technologies engineer count: sec.gov (page 4, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 4)
- Twilio engineer count: sec.gov (page 7, 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 16)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Yelp engineer count: sec.gov (page 12, referred to as employees in 'product development')
- Yelp employee count: sec.gov (page 12)
- BBC engineer count: linkedin.com
- BBC employee count: downloads.bbc.co.uk (page 62)
- Lyft engineer count: sec.gov (page 11, referred to as employees in 'product management, engineering, design and science')
- Lyft employee count: sec.gov (page 11)
- Zendesk engineer count: linkedin.com
- Zendesk employee count: sec.gov (page 54)
- NVIDIA engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 12)
- 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)
- Spotify engineer count: sec.gov (page 69, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 69)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- 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)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- 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)
- 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)
- NetEase engineer count: sec.gov (page 159, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 159)
- 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)
- 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)
- Samsung engineer count: samsung.com (page 103, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 103)
- Ericsson engineer count: sec.gov (page 9, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 11)
- 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)
- Palo Alto Networks employee count: sec.gov (page 11)
- Kitware employee count: linkedin.com
- DigitalOcean employee count: sec.gov (page 13)