Corporate GitHub Activity
Most Active Corporations on GitHub, 10 2023
Ranking companies with employees who, during 10 2023, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Grafana Labs | 40% 40% (n=204) of all Grafana Labs engineers (n=5161) were active on GitHub. | 17% 17% (n=204) of all Grafana Labs employees (n=1,2172) were active on GitHub. | 204 204 Grafana Labs employees were active on GitHub. | 
|---|---|---|---|
| 2. Vercel | 39% 39% (n=60) of all Vercel engineers (n=1543) were active on GitHub. | 13% 13% (n=60) of all Vercel employees (n=4734) were active on GitHub. | 60 60 Vercel employees were active on GitHub. | 
| 3. SUSE | 38% 38% (n=218) of all SUSE engineers (n=5755) were active on GitHub. | 9% 9% (n=218) of all SUSE employees (n=2,4006) were active on GitHub. | 218 218 SUSE employees were active on GitHub. | 
| 4. Automattic | 34% 34% (n=291) of all Automattic engineers (n=8667) were active on GitHub. | 15% 15% (n=291) of all Automattic employees (n=1,9308) were active on GitHub. | 291 291 Automattic employees were active on GitHub. | 
| 5. Mozilla | 28% 28% (n=166) of all Mozilla engineers (n=5859) were active on GitHub. | 10% 10% (n=166) of all Mozilla employees (n=1,74510) were active on GitHub. | 166 166 Mozilla employees were active on GitHub. | 
| 6. Elastic | 26% 26% (n=270) of all Elastic engineers (n=1,02211) were active on GitHub. | 8% 8% (n=270) of all Elastic employees (n=3,18712) were active on GitHub. | 270 270 Elastic employees were active on GitHub. | 
| 7. HashiCorp | 25% 25% (n=172) of all HashiCorp engineers (n=68013) were active on GitHub. | 8% 8% (n=172) of all HashiCorp employees (n=2,20014) were active on GitHub. | 172 172 HashiCorp employees were active on GitHub. | 
| 8. The Guardian | 19% 19% (n=28) of all The Guardian engineers (n=14415) were active on GitHub. | 1% 1% (n=28) of all The Guardian employees (n=2,50116) were active on GitHub. | 28 28 The Guardian employees were active on GitHub. | 
| 9. Docker | 18% 18% (n=30) of all Docker engineers (n=16717) were active on GitHub. | 4% 4% (n=30) of all Docker employees (n=76718) were active on GitHub. | 30 30 Docker employees were active on GitHub. | 
| 10. JetBrains | 15% 15% (n=149) of all JetBrains engineers (n=97219) were active on GitHub. | 8% 8% (n=149) of all JetBrains employees (n=1,80020) were active on GitHub. | 149 149 JetBrains employees were active on GitHub. | 
| 11. WSO2 | 14% 14% (n=96) of all WSO2 engineers (n=66421) were active on GitHub. | 9% 9% (n=96) of all WSO2 employees (n=1,02022) were active on GitHub. | 96 96 WSO2 employees were active on GitHub. | 
| 12. WikiMedia Foundation | 12% 12% (n=24) of all WikiMedia Foundation engineers (n=20423) were active on GitHub. | 3% 3% (n=24) of all WikiMedia Foundation employees (n=70024) were active on GitHub. | 24 24 WikiMedia Foundation employees were active on GitHub. | 
| 13. DataDog | 10% 10% (n=249) of all DataDog engineers (n=2,40025) were active on GitHub. | 5% 5% (n=249) of all DataDog employees (n=5,20026) were active on GitHub. | 249 249 DataDog employees were active on GitHub. | 
| 14. Cloudflare | 10% 10% (n=81) of all Cloudflare engineers (n=83027) were active on GitHub. | 2% 2% (n=81) of all Cloudflare employees (n=3,68228) were active on GitHub. | 81 81 Cloudflare employees were active on GitHub. | 
| 15. MongoDB | 9% 9% (n=112) of all MongoDB engineers (n=1,22629) were active on GitHub. | 2% 2% (n=112) of all MongoDB employees (n=5,03730) were active on GitHub. | 112 112 MongoDB employees were active on GitHub. | 
| 16. New Relic | 8% 8% (n=68) of all New Relic engineers (n=88431) were active on GitHub. | 3% 3% (n=68) of all New Relic employees (n=2,58432) were active on GitHub. | 68 68 New Relic employees were active on GitHub. | 
| 17. Liferay | 6% 6% (n=26) of all Liferay engineers (n=46033) were active on GitHub. | 2% 2% (n=26) of all Liferay employees (n=1,37534) were active on GitHub. | 26 26 Liferay employees were active on GitHub. | 
| 18. Odoo | 4% 4% (n=28) of all Odoo engineers (n=64535) were active on GitHub. | 2% 2% (n=28) of all Odoo employees (n=1,70036) were active on GitHub. | 28 28 Odoo employees were active on GitHub. | 
| 19. ESRI | 4% 4% (n=89) of all ESRI engineers (n=2,07437) were active on GitHub. | 1% 1% (n=89) of all ESRI employees (n=6,44738) were active on GitHub. | 89 89 ESRI employees were active on GitHub. | 
| 20. Shopify | 4% 4% (n=151) of all Shopify engineers (n=3,56439) were active on GitHub. | 2% 2% (n=151) of all Shopify employees (n=8,30040) were active on GitHub. | 151 151 Shopify employees were active on GitHub. | 
| 21. Confluent | 4% 4% (n=42) of all Confluent engineers (n=1,03441) were active on GitHub. | 2% 2% (n=42) of all Confluent employees (n=2,74442) were active on GitHub. | 42 42 Confluent employees were active on GitHub. | 
| 22. Microsoft | 4% 4% (n=2,722) of all Microsoft engineers (n=72,00043) were active on GitHub. | 1% 1% (n=2,722) of all Microsoft employees (n=221,00044) were active on GitHub. | 2,722 2,722 Microsoft employees were active on GitHub. | 
| 23. Progress Software | 3% 3% (n=31) of all Progress Software engineers (n=88645) were active on GitHub. | 1% 1% (n=31) of all Progress Software employees (n=2,28446) were active on GitHub. | 31 31 Progress Software employees were active on GitHub. | 
| 24. Okta | 3% 3% (n=46) of all Okta engineers (n=1,57047) were active on GitHub. | 1% 1% (n=46) of all Okta employees (n=5,90848) were active on GitHub. | 46 46 Okta employees were active on GitHub. | 
| 25. VMWare | 2% 2% (n=318) of all VMWare engineers (n=12,94449) were active on GitHub. | 1% 1% (n=318) of all VMWare employees (n=38,30050) were active on GitHub. | 318 318 VMWare employees were active on GitHub. | 
| 26. Alibaba | 2% 2% (n=236) of all Alibaba engineers (n=10,02551) were active on GitHub. | 0% 0% (n=236) of all Alibaba employees (n=224,95552) were active on GitHub. | 236 236 Alibaba employees were active on GitHub. | 
| 27. Snowflake, Inc. | 2% 2% (n=47) of all Snowflake, Inc. engineers (n=2,00253) were active on GitHub. | 1% 1% (n=47) of all Snowflake, Inc. employees (n=7,00454) were active on GitHub. | 47 47 Snowflake, Inc. employees were active on GitHub. | 
| 28. Square, Inc. | 2% 2% (n=47) of all Square, Inc. engineers (n=2,06055) were active on GitHub. | 0% 0% (n=47) of all Square, Inc. employees (n=12,98556) were active on GitHub. | 47 47 Square, Inc. employees were active on GitHub. | 
| 29. Amazon | 2% 2% (n=987) of all Amazon engineers (n=43,60557) were active on GitHub. | 1% 1% (n=987) of all Amazon employees (n=125,34558) were active on GitHub. | 987 987 Amazon employees were active on GitHub. | 
| 30. Hyland | 2% 2% (n=23) of all Hyland engineers (n=1,09259) were active on GitHub. | 1% 1% (n=23) of all Hyland employees (n=4,08560) were active on GitHub. | 23 23 Hyland employees were active on GitHub. | 
| 31. Adobe | 2% 2% (n=214) of all Adobe engineers (n=10,24761) were active on GitHub. | 1% 1% (n=214) of all Adobe employees (n=29,94562) were active on GitHub. | 214 214 Adobe employees were active on GitHub. | 
| 32. ThoughtWorks | 2% 2% (n=74) of all ThoughtWorks engineers (n=3,76563) were active on GitHub. | 1% 1% (n=74) of all ThoughtWorks employees (n=10,50064) were active on GitHub. | 74 74 ThoughtWorks employees were active on GitHub. | 
| 33. Zendesk | 2% 2% (n=27) of all Zendesk engineers (n=1,48165) were active on GitHub. | 0% 0% (n=27) of all Zendesk employees (n=6,17966) were active on GitHub. | 27 27 Zendesk employees were active on GitHub. | 
| 34. Twilio | 2% 2% (n=46) of all Twilio engineers (n=2,56367) were active on GitHub. | 1% 1% (n=46) of all Twilio employees (n=5,86768) were active on GitHub. | 46 46 Twilio employees were active on GitHub. | 
| 35. Arm Ltd | 2% 2% (n=83) of all Arm Ltd engineers (n=4,75369) were active on GitHub. | 1% 1% (n=83) of all Arm Ltd employees (n=5,96370) were active on GitHub. | 83 83 Arm Ltd employees were active on GitHub. | 
| 36. Netflix | 2% 2% (n=42) of all Netflix engineers (n=2,40971) were active on GitHub. | 0% 0% (n=42) of all Netflix employees (n=13,00072) were active on GitHub. | 42 42 Netflix employees were active on GitHub. | 
| 37. Splunk | 2% 2% (n=40) of all Splunk engineers (n=2,38773) were active on GitHub. | 1% 1% (n=40) of all Splunk employees (n=8,00074) were active on GitHub. | 40 40 Splunk employees were active on GitHub. | 
| 38. Zalando DE | 2% 2% (n=28) of all Zalando DE engineers (n=1,72275) were active on GitHub. | 0% 0% (n=28) of all Zalando DE employees (n=15,79376) were active on GitHub. | 28 28 Zalando DE employees were active on GitHub. | 
| 39. Google | 2% 2% (n=1,225) of all Google engineers (n=75,57177) were active on GitHub. | 1% 1% (n=1,225) of all Google employees (n=182,50278) were active on GitHub. | 1,225 1,225 Google employees were active on GitHub. | 
| 40. BBC | 2% 2% (n=29) of all BBC engineers (n=1,82279) were active on GitHub. | 0% 0% (n=29) of all BBC employees (n=21,63180) were active on GitHub. | 29 29 BBC employees were active on GitHub. | 
| 41. Yelp | 1% 1% (n=20) of all Yelp engineers (n=1,36481) were active on GitHub. | 0% 0% (n=20) of all Yelp employees (n=4,87282) were active on GitHub. | 20 20 Yelp employees were active on GitHub. | 
| 42. Tencent | 1% 1% (n=199) of all Tencent engineers (n=13,64283) were active on GitHub. | 0% 0% (n=199) of all Tencent employees (n=105,41784) were active on GitHub. | 199 199 Tencent employees were active on GitHub. | 
| 43. Unity Technologies | 1% 1% (n=56) of all Unity Technologies engineers (n=3,84485) were active on GitHub. | 1% 1% (n=56) of all Unity Technologies employees (n=6,74886) were active on GitHub. | 56 56 Unity Technologies employees were active on GitHub. | 
| 44. CyberAgent | 1% 1% (n=24) of all CyberAgent engineers (n=1,66087) were active on GitHub. | 0% 0% (n=24) of all CyberAgent employees (n=7,25188) were active on GitHub. | 24 24 CyberAgent employees were active on GitHub. | 
| 45. Stripe | 1% 1% (n=41) of all Stripe engineers (n=2,95289) were active on GitHub. | 0% 0% (n=41) of all Stripe employees (n=8,40990) were active on GitHub. | 41 41 Stripe employees were active on GitHub. | 
| 46. WIX | 1% 1% (n=30) of all WIX engineers (n=2,30191) were active on GitHub. | 1% 1% (n=30) of all WIX employees (n=4,60092) were active on GitHub. | 30 30 WIX employees were active on GitHub. | 
| 47. NVIDIA | 1% 1% (n=278) of all NVIDIA engineers (n=22,20093) were active on GitHub. | 1% 1% (n=278) of all NVIDIA employees (n=29,60094) were active on GitHub. | 278 278 NVIDIA employees were active on GitHub. | 
| 48. Spotify | 1% 1% (n=52) of all Spotify engineers (n=4,71995) were active on GitHub. | 1% 1% (n=52) of all Spotify employees (n=9,12396) were active on GitHub. | 52 52 Spotify employees were active on GitHub. | 
| 49. AMD | 1% 1% (n=139) of all AMD engineers (n=15,60697) were active on GitHub. | 1% 1% (n=139) of all AMD employees (n=26,00098) were active on GitHub. | 139 139 AMD employees were active on GitHub. | 
| 50. Uber | 1% 1% (n=56) of all Uber engineers (n=6,42699) were active on GitHub. | 0% 0% (n=56) of all Uber employees (n=30,400100) were active on GitHub. | 56 56 Uber employees were active on GitHub. | 
| 51. Indeed | 1% 1% (n=24) of all Indeed engineers (n=2,813101) were active on GitHub. | 0% 0% (n=24) of all Indeed employees (n=18,038102) were active on GitHub. | 24 24 Indeed employees were active on GitHub. | 
| 52. Atlassian | 1% 1% (n=45) of all Atlassian engineers (n=5,363103) were active on GitHub. | 0% 0% (n=45) of all Atlassian employees (n=10,726104) were active on GitHub. | 45 45 Atlassian employees were active on GitHub. | 
| 53. Autodesk | 1% 1% (n=35) of all Autodesk engineers (n=4,209105) were active on GitHub. | 0% 0% (n=35) of all Autodesk employees (n=14,100106) were active on GitHub. | 35 35 Autodesk employees were active on GitHub. | 
| 54. Meta | 1% 1% (n=260) of all Meta engineers (n=31,338107) were active on GitHub. | 0% 0% (n=260) of all Meta employees (n=67,317108) were active on GitHub. | 260 260 Meta employees were active on GitHub. | 
| 55. Booking.com | 1% 1% (n=22) of all Booking.com engineers (n=2,844109) were active on GitHub. | 0% 0% (n=22) of all Booking.com employees (n=23,600110) were active on GitHub. | 22 22 Booking.com employees were active on GitHub. | 
| 56. Intel | 1% 1% (n=434) of all Intel engineers (n=57,201111) were active on GitHub. | 0% 0% (n=434) of all Intel employees (n=124,800112) were active on GitHub. | 434 434 Intel employees were active on GitHub. | 
| 57. Salesforce | 1% 1% (n=139) of all Salesforce engineers (n=19,483113) were active on GitHub. | 0% 0% (n=139) of all Salesforce employees (n=72,682114) were active on GitHub. | 139 139 Salesforce employees were active on GitHub. | 
| 58. SAP SE | 1% 1% (n=238) of all SAP SE engineers (n=33,377115) were active on GitHub. | 0% 0% (n=238) of all SAP SE employees (n=107,602116) were active on GitHub. | 238 238 SAP SE employees were active on GitHub. | 
| 59. Bloomberg | 1% 1% (n=48) of all Bloomberg engineers (n=7,328117) were active on GitHub. | 0% 0% (n=48) of all Bloomberg employees (n=25,923118) were active on GitHub. | 48 48 Bloomberg employees were active on GitHub. | 
| 60. Yandex | 1% 1% (n=73) of all Yandex engineers (n=13,003119) were active on GitHub. | 0% 0% (n=73) of all Yandex employees (n=26,361120) were active on GitHub. | 73 73 Yandex employees were active on GitHub. | 
| 61. Cisco Systems | 0% 0% (n=108) of all Cisco Systems engineers (n=23,772121) were active on GitHub. | 0% 0% (n=108) of all Cisco Systems employees (n=84,900122) were active on GitHub. | 108 108 Cisco Systems employees were active on GitHub. | 
| 62. Oracle | 0% 0% (n=173) of all Oracle engineers (n=47,000123) were active on GitHub. | 0% 0% (n=173) of all Oracle employees (n=164,000124) were active on GitHub. | 173 173 Oracle employees were active on GitHub. | 
| 63. PayPal | 0% 0% (n=31) of all PayPal engineers (n=8,658125) were active on GitHub. | 0% 0% (n=31) of all PayPal employees (n=27,200126) were active on GitHub. | 31 31 PayPal employees were active on GitHub. | 
| 64. Baidu | 0% 0% (n=78) of all Baidu engineers (n=21,800127) were active on GitHub. | 0% 0% (n=78) of all Baidu employees (n=39,800128) were active on GitHub. | 78 78 Baidu employees were active on GitHub. | 
| 65. Apple | 0% 0% (n=150) of all Apple engineers (n=46,752129) were active on GitHub. | 0% 0% (n=150) of all Apple employees (n=161,000130) were active on GitHub. | 150 150 Apple employees were active on GitHub. | 
| 66. NetEase | 0% 0% (n=42) of all NetEase engineers (n=14,855131) were active on GitHub. | 0% 0% (n=42) of all NetEase employees (n=29,128132) were active on GitHub. | 42 42 NetEase employees were active on GitHub. | 
| 67. EPAM Systems | 0% 0% (n=86) of all EPAM Systems engineers (n=47,350133) were active on GitHub. | 0% 0% (n=86) of all EPAM Systems employees (n=53,150134) were active on GitHub. | 86 86 EPAM Systems employees were active on GitHub. | 
| 68. Ericsson | 0% 0% (n=36) of all Ericsson engineers (n=28,219135) were active on GitHub. | 0% 0% (n=36) of all Ericsson employees (n=99,952136) were active on GitHub. | 36 36 Ericsson employees were active on GitHub. | 
| 69. Nokia | 0% 0% (n=32) of all Nokia engineers (n=26,395137) were active on GitHub. | 0% 0% (n=32) of all Nokia employees (n=86,689138) were active on GitHub. | 32 32 Nokia employees were active on GitHub. | 
| 70. Capgemini | 0% 0% (n=56) of all Capgemini engineers (n=69,796139) were active on GitHub. | 0% 0% (n=56) of all Capgemini employees (n=340,400140) were active on GitHub. | 56 56 Capgemini employees were active on GitHub. | 
| 71. Samsung | 0% 0% (n=66) of all Samsung engineers (n=83,729141) were active on GitHub. | 0% 0% (n=66) of all Samsung employees (n=267,860142) were active on GitHub. | 66 66 Samsung employees were active on GitHub. | 
| 72. Huawei | 0% 0% (n=58) of all Huawei engineers (n=114,000143) were active on GitHub. | 0% 0% (n=58) of all Huawei employees (n=207,000144) were active on GitHub. | 58 58 Huawei employees were active on GitHub. | 
| 73. IBM | (n=1,592) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,592) of all IBM employees (n=282,200145) were active on GitHub. | 1,592 1,592 IBM employees were active on GitHub. | 
| 74. ByteDance | (n=157) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=157) of all ByteDance employees (n=NaN0) were active on GitHub. | 157 157 ByteDance employees were active on GitHub. | 
| 75. Canonical | (n=118) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=118) of all Canonical employees (n=NaN0) were active on GitHub. | 118 118 Canonical employees were active on GitHub. | 
| 76. Sentry.io | (n=71) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 19% 19% (n=71) of all Sentry.io employees (n=378146) were active on GitHub. | 71 71 Sentry.io employees were active on GitHub. | 
| 77. Accenture | (n=66) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=66) of all Accenture employees (n=733,000147) were active on GitHub. | 66 66 Accenture employees were active on GitHub. | 
| 78. Databricks | (n=61) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=61) of all Databricks employees (n=7,211148) were active on GitHub. | 61 61 Databricks employees were active on GitHub. | 
| 79. Software Mansion | (n=53) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=53) of all Software Mansion employees (n=NaN0) were active on GitHub. | 53 53 Software Mansion employees were active on GitHub. | 
| 80. Posit | (n=49) of all Posit engineers (n=NaN0) were active on GitHub. | (n=49) of all Posit employees (n=NaN0) were active on GitHub. | 49 49 Posit employees were active on GitHub. | 
| 81. @SSWConsulting | (n=44) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=44) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 44 44 @SSWConsulting employees were active on GitHub. | 
| 82. Intuit | (n=41) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=41) of all Intuit employees (n=18,200149) were active on GitHub. | 41 41 Intuit employees were active on GitHub. | 
| 83. Yahoo! | (n=40) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=40) of all Yahoo! employees (n=NaN0) were active on GitHub. | 40 40 Yahoo! employees were active on GitHub. | 
| 84. Harness | (n=33) of all Harness engineers (n=NaN0) were active on GitHub. | (n=33) of all Harness employees (n=NaN0) were active on GitHub. | 33 33 Harness employees were active on GitHub. | 
| 85. Kitware | (n=31) of all Kitware engineers (n=NaN0) were active on GitHub. | 18% 18% (n=31) of all Kitware employees (n=171150) were active on GitHub. | 31 31 Kitware employees were active on GitHub. | 
| 86. TU Delft | (n=27) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=27) of all TU Delft employees (n=NaN0) were active on GitHub. | 27 27 TU Delft employees were active on GitHub. | 
| 87. 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. | 
| 88. PingCAP | (n=27) of all PingCAP engineers (n=NaN0) were active on GitHub. | 7% 7% (n=27) of all PingCAP employees (n=410151) were active on GitHub. | 27 27 PingCAP employees were active on GitHub. | 
| 89. UCL | (n=25) of all UCL engineers (n=NaN0) were active on GitHub. | (n=25) of all UCL employees (n=NaN0) were active on GitHub. | 25 25 UCL employees were active on GitHub. | 
| 90. Palo Alto Networks | (n=25) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=25) of all Palo Alto Networks employees (n=13,948152) were active on GitHub. | 25 25 Palo Alto Networks employees were active on GitHub. | 
| 91. Ant Group | (n=22) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=22) of all Ant Group employees (n=NaN0) were active on GitHub. | 22 22 Ant Group employees were active on GitHub. | 
| 92. Orange S.A. | (n=22) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=22) of all Orange S.A. employees (n=127,109153) were active on GitHub. | 22 22 Orange S.A. employees were active on GitHub. | 
| 93. 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. | 
| 94. Qlik | (n=21) of all Qlik engineers (n=NaN0) were active on GitHub. | (n=21) of all Qlik employees (n=NaN0) were active on GitHub. | 21 21 Qlik employees were active on GitHub. | 
| 95. Sanity | (n=21) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=21) of all Sanity employees (n=NaN0) were active on GitHub. | 21 21 Sanity employees were active on GitHub. | 
| 96. ClickHouse | (n=20) of all ClickHouse engineers (n=NaN0) were active on GitHub. | 13% 13% (n=20) of all ClickHouse employees (n=150154) were active on GitHub. | 20 20 ClickHouse employees were active on GitHub. | 
| 97. @MathWorks | (n=20) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=20) of all @MathWorks employees (n=NaN0) were active on GitHub. | 20 20 @MathWorks employees were active on GitHub. | 
| 98. Cloudera | (n=20) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=20) of all Cloudera employees (n=NaN0) were active on GitHub. | 20 20 Cloudera employees were active on GitHub. | 
| 99. @paritytech | (n=20) of all @paritytech engineers (n=NaN0) were active on GitHub. | (n=20) of all @paritytech employees (n=NaN0) were active on GitHub. | 20 20 @paritytech employees were active on GitHub. | 
| 100. @apache | (n=20) of all @apache engineers (n=NaN0) were active on GitHub. | (n=20) of all @apache employees (n=NaN0) were active on GitHub. | 20 20 @apache employees were active on GitHub. | 
References
- Grafana Labs engineer count: linkedin.com
- Grafana Labs employee count: linkedin.com
- Vercel engineer count: linkedin.com
- Vercel employee count: linkedin.com
- SUSE engineer count: linkedin.com
- SUSE employee count: links.imagerelay.com (page 10)
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved December 2023)
- 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)
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 13)
- 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
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- WikiMedia Foundation engineer count: linkedin.com
- WikiMedia Foundation employee count: wikimediafoundation.org
- DataDog engineer count: sec.gov (page 10, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 11)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 17)
- MongoDB engineer count: sec.gov (page 12, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 9)
- 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
- Odoo engineer count: linkedin.com
- Odoo employee count: linkedin.com
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Shopify engineer count: linkedin.com (retrieved Dec 2023)
- Shopify employee count: s27.q4cdn.com (page 22)
- 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)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 14)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 16)
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Interim Report, page 15)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 17)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 20)
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Hyland engineer count: linkedin.com
- Hyland employee count: linkedin.com
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 18)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- Zendesk engineer count: linkedin.com (retrieved Dec 2023)
- Zendesk employee count: linkedin.com (retrieved Dec 2023)
- Twilio engineer count: sec.gov (page 8, 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)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- Splunk engineer count: linkedin.com
- Splunk employee count: sec.gov (page 11)
- 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)
- BBC engineer count: linkedin.com
- BBC employee count: bbc.co.uk (page 59)
- Yelp engineer count: sec.gov (page 13, referred to as employees in 'product development')
- Yelp employee count: sec.gov (page 13)
- 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)
- CyberAgent engineer count: cyberagent.co.jp (page 8)
- CyberAgent employee count: cyberagent.co.jp (page 8)
- 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)
- 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)
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 12)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 7)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- 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)
- Autodesk engineer count: linkedin.com (retrieved Dec 2023)
- Autodesk employee count: sec.gov (page 13)
- Meta engineer count: linkedin.com
- Meta employee count: sec.gov (page 60)
- Booking.com engineer count: linkedin.com
- Booking.com employee count: sec.gov (page 6)
- 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)
- 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)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- Yandex engineer count: sec.gov (page 54, referred to as employees in 'product development')
- Yandex employee count: sec.gov (page 54)
- 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)
- PayPal engineer count: linkedin.com
- PayPal employee count: sec.gov (page 13)
- Baidu engineer count: sec.gov (page 196, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 196)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- NetEase engineer count: sec.gov (page 156, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 156)
- 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)
- Capgemini engineer count: linkedin.com
- Capgemini employee count: investors.capgemini.com (page 4)
- Samsung engineer count: samsung.com (page 58, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 58)
- 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)
- Sentry.io employee count: linkedin.com
- Accenture employee count: sec.gov (page 25)
- Databricks employee count: linkedin.com
- Intuit employee count: sec.gov (page 12)
- Kitware employee count: linkedin.com
- PingCAP employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)
- Orange S.A. employee count: gallery.orange.com (page 58)
- ClickHouse employee count: linkedin.com (Retrieved September 2025)