Corporate GitHub Activity
Most Active Corporations on GitHub, 02 2022
Ranking companies with employees who, during 02 2022, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 41% 41% (n=216) of all SUSE engineers (n=5221) were active on GitHub. | 9% 9% (n=216) of all SUSE employees (n=2,3982) were active on GitHub. | 216 216 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Grafana Labs | 36% 36% (n=125) of all Grafana Labs engineers (n=3433) were active on GitHub. | 21% 21% (n=125) of all Grafana Labs employees (n=6004) were active on GitHub. | 125 125 Grafana Labs employees were active on GitHub. | 
| 3. Mozilla | 33% 33% (n=157) of all Mozilla engineers (n=4725) were active on GitHub. | 10% 10% (n=157) of all Mozilla employees (n=1,5106) were active on GitHub. | 157 157 Mozilla employees were active on GitHub. | 
| 4. Automattic | 29% 29% (n=238) of all Automattic engineers (n=8307) were active on GitHub. | 12% 12% (n=238) of all Automattic employees (n=2,0028) were active on GitHub. | 238 238 Automattic employees were active on GitHub. | 
| 5. Elastic | 27% 27% (n=251) of all Elastic engineers (n=9149) were active on GitHub. | 9% 9% (n=251) of all Elastic employees (n=2,88610) were active on GitHub. | 251 251 Elastic employees were active on GitHub. | 
| 6. The Guardian | 23% 23% (n=29) of all The Guardian engineers (n=12711) were active on GitHub. | 1% 1% (n=29) of all The Guardian employees (n=2,30012) were active on GitHub. | 29 29 The Guardian employees were active on GitHub. | 
| 7. JetBrains | 21% 21% (n=153) of all JetBrains engineers (n=71913) were active on GitHub. | 8% 8% (n=153) of all JetBrains employees (n=1,90014) were active on GitHub. | 153 153 JetBrains employees were active on GitHub. | 
| 8. Mapbox | 17% 17% (n=45) of all Mapbox engineers (n=25815) were active on GitHub. | 7% 7% (n=45) of all Mapbox employees (n=67816) were active on GitHub. | 45 45 Mapbox employees were active on GitHub. | 
| 9. HashiCorp | 17% 17% (n=113) of all HashiCorp engineers (n=67017) were active on GitHub. | 5% 5% (n=113) of all HashiCorp employees (n=2,40018) were active on GitHub. | 113 113 HashiCorp employees were active on GitHub. | 
| 10. WikiMedia Foundation | 12% 12% (n=23) of all WikiMedia Foundation engineers (n=19419) were active on GitHub. | (n=23) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 23 23 WikiMedia Foundation employees were active on GitHub. | 
| 11. WSO2 | 10% 10% (n=81) of all WSO2 engineers (n=77520) were active on GitHub. | 7% 7% (n=81) of all WSO2 employees (n=1,16521) were active on GitHub. | 81 81 WSO2 employees were active on GitHub. | 
| 12. MongoDB | 10% 10% (n=98) of all MongoDB engineers (n=1,03022) were active on GitHub. | 2% 2% (n=98) of all MongoDB employees (n=4,61923) were active on GitHub. | 98 98 MongoDB employees were active on GitHub. | 
| 13. Cloudflare | 9% 9% (n=56) of all Cloudflare engineers (n=61024) were active on GitHub. | 2% 2% (n=56) of all Cloudflare employees (n=3,21725) were active on GitHub. | 56 56 Cloudflare employees were active on GitHub. | 
| 14. New Relic | 8% 8% (n=69) of all New Relic engineers (n=81926) were active on GitHub. | 3% 3% (n=69) of all New Relic employees (n=2,66327) were active on GitHub. | 69 69 New Relic employees were active on GitHub. | 
| 15. DataDog | 8% 8% (n=163) of all DataDog engineers (n=2,00028) were active on GitHub. | 3% 3% (n=163) of all DataDog employees (n=4,80029) were active on GitHub. | 163 163 DataDog employees were active on GitHub. | 
| 16. Liferay | 7% 7% (n=33) of all Liferay engineers (n=44430) were active on GitHub. | 3% 3% (n=33) of all Liferay employees (n=1,28931) were active on GitHub. | 33 33 Liferay employees were active on GitHub. | 
| 17. Confluent | 6% 6% (n=52) of all Confluent engineers (n=81832) were active on GitHub. | 2% 2% (n=52) of all Confluent employees (n=2,76133) were active on GitHub. | 52 52 Confluent employees were active on GitHub. | 
| 18. Odoo | 5% 5% (n=26) of all Odoo engineers (n=47434) were active on GitHub. | 2% 2% (n=26) of all Odoo employees (n=1,32735) were active on GitHub. | 26 26 Odoo employees were active on GitHub. | 
| 19. Progress Software | 5% 5% (n=41) of all Progress Software engineers (n=84236) were active on GitHub. | 2% 2% (n=41) of all Progress Software employees (n=2,07137) were active on GitHub. | 41 41 Progress Software employees were active on GitHub. | 
| 20. Microsoft | 4% 4% (n=2,739) of all Microsoft engineers (n=73,00038) were active on GitHub. | 1% 1% (n=2,739) of all Microsoft employees (n=221,00039) were active on GitHub. | 2,739 2,739 Microsoft employees were active on GitHub. | 
| 21. Shopify | 4% 4% (n=150) of all Shopify engineers (n=4,03740) were active on GitHub. | 1% 1% (n=150) of all Shopify employees (n=11,60041) were active on GitHub. | 150 150 Shopify employees were active on GitHub. | 
| 22. Alibaba | 3% 3% (n=326) of all Alibaba engineers (n=9,44042) were active on GitHub. | 0% 0% (n=326) of all Alibaba employees (n=254,94143) were active on GitHub. | 326 326 Alibaba employees were active on GitHub. | 
| 23. Square, Inc. | 3% 3% (n=63) of all Square, Inc. engineers (n=1,83144) were active on GitHub. | 1% 1% (n=63) of all Square, Inc. employees (n=12,42845) were active on GitHub. | 63 63 Square, Inc. employees were active on GitHub. | 
| 24. ESRI | 3% 3% (n=64) of all ESRI engineers (n=1,94746) were active on GitHub. | 1% 1% (n=64) of all ESRI employees (n=5,87347) were active on GitHub. | 64 64 ESRI employees were active on GitHub. | 
| 25. Okta | 3% 3% (n=43) of all Okta engineers (n=1,39248) were active on GitHub. | 1% 1% (n=43) of all Okta employees (n=6,01349) were active on GitHub. | 43 43 Okta employees were active on GitHub. | 
| 26. VMWare | 3% 3% (n=392) of all VMWare engineers (n=13,33250) were active on GitHub. | 1% 1% (n=392) of all VMWare employees (n=38,30051) were active on GitHub. | 392 392 VMWare employees were active on GitHub. | 
| 27. Unity Technologies | 3% 3% (n=100) of all Unity Technologies engineers (n=3,75352) were active on GitHub. | 1% 1% (n=100) of all Unity Technologies employees (n=7,70353) were active on GitHub. | 100 100 Unity Technologies employees were active on GitHub. | 
| 28. Twitter | 2% 2% (n=34) of all Twitter engineers (n=1,36954) were active on GitHub. | 0% 0% (n=34) of all Twitter employees (n=9,40055) were active on GitHub. | 34 34 Twitter employees were active on GitHub. | 
| 29. Netflix | 2% 2% (n=55) of all Netflix engineers (n=2,22756) were active on GitHub. | 0% 0% (n=55) of all Netflix employees (n=12,80057) were active on GitHub. | 55 55 Netflix employees were active on GitHub. | 
| 30. Splunk | 2% 2% (n=46) of all Splunk engineers (n=2,07658) were active on GitHub. | 1% 1% (n=46) of all Splunk employees (n=8,00059) were active on GitHub. | 46 46 Splunk employees were active on GitHub. | 
| 31. Amazon | 2% 2% (n=803) of all Amazon engineers (n=37,13460) were active on GitHub. | 1% 1% (n=803) of all Amazon employees (n=112,31561) were active on GitHub. | 803 803 Amazon employees were active on GitHub. | 
| 32. BBC | 2% 2% (n=32) of all BBC engineers (n=1,52162) were active on GitHub. | 0% 0% (n=32) of all BBC employees (n=21,28163) were active on GitHub. | 32 32 BBC employees were active on GitHub. | 
| 33. WIX | 2% 2% (n=45) of all WIX engineers (n=2,20664) were active on GitHub. | 1% 1% (n=45) of all WIX employees (n=4,74265) were active on GitHub. | 45 45 WIX employees were active on GitHub. | 
| 34. ThoughtWorks | 2% 2% (n=82) of all ThoughtWorks engineers (n=4,15266) were active on GitHub. | 1% 1% (n=82) of all ThoughtWorks employees (n=12,50067) were active on GitHub. | 82 82 ThoughtWorks employees were active on GitHub. | 
| 35. Zendesk | 2% 2% (n=31) of all Zendesk engineers (n=1,62068) were active on GitHub. | 0% 0% (n=31) of all Zendesk employees (n=6,44069) were active on GitHub. | 31 31 Zendesk employees were active on GitHub. | 
| 36. Tencent | 2% 2% (n=242) of all Tencent engineers (n=12,97970) were active on GitHub. | 0% 0% (n=242) of all Tencent employees (n=108,43671) were active on GitHub. | 242 242 Tencent employees were active on GitHub. | 
| 37. Arm Ltd | 2% 2% (n=87) of all Arm Ltd engineers (n=4,75872) were active on GitHub. | 1% 1% (n=87) of all Arm Ltd employees (n=6,32973) were active on GitHub. | 87 87 Arm Ltd employees were active on GitHub. | 
| 38. Stripe | 2% 2% (n=52) of all Stripe engineers (n=2,96174) were active on GitHub. | 1% 1% (n=52) of all Stripe employees (n=8,37275) were active on GitHub. | 52 52 Stripe employees were active on GitHub. | 
| 39. Twilio | 2% 2% (n=63) of all Twilio engineers (n=3,59076) were active on GitHub. | 1% 1% (n=63) of all Twilio employees (n=8,15677) were active on GitHub. | 63 63 Twilio employees were active on GitHub. | 
| 40. Google | 2% 2% (n=1,195) of all Google engineers (n=71,08478) were active on GitHub. | 1% 1% (n=1,195) of all Google employees (n=190,23479) were active on GitHub. | 1,195 1,195 Google employees were active on GitHub. | 
| 41. CyberAgent | 2% 2% (n=24) of all CyberAgent engineers (n=1,47080) were active on GitHub. | 0% 0% (n=24) of all CyberAgent employees (n=6,33781) were active on GitHub. | 24 24 CyberAgent employees were active on GitHub. | 
| 42. Zalando DE | 2% 2% (n=26) of all Zalando DE engineers (n=1,60882) were active on GitHub. | 0% 0% (n=26) of all Zalando DE employees (n=16,99983) were active on GitHub. | 26 26 Zalando DE employees were active on GitHub. | 
| 43. Lyft | 2% 2% (n=29) of all Lyft engineers (n=1,81184) were active on GitHub. | 1% 1% (n=29) of all Lyft employees (n=4,41985) were active on GitHub. | 29 29 Lyft employees were active on GitHub. | 
| 44. Adobe | 1% 1% (n=129) of all Adobe engineers (n=9,45086) were active on GitHub. | 0% 0% (n=129) of all Adobe employees (n=29,23987) were active on GitHub. | 129 129 Adobe employees were active on GitHub. | 
| 45. Airbnb | 1% 1% (n=25) of all Airbnb engineers (n=1,90088) were active on GitHub. | 0% 0% (n=25) of all Airbnb employees (n=6,81189) were active on GitHub. | 25 25 Airbnb employees were active on GitHub. | 
| 46. Spotify | 1% 1% (n=52) of all Spotify engineers (n=4,16990) were active on GitHub. | 1% 1% (n=52) of all Spotify employees (n=8,35991) were active on GitHub. | 52 52 Spotify employees were active on GitHub. | 
| 47. Uber | 1% 1% (n=57) of all Uber engineers (n=5,50292) were active on GitHub. | 0% 0% (n=57) of all Uber employees (n=32,80093) were active on GitHub. | 57 57 Uber employees were active on GitHub. | 
| 48. NVIDIA | 1% 1% (n=194) of all NVIDIA engineers (n=19,53294) were active on GitHub. | 1% 1% (n=194) of all NVIDIA employees (n=26,19695) were active on GitHub. | 194 194 NVIDIA employees were active on GitHub. | 
| 49. Atlassian | 1% 1% (n=41) of all Atlassian engineers (n=4,40696) were active on GitHub. | 0% 0% (n=41) of all Atlassian employees (n=8,81397) were active on GitHub. | 41 41 Atlassian employees were active on GitHub. | 
| 50. Salesforce | 1% 1% (n=180) of all Salesforce engineers (n=20,53798) were active on GitHub. | 0% 0% (n=180) of all Salesforce employees (n=79,39099) were active on GitHub. | 180 180 Salesforce employees were active on GitHub. | 
| 51. Meta | 1% 1% (n=296) of all Meta engineers (n=35,611100) were active on GitHub. | 0% 0% (n=296) of all Meta employees (n=86,482101) were active on GitHub. | 296 296 Meta employees were active on GitHub. | 
| 52. SAP SE | 1% 1% (n=256) of all SAP SE engineers (n=34,122102) were active on GitHub. | 0% 0% (n=256) of all SAP SE employees (n=111,961103) were active on GitHub. | 256 256 SAP SE employees were active on GitHub. | 
| 53. Autodesk | 1% 1% (n=28) of all Autodesk engineers (n=3,800104) were active on GitHub. | 0% 0% (n=28) of all Autodesk employees (n=13,700105) were active on GitHub. | 28 28 Autodesk employees were active on GitHub. | 
| 54. Intel | 1% 1% (n=375) of all Intel engineers (n=57,090106) were active on GitHub. | 0% 0% (n=375) of all Intel employees (n=131,900107) were active on GitHub. | 375 375 Intel employees were active on GitHub. | 
| 55. Yandex | 1% 1% (n=66) of all Yandex engineers (n=10,708108) were active on GitHub. | 0% 0% (n=66) of all Yandex employees (n=20,850109) were active on GitHub. | 66 66 Yandex employees were active on GitHub. | 
| 56. Bloomberg | 1% 1% (n=36) of all Bloomberg engineers (n=6,326110) were active on GitHub. | 0% 0% (n=36) of all Bloomberg employees (n=23,033111) were active on GitHub. | 36 36 Bloomberg 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. Cisco Systems | 0% 0% (n=112) of all Cisco Systems engineers (n=23,407114) were active on GitHub. | 0% 0% (n=112) of all Cisco Systems employees (n=83,300115) were active on GitHub. | 112 112 Cisco Systems employees were active on GitHub. | 
| 59. Baidu | 0% 0% (n=112) of all Baidu engineers (n=23,600116) were active on GitHub. | 0% 0% (n=112) of all Baidu employees (n=41,300117) were active on GitHub. | 112 112 Baidu employees were active on GitHub. | 
| 60. Oracle | 0% 0% (n=160) of all Oracle engineers (n=44,000118) were active on GitHub. | 0% 0% (n=160) of all Oracle employees (n=143,000119) were active on GitHub. | 160 160 Oracle employees were active on GitHub. | 
| 61. Apple | 0% 0% (n=122) of all Apple engineers (n=39,361120) were active on GitHub. | 0% 0% (n=122) of all Apple employees (n=164,000121) were active on GitHub. | 122 122 Apple employees were active on GitHub. | 
| 62. PayPal | 0% 0% (n=25) of all PayPal engineers (n=8,805122) were active on GitHub. | 0% 0% (n=25) of all PayPal employees (n=29,900123) were active on GitHub. | 25 25 PayPal employees were active on GitHub. | 
| 63. NetEase | 0% 0% (n=43) of all NetEase engineers (n=15,211124) were active on GitHub. | 0% 0% (n=43) of all NetEase employees (n=31,119125) were active on GitHub. | 43 43 NetEase employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=99) of all EPAM Systems engineers (n=52,850126) were active on GitHub. | 0% 0% (n=99) of all EPAM Systems employees (n=59,300127) were active on GitHub. | 99 99 EPAM Systems employees were active on GitHub. | 
| 65. Ericsson | 0% 0% (n=37) of all Ericsson engineers (n=29,304128) were active on GitHub. | 0% 0% (n=37) of all Ericsson employees (n=105,529129) were active on GitHub. | 37 37 Ericsson employees were active on GitHub. | 
| 66. Nokia | 0% 0% (n=21) of all Nokia engineers (n=23,836130) were active on GitHub. | 0% 0% (n=21) of all Nokia employees (n=86,896131) were active on GitHub. | 21 21 Nokia employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=70) of all Samsung engineers (n=80,496132) were active on GitHub. | 0% 0% (n=70) of all Samsung employees (n=270,372133) were active on GitHub. | 70 70 Samsung employees were active on GitHub. | 
| 68. Huawei | 0% 0% (n=68) of all Huawei engineers (n=114,000134) were active on GitHub. | 0% 0% (n=68) of all Huawei employees (n=207,000135) were active on GitHub. | 68 68 Huawei employees were active on GitHub. | 
| 69. Capgemini | 0% 0% (n=37) of all Capgemini engineers (n=69,803136) were active on GitHub. | 0% 0% (n=37) of all Capgemini employees (n=360,000137) were active on GitHub. | 37 37 Capgemini employees were active on GitHub. | 
| 70. 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,300138) were active on GitHub. | 1,594 1,594 IBM employees were active on GitHub. | 
| 71. 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. | 
| 72. Canonical | (n=76) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=76) of all Canonical employees (n=NaN0) were active on GitHub. | 76 76 Canonical employees were active on GitHub. | 
| 73. Yahoo! | (n=55) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=55) of all Yahoo! employees (n=NaN0) were active on GitHub. | 55 55 Yahoo! employees were active on GitHub. | 
| 74. Accenture | (n=54) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=54) of all Accenture employees (n=721,000139) were active on GitHub. | 54 54 Accenture employees were active on GitHub. | 
| 75. PingCAP | (n=43) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=43) of all PingCAP employees (n=NaN0) were active on GitHub. | 43 43 PingCAP employees were active on GitHub. | 
| 76. Databricks | (n=42) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=42) of all Databricks employees (n=NaN0) were active on GitHub. | 42 42 Databricks employees were active on GitHub. | 
| 77. Sentry.io | (n=41) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=41) of all Sentry.io employees (n=NaN0) were active on GitHub. | 41 41 Sentry.io employees were active on GitHub. | 
| 78. Snyk | (n=41) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=41) of all Snyk employees (n=NaN0) were active on GitHub. | 41 41 Snyk employees were active on GitHub. | 
| 79. 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. | 
| 80. Kitware | (n=32) of all Kitware engineers (n=NaN0) were active on GitHub. | 18% 18% (n=32) of all Kitware employees (n=174140) were active on GitHub. | 32 32 Kitware employees were active on GitHub. | 
| 81. CircleCI | (n=32) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=32) of all CircleCI employees (n=NaN0) were active on GitHub. | 32 32 CircleCI employees were active on GitHub. | 
| 82. 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. | 
| 83. 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=12,561141) were active on GitHub. | 28 28 Palo Alto Networks employees were active on GitHub. | 
| 84. RStudio | (n=28) of all RStudio engineers (n=NaN0) were active on GitHub. | (n=28) of all RStudio employees (n=NaN0) were active on GitHub. | 28 28 RStudio employees were active on GitHub. | 
| 85. @bytedance | (n=28) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=28) of all @bytedance employees (n=NaN0) were active on GitHub. | 28 28 @bytedance employees were active on GitHub. | 
| 86. Dynatrace | (n=27) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=27) of all Dynatrace employees (n=NaN0) were active on GitHub. | 27 27 Dynatrace employees were active on GitHub. | 
| 87. Epitech | (n=26) of all Epitech engineers (n=NaN0) were active on GitHub. | (n=26) of all Epitech employees (n=NaN0) were active on GitHub. | 26 26 Epitech employees were active on GitHub. | 
| 88. 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. | 
| 89. Intuit | (n=25) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=25) of all Intuit employees (n=17,300142) were active on GitHub. | 25 25 Intuit employees were active on GitHub. | 
| 90. 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. | 
| 91. 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. | 
| 92. Harness | (n=22) of all Harness engineers (n=NaN0) were active on GitHub. | (n=22) of all Harness employees (n=NaN0) were active on GitHub. | 22 22 Harness employees were active on GitHub. | 
| 93. DigitalOcean | (n=22) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 2% 2% (n=22) of all DigitalOcean employees (n=1,204143) were active on GitHub. | 22 22 DigitalOcean employees were active on GitHub. | 
| 94. Trybe | (n=22) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=22) of all Trybe employees (n=NaN0) were active on GitHub. | 22 22 Trybe 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. Camptocamp | (n=21) of all Camptocamp engineers (n=NaN0) were active on GitHub. | (n=21) of all Camptocamp employees (n=NaN0) were active on GitHub. | 21 21 Camptocamp employees were active on GitHub. | 
| 97. 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. | 
| 98. TU Delft | (n=20) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=20) of all TU Delft employees (n=NaN0) were active on GitHub. | 20 20 TU Delft employees were active on GitHub. | 
| 99. Orange S.A. | (n=20) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=20) of all Orange S.A. employees (n=130,307144) were active on GitHub. | 20 20 Orange S.A. employees were active on GitHub. | 
| 100. @woowabros | (n=19) of all @woowabros engineers (n=NaN0) were active on GitHub. | (n=19) of all @woowabros employees (n=NaN0) were active on GitHub. | 19 19 @woowabros employees were active on GitHub. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: ir.suse.com (Annual Report FY22, page 249)
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- 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)
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- HashiCorp engineer count: sec.gov (page 13)
- HashiCorp employee count: sec.gov (page 14)
- WikiMedia Foundation engineer count: linkedin.com
- WSO2 engineer count: linkedin.com
- WSO2 employee 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)
- New Relic engineer count: linkedin.com
- New Relic 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)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Progress Software engineer count: sec.gov (page 8, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 8)
- Microsoft engineer count: sec.gov (page 8, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 8)
- Shopify engineer count: linkedin.com
- Shopify employee count: s27.q4cdn.com (page 23)
- 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)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Unity Technologies engineer count: sec.gov (page 4, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 4)
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- BBC engineer count: linkedin.com
- BBC employee count: downloads.bbc.co.uk (page 62)
- WIX engineer count: sec.gov (page 142, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 142)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Zendesk engineer count: linkedin.com
- Zendesk employee count: sec.gov (page 54)
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 87)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Twilio engineer count: sec.gov (page 7, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 8)
- CyberAgent engineer count: d2utiq8et4vl56.cloudfront.net (page 80)
- CyberAgent employee count: d2utiq8et4vl56.cloudfront.net (page 80)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- 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)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 16)
- Airbnb engineer count: sec.gov (page 4)
- Airbnb employee count: sec.gov (page 4)
- 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)
- 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)
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 10)
- 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)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 12)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- Yandex engineer count: sec.gov (page 48, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 48)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Cisco Systems engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 11)
- Baidu engineer count: sec.gov (page 197, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 197)
- 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)
- NetEase engineer count: sec.gov (page 159, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 159)
- 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)
- Nokia engineer count: linkedin.com
- Nokia employee count: sec.gov (page 86)
- 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)
- Intuit employee count: sec.gov (page 12)
- DigitalOcean employee count: sec.gov (page 13)
- Orange S.A. employee count: gallery.orange.com (page 57)