Corporate GitHub Activity
Most Active Corporations on GitHub, 10 2021
Ranking companies with employees who, during 10 2021, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Grafana Labs | 35% 35% (n=85) of all Grafana Labs engineers (n=2401) were active on GitHub. | 21% 21% (n=85) of all Grafana Labs employees (n=4002) were active on GitHub. | 85 85 Grafana Labs employees were active on GitHub. | 
|---|---|---|---|
| 2. SUSE | 30% 30% (n=142) of all SUSE engineers (n=4753) were active on GitHub. | 7% 7% (n=142) of all SUSE employees (n=2,0454) were active on GitHub. | 142 142 SUSE employees were active on GitHub. | 
| 3. Automattic | 26% 26% (n=171) of all Automattic engineers (n=6655) were active on GitHub. | 10% 10% (n=171) of all Automattic employees (n=1,7006) were active on GitHub. | 171 171 Automattic employees were active on GitHub. | 
| 4. JetBrains | 24% 24% (n=137) of all JetBrains engineers (n=5757) were active on GitHub. | 7% 7% (n=137) of all JetBrains employees (n=1,9008) were active on GitHub. | 137 137 JetBrains employees were active on GitHub. | 
| 5. Elastic | 23% 23% (n=212) of all Elastic engineers (n=9059) were active on GitHub. | 7% 7% (n=212) of all Elastic employees (n=2,97810) were active on GitHub. | 212 212 Elastic employees were active on GitHub. | 
| 6. HashiCorp | 21% 21% (n=103) of all HashiCorp engineers (n=50011) were active on GitHub. | 6% 6% (n=103) of all HashiCorp employees (n=1,85012) were active on GitHub. | 103 103 HashiCorp employees were active on GitHub. | 
| 7. Mozilla | 20% 20% (n=108) of all Mozilla engineers (n=54713) were active on GitHub. | 8% 8% (n=108) of all Mozilla employees (n=1,38514) were active on GitHub. | 108 108 Mozilla employees were active on GitHub. | 
| 8. The Guardian | 18% 18% (n=20) of all The Guardian engineers (n=11215) were active on GitHub. | 1% 1% (n=20) of all The Guardian employees (n=2,13016) were active on GitHub. | 20 20 The Guardian employees were active on GitHub. | 
| 9. Mapbox | 17% 17% (n=43) of all Mapbox engineers (n=25017) were active on GitHub. | 7% 7% (n=43) of all Mapbox employees (n=60118) were active on GitHub. | 43 43 Mapbox employees were active on GitHub. | 
| 10. Docker | 16% 16% (n=12) of all Docker engineers (n=7419) were active on GitHub. | 5% 5% (n=12) of all Docker employees (n=26320) were active on GitHub. | 12 12 Docker employees were active on GitHub. | 
| 11. DataDog | 10% 10% (n=133) of all DataDog engineers (n=1,40021) were active on GitHub. | 4% 4% (n=133) of all DataDog employees (n=3,20022) were active on GitHub. | 133 133 DataDog employees were active on GitHub. | 
| 12. Cloudflare | 8% 8% (n=40) of all Cloudflare engineers (n=52623) were active on GitHub. | 2% 2% (n=40) of all Cloudflare employees (n=2,44024) were active on GitHub. | 40 40 Cloudflare employees were active on GitHub. | 
| 13. WikiMedia Foundation | 7% 7% (n=13) of all WikiMedia Foundation engineers (n=18525) were active on GitHub. | (n=13) of all WikiMedia Foundation employees (n=NaN0) were active on GitHub. | 13 13 WikiMedia Foundation employees were active on GitHub. | 
| 14. MongoDB | 7% 7% (n=59) of all MongoDB engineers (n=86326) were active on GitHub. | 2% 2% (n=59) of all MongoDB employees (n=3,54427) were active on GitHub. | 59 59 MongoDB employees were active on GitHub. | 
| 15. New Relic | 6% 6% (n=44) of all New Relic engineers (n=74428) were active on GitHub. | 2% 2% (n=44) of all New Relic employees (n=2,21729) were active on GitHub. | 44 44 New Relic employees were active on GitHub. | 
| 16. WSO2 | 5% 5% (n=43) of all WSO2 engineers (n=85030) were active on GitHub. | 4% 4% (n=43) of all WSO2 employees (n=97831) were active on GitHub. | 43 43 WSO2 employees were active on GitHub. | 
| 17. Confluent | 4% 4% (n=29) of all Confluent engineers (n=65932) were active on GitHub. | 1% 1% (n=29) of all Confluent employees (n=1,98133) were active on GitHub. | 29 29 Confluent employees were active on GitHub. | 
| 18. Odoo | 4% 4% (n=15) of all Odoo engineers (n=37934) were active on GitHub. | 2% 2% (n=15) of all Odoo employees (n=94535) were active on GitHub. | 15 15 Odoo employees were active on GitHub. | 
| 19. Microsoft | 3% 3% (n=1,989) of all Microsoft engineers (n=60,00036) were active on GitHub. | 1% 1% (n=1,989) of all Microsoft employees (n=181,00037) were active on GitHub. | 1,989 1,989 Microsoft employees were active on GitHub. | 
| 20. Liferay | 3% 3% (n=14) of all Liferay engineers (n=43138) were active on GitHub. | 1% 1% (n=14) of all Liferay employees (n=1,19239) were active on GitHub. | 14 14 Liferay employees were active on GitHub. | 
| 21. Unity Technologies | 3% 3% (n=82) of all Unity Technologies engineers (n=2,77640) were active on GitHub. | 2% 2% (n=82) of all Unity Technologies employees (n=5,24541) were active on GitHub. | 82 82 Unity Technologies employees were active on GitHub. | 
| 22. Okta | 3% 3% (n=34) of all Okta engineers (n=1,23142) were active on GitHub. | 1% 1% (n=34) of all Okta employees (n=5,03043) were active on GitHub. | 34 34 Okta employees were active on GitHub. | 
| 23. Square, Inc. | 2% 2% (n=38) of all Square, Inc. engineers (n=1,62144) were active on GitHub. | 0% 0% (n=38) of all Square, Inc. employees (n=8,52145) were active on GitHub. | 38 38 Square, Inc. employees were active on GitHub. | 
| 24. ESRI | 2% 2% (n=39) of all ESRI engineers (n=1,82046) were active on GitHub. | 1% 1% (n=39) of all ESRI employees (n=5,42947) were active on GitHub. | 39 39 ESRI employees were active on GitHub. | 
| 25. Alibaba | 2% 2% (n=193) of all Alibaba engineers (n=9,25548) were active on GitHub. | 0% 0% (n=193) of all Alibaba employees (n=251,46249) were active on GitHub. | 193 193 Alibaba employees were active on GitHub. | 
| 26. Shopify | 2% 2% (n=82) of all Shopify engineers (n=4,36050) were active on GitHub. | 1% 1% (n=82) of all Shopify employees (n=10,00051) were active on GitHub. | 82 82 Shopify employees were active on GitHub. | 
| 27. Progress Software | 2% 2% (n=15) of all Progress Software engineers (n=81852) were active on GitHub. | 1% 1% (n=15) of all Progress Software employees (n=2,10353) were active on GitHub. | 15 15 Progress Software employees were active on GitHub. | 
| 28. Netflix | 2% 2% (n=37) of all Netflix engineers (n=2,12154) were active on GitHub. | 0% 0% (n=37) of all Netflix employees (n=11,30055) were active on GitHub. | 37 37 Netflix employees were active on GitHub. | 
| 29. VMWare | 2% 2% (n=236) of all VMWare engineers (n=13,96556) were active on GitHub. | 1% 1% (n=236) of all VMWare employees (n=37,50057) were active on GitHub. | 236 236 VMWare employees were active on GitHub. | 
| 30. Splunk | 2% 2% (n=34) of all Splunk engineers (n=2,11858) were active on GitHub. | 0% 0% (n=34) of all Splunk employees (n=7,00059) were active on GitHub. | 34 34 Splunk employees were active on GitHub. | 
| 31. WIX | 2% 2% (n=37) of all WIX engineers (n=2,34960) were active on GitHub. | 1% 1% (n=37) of all WIX employees (n=5,05761) were active on GitHub. | 37 37 WIX employees were active on GitHub. | 
| 32. Hyland | 2% 2% (n=16) of all Hyland engineers (n=1,02662) were active on GitHub. | 0% 0% (n=16) of all Hyland employees (n=4,10063) were active on GitHub. | 16 16 Hyland employees were active on GitHub. | 
| 33. Amazon | 1% 1% (n=566) of all Amazon engineers (n=38,27764) were active on GitHub. | 1% 1% (n=566) of all Amazon employees (n=85,26665) were active on GitHub. | 566 566 Amazon employees were active on GitHub. | 
| 34. Twilio | 1% 1% (n=45) of all Twilio engineers (n=3,10366) were active on GitHub. | 1% 1% (n=45) of all Twilio employees (n=7,86767) were active on GitHub. | 45 45 Twilio employees were active on GitHub. | 
| 35. Google | 1% 1% (n=900) of all Google engineers (n=62,37768) were active on GitHub. | 1% 1% (n=900) of all Google employees (n=156,50069) were active on GitHub. | 900 900 Google employees were active on GitHub. | 
| 36. ThoughtWorks | 1% 1% (n=50) of all ThoughtWorks engineers (n=3,65870) were active on GitHub. | 0% 0% (n=50) of all ThoughtWorks employees (n=10,60071) were active on GitHub. | 50 50 ThoughtWorks employees were active on GitHub. | 
| 37. Zalando DE | 1% 1% (n=21) of all Zalando DE engineers (n=1,54672) were active on GitHub. | 0% 0% (n=21) of all Zalando DE employees (n=17,04373) were active on GitHub. | 21 21 Zalando DE employees were active on GitHub. | 
| 38. Spotify | 1% 1% (n=42) of all Spotify engineers (n=3,17574) were active on GitHub. | 1% 1% (n=42) of all Spotify employees (n=6,61775) were active on GitHub. | 42 42 Spotify employees were active on GitHub. | 
| 39. Lyft | 1% 1% (n=22) of all Lyft engineers (n=1,78176) were active on GitHub. | 0% 0% (n=22) of all Lyft employees (n=4,45377) were active on GitHub. | 22 22 Lyft employees were active on GitHub. | 
| 40. Atlassian | 1% 1% (n=38) of all Atlassian engineers (n=3,21678) were active on GitHub. | 1% 1% (n=38) of all Atlassian employees (n=6,43379) were active on GitHub. | 38 38 Atlassian employees were active on GitHub. | 
| 41. Stripe | 1% 1% (n=35) of all Stripe engineers (n=3,05080) were active on GitHub. | 1% 1% (n=35) of all Stripe employees (n=4,65381) were active on GitHub. | 35 35 Stripe employees were active on GitHub. | 
| 42. Tencent | 1% 1% (n=115) of all Tencent engineers (n=11,57282) were active on GitHub. | 0% 0% (n=115) of all Tencent employees (n=112,77183) were active on GitHub. | 115 115 Tencent employees were active on GitHub. | 
| 43. Twitter | 1% 1% (n=23) of all Twitter engineers (n=2,42484) were active on GitHub. | 0% 0% (n=23) of all Twitter employees (n=8,20085) were active on GitHub. | 23 23 Twitter employees were active on GitHub. | 
| 44. Adobe | 1% 1% (n=86) of all Adobe engineers (n=9,60186) were active on GitHub. | 0% 0% (n=86) of all Adobe employees (n=25,98887) were active on GitHub. | 86 86 Adobe employees were active on GitHub. | 
| 45. Airbnb | 1% 1% (n=14) of all Airbnb engineers (n=1,67588) were active on GitHub. | 0% 0% (n=14) of all Airbnb employees (n=6,13289) were active on GitHub. | 14 14 Airbnb employees were active on GitHub. | 
| 46. NVIDIA | 1% 1% (n=133) of all NVIDIA engineers (n=16,24290) were active on GitHub. | 1% 1% (n=133) of all NVIDIA employees (n=22,47391) were active on GitHub. | 133 133 NVIDIA employees were active on GitHub. | 
| 47. Zendesk | 1% 1% (n=13) of all Zendesk engineers (n=1,65092) were active on GitHub. | 0% 0% (n=13) of all Zendesk employees (n=5,86093) were active on GitHub. | 13 13 Zendesk employees were active on GitHub. | 
| 48. Uber | 1% 1% (n=37) of all Uber engineers (n=4,78494) were active on GitHub. | 0% 0% (n=37) of all Uber employees (n=29,30095) were active on GitHub. | 37 37 Uber employees were active on GitHub. | 
| 49. Indeed | 1% 1% (n=14) of all Indeed engineers (n=2,15596) were active on GitHub. | 0% 0% (n=14) of all Indeed employees (n=12,70997) were active on GitHub. | 14 14 Indeed employees were active on GitHub. | 
| 50. Salesforce | 1% 1% (n=127) of all Salesforce engineers (n=21,35998) were active on GitHub. | 0% 0% (n=127) of all Salesforce employees (n=73,54199) were active on GitHub. | 127 127 Salesforce employees were active on GitHub. | 
| 51. CyberAgent | 1% 1% (n=15) of all CyberAgent engineers (n=2,549100) were active on GitHub. | 0% 0% (n=15) of all CyberAgent employees (n=5,944101) were active on GitHub. | 15 15 CyberAgent employees were active on GitHub. | 
| 52. Autodesk | 0% 0% (n=16) of all Autodesk engineers (n=3,519102) were active on GitHub. | 0% 0% (n=16) of all Autodesk employees (n=11,500103) were active on GitHub. | 16 16 Autodesk employees were active on GitHub. | 
| 53. SAP SE | 0% 0% (n=146) of all SAP SE engineers (n=32,244104) were active on GitHub. | 0% 0% (n=146) of all SAP SE employees (n=107,415105) were active on GitHub. | 146 146 SAP SE employees were active on GitHub. | 
| 54. Yandex | 0% 0% (n=38) of all Yandex engineers (n=9,192106) were active on GitHub. | 0% 0% (n=38) of all Yandex employees (n=18,004107) were active on GitHub. | 38 38 Yandex employees were active on GitHub. | 
| 55. Intel | 0% 0% (n=253) of all Intel engineers (n=61,806108) were active on GitHub. | 0% 0% (n=253) of all Intel employees (n=121,100109) were active on GitHub. | 253 253 Intel employees were active on GitHub. | 
| 56. Bloomberg | 0% 0% (n=20) of all Bloomberg engineers (n=5,316110) were active on GitHub. | 0% 0% (n=20) of all Bloomberg employees (n=21,559111) were active on GitHub. | 20 20 Bloomberg employees were active on GitHub. | 
| 57. AMD | 0% 0% (n=37) of all AMD engineers (n=10,749112) were active on GitHub. | 0% 0% (n=37) of all AMD employees (n=15,500113) were active on GitHub. | 37 37 AMD employees were active on GitHub. | 
| 58. Workday | 0% 0% (n=13) of all Workday engineers (n=4,886114) were active on GitHub. | 0% 0% (n=13) of all Workday employees (n=15,200115) were active on GitHub. | 13 13 Workday employees were active on GitHub. | 
| 59. Baidu | 0% 0% (n=73) of all Baidu engineers (n=27,500116) were active on GitHub. | 0% 0% (n=73) of all Baidu employees (n=45,500117) were active on GitHub. | 73 73 Baidu employees were active on GitHub. | 
| 60. Apple | 0% 0% (n=84) of all Apple engineers (n=33,076118) were active on GitHub. | 0% 0% (n=84) of all Apple employees (n=154,000119) were active on GitHub. | 84 84 Apple employees were active on GitHub. | 
| 61. Oracle | 0% 0% (n=75) of all Oracle engineers (n=40,000120) were active on GitHub. | 0% 0% (n=75) of all Oracle employees (n=132,000121) were active on GitHub. | 75 75 Oracle employees were active on GitHub. | 
| 62. Cisco Systems | 0% 0% (n=40) of all Cisco Systems engineers (n=23,532122) were active on GitHub. | 0% 0% (n=40) of all Cisco Systems employees (n=79,500123) were active on GitHub. | 40 40 Cisco Systems employees were active on GitHub. | 
| 63. PayPal | 0% 0% (n=14) of all PayPal engineers (n=9,157124) were active on GitHub. | 0% 0% (n=14) of all PayPal employees (n=30,900125) were active on GitHub. | 14 14 PayPal employees were active on GitHub. | 
| 64. NetEase | 0% 0% (n=19) of all NetEase engineers (n=15,292126) were active on GitHub. | 0% 0% (n=19) of all NetEase employees (n=32,064127) were active on GitHub. | 19 19 NetEase employees were active on GitHub. | 
| 65. EPAM Systems | 0% 0% (n=57) of all EPAM Systems engineers (n=52,617128) were active on GitHub. | 0% 0% (n=57) of all EPAM Systems employees (n=58,824129) were active on GitHub. | 57 57 EPAM Systems employees were active on GitHub. | 
| 66. Samsung | 0% 0% (n=51) of all Samsung engineers (n=75,229130) were active on GitHub. | 0% 0% (n=51) of all Samsung employees (n=266,673131) were active on GitHub. | 51 51 Samsung employees were active on GitHub. | 
| 67. Ericsson | 0% 0% (n=14) of all Ericsson engineers (n=27,379132) were active on GitHub. | 0% 0% (n=14) of all Ericsson employees (n=101,322133) were active on GitHub. | 14 14 Ericsson employees were active on GitHub. | 
| 68. Huawei | 0% 0% (n=35) of all Huawei engineers (n=107,000134) were active on GitHub. | 0% 0% (n=35) of all Huawei employees (n=195,000135) were active on GitHub. | 35 35 Huawei employees were active on GitHub. | 
| 69. Capgemini | 0% 0% (n=21) of all Capgemini engineers (n=67,119136) were active on GitHub. | 0% 0% (n=21) of all Capgemini employees (n=325,000137) were active on GitHub. | 21 21 Capgemini employees were active on GitHub. | 
| 70. IBM | (n=882) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=882) of all IBM employees (n=282,100138) were active on GitHub. | 882 882 IBM employees were active on GitHub. | 
| 71. Facebook | (n=203) of all Facebook engineers (n=NaN0) were active on GitHub. | 0% 0% (n=203) of all Facebook employees (n=71,970139) were active on GitHub. | 203 203 Facebook employees were active on GitHub. | 
| 72. ByteDance | (n=56) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=56) of all ByteDance employees (n=NaN0) were active on GitHub. | 56 56 ByteDance employees were active on GitHub. | 
| 73. Arm Ltd | (n=53) of all Arm Ltd engineers (n=NaN0) were active on GitHub. | (n=53) of all Arm Ltd employees (n=NaN0) were active on GitHub. | 53 53 Arm Ltd employees were active on GitHub. | 
| 74. 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. | 
| 75. Trybe | (n=39) of all Trybe engineers (n=NaN0) were active on GitHub. | (n=39) of all Trybe employees (n=NaN0) were active on GitHub. | 39 39 Trybe employees were active on GitHub. | 
| 76. Canonical | (n=39) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=39) of all Canonical employees (n=NaN0) were active on GitHub. | 39 39 Canonical employees were active on GitHub. | 
| 77. Sentry.io | (n=35) of all Sentry.io engineers (n=NaN0) were active on GitHub. | (n=35) of all Sentry.io employees (n=NaN0) were active on GitHub. | 35 35 Sentry.io employees were active on GitHub. | 
| 78. Snyk | (n=35) of all Snyk engineers (n=NaN0) were active on GitHub. | (n=35) of all Snyk employees (n=NaN0) were active on GitHub. | 35 35 Snyk employees were active on GitHub. | 
| 79. Accenture | (n=32) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=32) of all Accenture employees (n=624,000140) were active on GitHub. | 32 32 Accenture employees were active on GitHub. | 
| 80. Databricks | (n=28) of all Databricks engineers (n=NaN0) were active on GitHub. | (n=28) of all Databricks employees (n=NaN0) were active on GitHub. | 28 28 Databricks employees were active on GitHub. | 
| 81. CircleCI | (n=24) of all CircleCI engineers (n=NaN0) were active on GitHub. | (n=24) of all CircleCI employees (n=NaN0) were active on GitHub. | 24 24 CircleCI employees were active on GitHub. | 
| 82. 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. | 
| 83. Intuit | (n=22) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=22) of all Intuit employees (n=13,500141) were active on GitHub. | 22 22 Intuit employees were active on GitHub. | 
| 84. Kitware | (n=20) of all Kitware engineers (n=NaN0) were active on GitHub. | 12% 12% (n=20) of all Kitware employees (n=163142) were active on GitHub. | 20 20 Kitware employees were active on GitHub. | 
| 85. RStudio | (n=19) of all RStudio engineers (n=NaN0) were active on GitHub. | (n=19) of all RStudio employees (n=NaN0) were active on GitHub. | 19 19 RStudio employees were active on GitHub. | 
| 86. PingCAP | (n=19) of all PingCAP engineers (n=NaN0) were active on GitHub. | (n=19) of all PingCAP employees (n=NaN0) were active on GitHub. | 19 19 PingCAP employees were active on GitHub. | 
| 87. Cloudera | (n=19) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=19) of all Cloudera employees (n=NaN0) were active on GitHub. | 19 19 Cloudera employees were active on GitHub. | 
| 88. Ascensio System SIA | (n=18) of all Ascensio System SIA engineers (n=NaN0) were active on GitHub. | (n=18) of all Ascensio System SIA employees (n=NaN0) were active on GitHub. | 18 18 Ascensio System SIA employees were active on GitHub. | 
| 89. Vercel | (n=17) of all Vercel engineers (n=NaN0) were active on GitHub. | 16% 16% (n=17) of all Vercel employees (n=104143) were active on GitHub. | 17 17 Vercel employees were active on GitHub. | 
| 90. Palo Alto Networks | (n=17) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=17) of all Palo Alto Networks employees (n=10,473144) were active on GitHub. | 17 17 Palo Alto Networks employees were active on GitHub. | 
| 91. Expensify | (n=16) of all Expensify engineers (n=NaN0) were active on GitHub. | (n=16) of all Expensify employees (n=NaN0) were active on GitHub. | 16 16 Expensify employees were active on GitHub. | 
| 92. Dynatrace | (n=16) of all Dynatrace engineers (n=NaN0) were active on GitHub. | (n=16) of all Dynatrace employees (n=NaN0) were active on GitHub. | 16 16 Dynatrace employees were active on GitHub. | 
| 93. @sourcegraph | (n=16) of all @sourcegraph engineers (n=NaN0) were active on GitHub. | (n=16) of all @sourcegraph employees (n=NaN0) were active on GitHub. | 16 16 @sourcegraph employees were active on GitHub. | 
| 94. Akeneo | (n=15) of all Akeneo engineers (n=NaN0) were active on GitHub. | (n=15) of all Akeneo employees (n=NaN0) were active on GitHub. | 15 15 Akeneo employees were active on GitHub. | 
| 95. Sourcegraph | (n=15) of all Sourcegraph engineers (n=NaN0) were active on GitHub. | (n=15) of all Sourcegraph employees (n=NaN0) were active on GitHub. | 15 15 Sourcegraph employees were active on GitHub. | 
| 96. Tata Consultancy Services | (n=14) of all Tata Consultancy Services engineers (n=NaN0) were active on GitHub. | (n=14) of all Tata Consultancy Services employees (n=NaN0) were active on GitHub. | 14 14 Tata Consultancy Services employees were active on GitHub. | 
| 97. @wazuh | (n=14) of all @wazuh engineers (n=NaN0) were active on GitHub. | (n=14) of all @wazuh employees (n=NaN0) were active on GitHub. | 14 14 @wazuh employees were active on GitHub. | 
| 98. @paritytech | (n=14) of all @paritytech engineers (n=NaN0) were active on GitHub. | (n=14) of all @paritytech employees (n=NaN0) were active on GitHub. | 14 14 @paritytech employees were active on GitHub. | 
| 99. Infosys | (n=13) of all Infosys engineers (n=NaN0) were active on GitHub. | (n=13) of all Infosys employees (n=NaN0) were active on GitHub. | 13 13 Infosys employees were active on GitHub. | 
| 100. @paritytech | (n=12) of all @paritytech engineers (n=NaN0) were active on GitHub. | (n=12) of all @paritytech employees (n=NaN0) were active on GitHub. | 12 12 @paritytech 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 FY21, page 228)
- Automattic engineer count: linkedin.com
- Automattic employee count: automattic.com (retrieved March 2022)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Elastic engineer count: linkedin.com
- Elastic employee count: sec.gov (page 13)
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 14)
- Mozilla engineer count: linkedin.com
- Mozilla employee count: linkedin.com
- The Guardian engineer count: linkedin.com
- The Guardian employee count: linkedin.com
- Mapbox engineer count: linkedin.com
- Mapbox employee count: linkedin.com
- Docker engineer count: linkedin.com
- Docker 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)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 16)
- 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)
- New Relic engineer count: linkedin.com
- New Relic employee count: sec.gov (page 8)
- WSO2 engineer count: linkedin.com
- WSO2 employee count: linkedin.com
- Confluent engineer count: linkedin.com
- Confluent employee count: sec.gov (page 14)
- Odoo engineer count: linkedin.com
- Odoo 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)
- Liferay engineer count: linkedin.com
- Liferay employee count: linkedin.com
- Unity Technologies engineer count: sec.gov (page 11, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 11)
- Okta engineer count: linkedin.com
- Okta employee count: sec.gov (page 13)
- Square, Inc. engineer count: linkedin.com
- Square, Inc. employee count: sec.gov (page 13)
- ESRI engineer count: linkedin.com
- ESRI employee count: linkedin.com
- Alibaba engineer count: linkedin.com
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2023 Annual Report, page 168)
- Shopify engineer count: linkedin.com
- Shopify employee count: s27.q4cdn.com (page 22)
- Progress Software engineer count: sec.gov (page 9, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 9)
- Netflix engineer count: linkedin.com
- Netflix employee count: sec.gov (page 2)
- VMWare engineer count: linkedin.com
- VMWare employee count: sec.gov (page 14)
- 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)
- Hyland engineer count: linkedin.com
- Hyland employee count: linkedin.com
- Amazon engineer count: linkedin.com
- Amazon employee count: linkedin.com
- Twilio engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 12)
- Google engineer count: linkedin.com
- Google employee count: sec.gov (page 9)
- ThoughtWorks engineer count: linkedin.com
- ThoughtWorks employee count: sec.gov (page 6)
- 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)
- 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)
- 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)
- Stripe engineer count: linkedin.com
- Stripe employee count: linkedin.com
- Tencent engineer count: linkedin.com
- Tencent employee count: static.tencent.com (page 75)
- Twitter engineer count: linkedin.com
- Twitter employee count: sec.gov (page 11)
- Adobe engineer count: linkedin.com
- Adobe employee count: sec.gov (page 16)
- Airbnb engineer count: sec.gov (page 5)
- Airbnb employee count: sec.gov (page 6)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Zendesk engineer count: sec.gov (page 9, referred to as employees in 'research and development')
- Zendesk employee count: sec.gov (page 54)
- Uber engineer count: linkedin.com
- Uber employee count: sec.gov (page 8)
- Indeed engineer count: linkedin.com
- Indeed employee count: linkedin.com
- Salesforce engineer count: linkedin.com
- Salesforce employee count: sec.gov (page 9)
- CyberAgent engineer count: d2utiq8et4vl56.cloudfront.net (page 30, referred to as 'engineers and creators')
- CyberAgent employee count: d2utiq8et4vl56.cloudfront.net (page 127)
- Autodesk engineer count: linkedin.com
- Autodesk employee count: sec.gov (page 13)
- 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)
- 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)
- Bloomberg engineer count: linkedin.com
- Bloomberg employee count: linkedin.com
- AMD engineer count: linkedin.com
- AMD employee count: sec.gov (page 11)
- Workday engineer count: linkedin.com
- Workday employee count: sec.gov (page 3)
- Baidu engineer count: sec.gov (page 185, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 185)
- Apple engineer count: linkedin.com
- Apple employee count: sec.gov (page 4)
- 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)
- 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)
- Samsung engineer count: samsung.com (page 103, referred to as employees in 'development')
- Samsung employee count: samsung.com (page 103)
- Ericsson engineer count: sec.gov (page 9, referred to as employees in 'R&D')
- Ericsson employee count: sec.gov (page 8)
- 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
- Vercel employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 11)