Corporate GitHub Activity
Most Active Corporations on GitHub, 03 2023
Ranking companies with employees who, during 03 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. SUSE | 40% 40% (n=231) of all SUSE engineers (n=5751) were active on GitHub. | 10% 10% (n=231) of all SUSE employees (n=2,4002) were active on GitHub. | 231 231 SUSE employees were active on GitHub. | 
|---|---|---|---|
| 2. Grafana Labs | 36% 36% (n=187) of all Grafana Labs engineers (n=5163) were active on GitHub. | 15% 15% (n=187) of all Grafana Labs employees (n=1,2174) were active on GitHub. | 187 187 Grafana Labs employees were active on GitHub. | 
| 3. Automattic | 35% 35% (n=303) of all Automattic engineers (n=8665) were active on GitHub. | 16% 16% (n=303) of all Automattic employees (n=1,9306) were active on GitHub. | 303 303 Automattic employees were active on GitHub. | 
| 4. HashiCorp | 28% 28% (n=190) of all HashiCorp engineers (n=6807) were active on GitHub. | 9% 9% (n=190) of all HashiCorp employees (n=2,2008) were active on GitHub. | 190 190 HashiCorp employees were active on GitHub. | 
| 5. Mozilla | 27% 27% (n=160) of all Mozilla engineers (n=5859) were active on GitHub. | 9% 9% (n=160) of all Mozilla employees (n=1,74510) were active on GitHub. | 160 160 Mozilla employees were active on GitHub. | 
| 6. Elastic | 26% 26% (n=262) of all Elastic engineers (n=1,02211) were active on GitHub. | 8% 8% (n=262) of all Elastic employees (n=3,18712) were active on GitHub. | 262 262 Elastic employees were active on GitHub. | 
| 7. The Guardian | 22% 22% (n=32) of all The Guardian engineers (n=14413) were active on GitHub. | 1% 1% (n=32) of all The Guardian employees (n=2,50114) were active on GitHub. | 32 32 The Guardian employees were active on GitHub. | 
| 8. Docker | 22% 22% (n=36) of all Docker engineers (n=16715) were active on GitHub. | 5% 5% (n=36) of all Docker employees (n=76716) were active on GitHub. | 36 36 Docker employees were active on GitHub. | 
| 9. JetBrains | 17% 17% (n=165) of all JetBrains engineers (n=97217) were active on GitHub. | 9% 9% (n=165) of all JetBrains employees (n=1,80018) were active on GitHub. | 165 165 JetBrains employees were active on GitHub. | 
| 10. Odoo | 17% 17% (n=109) of all Odoo engineers (n=64519) were active on GitHub. | 6% 6% (n=109) of all Odoo employees (n=1,70020) were active on GitHub. | 109 109 Odoo employees were active on GitHub. | 
| 11. Vercel | 16% 16% (n=24) of all Vercel engineers (n=15421) were active on GitHub. | 5% 5% (n=24) of all Vercel employees (n=47322) were active on GitHub. | 24 24 Vercel employees were active on GitHub. | 
| 12. WSO2 | 14% 14% (n=90) of all WSO2 engineers (n=66423) were active on GitHub. | 9% 9% (n=90) of all WSO2 employees (n=1,02024) were active on GitHub. | 90 90 WSO2 employees were active on GitHub. | 
| 13. WikiMedia Foundation | 12% 12% (n=24) of all WikiMedia Foundation engineers (n=20425) were active on GitHub. | 3% 3% (n=24) of all WikiMedia Foundation employees (n=70026) were active on GitHub. | 24 24 WikiMedia Foundation employees were active on GitHub. | 
| 14. Mapbox | 12% 12% (n=28) of all Mapbox engineers (n=24027) were active on GitHub. | 4% 4% (n=28) of all Mapbox employees (n=65428) were active on GitHub. | 28 28 Mapbox employees were active on GitHub. | 
| 15. MongoDB | 9% 9% (n=115) of all MongoDB engineers (n=1,22629) were active on GitHub. | 2% 2% (n=115) of all MongoDB employees (n=5,03730) were active on GitHub. | 115 115 MongoDB employees were active on GitHub. | 
| 16. Cloudflare | 9% 9% (n=77) of all Cloudflare engineers (n=83031) were active on GitHub. | 2% 2% (n=77) of all Cloudflare employees (n=3,68232) were active on GitHub. | 77 77 Cloudflare employees were active on GitHub. | 
| 17. DataDog | 9% 9% (n=215) of all DataDog engineers (n=2,40033) were active on GitHub. | 4% 4% (n=215) of all DataDog employees (n=5,20034) were active on GitHub. | 215 215 DataDog employees were active on GitHub. | 
| 18. New Relic | 9% 9% (n=77) of all New Relic engineers (n=88435) were active on GitHub. | 3% 3% (n=77) of all New Relic employees (n=2,58436) were active on GitHub. | 77 77 New Relic employees were active on GitHub. | 
| 19. Liferay | 7% 7% (n=32) of all Liferay engineers (n=46037) were active on GitHub. | 2% 2% (n=32) of all Liferay employees (n=1,37538) were active on GitHub. | 32 32 Liferay employees were active on GitHub. | 
| 20. Shopify | 6% 6% (n=210) of all Shopify engineers (n=3,56439) were active on GitHub. | 3% 3% (n=210) of all Shopify employees (n=8,30040) were active on GitHub. | 210 210 Shopify employees were active on GitHub. | 
| 21. Twitter | 6% 6% (n=31) of all Twitter engineers (n=54941) were active on GitHub. | 1% 1% (n=31) of all Twitter employees (n=2,14042) were active on GitHub. | 31 31 Twitter employees were active on GitHub. | 
| 22. ESRI | 5% 5% (n=105) of all ESRI engineers (n=2,07443) were active on GitHub. | 2% 2% (n=105) of all ESRI employees (n=6,44744) were active on GitHub. | 105 105 ESRI employees were active on GitHub. | 
| 23. Confluent | 5% 5% (n=49) of all Confluent engineers (n=1,03445) were active on GitHub. | 2% 2% (n=49) of all Confluent employees (n=2,74446) were active on GitHub. | 49 49 Confluent employees were active on GitHub. | 
| 24. Microsoft | 4% 4% (n=3,088) of all Microsoft engineers (n=72,00047) were active on GitHub. | 1% 1% (n=3,088) of all Microsoft employees (n=221,00048) were active on GitHub. | 3,088 3,088 Microsoft employees were active on GitHub. | 
| 25. Progress Software | 3% 3% (n=31) of all Progress Software engineers (n=88649) were active on GitHub. | 1% 1% (n=31) of all Progress Software employees (n=2,28450) were active on GitHub. | 31 31 Progress Software employees were active on GitHub. | 
| 26. Square, Inc. | 3% 3% (n=71) of all Square, Inc. engineers (n=2,06051) were active on GitHub. | 1% 1% (n=71) of all Square, Inc. employees (n=12,98552) were active on GitHub. | 71 71 Square, Inc. employees were active on GitHub. | 
| 27. Alibaba | 3% 3% (n=345) of all Alibaba engineers (n=10,02553) were active on GitHub. | 0% 0% (n=345) of all Alibaba employees (n=224,95554) were active on GitHub. | 345 345 Alibaba employees were active on GitHub. | 
| 28. VMWare | 3% 3% (n=394) of all VMWare engineers (n=12,94455) were active on GitHub. | 1% 1% (n=394) of all VMWare employees (n=38,30056) were active on GitHub. | 394 394 VMWare employees were active on GitHub. | 
| 29. Okta | 3% 3% (n=46) of all Okta engineers (n=1,57057) were active on GitHub. | 1% 1% (n=46) of all Okta employees (n=5,90858) were active on GitHub. | 46 46 Okta employees were active on GitHub. | 
| 30. ThoughtWorks | 3% 3% (n=109) of all ThoughtWorks engineers (n=3,76559) were active on GitHub. | 1% 1% (n=109) of all ThoughtWorks employees (n=10,50060) were active on GitHub. | 109 109 ThoughtWorks employees were active on GitHub. | 
| 31. Andela | 3% 3% (n=25) of all Andela engineers (n=88861) were active on GitHub. | 2% 2% (n=25) of all Andela employees (n=1,57062) were active on GitHub. | 25 25 Andela employees were active on GitHub. | 
| 32. Snowflake, Inc. | 3% 3% (n=52) of all Snowflake, Inc. engineers (n=2,00263) were active on GitHub. | 1% 1% (n=52) of all Snowflake, Inc. employees (n=7,00464) were active on GitHub. | 52 52 Snowflake, Inc. employees were active on GitHub. | 
| 33. Amazon | 3% 3% (n=1,091) of all Amazon engineers (n=43,60565) were active on GitHub. | 1% 1% (n=1,091) of all Amazon employees (n=125,34566) were active on GitHub. | 1,091 1,091 Amazon employees were active on GitHub. | 
| 34. Zendesk | 2% 2% (n=36) of all Zendesk engineers (n=1,48167) were active on GitHub. | 1% 1% (n=36) of all Zendesk employees (n=6,17968) were active on GitHub. | 36 36 Zendesk employees were active on GitHub. | 
| 35. Netflix | 2% 2% (n=57) of all Netflix engineers (n=2,40969) were active on GitHub. | 0% 0% (n=57) of all Netflix employees (n=13,00070) were active on GitHub. | 57 57 Netflix employees were active on GitHub. | 
| 36. Twilio | 2% 2% (n=59) of all Twilio engineers (n=2,56371) were active on GitHub. | 1% 1% (n=59) of all Twilio employees (n=5,86772) were active on GitHub. | 59 59 Twilio employees were active on GitHub. | 
| 37. Adobe | 2% 2% (n=216) of all Adobe engineers (n=10,24773) were active on GitHub. | 1% 1% (n=216) of all Adobe employees (n=29,94574) were active on GitHub. | 216 216 Adobe employees were active on GitHub. | 
| 38. Arm Ltd | 2% 2% (n=94) of all Arm Ltd engineers (n=4,75375) were active on GitHub. | 2% 2% (n=94) of all Arm Ltd employees (n=5,96376) were active on GitHub. | 94 94 Arm Ltd employees were active on GitHub. | 
| 39. Zalando DE | 2% 2% (n=33) of all Zalando DE engineers (n=1,72277) were active on GitHub. | 0% 0% (n=33) of all Zalando DE employees (n=15,79378) were active on GitHub. | 33 33 Zalando DE employees were active on GitHub. | 
| 40. Google | 2% 2% (n=1,395) of all Google engineers (n=75,57179) were active on GitHub. | 1% 1% (n=1,395) of all Google employees (n=182,50280) were active on GitHub. | 1,395 1,395 Google employees were active on GitHub. | 
| 41. Tencent | 2% 2% (n=245) of all Tencent engineers (n=13,64281) were active on GitHub. | 0% 0% (n=245) of all Tencent employees (n=105,41782) were active on GitHub. | 245 245 Tencent employees were active on GitHub. | 
| 42. Unity Technologies | 2% 2% (n=69) of all Unity Technologies engineers (n=3,84483) were active on GitHub. | 1% 1% (n=69) of all Unity Technologies employees (n=6,74884) were active on GitHub. | 69 69 Unity Technologies employees were active on GitHub. | 
| 43. BBC | 2% 2% (n=31) of all BBC engineers (n=1,82285) were active on GitHub. | 0% 0% (n=31) of all BBC employees (n=21,63186) were active on GitHub. | 31 31 BBC employees were active on GitHub. | 
| 44. Stripe | 2% 2% (n=49) of all Stripe engineers (n=2,95287) were active on GitHub. | 1% 1% (n=49) of all Stripe employees (n=8,40988) were active on GitHub. | 49 49 Stripe employees were active on GitHub. | 
| 45. WIX | 1% 1% (n=31) of all WIX engineers (n=2,30189) were active on GitHub. | 1% 1% (n=31) of all WIX employees (n=4,60090) were active on GitHub. | 31 31 WIX employees were active on GitHub. | 
| 46. Splunk | 1% 1% (n=31) of all Splunk engineers (n=2,38791) were active on GitHub. | 0% 0% (n=31) of all Splunk employees (n=8,00092) were active on GitHub. | 31 31 Splunk employees were active on GitHub. | 
| 47. NVIDIA | 1% 1% (n=283) of all NVIDIA engineers (n=22,20093) were active on GitHub. | 1% 1% (n=283) of all NVIDIA employees (n=29,60094) were active on GitHub. | 283 283 NVIDIA employees were active on GitHub. | 
| 48. Spotify | 1% 1% (n=57) of all Spotify engineers (n=4,71995) were active on GitHub. | 1% 1% (n=57) of all Spotify employees (n=9,12396) were active on GitHub. | 57 57 Spotify employees were active on GitHub. | 
| 49. Atlassian | 1% 1% (n=53) of all Atlassian engineers (n=5,36397) were active on GitHub. | 0% 0% (n=53) of all Atlassian employees (n=10,72698) were active on GitHub. | 53 53 Atlassian employees were active on GitHub. | 
| 50. Meta | 1% 1% (n=275) of all Meta engineers (n=31,33899) were active on GitHub. | 0% 0% (n=275) of all Meta employees (n=67,317100) were active on GitHub. | 275 275 Meta employees were active on GitHub. | 
| 51. Intel | 1% 1% (n=486) of all Intel engineers (n=57,201101) were active on GitHub. | 0% 0% (n=486) of all Intel employees (n=124,800102) were active on GitHub. | 486 486 Intel employees were active on GitHub. | 
| 52. Salesforce | 1% 1% (n=161) of all Salesforce engineers (n=19,483103) were active on GitHub. | 0% 0% (n=161) of all Salesforce employees (n=72,682104) were active on GitHub. | 161 161 Salesforce employees were active on GitHub. | 
| 53. Uber | 1% 1% (n=49) of all Uber engineers (n=6,426105) were active on GitHub. | 0% 0% (n=49) of all Uber employees (n=30,400106) were active on GitHub. | 49 49 Uber employees were active on GitHub. | 
| 54. SAP SE | 1% 1% (n=245) of all SAP SE engineers (n=33,377107) were active on GitHub. | 0% 0% (n=245) of all SAP SE employees (n=107,602108) were active on GitHub. | 245 245 SAP SE employees were active on GitHub. | 
| 55. Autodesk | 1% 1% (n=28) of all Autodesk engineers (n=4,209109) were active on GitHub. | 0% 0% (n=28) of all Autodesk employees (n=14,100110) were active on GitHub. | 28 28 Autodesk employees were active on GitHub. | 
| 56. Yandex | 1% 1% (n=82) of all Yandex engineers (n=13,003111) were active on GitHub. | 0% 0% (n=82) of all Yandex employees (n=26,361112) were active on GitHub. | 82 82 Yandex employees were active on GitHub. | 
| 57. AMD | 1% 1% (n=88) of all AMD engineers (n=15,606113) were active on GitHub. | 0% 0% (n=88) of all AMD employees (n=26,000114) were active on GitHub. | 88 88 AMD employees were active on GitHub. | 
| 58. Baidu | 1% 1% (n=116) of all Baidu engineers (n=21,800115) were active on GitHub. | 0% 0% (n=116) of all Baidu employees (n=39,800116) were active on GitHub. | 116 116 Baidu employees were active on GitHub. | 
| 59. Bloomberg | 0% 0% (n=33) of all Bloomberg engineers (n=7,328117) were active on GitHub. | 0% 0% (n=33) of all Bloomberg employees (n=25,923118) were active on GitHub. | 33 33 Bloomberg employees were active on GitHub. | 
| 60. NetEase | 0% 0% (n=64) of all NetEase engineers (n=14,855119) were active on GitHub. | 0% 0% (n=64) of all NetEase employees (n=29,128120) were active on GitHub. | 64 64 NetEase employees were active on GitHub. | 
| 61. Cisco Systems | 0% 0% (n=98) of all Cisco Systems engineers (n=23,772121) were active on GitHub. | 0% 0% (n=98) of all Cisco Systems employees (n=84,900122) were active on GitHub. | 98 98 Cisco Systems employees were active on GitHub. | 
| 62. Oracle | 0% 0% (n=162) of all Oracle engineers (n=47,000123) were active on GitHub. | 0% 0% (n=162) of all Oracle employees (n=164,000124) were active on GitHub. | 162 162 Oracle employees were active on GitHub. | 
| 63. Apple | 0% 0% (n=160) of all Apple engineers (n=46,752125) were active on GitHub. | 0% 0% (n=160) of all Apple employees (n=161,000126) were active on GitHub. | 160 160 Apple employees were active on GitHub. | 
| 64. PayPal | 0% 0% (n=28) of all PayPal engineers (n=8,658127) were active on GitHub. | 0% 0% (n=28) of all PayPal employees (n=27,200128) were active on GitHub. | 28 28 PayPal employees were active on GitHub. | 
| 65. EPAM Systems | 0% 0% (n=107) of all EPAM Systems engineers (n=47,350129) were active on GitHub. | 0% 0% (n=107) of all EPAM Systems employees (n=53,150130) were active on GitHub. | 107 107 EPAM Systems employees were active on GitHub. | 
| 66. Ericsson | 0% 0% (n=39) of all Ericsson engineers (n=28,219131) were active on GitHub. | 0% 0% (n=39) of all Ericsson employees (n=99,952132) were active on GitHub. | 39 39 Ericsson employees were active on GitHub. | 
| 67. Nokia | 0% 0% (n=25) of all Nokia engineers (n=26,395133) were active on GitHub. | 0% 0% (n=25) of all Nokia employees (n=86,689134) were active on GitHub. | 25 25 Nokia employees were active on GitHub. | 
| 68. Samsung | 0% 0% (n=74) of all Samsung engineers (n=83,729135) were active on GitHub. | 0% 0% (n=74) of all Samsung employees (n=267,860136) were active on GitHub. | 74 74 Samsung employees were active on GitHub. | 
| 69. Capgemini | 0% 0% (n=55) of all Capgemini engineers (n=69,796137) were active on GitHub. | 0% 0% (n=55) of all Capgemini employees (n=340,400138) were active on GitHub. | 55 55 Capgemini employees were active on GitHub. | 
| 70. Huawei | 0% 0% (n=73) of all Huawei engineers (n=114,000139) were active on GitHub. | 0% 0% (n=73) of all Huawei employees (n=207,000140) were active on GitHub. | 73 73 Huawei employees were active on GitHub. | 
| 71. IBM | (n=1,739) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,739) of all IBM employees (n=282,200141) were active on GitHub. | 1,739 1,739 IBM employees were active on GitHub. | 
| 72. Canonical | (n=101) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=101) of all Canonical employees (n=NaN0) were active on GitHub. | 101 101 Canonical employees were active on GitHub. | 
| 73. ByteDance | (n=94) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=94) of all ByteDance employees (n=NaN0) were active on GitHub. | 94 94 ByteDance employees were active on GitHub. | 
| 74. Accenture | (n=77) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=77) of all Accenture employees (n=733,000142) were active on GitHub. | 77 77 Accenture employees were active on GitHub. | 
| 75. Sentry.io | (n=64) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 17% 17% (n=64) of all Sentry.io employees (n=378143) were active on GitHub. | 64 64 Sentry.io employees were active on GitHub. | 
| 76. Databricks | (n=60) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=60) of all Databricks employees (n=7,211144) were active on GitHub. | 60 60 Databricks employees were active on GitHub. | 
| 77. 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. | 
| 78. Software Mansion | (n=52) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=52) of all Software Mansion employees (n=NaN0) were active on GitHub. | 52 52 Software Mansion employees were active on GitHub. | 
| 79. PingCAP | (n=47) of all PingCAP engineers (n=NaN0) were active on GitHub. | 11% 11% (n=47) of all PingCAP employees (n=410145) were active on GitHub. | 47 47 PingCAP employees were active on GitHub. | 
| 80. @bytedance | (n=41) of all @bytedance engineers (n=NaN0) were active on GitHub. | (n=41) of all @bytedance employees (n=NaN0) were active on GitHub. | 41 41 @bytedance employees were active on GitHub. | 
| 81. R3 | (n=35) of all R3 engineers (n=NaN0) were active on GitHub. | (n=35) of all R3 employees (n=NaN0) were active on GitHub. | 35 35 R3 employees were active on GitHub. | 
| 82. Snyk | (n=33) of all Snyk engineers (n=NaN0) were active on GitHub. | 3% 3% (n=33) of all Snyk employees (n=1,171146) were active on GitHub. | 33 33 Snyk employees were active on GitHub. | 
| 83. Posit | (n=33) of all Posit engineers (n=NaN0) were active on GitHub. | (n=33) of all Posit employees (n=NaN0) were active on GitHub. | 33 33 Posit employees were active on GitHub. | 
| 84. Harness | (n=32) of all Harness engineers (n=NaN0) were active on GitHub. | (n=32) of all Harness employees (n=NaN0) were active on GitHub. | 32 32 Harness employees were active on GitHub. | 
| 85. TU Delft | (n=31) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=31) of all TU Delft employees (n=NaN0) were active on GitHub. | 31 31 TU Delft employees were active on GitHub. | 
| 86. 100Devs | (n=30) of all 100Devs engineers (n=NaN0) were active on GitHub. | (n=30) of all 100Devs employees (n=NaN0) were active on GitHub. | 30 30 100Devs employees were active on GitHub. | 
| 87. Remote | (n=29) of all Remote engineers (n=NaN0) were active on GitHub. | (n=29) of all Remote employees (n=NaN0) were active on GitHub. | 29 29 Remote employees were active on GitHub. | 
| 88. Palo Alto Networks | (n=29) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=29) of all Palo Alto Networks employees (n=13,948147) were active on GitHub. | 29 29 Palo Alto Networks employees were active on GitHub. | 
| 89. Intuit | (n=29) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=29) of all Intuit employees (n=18,200148) were active on GitHub. | 29 29 Intuit employees were active on GitHub. | 
| 90. 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. | 
| 91. @apache | (n=28) of all @apache engineers (n=NaN0) were active on GitHub. | (n=28) of all @apache employees (n=NaN0) were active on GitHub. | 28 28 @apache employees were active on GitHub. | 
| 92. UCL | (n=27) of all UCL engineers (n=NaN0) were active on GitHub. | (n=27) of all UCL employees (n=NaN0) were active on GitHub. | 27 27 UCL employees were active on GitHub. | 
| 93. @vercel | (n=27) of all @vercel engineers (n=NaN0) were active on GitHub. | (n=27) of all @vercel employees (n=NaN0) were active on GitHub. | 27 27 @vercel employees were active on GitHub. | 
| 94. Kitware | (n=27) of all Kitware engineers (n=NaN0) were active on GitHub. | 16% 16% (n=27) of all Kitware employees (n=171149) were active on GitHub. | 27 27 Kitware employees were active on GitHub. | 
| 95. @SSWConsulting | (n=27) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=27) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 27 27 @SSWConsulting employees were active on GitHub. | 
| 96. @MathWorks | (n=27) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=27) of all @MathWorks employees (n=NaN0) were active on GitHub. | 27 27 @MathWorks employees were active on GitHub. | 
| 97. 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. | 
| 98. 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. | 
| 99. ALX | (n=25) of all ALX engineers (n=NaN0) were active on GitHub. | (n=25) of all ALX employees (n=NaN0) were active on GitHub. | 25 25 ALX employees were active on GitHub. | 
| 100. 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. | 
References
- SUSE engineer count: linkedin.com
- SUSE employee count: links.imagerelay.com (page 10)
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved December 2023)
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 13)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- Elastic engineer count: linkedin.com (retrieved Dec 2023)
- Elastic employee count: sec.gov (page 15)
- The Guardian engineer count: linkedin.com (retrieved Dec 2023)
- The Guardian employee count: linkedin.com (retrieved Dec 2023)
- Docker engineer count: linkedin.com
- Docker employee count: linkedin.com
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- WikiMedia Foundation employee count: wikimediafoundation.org
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- MongoDB engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 9)
- 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)
- New Relic engineer count: linkedin.com (Retrieved December 2023)
- New Relic employee count: linkedin.com (Retrieved December 2023)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Shopify engineer count: linkedin.com (retrieved Dec 2023)
- Shopify employee count: s27.q4cdn.com (page 22)
- Twitter engineer count: linkedin.com
- Twitter employee count: linkedin.com
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 15)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- Progress Software engineer count: sec.gov (page 7, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 7)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 20)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Interim Report, page 15)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 14)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Andela engineer count: linkedin.com
- Andela employee count: linkedin.com
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 17)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Twilio engineer count: sec.gov (page 8, 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 18)
- 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)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 10)
- Tencent engineer count: linkedin.com (retrieved Dec 2023)
- Tencent employee count: static.tencent.com (page 56)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- BBC engineer count: linkedin.com
- BBC employee count: bbc.co.uk (page 59)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- WIX engineer count: sec.gov (page 89, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 149)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Spotify engineer count: sec.gov (page 68, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 68)
- Atlassian engineer count: sec.gov (page 9, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 12)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 60)
- Intel engineer count: linkedin.com
- Intel employee count: sec.gov (page 15)
- Salesforce engineer count: linkedin.com (retrieved Dec 2023)
- Salesforce employee count: sec.gov (page 10)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- SAP SE engineer count: sec.gov (page F-23, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 102)
- Autodesk engineer count: linkedin.com (retrieved Dec 2023)
- Autodesk employee count: sec.gov (page 13)
- Yandex engineer count: sec.gov (page 54, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 54)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 12)
- Baidu engineer count: sec.gov (page 196, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 196)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- NetEase engineer count: sec.gov (page 156, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 156)
- Cisco Systems engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 10)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- 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 6, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- Nokia engineer count: linkedin.com (retrieved Dec 2023)
- Nokia employee count: sec.gov (page 105)
- Samsung engineer count: samsung.com (page 58, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 58)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 4)
- Huawei engineer count: www-file.huawei.com (page 67, referred to as employees in 'R&D')
- Huawei employee count: www-file.huawei.com (page 1)
- IBM employee count: sec.gov (page 16)
- Accenture employee count: sec.gov (page 25)
- Sentry.io employee count: linkedin.com
- Databricks employee count: linkedin.com
- PingCAP employee count: linkedin.com
- Snyk employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- Intuit employee count: sec.gov (page 12)
- Kitware employee count: linkedin.com