Corporate GitHub Activity
Most Active Corporations on GitHub, 07 2025
Ranking companies with employees who, during 07 2025, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Sentry.io | 43% 43% (n=85) of all Sentry.io engineers (n=1971) were active on GitHub. | 20% 20% (n=85) of all Sentry.io employees (n=4192) were active on GitHub. | 85 85 Sentry.io employees were active on GitHub. | 
|---|---|---|---|
| 2. Vercel | 34% 34% (n=75) of all Vercel engineers (n=2203) were active on GitHub. | 10% 10% (n=75) of all Vercel employees (n=7314) were active on GitHub. | 75 75 Vercel employees were active on GitHub. | 
| 3. Grafana Labs | 32% 32% (n=209) of all Grafana Labs engineers (n=6495) were active on GitHub. | 13% 13% (n=209) of all Grafana Labs employees (n=1,5916) were active on GitHub. | 209 209 Grafana Labs employees were active on GitHub. | 
| 4. SUSE | 29% 29% (n=207) of all SUSE engineers (n=7187) were active on GitHub. | 8% 8% (n=207) of all SUSE employees (n=2,6638) were active on GitHub. | 207 207 SUSE employees were active on GitHub. | 
| 5. Kitware | 27% 27% (n=27) of all Kitware engineers (n=999) were active on GitHub. | 18% 18% (n=27) of all Kitware employees (n=15310) were active on GitHub. | 27 27 Kitware employees were active on GitHub. | 
| 6. Automattic | 23% 23% (n=157) of all Automattic engineers (n=67911) were active on GitHub. | 18% 18% (n=157) of all Automattic employees (n=88712) were active on GitHub. | 157 157 Automattic employees were active on GitHub. | 
| 7. Elastic | 22% 22% (n=286) of all Elastic engineers (n=1,32213) were active on GitHub. | 8% 8% (n=286) of all Elastic employees (n=3,53714) were active on GitHub. | 286 286 Elastic employees were active on GitHub. | 
| 8. Mozilla | 18% 18% (n=118) of all Mozilla engineers (n=64815) were active on GitHub. | 7% 7% (n=118) of all Mozilla employees (n=1,74916) were active on GitHub. | 118 118 Mozilla employees were active on GitHub. | 
| 9. Docker | 15% 15% (n=30) of all Docker engineers (n=19417) were active on GitHub. | 3% 3% (n=30) of all Docker employees (n=94118) were active on GitHub. | 30 30 Docker employees were active on GitHub. | 
| 10. ClickHouse | 15% 15% (n=25) of all ClickHouse engineers (n=16219) were active on GitHub. | 7% 7% (n=25) of all ClickHouse employees (n=35420) were active on GitHub. | 25 25 ClickHouse employees were active on GitHub. | 
| 11. JetBrains | 12% 12% (n=142) of all JetBrains engineers (n=1,15521) were active on GitHub. | 6% 6% (n=142) of all JetBrains employees (n=2,24522) were active on GitHub. | 142 142 JetBrains employees were active on GitHub. | 
| 12. Tenstorrent | 11% 11% (n=63) of all Tenstorrent engineers (n=57123) were active on GitHub. | 6% 6% (n=63) of all Tenstorrent employees (n=99924) were active on GitHub. | 63 63 Tenstorrent employees were active on GitHub. | 
| 13. PingCAP | 10% 10% (n=20) of all PingCAP engineers (n=20725) were active on GitHub. | 4% 4% (n=20) of all PingCAP employees (n=46726) were active on GitHub. | 20 20 PingCAP employees were active on GitHub. | 
| 14. WSO2 | 8% 8% (n=58) of all WSO2 engineers (n=69427) were active on GitHub. | 5% 5% (n=58) of all WSO2 employees (n=1,16928) were active on GitHub. | 58 58 WSO2 employees were active on GitHub. | 
| 15. DataDog | 8% 8% (n=257) of all DataDog engineers (n=3,10029) were active on GitHub. | 4% 4% (n=257) of all DataDog employees (n=6,50030) were active on GitHub. | 257 257 DataDog employees were active on GitHub. | 
| 16. Cloudflare | 8% 8% (n=91) of all Cloudflare engineers (n=1,10531) were active on GitHub. | 2% 2% (n=91) of all Cloudflare employees (n=4,26332) were active on GitHub. | 91 91 Cloudflare employees were active on GitHub. | 
| 17. WikiMedia Foundation | 7% 7% (n=17) of all WikiMedia Foundation engineers (n=23233) were active on GitHub. | 2% 2% (n=17) of all WikiMedia Foundation employees (n=1,06934) were active on GitHub. | 17 17 WikiMedia Foundation employees were active on GitHub. | 
| 18. MongoDB | 7% 7% (n=95) of all MongoDB engineers (n=1,32735) were active on GitHub. | 2% 2% (n=95) of all MongoDB employees (n=5,55836) were active on GitHub. | 95 95 MongoDB employees were active on GitHub. | 
| 19. Mapbox | 5% 5% (n=17) of all Mapbox engineers (n=32537) were active on GitHub. | 2% 2% (n=17) of all Mapbox employees (n=83838) were active on GitHub. | 17 17 Mapbox employees were active on GitHub. | 
| 20. Snyk | 4% 4% (n=19) of all Snyk engineers (n=46939) were active on GitHub. | 1% 1% (n=19) of all Snyk employees (n=1,27440) were active on GitHub. | 19 19 Snyk employees were active on GitHub. | 
| 21. ESRI | 3% 3% (n=79) of all ESRI engineers (n=2,25841) were active on GitHub. | 1% 1% (n=79) of all ESRI employees (n=7,01142) were active on GitHub. | 79 79 ESRI employees were active on GitHub. | 
| 22. Confluent | 3% 3% (n=36) of all Confluent engineers (n=1,36343) were active on GitHub. | 1% 1% (n=36) of all Confluent employees (n=3,06044) were active on GitHub. | 36 36 Confluent employees were active on GitHub. | 
| 23. Shopify | 3% 3% (n=113) of all Shopify engineers (n=4,39245) were active on GitHub. | 1% 1% (n=113) of all Shopify employees (n=8,10046) were active on GitHub. | 113 113 Shopify employees were active on GitHub. | 
| 24. Microsoft | 2% 2% (n=1,963) of all Microsoft engineers (n=80,00047) were active on GitHub. | 1% 1% (n=1,963) of all Microsoft employees (n=228,00048) were active on GitHub. | 1,963 1,963 Microsoft employees were active on GitHub. | 
| 25. New Relic | 2% 2% (n=25) of all New Relic engineers (n=1,08849) were active on GitHub. | 1% 1% (n=25) of all New Relic employees (n=2,92350) were active on GitHub. | 25 25 New Relic employees were active on GitHub. | 
| 26. Odoo | 2% 2% (n=22) of all Odoo engineers (n=96651) were active on GitHub. | 0% 0% (n=22) of all Odoo employees (n=6,65152) were active on GitHub. | 22 22 Odoo employees were active on GitHub. | 
| 27. Progress Software | 2% 2% (n=23) of all Progress Software engineers (n=1,05553) were active on GitHub. | 1% 1% (n=23) of all Progress Software employees (n=2,81554) were active on GitHub. | 23 23 Progress Software employees were active on GitHub. | 
| 28. Snowflake, Inc. | 2% 2% (n=48) of all Snowflake, Inc. engineers (n=2,25755) were active on GitHub. | 1% 1% (n=48) of all Snowflake, Inc. employees (n=7,83456) were active on GitHub. | 48 48 Snowflake, Inc. employees were active on GitHub. | 
| 29. GitLab | 2% 2% (n=17) of all GitLab engineers (n=86557) were active on GitHub. | 1% 1% (n=17) of all GitLab employees (n=2,37558) were active on GitHub. | 17 17 GitLab employees were active on GitHub. | 
| 30. Okta | 2% 2% (n=35) of all Okta engineers (n=1,79959) were active on GitHub. | 1% 1% (n=35) of all Okta employees (n=5,91460) were active on GitHub. | 35 35 Okta employees were active on GitHub. | 
| 31. Hyland | 2% 2% (n=20) of all Hyland engineers (n=1,14361) were active on GitHub. | 0% 0% (n=20) of all Hyland employees (n=4,14162) were active on GitHub. | 20 20 Hyland employees were active on GitHub. | 
| 32. Alibaba | 2% 2% (n=167) of all Alibaba engineers (n=9,80963) were active on GitHub. | 0% 0% (n=167) of all Alibaba employees (n=124,32064) were active on GitHub. | 167 167 Alibaba employees were active on GitHub. | 
| 33. NVIDIA | 2% 2% (n=435) of all NVIDIA engineers (n=27,10065) were active on GitHub. | 1% 1% (n=435) of all NVIDIA employees (n=36,00066) were active on GitHub. | 435 435 NVIDIA employees were active on GitHub. | 
| 34. Adobe | 1% 1% (n=157) of all Adobe engineers (n=11,21367) were active on GitHub. | 1% 1% (n=157) of all Adobe employees (n=30,70968) were active on GitHub. | 157 157 Adobe employees were active on GitHub. | 
| 35. Amazon | 1% 1% (n=694) of all Amazon engineers (n=49,92069) were active on GitHub. | 0% 0% (n=694) of all Amazon employees (n=146,76470) were active on GitHub. | 694 694 Amazon employees were active on GitHub. | 
| 36. Arm Ltd | 1% 1% (n=96) of all Arm Ltd engineers (n=6,94371) were active on GitHub. | 1% 1% (n=96) of all Arm Ltd employees (n=8,33072) were active on GitHub. | 96 96 Arm Ltd employees were active on GitHub. | 
| 37. Unity Technologies | 1% 1% (n=41) of all Unity Technologies engineers (n=3,21773) were active on GitHub. | 1% 1% (n=41) of all Unity Technologies employees (n=4,98774) were active on GitHub. | 41 41 Unity Technologies employees were active on GitHub. | 
| 38. Google | 1% 1% (n=948) of all Google engineers (n=81,83775) were active on GitHub. | 1% 1% (n=948) of all Google employees (n=183,32376) were active on GitHub. | 948 948 Google employees were active on GitHub. | 
| 39. Zendesk | 1% 1% (n=18) of all Zendesk engineers (n=1,55877) were active on GitHub. | 0% 0% (n=18) of all Zendesk employees (n=7,14478) were active on GitHub. | 18 18 Zendesk employees were active on GitHub. | 
| 40. Databricks | 1% 1% (n=58) of all Databricks engineers (n=5,10279) were active on GitHub. | 0% 0% (n=58) of all Databricks employees (n=12,06980) were active on GitHub. | 58 58 Databricks employees were active on GitHub. | 
| 41. OpenAI | 1% 1% (n=23) of all OpenAI engineers (n=2,14581) were active on GitHub. | 0% 0% (n=23) of all OpenAI employees (n=6,88082) were active on GitHub. | 23 23 OpenAI employees were active on GitHub. | 
| 42. Tencent | 1% 1% (n=139) of all Tencent engineers (n=13,12483) were active on GitHub. | 0% 0% (n=139) of all Tencent employees (n=110,55884) were active on GitHub. | 139 139 Tencent employees were active on GitHub. | 
| 43. Square, Inc. | 1% 1% (n=38) of all Square, Inc. engineers (n=3,73385) were active on GitHub. | 0% 0% (n=38) of all Square, Inc. employees (n=11,37286) were active on GitHub. | 38 38 Square, Inc. employees were active on GitHub. | 
| 44. Netflix | 1% 1% (n=30) of all Netflix engineers (n=2,95787) were active on GitHub. | 0% 0% (n=30) of all Netflix employees (n=14,00088) were active on GitHub. | 30 30 Netflix employees were active on GitHub. | 
| 45. AMD | 1% 1% (n=185) of all AMD engineers (n=19,69789) were active on GitHub. | 1% 1% (n=185) of all AMD employees (n=28,00090) were active on GitHub. | 185 185 AMD employees were active on GitHub. | 
| 46. Palantir Technologies | 1% 1% (n=20) of all Palantir Technologies engineers (n=2,14891) were active on GitHub. | 1% 1% (n=20) of all Palantir Technologies employees (n=3,93692) were active on GitHub. | 20 20 Palantir Technologies employees were active on GitHub. | 
| 47. Stripe | 1% 1% (n=35) of all Stripe engineers (n=3,81693) were active on GitHub. | 0% 0% (n=35) of all Stripe employees (n=12,04994) were active on GitHub. | 35 35 Stripe employees were active on GitHub. | 
| 48. Zalando DE | 1% 1% (n=17) of all Zalando DE engineers (n=1,93395) were active on GitHub. | 0% 0% (n=17) of all Zalando DE employees (n=15,30996) were active on GitHub. | 17 17 Zalando DE employees were active on GitHub. | 
| 49. ThoughtWorks | 1% 1% (n=33) of all ThoughtWorks engineers (n=3,81697) were active on GitHub. | 0% 0% (n=33) of all ThoughtWorks employees (n=10,50098) were active on GitHub. | 33 33 ThoughtWorks employees were active on GitHub. | 
| 50. BBC | 1% 1% (n=18) of all BBC engineers (n=2,18899) were active on GitHub. | 0% 0% (n=18) of all BBC employees (n=21,508100) were active on GitHub. | 18 18 BBC employees were active on GitHub. | 
| 51. Twilio | 1% 1% (n=21) of all Twilio engineers (n=2,581101) were active on GitHub. | 0% 0% (n=21) of all Twilio employees (n=5,535102) were active on GitHub. | 21 21 Twilio employees were active on GitHub. | 
| 52. WIX | 1% 1% (n=18) of all WIX engineers (n=2,428103) were active on GitHub. | 0% 0% (n=18) of all WIX employees (n=4,568104) were active on GitHub. | 18 18 WIX employees were active on GitHub. | 
| 53. Broadcom | 1% 1% (n=144) of all Broadcom engineers (n=20,350105) were active on GitHub. | 0% 0% (n=144) of all Broadcom employees (n=37,000106) were active on GitHub. | 144 144 Broadcom employees were active on GitHub. | 
| 54. Autodesk | 1% 1% (n=30) of all Autodesk engineers (n=4,705107) were active on GitHub. | 0% 0% (n=30) of all Autodesk employees (n=15,300108) were active on GitHub. | 30 30 Autodesk employees were active on GitHub. | 
| 55. Intel | 1% 1% (n=339) of all Intel engineers (n=54,924109) were active on GitHub. | 0% 0% (n=339) of all Intel employees (n=108,900110) were active on GitHub. | 339 339 Intel employees were active on GitHub. | 
| 56. Spotify | 1% 1% (n=24) of all Spotify engineers (n=3,944111) were active on GitHub. | 0% 0% (n=24) of all Spotify employees (n=7,691112) were active on GitHub. | 24 24 Spotify employees were active on GitHub. | 
| 57. Meta | 1% 1% (n=236) of all Meta engineers (n=39,058113) were active on GitHub. | 0% 0% (n=236) of all Meta employees (n=74,067114) were active on GitHub. | 236 236 Meta employees were active on GitHub. | 
| 58. SAP SE | 1% 1% (n=191) of all SAP SE engineers (n=37,590115) were active on GitHub. | 0% 0% (n=191) of all SAP SE employees (n=109,973116) were active on GitHub. | 191 191 SAP SE employees were active on GitHub. | 
| 59. Uber | 0% 0% (n=40) of all Uber engineers (n=8,071117) were active on GitHub. | 0% 0% (n=40) of all Uber employees (n=31,100118) were active on GitHub. | 40 40 Uber employees were active on GitHub. | 
| 60. Airbnb | 0% 0% (n=16) of all Airbnb engineers (n=3,387119) were active on GitHub. | 0% 0% (n=16) of all Airbnb employees (n=7,300120) were active on GitHub. | 16 16 Airbnb employees were active on GitHub. | 
| 61. Yandex | 0% 0% (n=50) of all Yandex engineers (n=11,020121) were active on GitHub. | 0% 0% (n=50) of all Yandex employees (n=29,000122) were active on GitHub. | 50 50 Yandex employees were active on GitHub. | 
| 62. Bloomberg | 0% 0% (n=35) of all Bloomberg engineers (n=8,192123) were active on GitHub. | 0% 0% (n=35) of all Bloomberg employees (n=25,356124) were active on GitHub. | 35 35 Bloomberg employees were active on GitHub. | 
| 63. Salesforce | 0% 0% (n=100) of all Salesforce engineers (n=23,597125) were active on GitHub. | 0% 0% (n=100) of all Salesforce employees (n=76,453126) were active on GitHub. | 100 100 Salesforce employees were active on GitHub. | 
| 64. Cisco Systems | 0% 0% (n=102) of all Cisco Systems engineers (n=25,256127) were active on GitHub. | 0% 0% (n=102) of all Cisco Systems employees (n=86,200128) were active on GitHub. | 102 102 Cisco Systems employees were active on GitHub. | 
| 65. Atlassian | 0% 0% (n=27) of all Atlassian engineers (n=6,906129) were active on GitHub. | 0% 0% (n=27) of all Atlassian employees (n=13,813130) were active on GitHub. | 27 27 Atlassian employees were active on GitHub. | 
| 66. Intuit | 0% 0% (n=21) of all Intuit engineers (n=5,868131) were active on GitHub. | 0% 0% (n=21) of all Intuit employees (n=18,800132) were active on GitHub. | 21 21 Intuit employees were active on GitHub. | 
| 67. Apple | 0% 0% (n=149) of all Apple engineers (n=44,947133) were active on GitHub. | 0% 0% (n=149) of all Apple employees (n=164,000134) were active on GitHub. | 149 149 Apple employees were active on GitHub. | 
| 68. Baidu | 0% 0% (n=51) of all Baidu engineers (n=19,500135) were active on GitHub. | 0% 0% (n=51) of all Baidu employees (n=35,900136) were active on GitHub. | 51 51 Baidu employees were active on GitHub. | 
| 69. Oracle | 0% 0% (n=120) of all Oracle engineers (n=50,000137) were active on GitHub. | 0% 0% (n=120) of all Oracle employees (n=162,000138) were active on GitHub. | 120 120 Oracle employees were active on GitHub. | 
| 70. NetEase | 0% 0% (n=24) of all NetEase engineers (n=12,754139) were active on GitHub. | 0% 0% (n=24) of all NetEase employees (n=26,028140) were active on GitHub. | 24 24 NetEase employees were active on GitHub. | 
| 71. EPAM Systems | 0% 0% (n=63) of all EPAM Systems engineers (n=55,100141) were active on GitHub. | 0% 0% (n=63) of all EPAM Systems employees (n=61,200142) were active on GitHub. | 63 63 EPAM Systems employees were active on GitHub. | 
| 72. Ericsson | 0% 0% (n=24) of all Ericsson engineers (n=26,744143) were active on GitHub. | 0% 0% (n=24) of all Ericsson employees (n=94,326144) were active on GitHub. | 24 24 Ericsson employees were active on GitHub. | 
| 73. Nokia | 0% 0% (n=24) of all Nokia engineers (n=29,189145) were active on GitHub. | 0% 0% (n=24) of all Nokia employees (n=78,434146) were active on GitHub. | 24 24 Nokia employees were active on GitHub. | 
| 74. Capgemini | 0% 0% (n=30) of all Capgemini engineers (n=77,872147) were active on GitHub. | 0% 0% (n=30) of all Capgemini employees (n=341,100148) were active on GitHub. | 30 30 Capgemini employees were active on GitHub. | 
| 75. Huawei | 0% 0% (n=42) of all Huawei engineers (n=113,000149) were active on GitHub. | 0% 0% (n=42) of all Huawei employees (n=208,000150) were active on GitHub. | 42 42 Huawei employees were active on GitHub. | 
| 76. Samsung | 0% 0% (n=29) of all Samsung engineers (n=88,984151) were active on GitHub. | 0% 0% (n=29) of all Samsung employees (n=262,647152) were active on GitHub. | 29 29 Samsung employees were active on GitHub. | 
| 77. IBM | (n=1,434) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=1,434) of all IBM employees (n=270,300153) were active on GitHub. | 1,434 1,434 IBM employees were active on GitHub. | 
| 78. ByteDance | (n=173) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=173) of all ByteDance employees (n=NaN0) were active on GitHub. | 173 173 ByteDance employees were active on GitHub. | 
| 79. Canonical | (n=135) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=135) of all Canonical employees (n=NaN0) were active on GitHub. | 135 135 Canonical employees were active on GitHub. | 
| 80. Software Mansion | (n=93) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=93) of all Software Mansion employees (n=NaN0) were active on GitHub. | 93 93 Software Mansion employees were active on GitHub. | 
| 81. Accenture | (n=49) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=49) of all Accenture employees (n=774,000154) were active on GitHub. | 49 49 Accenture employees were active on GitHub. | 
| 82. Posit | (n=46) of all Posit engineers (n=NaN0) were active on GitHub. | (n=46) of all Posit employees (n=NaN0) were active on GitHub. | 46 46 Posit employees were active on GitHub. | 
| 83. @pass-culture | (n=31) of all @pass-culture engineers (n=NaN0) were active on GitHub. | (n=31) of all @pass-culture employees (n=NaN0) were active on GitHub. | 31 31 @pass-culture employees were active on GitHub. | 
| 84. Orange S.A. | (n=23) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=23) of all Orange S.A. employees (n=119,270155) were active on GitHub. | 23 23 Orange S.A. employees were active on GitHub. | 
| 85. @apache | (n=23) of all @apache engineers (n=NaN0) were active on GitHub. | (n=23) of all @apache employees (n=NaN0) were active on GitHub. | 23 23 @apache employees were active on GitHub. | 
| 86. UCL | (n=20) of all UCL engineers (n=NaN0) were active on GitHub. | (n=20) of all UCL employees (n=NaN0) were active on GitHub. | 20 20 UCL employees were active on GitHub. | 
| 87. Ant Group | (n=20) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=20) of all Ant Group employees (n=NaN0) were active on GitHub. | 20 20 Ant Group employees were active on GitHub. | 
| 88. @SSWConsulting | (n=20) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=20) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 20 20 @SSWConsulting employees were active on GitHub. | 
| 89. Palo Alto Networks | (n=19) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=19) of all Palo Alto Networks employees (n=16,068156) were active on GitHub. | 19 19 Palo Alto Networks employees were active on GitHub. | 
| 90. TU Delft | (n=19) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=19) of all TU Delft employees (n=NaN0) were active on GitHub. | 19 19 TU Delft employees were active on GitHub. | 
| 91. @ClickHouse | (n=19) of all @ClickHouse engineers (n=NaN0) were active on GitHub. | (n=19) of all @ClickHouse employees (n=NaN0) were active on GitHub. | 19 19 @ClickHouse employees were active on GitHub. | 
| 92. Sanity | (n=19) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=19) of all Sanity employees (n=NaN0) were active on GitHub. | 19 19 Sanity employees were active on GitHub. | 
| 93. Sentry | (n=17) of all Sentry engineers (n=NaN0) were active on GitHub. | (n=17) of all Sentry employees (n=NaN0) were active on GitHub. | 17 17 Sentry employees were active on GitHub. | 
| 94. PostHog | (n=17) of all PostHog engineers (n=NaN0) were active on GitHub. | (n=17) of all PostHog employees (n=NaN0) were active on GitHub. | 17 17 PostHog employees were active on GitHub. | 
| 95. Tata Consultancy Services | (n=17) of all Tata Consultancy Services engineers (n=NaN0) were active on GitHub. | (n=17) of all Tata Consultancy Services employees (n=NaN0) were active on GitHub. | 17 17 Tata Consultancy Services employees were active on GitHub. | 
| 96. @espressif | (n=17) of all @espressif engineers (n=NaN0) were active on GitHub. | (n=17) of all @espressif employees (n=NaN0) were active on GitHub. | 17 17 @espressif employees were active on GitHub. | 
| 97. SLIIT | (n=17) of all SLIIT engineers (n=NaN0) were active on GitHub. | (n=17) of all SLIIT employees (n=NaN0) were active on GitHub. | 17 17 SLIIT employees were active on GitHub. | 
| 98. Cloudera | (n=17) of all Cloudera engineers (n=NaN0) were active on GitHub. | (n=17) of all Cloudera employees (n=NaN0) were active on GitHub. | 17 17 Cloudera employees were active on GitHub. | 
| 99. @shopware | (n=17) of all @shopware engineers (n=NaN0) were active on GitHub. | (n=17) of all @shopware employees (n=NaN0) were active on GitHub. | 17 17 @shopware employees were active on GitHub. | 
| 100. 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. | 
References
- Sentry.io engineer count: linkedin.com (Retrieved August 2025)
- Sentry.io employee count: linkedin.com (Retrieved August 2025)
- Vercel engineer count: linkedin.com (Retrieved July 2025)
- Vercel employee count: linkedin.com (Retrieved July 2025)
- Grafana Labs engineer count: linkedin.com (Retrieved July 2025)
- Grafana Labs employee count: linkedin.com (Retrieved July 2025)
- SUSE engineer count: linkedin.com (Retrieved July 2025)
- SUSE employee count: linkedin.com (Retrieved July 2025)
- Kitware engineer count: linkedin.com (Retrieved July 2025)
- Kitware employee count: linkedin.com (Retrieved July 2025)
- Automattic engineer count: linkedin.com (Retrieved October 2025)
- Automattic employee count: automattic.com (Retrieved October 2025)
- Elastic engineer count: linkedin.com (retrieved July 2025)
- Elastic employee count: sec.gov (page 15)
- Mozilla engineer count: linkedin.com (Retrieved October 2025)
- Mozilla employee count: linkedin.com (Retrieved October 2025)
- Docker engineer count: linkedin.com (Retrieved July 2025)
- Docker employee count: linkedin.com (Retrieved July 2025)
- ClickHouse engineer count: linkedin.com (Retrieved September 2025)
- ClickHouse employee count: linkedin.com (Retrieved September 2025)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Tenstorrent engineer count: linkedin.com
- Tenstorrent employee count: linkedin.com
- PingCAP engineer count: linkedin.com (Retrieved August 2025)
- PingCAP employee count: linkedin.com (Retrieved August 2025)
- WSO2 engineer count: linkedin.com (Retrieved October 2025)
- WSO2 employee count: linkedin.com (Retrieved October 2025)
- DataDog engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 12)
- Cloudflare engineer count: linkedin.com (Retrieved July 2025)
- Cloudflare employee count: sec.gov (page 18)
- WikiMedia Foundation engineer count: linkedin.com (Retrieved July 2025)
- WikiMedia Foundation employee count: linkedin.com (Retrieved July 2025)
- MongoDB engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- MongoDB employee count: sec.gov (page 8)
- Mapbox engineer count: linkedin.com (Retrieved July 2025)
- Mapbox employee count: linkedin.com (Retrieved July 2025)
- Snyk engineer count: linkedin.com (Retrieved August 2025)
- Snyk employee count: linkedin.com (Retrieved August 2025)
- ESRI engineer count: linkedin.com (Retrieved July 2025)
- ESRI employee count: linkedin.com (Retrieved July 2025)
- Confluent engineer count: linkedin.com (Retrieved July 2025)
- Confluent employee count: sec.gov (page 18)
- Shopify engineer count: linkedin.com (Retrieved July 2025)
- Shopify employee count: sec.gov (page 10)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- New Relic engineer count: linkedin.com (Retrieved July 2025)
- New Relic employee count: linkedin.com (Retrieved July 2025)
- Odoo engineer count: linkedin.com (Retrieved July 2025)
- Odoo employee count: linkedin.com (Retrieved July 2025)
- Progress Software engineer count: sec.gov (page 8, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 8)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- GitLab engineer count: linkedin.com (Retrieved July 2025)
- GitLab employee count: sec.gov (page 12)
- Okta engineer count: linkedin.com (Retrieved July 2025)
- Okta employee count: sec.gov (page 13)
- Hyland engineer count: linkedin.com (Retrieved July 2025)
- Hyland employee count: linkedin.com (Retrieved July 2025)
- Alibaba engineer count: linkedin.com (Retrieved September 2025)
- Alibaba employee count: data.alibabagroup.com (page 180)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Adobe engineer count: linkedin.com (Retrieved July 2025)
- Adobe employee count: sec.gov (page 19)
- Amazon engineer count: linkedin.com (Retrieved July 2025)
- Amazon employee count: linkedin.com (Retrieved July 2025)
- Arm Ltd engineer count: sec.gov (page 110)
- Arm Ltd employee count: sec.gov (page 110)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Google engineer count: linkedin.com (Retrieved July 2025)
- Google employee count: sec.gov (page 9)
- Zendesk engineer count: linkedin.com (Retrieved July 2025)
- Zendesk employee count: linkedin.com (Retrieved July 2025)
- Databricks engineer count: linkedin.com (Retrieved August 2025)
- Databricks employee count: linkedin.com (Retrieved August 2025)
- OpenAI engineer count: linkedin.com (Retrieved August 2025)
- OpenAI employee count: linkedin.com (Retrieved August 2025)
- Tencent engineer count: linkedin.com (Retrieved July 2025)
- Tencent employee count: static.tencent.com (page 52)
- Square, Inc. engineer count: linkedin.com (Retrieved July 2025)
- Square, Inc. employee count: sec.gov (page 20)
- Netflix engineer count: linkedin.com (Retrieved July 2025)
- Netflix employee count: sec.gov (page 2)
- AMD engineer count: linkedin.com (Retrieved July 2025)
- AMD employee count: sec.gov (page 10)
- Palantir Technologies engineer count: linkedin.com (Retrieved July 2025)
- Palantir Technologies employee count: sec.gov (page 11)
- Stripe engineer count: linkedin.com (Retrieved July 2025)
- Stripe employee count: linkedin.com (Retrieved July 2025)
- Zalando DE engineer count: linkedin.com (Retrieved July 2025)
- Zalando DE employee count: corporate.zalando.com (page 2)
- ThoughtWorks engineer count: linkedin.com (Retrieved July 2025)
- ThoughtWorks employee count: sec.gov (page 6)
- BBC engineer count: linkedin.com (Retrieved August 2025)
- BBC employee count: bbc.co.uk (page 59)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- WIX engineer count: sec.gov (page 91, referred to as employees in 'research and development')
- WIX employee count: sec.gov (page 152)
- Broadcom engineer count: sec.gov (page 13, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 13)
- Autodesk engineer count: linkedin.com (Retrieved July 2025)
- Autodesk employee count: sec.gov (page 13)
- Intel engineer count: linkedin.com (Retrieved July 2025)
- Intel employee count: sec.gov (page 10)
- Spotify engineer count: sec.gov (page 65, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 65)
- Meta engineer count: linkedin.com (Retrieved October 2025)
- Meta employee count: sec.gov (page 12)
- SAP SE engineer count: sec.gov (page F-24, referred to as employees in 'research and development')
- SAP SE employee count: sec.gov (page 98)
- Uber engineer count: linkedin.com (Retrieved July 2025)
- Uber employee count: sec.gov (page 7)
- Airbnb engineer count: linkedin.com (Retrieved September 2025)
- Airbnb employee count: sec.gov (page 5)
- Yandex engineer count: yastatic.net (page 54, referred to as 'developers)
- Yandex employee count: yastatic.net (page 12)
- Bloomberg engineer count: linkedin.com (Retrieved July 2025)
- Bloomberg employee count: linkedin.com (Retrieved July 2025)
- Salesforce engineer count: linkedin.com (Retrieved July 2025)
- Salesforce employee count: sec.gov (page 10)
- Cisco Systems engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 8)
- Atlassian engineer count: sec.gov (page 8, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 11)
- Intuit engineer count: linkedin.com (Retrieved August 2025)
- Intuit employee count: sec.gov (page 11)
- Apple engineer count: linkedin.com (Retrieved October 2025)
- Apple employee count: sec.gov (page 4)
- Baidu engineer count: sec.gov (page 201, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 201)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle 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 '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 July 2025)
- Nokia employee count: sec.gov (page 70)
- Capgemini engineer count: linkedin.com (Retrieved July 2025)
- Capgemini employee count: investors.capgemini.com (page 4)
- Huawei engineer count: huawei.com (page 72, referred to as employees in 'R&D')
- Huawei employee count: huawei.com (page 1)
- Samsung engineer count: images.samsung.com (page 64, referred to as employees in 'development')
- Samsung employee count: images.samsung.com (page 64)
- IBM employee count: sec.gov (page 14)
- Accenture employee count: sec.gov (page 3)
- Orange S.A. employee count: gallery.orange.com (page 63)
- Palo Alto Networks employee count: sec.gov (page 11)