Corporate GitHub Activity
Most Active Corporations on GitHub, 05 2021
Ranking companies with employees who, during 05 2021, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 33% 33% (n=159) of all SUSE engineers (n=4751) were active on GitHub. | 8% 8% (n=159) of all SUSE employees (n=2,0452) were active on GitHub. | 159 159 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Grafana Labs | 31% 31% (n=74) of all Grafana Labs engineers (n=2403) were active on GitHub. | 19% 19% (n=74) of all Grafana Labs employees (n=4004) were active on GitHub. | 74 74 Grafana Labs employees were active on GitHub. | 
| 3. Automattic | 31% 31% (n=205) of all Automattic engineers (n=6655) were active on GitHub. | 12% 12% (n=205) of all Automattic employees (n=1,7006) were active on GitHub. | 205 205 Automattic employees were active on GitHub. | 
| 4. Mozilla | 27% 27% (n=147) of all Mozilla engineers (n=5477) were active on GitHub. | 11% 11% (n=147) of all Mozilla employees (n=1,3858) were active on GitHub. | 147 147 Mozilla employees were active on GitHub. | 
| 5. JetBrains | 26% 26% (n=151) of all JetBrains engineers (n=5759) were active on GitHub. | 8% 8% (n=151) of all JetBrains employees (n=1,90010) were active on GitHub. | 151 151 JetBrains employees were active on GitHub. | 
| 6. HashiCorp | 24% 24% (n=120) of all HashiCorp engineers (n=50011) were active on GitHub. | 6% 6% (n=120) of all HashiCorp employees (n=1,85012) were active on GitHub. | 120 120 HashiCorp employees were active on GitHub. | 
| 7. Elastic | 23% 23% (n=211) of all Elastic engineers (n=90513) were active on GitHub. | 7% 7% (n=211) of all Elastic employees (n=2,97814) were active on GitHub. | 211 211 Elastic employees were active on GitHub. | 
| 8. The Guardian | 21% 21% (n=24) of all The Guardian engineers (n=11215) were active on GitHub. | 1% 1% (n=24) of all The Guardian employees (n=2,13016) were active on GitHub. | 24 24 The Guardian employees were active on GitHub. | 
| 9. Odoo | 19% 19% (n=71) of all Odoo engineers (n=37917) were active on GitHub. | 8% 8% (n=71) of all Odoo employees (n=94518) were active on GitHub. | 71 71 Odoo employees were active on GitHub. | 
| 10. WikiMedia Foundation | 16% 16% (n=29) of all WikiMedia Foundation engineers (n=18519) were active on GitHub. | (n=29) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 29 29 WikiMedia Foundation employees were active on GitHub. | 
| 11. Mapbox | 16% 16% (n=39) of all Mapbox engineers (n=25020) were active on GitHub. | 6% 6% (n=39) of all Mapbox employees (n=60121) were active on GitHub. | 39 39 Mapbox employees were active on GitHub. | 
| 12. DataDog | 10% 10% (n=140) of all DataDog engineers (n=1,40022) were active on GitHub. | 4% 4% (n=140) of all DataDog employees (n=3,20023) were active on GitHub. | 140 140 DataDog employees were active on GitHub. | 
| 13. MongoDB | 9% 9% (n=81) of all MongoDB engineers (n=86324) were active on GitHub. | 2% 2% (n=81) of all MongoDB employees (n=3,54425) were active on GitHub. | 81 81 MongoDB employees were active on GitHub. | 
| 14. Cloudflare | 9% 9% (n=49) of all Cloudflare engineers (n=52626) were active on GitHub. | 2% 2% (n=49) of all Cloudflare employees (n=2,44027) were active on GitHub. | 49 49 Cloudflare employees were active on GitHub. | 
| 15. WSO2 | 8% 8% (n=70) of all WSO2 engineers (n=85028) were active on GitHub. | 7% 7% (n=70) of all WSO2 employees (n=97829) were active on GitHub. | 70 70 WSO2 employees were active on GitHub. | 
| 16. New Relic | 8% 8% (n=57) of all New Relic engineers (n=74430) were active on GitHub. | 3% 3% (n=57) of all New Relic employees (n=2,21731) were active on GitHub. | 57 57 New Relic employees were active on GitHub. | 
| 17. Confluent | 7% 7% (n=49) of all Confluent engineers (n=65932) were active on GitHub. | 2% 2% (n=49) of all Confluent employees (n=1,98133) were active on GitHub. | 49 49 Confluent employees were active on GitHub. | 
| 18. Liferay | 5% 5% (n=23) of all Liferay engineers (n=43134) were active on GitHub. | 2% 2% (n=23) of all Liferay employees (n=1,19235) were active on GitHub. | 23 23 Liferay employees were active on GitHub. | 
| 19. Microsoft | 4% 4% (n=2,651) of all Microsoft engineers (n=60,00036) were active on GitHub. | 1% 1% (n=2,651) of all Microsoft employees (n=181,00037) were active on GitHub. | 2,651 2,651 Microsoft employees were active on GitHub. | 
| 20. Okta | 4% 4% (n=54) of all Okta engineers (n=1,23138) were active on GitHub. | 1% 1% (n=54) of all Okta employees (n=5,03039) were active on GitHub. | 54 54 Okta employees were active on GitHub. | 
| 21. Unity Technologies | 4% 4% (n=113) of all Unity Technologies engineers (n=2,77640) were active on GitHub. | 2% 2% (n=113) of all Unity Technologies employees (n=5,24541) were active on GitHub. | 113 113 Unity Technologies employees were active on GitHub. | 
| 22. Square, Inc. | 3% 3% (n=56) of all Square, Inc. engineers (n=1,62142) were active on GitHub. | 1% 1% (n=56) of all Square, Inc. employees (n=8,52143) were active on GitHub. | 56 56 Square, Inc. employees were active on GitHub. | 
| 23. Progress Software | 3% 3% (n=28) of all Progress Software engineers (n=81844) were active on GitHub. | 1% 1% (n=28) of all Progress Software employees (n=2,10345) were active on GitHub. | 28 28 Progress Software employees were active on GitHub. | 
| 24. ESRI | 3% 3% (n=55) of all ESRI engineers (n=1,82046) were active on GitHub. | 1% 1% (n=55) of all ESRI employees (n=5,42947) were active on GitHub. | 55 55 ESRI employees were active on GitHub. | 
| 25. Shopify | 3% 3% (n=130) of all Shopify engineers (n=4,36048) were active on GitHub. | 1% 1% (n=130) of all Shopify employees (n=10,00049) were active on GitHub. | 130 130 Shopify employees were active on GitHub. | 
| 26. ThoughtWorks | 3% 3% (n=96) of all ThoughtWorks engineers (n=3,65850) were active on GitHub. | 1% 1% (n=96) of all ThoughtWorks employees (n=10,60051) were active on GitHub. | 96 96 ThoughtWorks employees were active on GitHub. | 
| 27. Alibaba | 3% 3% (n=242) of all Alibaba engineers (n=9,25552) were active on GitHub. | 0% 0% (n=242) of all Alibaba employees (n=251,46253) were active on GitHub. | 242 242 Alibaba employees were active on GitHub. | 
| 28. VMWare | 3% 3% (n=357) of all VMWare engineers (n=13,96554) were active on GitHub. | 1% 1% (n=357) of all VMWare employees (n=37,50055) were active on GitHub. | 357 357 VMWare employees were active on GitHub. | 
| 29. Netflix | 2% 2% (n=53) of all Netflix engineers (n=2,12156) were active on GitHub. | 0% 0% (n=53) of all Netflix employees (n=11,30057) were active on GitHub. | 53 53 Netflix employees were active on GitHub. | 
| 30. Splunk | 2% 2% (n=49) of all Splunk engineers (n=2,11858) were active on GitHub. | 1% 1% (n=49) of all Splunk employees (n=7,00059) were active on GitHub. | 49 49 Splunk employees were active on GitHub. | 
| 31. WIX | 2% 2% (n=54) of all WIX engineers (n=2,34960) were active on GitHub. | 1% 1% (n=54) of all WIX employees (n=5,05761) were active on GitHub. | 54 54 WIX employees were active on GitHub. | 
| 32. Amazon | 2% 2% (n=733) of all Amazon engineers (n=38,27762) were active on GitHub. | 1% 1% (n=733) of all Amazon employees (n=85,26663) were active on GitHub. | 733 733 Amazon employees were active on GitHub. | 
| 33. Tencent | 2% 2% (n=217) of all Tencent engineers (n=11,57264) were active on GitHub. | 0% 0% (n=217) of all Tencent employees (n=112,77165) were active on GitHub. | 217 217 Tencent employees were active on GitHub. | 
| 34. Google | 2% 2% (n=1,156) of all Google engineers (n=62,37766) were active on GitHub. | 1% 1% (n=1,156) of all Google employees (n=156,50067) were active on GitHub. | 1,156 1,156 Google employees were active on GitHub. | 
| 35. Zendesk | 2% 2% (n=30) of all Zendesk engineers (n=1,65068) were active on GitHub. | 1% 1% (n=30) of all Zendesk employees (n=5,86069) were active on GitHub. | 30 30 Zendesk employees were active on GitHub. | 
| 36. Zalando DE | 2% 2% (n=28) of all Zalando DE engineers (n=1,54670) were active on GitHub. | 0% 0% (n=28) of all Zalando DE employees (n=17,04371) were active on GitHub. | 28 28 Zalando DE employees were active on GitHub. | 
| 37. Spotify | 2% 2% (n=54) of all Spotify engineers (n=3,17572) were active on GitHub. | 1% 1% (n=54) of all Spotify employees (n=6,61773) were active on GitHub. | 54 54 Spotify employees were active on GitHub. | 
| 38. Airbnb | 2% 2% (n=26) of all Airbnb engineers (n=1,67574) were active on GitHub. | 0% 0% (n=26) of all Airbnb employees (n=6,13275) were active on GitHub. | 26 26 Airbnb employees were active on GitHub. | 
| 39. Lyft | 2% 2% (n=27) of all Lyft engineers (n=1,78176) were active on GitHub. | 1% 1% (n=27) of all Lyft employees (n=4,45377) were active on GitHub. | 27 27 Lyft employees were active on GitHub. | 
| 40. Stripe | 2% 2% (n=46) of all Stripe engineers (n=3,05078) were active on GitHub. | 1% 1% (n=46) of all Stripe employees (n=4,65379) were active on GitHub. | 46 46 Stripe employees were active on GitHub. | 
| 41. BBC | 1% 1% (n=20) of all BBC engineers (n=1,35880) were active on GitHub. | 0% 0% (n=20) of all BBC employees (n=22,21981) were active on GitHub. | 20 20 BBC employees were active on GitHub. | 
| 42. Twilio | 1% 1% (n=45) of all Twilio engineers (n=3,10382) were active on GitHub. | 1% 1% (n=45) of all Twilio employees (n=7,86783) were active on GitHub. | 45 45 Twilio employees were active on GitHub. | 
| 43. Adobe | 1% 1% (n=137) of all Adobe engineers (n=9,60184) were active on GitHub. | 1% 1% (n=137) of all Adobe employees (n=25,98885) were active on GitHub. | 137 137 Adobe employees were active on GitHub. | 
| 44. Booking.com | 1% 1% (n=20) of all Booking.com engineers (n=1,48986) were active on GitHub. | 0% 0% (n=20) of all Booking.com employees (n=20,30087) were active on GitHub. | 20 20 Booking.com employees were active on GitHub. | 
| 45. Atlassian | 1% 1% (n=42) of all Atlassian engineers (n=3,21688) were active on GitHub. | 1% 1% (n=42) of all Atlassian employees (n=6,43389) were active on GitHub. | 42 42 Atlassian employees were active on GitHub. | 
| 46. Twitter | 1% 1% (n=29) of all Twitter engineers (n=2,42490) were active on GitHub. | 0% 0% (n=29) of all Twitter employees (n=8,20091) were active on GitHub. | 29 29 Twitter employees were active on GitHub. | 
| 47. Uber | 1% 1% (n=57) of all Uber engineers (n=4,78492) were active on GitHub. | 0% 0% (n=57) of all Uber employees (n=29,30093) were active on GitHub. | 57 57 Uber employees were active on GitHub. | 
| 48. NVIDIA | 1% 1% (n=190) of all NVIDIA engineers (n=16,24294) were active on GitHub. | 1% 1% (n=190) of all NVIDIA employees (n=22,47395) were active on GitHub. | 190 190 NVIDIA employees were active on GitHub. | 
| 49. Autodesk | 1% 1% (n=38) of all Autodesk engineers (n=3,51996) were active on GitHub. | 0% 0% (n=38) of all Autodesk employees (n=11,50097) were active on GitHub. | 38 38 Autodesk employees were active on GitHub. | 
| 50. Indeed | 1% 1% (n=18) of all Indeed engineers (n=2,15598) were active on GitHub. | 0% 0% (n=18) of all Indeed employees (n=12,70999) were active on GitHub. | 18 18 Indeed employees were active on GitHub. | 
| 51. Salesforce | 1% 1% (n=177) of all Salesforce engineers (n=21,359100) were active on GitHub. | 0% 0% (n=177) of all Salesforce employees (n=73,541101) were active on GitHub. | 177 177 Salesforce employees were active on GitHub. | 
| 52. SAP SE | 1% 1% (n=261) of all SAP SE engineers (n=32,244102) were active on GitHub. | 0% 0% (n=261) of all SAP SE employees (n=107,415103) were active on GitHub. | 261 261 SAP SE employees were active on GitHub. | 
| 53. CyberAgent | 1% 1% (n=19) of all CyberAgent engineers (n=2,549104) were active on GitHub. | 0% 0% (n=19) of all CyberAgent employees (n=5,944105) were active on GitHub. | 19 19 CyberAgent employees were active on GitHub. | 
| 54. Bloomberg | 1% 1% (n=34) of all Bloomberg engineers (n=5,316106) were active on GitHub. | 0% 0% (n=34) of all Bloomberg employees (n=21,559107) were active on GitHub. | 34 34 Bloomberg employees were active on GitHub. | 
| 55. Yandex | 1% 1% (n=57) of all Yandex engineers (n=9,192108) were active on GitHub. | 0% 0% (n=57) of all Yandex employees (n=18,004109) were active on GitHub. | 57 57 Yandex employees were active on GitHub. | 
| 56. Intel | 1% 1% (n=350) of all Intel engineers (n=61,806110) were active on GitHub. | 0% 0% (n=350) of all Intel employees (n=121,100111) were active on GitHub. | 350 350 Intel employees were active on GitHub. | 
| 57. AMD | 0% 0% (n=47) of all AMD engineers (n=10,749112) were active on GitHub. | 0% 0% (n=47) of all AMD employees (n=15,500113) were active on GitHub. | 47 47 AMD employees were active on GitHub. | 
| 58. Baidu | 0% 0% (n=99) of all Baidu engineers (n=27,500114) were active on GitHub. | 0% 0% (n=99) of all Baidu employees (n=45,500115) were active on GitHub. | 99 99 Baidu employees were active on GitHub. | 
| 59. Oracle | 0% 0% (n=131) of all Oracle engineers (n=40,000116) were active on GitHub. | 0% 0% (n=131) of all Oracle employees (n=132,000117) were active on GitHub. | 131 131 Oracle employees were active on GitHub. | 
| 60. Cisco Systems | 0% 0% (n=77) of all Cisco Systems engineers (n=23,532118) were active on GitHub. | 0% 0% (n=77) of all Cisco Systems employees (n=79,500119) were active on GitHub. | 77 77 Cisco Systems employees were active on GitHub. | 
| 61. Apple | 0% 0% (n=96) of all Apple engineers (n=33,076120) were active on GitHub. | 0% 0% (n=96) of all Apple employees (n=154,000121) were active on GitHub. | 96 96 Apple employees were active on GitHub. | 
| 62. PayPal | 0% 0% (n=26) of all PayPal engineers (n=9,157122) were active on GitHub. | 0% 0% (n=26) of all PayPal employees (n=30,900123) were active on GitHub. | 26 26 PayPal employees were active on GitHub. | 
| 63. NetEase | 0% 0% (n=43) of all NetEase engineers (n=15,292124) were active on GitHub. | 0% 0% (n=43) of all NetEase employees (n=32,064125) were active on GitHub. | 43 43 NetEase employees were active on GitHub. | 
| 64. EPAM Systems | 0% 0% (n=94) of all EPAM Systems engineers (n=52,617126) were active on GitHub. | 0% 0% (n=94) of all EPAM Systems employees (n=58,824127) were active on GitHub. | 94 94 EPAM Systems employees were active on GitHub. | 
| 65. Ericsson | 0% 0% (n=34) of all Ericsson engineers (n=27,379128) were active on GitHub. | 0% 0% (n=34) of all Ericsson employees (n=101,322129) were active on GitHub. | 34 34 Ericsson employees were active on GitHub. | 
| 66. Nokia | 0% 0% (n=25) of all Nokia engineers (n=22,030130) were active on GitHub. | 0% 0% (n=25) of all Nokia employees (n=87,927131) were active on GitHub. | 25 25 Nokia employees were active on GitHub. | 
| 67. Samsung | 0% 0% (n=66) of all Samsung engineers (n=75,229132) were active on GitHub. | 0% 0% (n=66) of all Samsung employees (n=266,673133) were active on GitHub. | 66 66 Samsung employees were active on GitHub. | 
| 68. Huawei | 0% 0% (n=66) of all Huawei engineers (n=107,000134) were active on GitHub. | 0% 0% (n=66) of all Huawei employees (n=195,000135) were active on GitHub. | 66 66 Huawei employees were active on GitHub. | 
| 69. Capgemini | 0% 0% (n=29) of all Capgemini engineers (n=67,119136) were active on GitHub. | 0% 0% (n=29) of all Capgemini employees (n=325,000137) were active on GitHub. | 29 29 Capgemini employees were active on GitHub. | 
| 70. IBM | (n=1,457) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,457) of all IBM employees (n=282,100138) were active on GitHub. | 1,457 1,457 IBM employees were active on GitHub. | 
| 71. Facebook | (n=263) of all Facebook engineers (n=NaN0) were active on GitHub. | 0% 0% (n=263) of all Facebook employees (n=71,970139) were active on GitHub. | 263 263 Facebook employees were active on GitHub. | 
| 72. Arm Ltd | (n=89) of all Arm Ltd engineers (n=NaN0) were active on GitHub. | (n=89) of all Arm Ltd employees (n=NaN0) were active on GitHub. | 89 89 Arm Ltd employees were active on GitHub. | 
| 73. ByteDance | (n=89) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=89) of all ByteDance employees (n=NaN0) were active on GitHub. | 89 89 ByteDance employees were active on GitHub. | 
| 74. Canonical | (n=70) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=70) of all Canonical employees (n=NaN0) were active on GitHub. | 70 70 Canonical employees were active on GitHub. | 
| 75. Accenture | (n=62) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=62) of all Accenture employees (n=624,000140) were active on GitHub. | 62 62 Accenture employees were active on GitHub. | 
| 76. Yahoo! | (n=43) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=43) of all Yahoo! employees (n=NaN0) were active on GitHub. | 43 43 Yahoo! employees were active on GitHub. | 
| 77. PingCAP | (n=42) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=42) of all PingCAP employees (n=NaN0) were active on GitHub. | 42 42 PingCAP employees were active on GitHub. | 
| 78. Intuit | (n=35) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=35) of all Intuit employees (n=13,500141) were active on GitHub. | 35 35 Intuit employees were active on GitHub. | 
| 79. Sentry.io | (n=33) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=33) of all Sentry.io employees (n=NaN0) were active on GitHub. | 33 33 Sentry.io employees were active on GitHub. | 
| 80. Snyk | (n=33) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=33) of all Snyk employees (n=NaN0) were active on GitHub. | 33 33 Snyk employees were active on GitHub. | 
| 81. Databricks | (n=31) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=31) of all Databricks employees (n=NaN0) were active on GitHub. | 31 31 Databricks employees were active on GitHub. | 
| 82. Trybe | (n=31) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=31) of all Trybe employees (n=NaN0) were active on GitHub. | 31 31 Trybe employees were active on GitHub. | 
| 83. Kitware | (n=31) of all Kitware engineers (n=NaN0) were active on GitHub. | 19% 19% (n=31) of all Kitware employees (n=163142) were active on GitHub. | 31 31 Kitware employees were active on GitHub. | 
| 84. Palo Alto Networks | (n=30) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=30) of all Palo Alto Networks employees (n=10,473143) were active on GitHub. | 30 30 Palo Alto Networks employees were active on GitHub. | 
| 85. Puppet Labs | (n=27) of all Puppet Labs engineers (n=NaN0) were active on GitHub. | (n=27) of all Puppet Labs employees (n=NaN0) were active on GitHub. | 27 27 Puppet Labs employees were active on GitHub. | 
| 86. DigitalOcean | (n=25) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 3% 3% (n=25) of all DigitalOcean employees (n=786144) were active on GitHub. | 25 25 DigitalOcean employees were active on GitHub. | 
| 87. Cloudera | (n=25) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=25) of all Cloudera employees (n=NaN0) were active on GitHub. | 25 25 Cloudera employees were active on GitHub. | 
| 88. Broad Institute | (n=24) of all Broad Institute engineers (n=NaN0) were active on GitHub. | (n=24) of all Broad Institute employees (n=NaN0) were active on GitHub. | 24 24 Broad Institute employees were active on GitHub. | 
| 89. RStudio | (n=24) of all RStudio engineers (n=NaN0) were active on GitHub. | (n=24) of all RStudio employees (n=NaN0) were active on GitHub. | 24 24 RStudio employees were active on GitHub. | 
| 90. Dynatrace | (n=24) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=24) of all Dynatrace employees (n=NaN0) were active on GitHub. | 24 24 Dynatrace employees were active on GitHub. | 
| 91. Ascensio System SIA | (n=23) of all Ascensio System SIA engineers (n=NaN0) were active on GitHub. | (n=23) of all Ascensio System SIA employees (n=NaN0) were active on GitHub. | 23 23 Ascensio System SIA employees were active on GitHub. | 
| 92. Software Mansion | (n=23) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=23) of all Software Mansion employees (n=NaN0) were active on GitHub. | 23 23 Software Mansion employees were active on GitHub. | 
| 93. Talend | (n=22) of all Talend engineers (n=NaN0) were active on GitHub. | (n=22) of all Talend employees (n=NaN0) were active on GitHub. | 22 22 Talend employees were active on GitHub. | 
| 94. MIPT | (n=21) of all MIPT engineers (n=NaN0) were active on GitHub. | (n=21) of all MIPT employees (n=NaN0) were active on GitHub. | 21 21 MIPT employees were active on GitHub. | 
| 95. HERE Technologies | (n=21) of all HERE Technologies engineers (n=NaN0) were active on GitHub. | (n=21) of all HERE Technologies employees (n=NaN0) were active on GitHub. | 21 21 HERE Technologies employees were active on GitHub. | 
| 96. Akeneo | (n=19) of all Akeneo engineers (n=NaN0) were active on GitHub. | (n=19) of all Akeneo employees (n=NaN0) were active on GitHub. | 19 19 Akeneo employees were active on GitHub. | 
| 97. App Academy (@appacademy) | (n=19) of all App Academy (@appacademy) engineers (n=NaN0) were active on GitHub. | (n=19) of all App Academy (@appacademy) employees (n=NaN0) were active on GitHub. | 19 19 App Academy (@appacademy) employees were active on GitHub. | 
| 98. Tata Consultancy Services | (n=19) of all Tata Consultancy Services engineers (n=NaN0) were active on GitHub. | (n=19) of all Tata Consultancy Services employees (n=NaN0) were active on GitHub. | 19 19 Tata Consultancy Services employees were active on GitHub. | 
| 99. TU Delft | (n=19) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=19) of all TU Delft employees (n=NaN0) were active on GitHub. | 19 19 TU Delft employees were active on GitHub. | 
| 100. @paritytech | (n=19) of all @paritytech engineers (n=NaN0) were active on GitHub. | (n=19) of all @paritytech employees (n=NaN0) were active on GitHub. | 19 19 @paritytech employees were active on GitHub. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: ir.suse.com (Annual Report FY21, page 228)
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved March 2022)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 14)
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- Mapbox engineer count: linkedin.com
- Mapbox 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)
- 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 16)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- New Relic engineer count: linkedin.com
- New Relic employee count: sec.gov (page 8)
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 14)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Microsoft engineer count: sec.gov (page 8, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 8)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- Unity Technologies engineer count: sec.gov (page 11, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 11)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 13)
- Progress Software engineer count: sec.gov (page 9, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 9)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Shopify engineer count: linkedin.com
- Shopify employee count: s27.q4cdn.com (page 22)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Annual Report, page 168)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 14)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 12)
- WIX engineer count: sec.gov (page 139, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 139)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 75)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 9)
- Zendesk engineer count: sec.gov (page 9, referred to as employees in 'research and development')
- Zendesk employee count: sec.gov (page 54)
- 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)
- Airbnb engineer count: sec.gov (page 5)
- Airbnb employee count: sec.gov (page 6)
- Lyft engineer count: sec.gov (page 12, referred to as employees in 'product management, engineering, design and science')
- Lyft employee count: sec.gov (page 12)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- BBC engineer count: linkedin.com
- BBC employee count: downloads.bbc.co.uk (page 53)
- Twilio engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 12)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 16)
- Booking.com engineer count: linkedin.com
- Booking.com 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 78)
- Twitter engineer count: linkedin.com
- Twitter employee count: sec.gov (page 11)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 13)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 9)
- SAP SE engineer count: sec.gov (page F-22, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 84)
- CyberAgent engineer count: d2utiq8et4vl56.cloudfront.net (page 30, referred to as 'engineers and creators')
- CyberAgent employee count: d2utiq8et4vl56.cloudfront.net (page 127)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Yandex engineer count: sec.gov (page 50, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 50)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 13)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Baidu engineer count: sec.gov (page 185, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 185)
- Oracle engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 14)
- Cisco Systems engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 10)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- NetEase engineer count: sec.gov (page 146, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 146)
- EPAM Systems engineer count: sec.gov (page 5, referred to as 'core information technology professionals as well as designers, consultants and scientists')
- 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 8)
- Nokia engineer count: linkedin.com
- Nokia employee count: sec.gov (page 61)
- 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 72, 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 3)
- IBM employee count: ibm.com (page 15)
- Facebook employee count: sec.gov (page 10)
- Accenture employee count: sec.gov (page 21)
- Intuit employee count: sec.gov (page 14)
- Kitware employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- DigitalOcean employee count: sec.gov (page 15)