Corporate GitHub Activity
Most Active Corporations on GitHub, 10 2022
Ranking companies with employees who, during 10 2022, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Grafana Labs | 48% 48% (n=166) of all Grafana Labs engineers (n=3431) were active on GitHub. | 28% 28% (n=166) of all Grafana Labs employees (n=6002) were active on GitHub. | 166 166 Grafana Labs employees were active on GitHub. | 
|---|---|---|---|
| 2. SUSE | 39% 39% (n=204) of all SUSE engineers (n=5223) were active on GitHub. | 9% 9% (n=204) of all SUSE employees (n=2,3984) were active on GitHub. | 204 204 SUSE employees were active on GitHub. | 
| 3. Mozilla | 34% 34% (n=161) of all Mozilla engineers (n=4725) were active on GitHub. | 11% 11% (n=161) of all Mozilla employees (n=1,5106) were active on GitHub. | 161 161 Mozilla employees were active on GitHub. | 
| 4. Docker | 34% 34% (n=34) of all Docker engineers (n=1017) were active on GitHub. | 8% 8% (n=34) of all Docker employees (n=4358) were active on GitHub. | 34 34 Docker employees were active on GitHub. | 
| 5. Automattic | 33% 33% (n=272) of all Automattic engineers (n=8309) were active on GitHub. | 14% 14% (n=272) of all Automattic employees (n=2,00210) were active on GitHub. | 272 272 Automattic employees were active on GitHub. | 
| 6. The Guardian | 29% 29% (n=37) of all The Guardian engineers (n=12711) were active on GitHub. | 2% 2% (n=37) of all The Guardian employees (n=2,30012) were active on GitHub. | 37 37 The Guardian employees were active on GitHub. | 
| 7. Elastic | 28% 28% (n=253) of all Elastic engineers (n=91413) were active on GitHub. | 9% 9% (n=253) of all Elastic employees (n=2,88614) were active on GitHub. | 253 253 Elastic employees were active on GitHub. | 
| 8. HashiCorp | 26% 26% (n=171) of all HashiCorp engineers (n=67015) were active on GitHub. | 7% 7% (n=171) of all HashiCorp employees (n=2,40016) were active on GitHub. | 171 171 HashiCorp employees were active on GitHub. | 
| 9. Odoo | 23% 23% (n=107) of all Odoo engineers (n=47417) were active on GitHub. | 8% 8% (n=107) of all Odoo employees (n=1,32718) were active on GitHub. | 107 107 Odoo employees were active on GitHub. | 
| 10. JetBrains | 21% 21% (n=149) of all JetBrains engineers (n=71919) were active on GitHub. | 8% 8% (n=149) of all JetBrains employees (n=1,90020) were active on GitHub. | 149 149 JetBrains employees were active on GitHub. | 
| 11. Mapbox | 14% 14% (n=37) of all Mapbox engineers (n=25821) were active on GitHub. | 5% 5% (n=37) of all Mapbox employees (n=67822) were active on GitHub. | 37 37 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. MongoDB | 11% 11% (n=111) of all MongoDB engineers (n=1,03024) were active on GitHub. | 2% 2% (n=111) of all MongoDB employees (n=4,61925) were active on GitHub. | 111 111 MongoDB employees were active on GitHub. | 
| 14. Cloudflare | 10% 10% (n=58) of all Cloudflare engineers (n=61026) were active on GitHub. | 2% 2% (n=58) of all Cloudflare employees (n=3,21727) were active on GitHub. | 58 58 Cloudflare employees were active on GitHub. | 
| 15. WSO2 | 9% 9% (n=72) of all WSO2 engineers (n=77528) were active on GitHub. | 6% 6% (n=72) of all WSO2 employees (n=1,16529) were active on GitHub. | 72 72 WSO2 employees were active on GitHub. | 
| 16. DataDog | 9% 9% (n=185) of all DataDog engineers (n=2,00030) were active on GitHub. | 4% 4% (n=185) of all DataDog employees (n=4,80031) were active on GitHub. | 185 185 DataDog employees were active on GitHub. | 
| 17. New Relic | 8% 8% (n=65) of all New Relic engineers (n=81932) were active on GitHub. | 2% 2% (n=65) of all New Relic employees (n=2,66333) were active on GitHub. | 65 65 New Relic employees were active on GitHub. | 
| 18. Liferay | 7% 7% (n=29) of all Liferay engineers (n=44434) were active on GitHub. | 2% 2% (n=29) of all Liferay employees (n=1,28935) were active on GitHub. | 29 29 Liferay employees were active on GitHub. | 
| 19. Confluent | 6% 6% (n=45) of all Confluent engineers (n=81836) were active on GitHub. | 2% 2% (n=45) of all Confluent employees (n=2,76137) were active on GitHub. | 45 45 Confluent employees were active on GitHub. | 
| 20. ESRI | 4% 4% (n=82) of all ESRI engineers (n=1,94738) were active on GitHub. | 1% 1% (n=82) of all ESRI employees (n=5,87339) were active on GitHub. | 82 82 ESRI employees were active on GitHub. | 
| 21. Progress Software | 4% 4% (n=35) of all Progress Software engineers (n=84240) were active on GitHub. | 2% 2% (n=35) of all Progress Software employees (n=2,07141) were active on GitHub. | 35 35 Progress Software employees were active on GitHub. | 
| 22. Shopify | 4% 4% (n=164) of all Shopify engineers (n=4,03742) were active on GitHub. | 1% 1% (n=164) of all Shopify employees (n=11,60043) were active on GitHub. | 164 164 Shopify employees were active on GitHub. | 
| 23. Microsoft | 4% 4% (n=2,866) of all Microsoft engineers (n=73,00044) were active on GitHub. | 1% 1% (n=2,866) of all Microsoft employees (n=221,00045) were active on GitHub. | 2,866 2,866 Microsoft employees were active on GitHub. | 
| 24. Square, Inc. | 3% 3% (n=58) of all Square, Inc. engineers (n=1,83146) were active on GitHub. | 0% 0% (n=58) of all Square, Inc. employees (n=12,42847) were active on GitHub. | 58 58 Square, Inc. employees were active on GitHub. | 
| 25. Alibaba | 3% 3% (n=293) of all Alibaba engineers (n=9,44048) were active on GitHub. | 0% 0% (n=293) of all Alibaba employees (n=254,94149) were active on GitHub. | 293 293 Alibaba employees were active on GitHub. | 
| 26. Okta | 3% 3% (n=43) of all Okta engineers (n=1,39250) were active on GitHub. | 1% 1% (n=43) of all Okta employees (n=6,01351) were active on GitHub. | 43 43 Okta employees were active on GitHub. | 
| 27. Snowflake, Inc. | 3% 3% (n=41) of all Snowflake, Inc. engineers (n=1,37852) were active on GitHub. | 1% 1% (n=41) of all Snowflake, Inc. employees (n=5,88453) were active on GitHub. | 41 41 Snowflake, Inc. employees were active on GitHub. | 
| 28. VMWare | 3% 3% (n=387) of all VMWare engineers (n=13,33254) were active on GitHub. | 1% 1% (n=387) of all VMWare employees (n=38,30055) were active on GitHub. | 387 387 VMWare employees were active on GitHub. | 
| 29. Twitter | 3% 3% (n=39) of all Twitter engineers (n=1,36956) were active on GitHub. | 0% 0% (n=39) of all Twitter employees (n=9,40057) were active on GitHub. | 39 39 Twitter employees were active on GitHub. | 
| 30. ThoughtWorks | 3% 3% (n=110) of all ThoughtWorks engineers (n=4,15258) were active on GitHub. | 1% 1% (n=110) of all ThoughtWorks employees (n=12,50059) were active on GitHub. | 110 110 ThoughtWorks employees were active on GitHub. | 
| 31. Amazon | 3% 3% (n=979) of all Amazon engineers (n=37,13460) were active on GitHub. | 1% 1% (n=979) of all Amazon employees (n=112,31561) were active on GitHub. | 979 979 Amazon employees were active on GitHub. | 
| 32. Netflix | 2% 2% (n=52) of all Netflix engineers (n=2,22762) were active on GitHub. | 0% 0% (n=52) of all Netflix employees (n=12,80063) were active on GitHub. | 52 52 Netflix employees were active on GitHub. | 
| 33. Stripe | 2% 2% (n=59) of all Stripe engineers (n=2,96164) were active on GitHub. | 1% 1% (n=59) of all Stripe employees (n=8,37265) were active on GitHub. | 59 59 Stripe employees were active on GitHub. | 
| 34. Google | 2% 2% (n=1,342) of all Google engineers (n=71,08466) were active on GitHub. | 1% 1% (n=1,342) of all Google employees (n=190,23467) were active on GitHub. | 1,342 1,342 Google employees were active on GitHub. | 
| 35. Tencent | 2% 2% (n=245) of all Tencent engineers (n=12,97968) were active on GitHub. | 0% 0% (n=245) of all Tencent employees (n=108,43669) were active on GitHub. | 245 245 Tencent employees were active on GitHub. | 
| 36. Adobe | 2% 2% (n=171) of all Adobe engineers (n=9,45070) were active on GitHub. | 1% 1% (n=171) of all Adobe employees (n=29,23971) were active on GitHub. | 171 171 Adobe employees were active on GitHub. | 
| 37. Splunk | 2% 2% (n=37) of all Splunk engineers (n=2,07672) were active on GitHub. | 0% 0% (n=37) of all Splunk employees (n=8,00073) were active on GitHub. | 37 37 Splunk employees were active on GitHub. | 
| 38. Unity Technologies | 2% 2% (n=66) of all Unity Technologies engineers (n=3,75374) were active on GitHub. | 1% 1% (n=66) of all Unity Technologies employees (n=7,70375) were active on GitHub. | 66 66 Unity Technologies 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. Arm Ltd | 2% 2% (n=82) of all Arm Ltd engineers (n=4,75878) were active on GitHub. | 1% 1% (n=82) of all Arm Ltd employees (n=6,32979) were active on GitHub. | 82 82 Arm Ltd employees were active on GitHub. | 
| 41. Zalando DE | 2% 2% (n=26) of all Zalando DE engineers (n=1,60880) were active on GitHub. | 0% 0% (n=26) of all Zalando DE employees (n=16,99981) were active on GitHub. | 26 26 Zalando DE employees were active on GitHub. | 
| 42. BBC | 2% 2% (n=23) of all BBC engineers (n=1,52182) were active on GitHub. | 0% 0% (n=23) of all BBC employees (n=21,28183) were active on GitHub. | 23 23 BBC employees were active on GitHub. | 
| 43. Lyft | 1% 1% (n=27) of all Lyft engineers (n=1,81184) were active on GitHub. | 1% 1% (n=27) of all Lyft employees (n=4,41985) were active on GitHub. | 27 27 Lyft employees were active on GitHub. | 
| 44. Zendesk | 1% 1% (n=23) of all Zendesk engineers (n=1,62086) were active on GitHub. | 0% 0% (n=23) of all Zendesk employees (n=6,44087) were active on GitHub. | 23 23 Zendesk employees were active on GitHub. | 
| 45. WIX | 1% 1% (n=29) of all WIX engineers (n=2,20688) were active on GitHub. | 1% 1% (n=29) of all WIX employees (n=4,74289) were active on GitHub. | 29 29 WIX employees were active on GitHub. | 
| 46. NVIDIA | 1% 1% (n=248) of all NVIDIA engineers (n=19,53290) were active on GitHub. | 1% 1% (n=248) of all NVIDIA employees (n=26,19691) were active on GitHub. | 248 248 NVIDIA employees were active on GitHub. | 
| 47. Atlassian | 1% 1% (n=54) of all Atlassian engineers (n=4,40692) were active on GitHub. | 1% 1% (n=54) of all Atlassian employees (n=8,81393) were active on GitHub. | 54 54 Atlassian employees were active on GitHub. | 
| 48. Spotify | 1% 1% (n=48) of all Spotify engineers (n=4,16994) were active on GitHub. | 1% 1% (n=48) of all Spotify employees (n=8,35995) were active on GitHub. | 48 48 Spotify employees were active on GitHub. | 
| 49. Uber | 1% 1% (n=50) of all Uber engineers (n=5,50296) were active on GitHub. | 0% 0% (n=50) of all Uber employees (n=32,80097) were active on GitHub. | 50 50 Uber employees were active on GitHub. | 
| 50. Salesforce | 1% 1% (n=169) of all Salesforce engineers (n=20,53798) were active on GitHub. | 0% 0% (n=169) of all Salesforce employees (n=79,39099) were active on GitHub. | 169 169 Salesforce employees were active on GitHub. | 
| 51. Meta | 1% 1% (n=266) of all Meta engineers (n=35,611100) were active on GitHub. | 0% 0% (n=266) of all Meta employees (n=86,482101) were active on GitHub. | 266 266 Meta employees were active on GitHub. | 
| 52. Intel | 1% 1% (n=426) of all Intel engineers (n=57,090102) were active on GitHub. | 0% 0% (n=426) of all Intel employees (n=131,900103) were active on GitHub. | 426 426 Intel employees were active on GitHub. | 
| 53. SAP SE | 1% 1% (n=254) of all SAP SE engineers (n=34,122104) were active on GitHub. | 0% 0% (n=254) of all SAP SE employees (n=111,961105) were active on GitHub. | 254 254 SAP SE employees were active on GitHub. | 
| 54. AMD | 1% 1% (n=76) of all AMD engineers (n=12,146106) were active on GitHub. | 0% 0% (n=76) of all AMD employees (n=25,000107) were active on GitHub. | 76 76 AMD employees were active on GitHub. | 
| 55. Bloomberg | 1% 1% (n=32) of all Bloomberg engineers (n=6,326108) were active on GitHub. | 0% 0% (n=32) of all Bloomberg employees (n=23,033109) were active on GitHub. | 32 32 Bloomberg employees were active on GitHub. | 
| 56. Yandex | 1% 1% (n=54) of all Yandex engineers (n=10,708110) were active on GitHub. | 0% 0% (n=54) of all Yandex employees (n=20,850111) were active on GitHub. | 54 54 Yandex employees were active on GitHub. | 
| 57. Cisco Systems | 0% 0% (n=117) of all Cisco Systems engineers (n=23,407112) were active on GitHub. | 0% 0% (n=117) of all Cisco Systems employees (n=83,300113) were active on GitHub. | 117 117 Cisco Systems employees were active on GitHub. | 
| 58. Baidu | 0% 0% (n=103) of all Baidu engineers (n=23,600114) were active on GitHub. | 0% 0% (n=103) of all Baidu employees (n=41,300115) were active on GitHub. | 103 103 Baidu employees were active on GitHub. | 
| 59. Oracle | 0% 0% (n=169) of all Oracle engineers (n=44,000116) were active on GitHub. | 0% 0% (n=169) of all Oracle employees (n=143,000117) were active on GitHub. | 169 169 Oracle employees were active on GitHub. | 
| 60. Apple | 0% 0% (n=147) of all Apple engineers (n=39,361118) were active on GitHub. | 0% 0% (n=147) of all Apple employees (n=164,000119) were active on GitHub. | 147 147 Apple employees were active on GitHub. | 
| 61. NetEase | 0% 0% (n=49) of all NetEase engineers (n=15,211120) were active on GitHub. | 0% 0% (n=49) of all NetEase employees (n=31,119121) were active on GitHub. | 49 49 NetEase employees were active on GitHub. | 
| 62. PayPal | 0% 0% (n=26) of all PayPal engineers (n=8,805122) were active on GitHub. | 0% 0% (n=26) of all PayPal employees (n=29,900123) were active on GitHub. | 26 26 PayPal employees were active on GitHub. | 
| 63. EPAM Systems | 0% 0% (n=96) of all EPAM Systems engineers (n=52,850124) were active on GitHub. | 0% 0% (n=96) of all EPAM Systems employees (n=59,300125) were active on GitHub. | 96 96 EPAM Systems employees were active on GitHub. | 
| 64. Ericsson | 0% 0% (n=38) of all Ericsson engineers (n=29,304126) were active on GitHub. | 0% 0% (n=38) of all Ericsson employees (n=105,529127) were active on GitHub. | 38 38 Ericsson employees were active on GitHub. | 
| 65. Nokia | 0% 0% (n=23) of all Nokia engineers (n=23,836128) were active on GitHub. | 0% 0% (n=23) of all Nokia employees (n=86,896129) were active on GitHub. | 23 23 Nokia employees were active on GitHub. | 
| 66. Samsung | 0% 0% (n=71) of all Samsung engineers (n=80,496130) were active on GitHub. | 0% 0% (n=71) of all Samsung employees (n=270,372131) were active on GitHub. | 71 71 Samsung employees were active on GitHub. | 
| 67. Capgemini | 0% 0% (n=51) of all Capgemini engineers (n=69,803132) were active on GitHub. | 0% 0% (n=51) of all Capgemini employees (n=360,000133) were active on GitHub. | 51 51 Capgemini employees were active on GitHub. | 
| 68. Huawei | 0% 0% (n=72) of all Huawei engineers (n=114,000134) were active on GitHub. | 0% 0% (n=72) of all Huawei employees (n=207,000135) were active on GitHub. | 72 72 Huawei employees were active on GitHub. | 
| 69. IBM | (n=1,652) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,652) of all IBM employees (n=288,300136) were active on GitHub. | 1,652 1,652 IBM employees were active on GitHub. | 
| 70. Canonical | (n=96) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=96) of all Canonical employees (n=NaN0) were active on GitHub. | 96 96 Canonical employees were active on GitHub. | 
| 71. ByteDance | (n=87) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=87) of all ByteDance employees (n=NaN0) were active on GitHub. | 87 87 ByteDance employees were active on GitHub. | 
| 72. Accenture | (n=81) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=81) of all Accenture employees (n=721,000137) were active on GitHub. | 81 81 Accenture employees were active on GitHub. | 
| 73. Yahoo! | (n=60) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=60) of all Yahoo! employees (n=NaN0) were active on GitHub. | 60 60 Yahoo! employees were active on GitHub. | 
| 74. Sentry.io | (n=55) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=55) of all Sentry.io employees (n=NaN0) were active on GitHub. | 55 55 Sentry.io employees were active on GitHub. | 
| 75. 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. | 
| 76. PingCAP | (n=45) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=45) of all PingCAP employees (n=NaN0) were active on GitHub. | 45 45 PingCAP employees were active on GitHub. | 
| 77. 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. | 
| 78. Apple Developer Academy @ POSTECH | (n=42) of all Apple Developer Academy @ POSTECH engineers (n=NaN0) were active on GitHub. | (n=42) of all Apple Developer Academy @ POSTECH employees (n=NaN0) were active on GitHub. | 42 42 Apple Developer Academy @ POSTECH employees were active on GitHub. | 
| 79. Intuit | (n=41) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=41) of all Intuit employees (n=17,300138) were active on GitHub. | 41 41 Intuit employees were active on GitHub. | 
| 80. Snyk | (n=39) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=39) of all Snyk employees (n=NaN0) were active on GitHub. | 39 39 Snyk employees were active on GitHub. | 
| 81. Palo Alto Networks | (n=36) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=36) of all Palo Alto Networks employees (n=12,561139) were active on GitHub. | 36 36 Palo Alto Networks employees were active on GitHub. | 
| 82. 100Devs | (n=36) of all 100Devs engineers (n=NaN0) were active on GitHub. | (n=36) of all 100Devs employees (n=NaN0) were active on GitHub. | 36 36 100Devs employees were active on GitHub. | 
| 83. R3 | (n=34) of all R3 engineers (n=NaN0) were active on GitHub. | (n=34) of all R3 employees (n=NaN0) were active on GitHub. | 34 34 R3 employees were active on GitHub. | 
| 84. Posit | (n=32) of all Posit engineers (n=NaN0) were active on GitHub. | (n=32) of all Posit employees (n=NaN0) were active on GitHub. | 32 32 Posit employees were active on GitHub. | 
| 85. DigitalOcean | (n=30) of all DigitalOcean engineers (n=NaN0) were active on GitHub. | 2% 2% (n=30) of all DigitalOcean employees (n=1,204140) were active on GitHub. | 30 30 DigitalOcean employees were active on GitHub. | 
| 86. @bytedance | (n=30) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=30) of all @bytedance employees (n=NaN0) were active on GitHub. | 30 30 @bytedance employees were active on GitHub. | 
| 87. TU Delft | (n=29) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=29) of all TU Delft employees (n=NaN0) were active on GitHub. | 29 29 TU Delft employees were active on GitHub. | 
| 88. Cloudera | (n=28) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=28) of all Cloudera employees (n=NaN0) were active on GitHub. | 28 28 Cloudera employees were active on GitHub. | 
| 89. Epitech | (n=27) of all Epitech engineers (n=NaN0) were active on GitHub. | (n=27) of all Epitech employees (n=NaN0) were active on GitHub. | 27 27 Epitech employees were active on GitHub. | 
| 90. Talend | (n=27) of all Talend engineers (n=NaN0) were active on GitHub. | (n=27) of all Talend employees (n=NaN0) were active on GitHub. | 27 27 Talend employees were active on GitHub. | 
| 91. UCL | (n=26) of all UCL engineers (n=NaN0) were active on GitHub. | (n=26) of all UCL employees (n=NaN0) were active on GitHub. | 26 26 UCL employees were active on GitHub. | 
| 92. 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. | 
| 93. @apache | (n=26) of all @apache engineers (n=NaN0) were active on GitHub. | (n=26) of all @apache employees (n=NaN0) were active on GitHub. | 26 26 @apache employees were active on GitHub. | 
| 94. Protocol Labs | (n=25) of all Protocol Labs engineers (n=NaN0) were active on GitHub. | (n=25) of all Protocol Labs employees (n=NaN0) were active on GitHub. | 25 25 Protocol Labs employees were active on GitHub. | 
| 95. Harvard Medical School | (n=24) of all Harvard Medical School engineers (n=NaN0) were active on GitHub. | (n=24) of all Harvard Medical School employees (n=NaN0) were active on GitHub. | 24 24 Harvard Medical School employees were active on GitHub. | 
| 96. Masai | (n=23) of all Masai engineers (n=NaN0) were active on GitHub. | (n=23) of all Masai employees (n=NaN0) were active on GitHub. | 23 23 Masai employees were active on GitHub. | 
| 97. @vercel | (n=23) of all @vercel engineers (n=NaN0) were active on GitHub. | (n=23) of all @vercel employees (n=NaN0) were active on GitHub. | 23 23 @vercel employees were active on GitHub. | 
| 98. @protocol | (n=22) of all @protocol engineers (n=NaN0) were active on GitHub. | (n=22) of all @protocol employees (n=NaN0) were active on GitHub. | 22 22 @protocol employees were active on GitHub. | 
| 99. Kitware | (n=22) of all Kitware engineers (n=NaN0) were active on GitHub. | 13% 13% (n=22) of all Kitware employees (n=174141) were active on GitHub. | 22 22 Kitware employees were active on GitHub. | 
| 100. CircleCI | (n=22) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=22) of all CircleCI employees (n=NaN0) were active on GitHub. | 22 22 CircleCI 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
- Docker engineer count: linkedin.com
- Docker 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
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- HashiCorp engineer count: sec.gov (page 13)
- HashiCorp employee count: sec.gov (page 14)
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.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)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- ESRI engineer count: linkedin.com
- ESRI 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)
- 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)
- 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)
- 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
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 8)
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 87)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 16)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- 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)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Zalando DE engineer count: linkedin.com
- Zalando DE employee count: corporate.zalando.com (page 2)
- 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)
- WIX engineer count: sec.gov (page 142, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 142)
- 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)
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 10)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 55)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- 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)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- 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)
- 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)
- 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)
- 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)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 17)
- 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)
- IBM employee count: ibm.com (page 15)
- Accenture employee count: sec.gov (page 24)
- Intuit employee count: sec.gov (page 12)
- Palo Alto Networks employee count: sec.gov (page 11)
- DigitalOcean employee count: sec.gov (page 13)
- Kitware employee count: linkedin.com