Corporate GitHub Activity
Most Active Corporations on GitHub, Q4 2024
Ranking companies with employees who, during Q4 2024, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Vercel | 54% 54% (n=88) of all Vercel engineers (n=1641) were active on GitHub. | 16% 16% (n=88) of all Vercel employees (n=5662) were active on GitHub. | 88 88 Vercel employees were active on GitHub. | 
|---|---|---|---|
| 2. SUSE | 50% 50% (n=332) of all SUSE engineers (n=6643) were active on GitHub. | 14% 14% (n=332) of all SUSE employees (n=2,3984) were active on GitHub. | 332 332 SUSE employees were active on GitHub. | 
| 3. Grafana Labs | 46% 46% (n=265) of all Grafana Labs engineers (n=5765) were active on GitHub. | 19% 19% (n=265) of all Grafana Labs employees (n=1,3836) were active on GitHub. | 265 265 Grafana Labs employees were active on GitHub. | 
| 4. Automattic | 40% 40% (n=333) of all Automattic engineers (n=8427) were active on GitHub. | 19% 19% (n=333) of all Automattic employees (n=1,7318) were active on GitHub. | 333 333 Automattic employees were active on GitHub. | 
| 5. Mozilla | 32% 32% (n=201) of all Mozilla engineers (n=6299) were active on GitHub. | 11% 11% (n=201) of all Mozilla employees (n=1,79010) were active on GitHub. | 201 201 Mozilla employees were active on GitHub. | 
| 6. Elastic | 32% 32% (n=361) of all Elastic engineers (n=1,14011) were active on GitHub. | 10% 10% (n=361) of all Elastic employees (n=3,53712) were active on GitHub. | 361 361 Elastic employees were active on GitHub. | 
| 7. The Guardian | 29% 29% (n=37) of all The Guardian engineers (n=12813) were active on GitHub. | 1% 1% (n=37) of all The Guardian employees (n=2,48314) were active on GitHub. | 37 37 The Guardian employees were active on GitHub. | 
| 8. HashiCorp | 28% 28% (n=188) of all HashiCorp engineers (n=68015) were active on GitHub. | 9% 9% (n=188) of all HashiCorp employees (n=2,20016) were active on GitHub. | 188 188 HashiCorp employees were active on GitHub. | 
| 9. WikiMedia Foundation | 25% 25% (n=53) of all WikiMedia Foundation engineers (n=20917) were active on GitHub. | 5% 5% (n=53) of all WikiMedia Foundation employees (n=1,02918) were active on GitHub. | 53 53 WikiMedia Foundation employees were active on GitHub. | 
| 10. Docker | 21% 21% (n=46) of all Docker engineers (n=22019) were active on GitHub. | 5% 5% (n=46) of all Docker employees (n=97020) were active on GitHub. | 46 46 Docker employees were active on GitHub. | 
| 11. JetBrains | 21% 21% (n=216) of all JetBrains engineers (n=1,04321) were active on GitHub. | 10% 10% (n=216) of all JetBrains employees (n=2,24522) were active on GitHub. | 216 216 JetBrains employees were active on GitHub. | 
| 12. Odoo | 20% 20% (n=155) of all Odoo engineers (n=76923) were active on GitHub. | 3% 3% (n=155) of all Odoo employees (n=4,95024) were active on GitHub. | 155 155 Odoo employees were active on GitHub. | 
| 13. WSO2 | 17% 17% (n=113) of all WSO2 engineers (n=66425) were active on GitHub. | 10% 10% (n=113) of all WSO2 employees (n=1,13026) were active on GitHub. | 113 113 WSO2 employees were active on GitHub. | 
| 14. Cloudflare | 17% 17% (n=141) of all Cloudflare engineers (n=83027) were active on GitHub. | 3% 3% (n=141) of all Cloudflare employees (n=4,26328) were active on GitHub. | 141 141 Cloudflare employees were active on GitHub. | 
| 15. DataDog | 12% 12% (n=360) of all DataDog engineers (n=3,10029) were active on GitHub. | 6% 6% (n=360) of all DataDog employees (n=6,50030) were active on GitHub. | 360 360 DataDog employees were active on GitHub. | 
| 16. MongoDB | 11% 11% (n=149) of all MongoDB engineers (n=1,32731) were active on GitHub. | 3% 3% (n=149) of all MongoDB employees (n=5,55832) were active on GitHub. | 149 149 MongoDB employees were active on GitHub. | 
| 17. New Relic | 9% 9% (n=75) of all New Relic engineers (n=87833) were active on GitHub. | 3% 3% (n=75) of all New Relic employees (n=2,50234) were active on GitHub. | 75 75 New Relic employees were active on GitHub. | 
| 18. ESRI | 7% 7% (n=157) of all ESRI engineers (n=2,14835) were active on GitHub. | 2% 2% (n=157) of all ESRI employees (n=6,70836) were active on GitHub. | 157 157 ESRI employees were active on GitHub. | 
| 19. Confluent | 7% 7% (n=82) of all Confluent engineers (n=1,17137) were active on GitHub. | 3% 3% (n=82) of all Confluent employees (n=3,06038) were active on GitHub. | 82 82 Confluent employees were active on GitHub. | 
| 20. Shopify | 6% 6% (n=223) of all Shopify engineers (n=3,89239) were active on GitHub. | 3% 3% (n=223) of all Shopify employees (n=8,10040) were active on GitHub. | 223 223 Shopify employees were active on GitHub. | 
| 21. Progress Software | 5% 5% (n=54) of all Progress Software engineers (n=1,05541) were active on GitHub. | 2% 2% (n=54) of all Progress Software employees (n=2,81542) were active on GitHub. | 54 54 Progress Software employees were active on GitHub. | 
| 22. Microsoft | 5% 5% (n=3,967) of all Microsoft engineers (n=81,00043) were active on GitHub. | 2% 2% (n=3,967) of all Microsoft employees (n=228,00044) were active on GitHub. | 3,967 3,967 Microsoft employees were active on GitHub. | 
| 23. Okta | 4% 4% (n=71) of all Okta engineers (n=1,67745) were active on GitHub. | 1% 1% (n=71) of all Okta employees (n=5,91446) were active on GitHub. | 71 71 Okta employees were active on GitHub. | 
| 24. Snowflake, Inc. | 4% 4% (n=80) of all Snowflake, Inc. engineers (n=2,25747) were active on GitHub. | 1% 1% (n=80) of all Snowflake, Inc. employees (n=7,83448) were active on GitHub. | 80 80 Snowflake, Inc. employees were active on GitHub. | 
| 25. Alibaba | 3% 3% (n=351) of all Alibaba engineers (n=10,18749) were active on GitHub. | 0% 0% (n=351) of all Alibaba employees (n=197,99150) were active on GitHub. | 351 351 Alibaba employees were active on GitHub. | 
| 26. Amazon | 3% 3% (n=1,566) of all Amazon engineers (n=45,46251) were active on GitHub. | 1% 1% (n=1,566) of all Amazon employees (n=131,95552) were active on GitHub. | 1,566 1,566 Amazon employees were active on GitHub. | 
| 27. Adobe | 3% 3% (n=361) of all Adobe engineers (n=11,13553) were active on GitHub. | 1% 1% (n=361) of all Adobe employees (n=30,70954) were active on GitHub. | 361 361 Adobe employees were active on GitHub. | 
| 28. ThoughtWorks | 3% 3% (n=110) of all ThoughtWorks engineers (n=3,67455) were active on GitHub. | 1% 1% (n=110) of all ThoughtWorks employees (n=10,50056) were active on GitHub. | 110 110 ThoughtWorks employees were active on GitHub. | 
| 29. Netflix | 3% 3% (n=83) of all Netflix engineers (n=2,86657) were active on GitHub. | 1% 1% (n=83) of all Netflix employees (n=14,00058) were active on GitHub. | 83 83 Netflix employees were active on GitHub. | 
| 30. Unity Technologies | 3% 3% (n=92) of all Unity Technologies engineers (n=3,21759) were active on GitHub. | 2% 2% (n=92) of all Unity Technologies employees (n=4,98760) were active on GitHub. | 92 92 Unity Technologies employees were active on GitHub. | 
| 31. Arm Ltd | 3% 3% (n=148) of all Arm Ltd engineers (n=5,88761) were active on GitHub. | 2% 2% (n=148) of all Arm Ltd employees (n=7,09662) were active on GitHub. | 148 148 Arm Ltd employees were active on GitHub. | 
| 32. Tencent | 2% 2% (n=301) of all Tencent engineers (n=12,71763) were active on GitHub. | 0% 0% (n=301) of all Tencent employees (n=110,55864) were active on GitHub. | 301 301 Tencent employees were active on GitHub. | 
| 33. Twilio | 2% 2% (n=61) of all Twilio engineers (n=2,58165) were active on GitHub. | 1% 1% (n=61) of all Twilio employees (n=5,53566) were active on GitHub. | 61 61 Twilio employees were active on GitHub. | 
| 34. Google | 2% 2% (n=1,825) of all Google engineers (n=79,91067) were active on GitHub. | 1% 1% (n=1,825) of all Google employees (n=183,32368) were active on GitHub. | 1,825 1,825 Google employees were active on GitHub. | 
| 35. CyberAgent | 2% 2% (n=39) of all CyberAgent engineers (n=1,78369) were active on GitHub. | 1% 1% (n=39) of all CyberAgent employees (n=7,72070) were active on GitHub. | 39 39 CyberAgent employees were active on GitHub. | 
| 36. Stripe | 2% 2% (n=67) of all Stripe engineers (n=3,07671) were active on GitHub. | 1% 1% (n=67) of all Stripe employees (n=8,87672) were active on GitHub. | 67 67 Stripe employees were active on GitHub. | 
| 37. NVIDIA | 2% 2% (n=559) of all NVIDIA engineers (n=27,10073) were active on GitHub. | 2% 2% (n=559) of all NVIDIA employees (n=36,00074) were active on GitHub. | 559 559 NVIDIA employees were active on GitHub. | 
| 38. Square, Inc. | 2% 2% (n=73) of all Square, Inc. engineers (n=3,91375) were active on GitHub. | 1% 1% (n=73) of all Square, Inc. employees (n=11,37276) were active on GitHub. | 73 73 Square, Inc. employees were active on GitHub. | 
| 39. Spotify | 2% 2% (n=66) of all Spotify engineers (n=3,94477) were active on GitHub. | 1% 1% (n=66) of all Spotify employees (n=7,69178) were active on GitHub. | 66 66 Spotify employees were active on GitHub. | 
| 40. WIX | 2% 2% (n=38) of all WIX engineers (n=2,42879) were active on GitHub. | 1% 1% (n=38) of all WIX employees (n=4,56880) were active on GitHub. | 38 38 WIX employees were active on GitHub. | 
| 41. Broadcom | 2% 2% (n=316) of all Broadcom engineers (n=20,35081) were active on GitHub. | 1% 1% (n=316) of all Broadcom employees (n=37,00082) were active on GitHub. | 316 316 Broadcom employees were active on GitHub. | 
| 42. AMD | 2% 2% (n=279) of all AMD engineers (n=18,12183) were active on GitHub. | 1% 1% (n=279) of all AMD employees (n=28,00084) were active on GitHub. | 279 279 AMD employees were active on GitHub. | 
| 43. Autodesk | 1% 1% (n=70) of all Autodesk engineers (n=4,70685) were active on GitHub. | 0% 0% (n=70) of all Autodesk employees (n=15,30086) were active on GitHub. | 70 70 Autodesk employees were active on GitHub. | 
| 44. Yandex | 1% 1% (n=162) of all Yandex engineers (n=11,02087) were active on GitHub. | 1% 1% (n=162) of all Yandex employees (n=29,00088) were active on GitHub. | 162 162 Yandex employees were active on GitHub. | 
| 45. Meta | 1% 1% (n=432) of all Meta engineers (n=35,87389) were active on GitHub. | 1% 1% (n=432) of all Meta employees (n=74,06790) were active on GitHub. | 432 432 Meta employees were active on GitHub. | 
| 46. SAP SE | 1% 1% (n=442) of all SAP SE engineers (n=37,59091) were active on GitHub. | 0% 0% (n=442) of all SAP SE employees (n=109,97392) were active on GitHub. | 442 442 SAP SE employees were active on GitHub. | 
| 47. Uber | 1% 1% (n=81) of all Uber engineers (n=6,93593) were active on GitHub. | 0% 0% (n=81) of all Uber employees (n=31,10094) were active on GitHub. | 81 81 Uber employees were active on GitHub. | 
| 48. Booking.com | 1% 1% (n=36) of all Booking.com engineers (n=3,09795) were active on GitHub. | 0% 0% (n=36) of all Booking.com employees (n=24,30096) were active on GitHub. | 36 36 Booking.com employees were active on GitHub. | 
| 49. Atlassian | 1% 1% (n=67) of all Atlassian engineers (n=6,07897) were active on GitHub. | 1% 1% (n=67) of all Atlassian employees (n=12,15798) were active on GitHub. | 67 67 Atlassian employees were active on GitHub. | 
| 50. Intel | 1% 1% (n=630) of all Intel engineers (n=59,05799) were active on GitHub. | 1% 1% (n=630) of all Intel employees (n=108,900100) were active on GitHub. | 630 630 Intel employees were active on GitHub. | 
| 51. Salesforce | 1% 1% (n=222) of all Salesforce engineers (n=22,809101) were active on GitHub. | 0% 0% (n=222) of all Salesforce employees (n=76,453102) were active on GitHub. | 222 222 Salesforce employees were active on GitHub. | 
| 52. Cisco Systems | 1% 1% (n=241) of all Cisco Systems engineers (n=24,770103) were active on GitHub. | 0% 0% (n=241) of all Cisco Systems employees (n=90,400104) were active on GitHub. | 241 241 Cisco Systems employees were active on GitHub. | 
| 53. Bloomberg | 1% 1% (n=68) of all Bloomberg engineers (n=7,862105) were active on GitHub. | 0% 0% (n=68) of all Bloomberg employees (n=24,577106) were active on GitHub. | 68 68 Bloomberg employees were active on GitHub. | 
| 54. Oracle | 1% 1% (n=288) of all Oracle engineers (n=47,000107) were active on GitHub. | 0% 0% (n=288) of all Oracle employees (n=159,000108) were active on GitHub. | 288 288 Oracle employees were active on GitHub. | 
| 55. Apple | 1% 1% (n=249) of all Apple engineers (n=41,538109) were active on GitHub. | 0% 0% (n=249) of all Apple employees (n=164,000110) were active on GitHub. | 249 249 Apple employees were active on GitHub. | 
| 56. Baidu | 1% 1% (n=113) of all Baidu engineers (n=19,500111) were active on GitHub. | 0% 0% (n=113) of all Baidu employees (n=35,900112) were active on GitHub. | 113 113 Baidu employees were active on GitHub. | 
| 57. PayPal | 0% 0% (n=40) of all PayPal engineers (n=8,683113) were active on GitHub. | 0% 0% (n=40) of all PayPal employees (n=24,400114) were active on GitHub. | 40 40 PayPal employees were active on GitHub. | 
| 58. NetEase | 0% 0% (n=44) of all NetEase engineers (n=12,754115) were active on GitHub. | 0% 0% (n=44) of all NetEase employees (n=26,028116) were active on GitHub. | 44 44 NetEase employees were active on GitHub. | 
| 59. Capital One | 0% 0% (n=45) of all Capital One engineers (n=14,170117) were active on GitHub. | 0% 0% (n=45) of all Capital One employees (n=52,600118) were active on GitHub. | 45 45 Capital One employees were active on GitHub. | 
| 60. EPAM Systems | 0% 0% (n=171) of all EPAM Systems engineers (n=55,100119) were active on GitHub. | 0% 0% (n=171) of all EPAM Systems employees (n=61,200120) were active on GitHub. | 171 171 EPAM Systems employees were active on GitHub. | 
| 61. Ericsson | 0% 0% (n=67) of all Ericsson engineers (n=26,744121) were active on GitHub. | 0% 0% (n=67) of all Ericsson employees (n=94,326122) were active on GitHub. | 67 67 Ericsson employees were active on GitHub. | 
| 62. Nokia | 0% 0% (n=65) of all Nokia engineers (n=29,054123) were active on GitHub. | 0% 0% (n=65) of all Nokia employees (n=78,434124) were active on GitHub. | 65 65 Nokia employees were active on GitHub. | 
| 63. Samsung | 0% 0% (n=146) of all Samsung engineers (n=83,729125) were active on GitHub. | 0% 0% (n=146) of all Samsung employees (n=267,860126) were active on GitHub. | 146 146 Samsung employees were active on GitHub. | 
| 64. Capgemini | 0% 0% (n=108) of all Capgemini engineers (n=72,706127) were active on GitHub. | 0% 0% (n=108) of all Capgemini employees (n=341,100128) were active on GitHub. | 108 108 Capgemini employees were active on GitHub. | 
| 65. Huawei | 0% 0% (n=119) of all Huawei engineers (n=113,000129) were active on GitHub. | 0% 0% (n=119) of all Huawei employees (n=208,000130) were active on GitHub. | 119 119 Huawei employees were active on GitHub. | 
| 66. IBM | (n=2,662) of all IBM engineers (n=NaN0) were active on GitHub. | 1% 1% (n=2,662) of all IBM employees (n=270,300131) were active on GitHub. | 2,662 2,662 IBM employees were active on GitHub. | 
| 67. ByteDance | (n=264) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=264) of all ByteDance employees (n=NaN0) were active on GitHub. | 264 264 ByteDance employees were active on GitHub. | 
| 68. Canonical | (n=220) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=220) of all Canonical employees (n=NaN0) were active on GitHub. | 220 220 Canonical employees were active on GitHub. | 
| 69. Accenture | (n=168) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=168) of all Accenture employees (n=774,000132) were active on GitHub. | 168 168 Accenture employees were active on GitHub. | 
| 70. Databricks | (n=107) of all Databricks engineers (n=NaN0) were active on GitHub. | 1% 1% (n=107) of all Databricks employees (n=9,311133) were active on GitHub. | 107 107 Databricks employees were active on GitHub. | 
| 71. Software Mansion | (n=96) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=96) of all Software Mansion employees (n=NaN0) were active on GitHub. | 96 96 Software Mansion employees were active on GitHub. | 
| 72. Sentry.io | (n=82) of all Sentry.io engineers (n=NaN0) were active on GitHub. | 21% 21% (n=82) of all Sentry.io employees (n=382134) were active on GitHub. | 82 82 Sentry.io employees were active on GitHub. | 
| 73. TU Delft | (n=65) of all TU Delft engineers (n=NaN0) were active on GitHub. | (n=65) of all TU Delft employees (n=NaN0) were active on GitHub. | 65 65 TU Delft employees were active on GitHub. | 
| 74. Posit | (n=63) of all Posit engineers (n=NaN0) were active on GitHub. | (n=63) of all Posit employees (n=NaN0) were active on GitHub. | 63 63 Posit employees were active on GitHub. | 
| 75. Snyk | (n=56) of all Snyk engineers (n=NaN0) were active on GitHub. | 4% 4% (n=56) of all Snyk employees (n=1,274135) were active on GitHub. | 56 56 Snyk employees were active on GitHub. | 
| 76. ITMO | (n=56) of all ITMO engineers (n=NaN0) were active on GitHub. | (n=56) of all ITMO employees (n=NaN0) were active on GitHub. | 56 56 ITMO employees were active on GitHub. | 
| 77. SUSTech | (n=53) of all SUSTech engineers (n=NaN0) were active on GitHub. | (n=53) of all SUSTech employees (n=NaN0) were active on GitHub. | 53 53 SUSTech employees were active on GitHub. | 
| 78. @SSWConsulting | (n=50) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=50) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 50 50 @SSWConsulting employees were active on GitHub. | 
| 79. Tenstorrent | (n=47) of all Tenstorrent engineers (n=NaN0) were active on GitHub. | 9% 9% (n=47) of all Tenstorrent employees (n=552136) were active on GitHub. | 47 47 Tenstorrent employees were active on GitHub. | 
| 80. Orange S.A. | (n=47) of all Orange S.A. engineers (n=NaN0) were active on GitHub. | 0% 0% (n=47) of all Orange S.A. employees (n=119,270137) were active on GitHub. | 47 47 Orange S.A. employees were active on GitHub. | 
| 81. @MathWorks | (n=43) of all @MathWorks engineers (n=NaN0) were active on GitHub. | (n=43) of all @MathWorks employees (n=NaN0) were active on GitHub. | 43 43 @MathWorks employees were active on GitHub. | 
| 82. FEUP | (n=42) of all FEUP engineers (n=NaN0) were active on GitHub. | (n=42) of all FEUP employees (n=NaN0) were active on GitHub. | 42 42 FEUP employees were active on GitHub. | 
| 83. UCL | (n=41) of all UCL engineers (n=NaN0) were active on GitHub. | (n=41) of all UCL employees (n=NaN0) were active on GitHub. | 41 41 UCL employees were active on GitHub. | 
| 84. OpenAI | (n=40) of all OpenAI engineers (n=NaN0) were active on GitHub. | 1% 1% (n=40) of all OpenAI employees (n=3,180138) were active on GitHub. | 40 40 OpenAI employees were active on GitHub. | 
| 85. Intuit | (n=40) of all Intuit engineers (n=NaN0) were active on GitHub. | 0% 0% (n=40) of all Intuit employees (n=18,800139) were active on GitHub. | 40 40 Intuit employees were active on GitHub. | 
| 86. Remote | (n=39) of all Remote engineers (n=NaN0) were active on GitHub. | (n=39) of all Remote employees (n=NaN0) were active on GitHub. | 39 39 Remote employees were active on GitHub. | 
| 87. TUM | (n=39) of all TUM engineers (n=NaN0) were active on GitHub. | (n=39) of all TUM employees (n=NaN0) were active on GitHub. | 39 39 TUM employees were active on GitHub. | 
| 88. PingCAP | (n=39) of all PingCAP engineers (n=NaN0) were active on GitHub. | 9% 9% (n=39) of all PingCAP employees (n=431140) were active on GitHub. | 39 39 PingCAP employees were active on GitHub. | 
| 89. Yahoo! | (n=39) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=39) of all Yahoo! employees (n=NaN0) were active on GitHub. | 39 39 Yahoo! employees were active on GitHub. | 
| 90. 42 | (n=38) of all 42 engineers (n=NaN0) were active on GitHub. | (n=38) of all 42 employees (n=NaN0) were active on GitHub. | 38 38 42 employees were active on GitHub. | 
| 91. Infosys | (n=38) of all Infosys engineers (n=NaN0) were active on GitHub. | (n=38) of all Infosys employees (n=NaN0) were active on GitHub. | 38 38 Infosys employees were active on GitHub. | 
| 92. Palo Alto Networks | (n=38) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=38) of all Palo Alto Networks employees (n=15,289141) were active on GitHub. | 38 38 Palo Alto Networks employees were active on GitHub. | 
| 93. UIUC | (n=38) of all UIUC engineers (n=NaN0) were active on GitHub. | (n=38) of all UIUC employees (n=NaN0) were active on GitHub. | 38 38 UIUC employees were active on GitHub. | 
| 94. Epitech | (n=38) of all Epitech engineers (n=NaN0) were active on GitHub. | (n=38) of all Epitech employees (n=NaN0) were active on GitHub. | 38 38 Epitech employees were active on GitHub. | 
| 95. TCS | (n=37) of all TCS engineers (n=NaN0) were active on GitHub. | (n=37) of all TCS employees (n=NaN0) were active on GitHub. | 37 37 TCS employees were active on GitHub. | 
| 96. Deloitte | (n=37) of all Deloitte engineers (n=NaN0) were active on GitHub. | (n=37) of all Deloitte employees (n=NaN0) were active on GitHub. | 37 37 Deloitte employees were active on GitHub. | 
| 97. POSTECH | (n=37) of all POSTECH engineers (n=NaN0) were active on GitHub. | (n=37) of all POSTECH employees (n=NaN0) were active on GitHub. | 37 37 POSTECH employees were active on GitHub. | 
| 98. Upwork | (n=37) of all Upwork engineers (n=NaN0) were active on GitHub. | (n=37) of all Upwork employees (n=NaN0) were active on GitHub. | 37 37 Upwork employees were active on GitHub. | 
| 99. Tata Consultancy Services | (n=36) of all Tata Consultancy Services engineers (n=NaN0) were active on GitHub. | (n=36) of all Tata Consultancy Services employees (n=NaN0) were active on GitHub. | 36 36 Tata Consultancy Services employees were active on GitHub. | 
| 100. Kitware | (n=36) of all Kitware engineers (n=NaN0) were active on GitHub. | 21% 21% (n=36) of all Kitware employees (n=174142) were active on GitHub. | 36 36 Kitware employees were active on GitHub. | 
References
- Vercel engineer count: linkedin.com (Retrieved October 2024)
- Vercel employee count: linkedin.com (Retrieved October 2024)
- SUSE engineer count: linkedin.com (Retrieved October 2024)
- SUSE employee count: ir.suse.com (Annual Report FY22, page 249)
- Grafana Labs engineer count: linkedin.com (Retrieved October 2024)
- Grafana Labs employee count: linkedin.com (Retrieved October 2024)
- Automattic engineer count: linkedin.com (Retrieved October 2024)
- Automattic employee count: automattic.com (Retrieved October 2024)
- Mozilla engineer count: linkedin.com (Retrieved October 2024)
- Mozilla employee count: linkedin.com (Retrieved October 2024)
- Elastic engineer count: linkedin.com (retrieved October 2024)
- Elastic employee count: sec.gov (page 15)
- The Guardian engineer count: linkedin.com (Retrieved October 2024)
- The Guardian employee count: linkedin.com (Retrieved October 2024)
- HashiCorp engineer count: sec.gov (page 12)
- HashiCorp employee count: sec.gov (page 13)
- WikiMedia Foundation engineer count: linkedin.com (Retrieved October 2024)
- WikiMedia Foundation employee count: linkedin.com (Retrieved October 2024)
- Docker engineer count: linkedin.com (Retrieved October 2024)
- Docker employee count: linkedin.com (Retrieved October 2024)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Odoo engineer count: linkedin.com (Retrieved October 2024)
- Odoo employee count: linkedin.com (Retrieved October 2024)
- WSO2 engineer count: linkedin.com (Retrieved October 2024)
- WSO2 employee count: linkedin.com (Retrieved October 2024)
- Cloudflare engineer count: linkedin.com
- Cloudflare employee count: sec.gov (page 18)
- DataDog engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 12)
- 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 (Retrieved June 2024)
- New Relic employee count: linkedin.com (Retrieved June 2024)
- ESRI engineer count: linkedin.com (Retrieved October 2024)
- ESRI employee count: linkedin.com (Retrieved October 2024)
- Confluent engineer count: linkedin.com (Retrieved October 2024)
- Confluent employee count: sec.gov (page 18)
- Shopify engineer count: linkedin.com (Retrieved October 2024)
- Shopify employee count: sec.gov (page 10)
- Progress Software engineer count: sec.gov (page 8, referred to as employees in 'product development')
- Progress Software employee count: sec.gov (page 8)
- Microsoft engineer count: sec.gov (page 8, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 8)
- Okta engineer count: linkedin.com (Retrieved October 2024)
- Okta employee count: sec.gov (page 13)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- Alibaba engineer count: linkedin.com (Retrieved October 2024)
- Alibaba employee count: alibabagroup.com (see Fiscal Year 2025 Interim Report, page 15)
- Amazon engineer count: linkedin.com (Retrieved October 2024)
- Amazon employee count: linkedin.com (Retrieved October 2024)
- Adobe engineer count: linkedin.com (Retrieved October 2024)
- Adobe employee count: sec.gov (page 19)
- ThoughtWorks engineer count: linkedin.com (Retrieved October 2024)
- ThoughtWorks employee count: sec.gov (page 6)
- Netflix engineer count: linkedin.com (Retrieved October 2024)
- Netflix employee count: sec.gov (page 2)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Arm Ltd engineer count: sec.gov (page 111)
- Arm Ltd employee count: sec.gov (page 111)
- Tencent engineer count: linkedin.com (Retrieved October 2024)
- Tencent employee count: static.tencent.com (page 52)
- Twilio engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Twilio employee count: sec.gov (page 10)
- Google engineer count: linkedin.com (Retrieved October 2024)
- Google employee count: sec.gov (page 9)
- CyberAgent engineer count: cyberagent.co.jp (Under "Composition ratio", 23.1% are engineers (multiplied by 7720 total employees))
- CyberAgent employee count: cyberagent.co.jp (Under "Total no. of consolidated employees, FY2024")
- Stripe engineer count: linkedin.com (Retrieved March 2024)
- Stripe employee count: linkedin.com (Retrieved March 2024)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- Square, Inc. engineer count: linkedin.com (Retrieved October 2024)
- Square, Inc. employee count: sec.gov (page 20)
- Spotify engineer count: sec.gov (page 65, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 65)
- 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)
- AMD engineer count: linkedin.com (Retrieved October 2024)
- AMD employee count: sec.gov (page 10)
- Autodesk engineer count: linkedin.com (Retrieved October 2024)
- Autodesk employee count: sec.gov (page 13)
- Yandex engineer count: yastatic.net (page 54, referred to as 'developers)
- Yandex employee count: yastatic.net (page 12)
- Meta engineer count: linkedin.com (Retrieved October 2024)
- 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 October 2024)
- Uber employee count: sec.gov (page 7)
- Booking.com engineer count: linkedin.com (Retrieved October 2024)
- Booking.com employee count: sec.gov (page 5)
- 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)
- Intel engineer count: linkedin.com (Retrieved October 2024)
- Intel employee count: sec.gov (page 10)
- Salesforce engineer count: linkedin.com (Retrieved October 2024)
- 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)
- Bloomberg engineer count: linkedin.com (Retrieved October 2024)
- Bloomberg employee count: linkedin.com (Retrieved October 2024)
- Oracle engineer count: sec.gov (page 14, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 14)
- Apple engineer count: linkedin.com (Retrieved October 2024)
- 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)
- PayPal engineer count: linkedin.com (Retrieved October 2024)
- PayPal employee count: sec.gov (page 12)
- NetEase engineer count: sec.gov (page 146, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 146)
- Capital One engineer count: linkedin.com (Retrieved October 2024)
- Capital One employee count: sec.gov (page 18)
- 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 October 2024)
- Nokia employee count: sec.gov (page 70)
- 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 (Retrieved October 2024)
- 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)
- IBM employee count: sec.gov (page 14)
- Accenture employee count: sec.gov (page 3)
- Databricks employee count: linkedin.com
- Sentry.io employee count: linkedin.com
- Snyk employee count: linkedin.com
- Tenstorrent employee count: linkedin.com (Retrieved September 2025)
- Orange S.A. employee count: gallery.orange.com (page 63)
- OpenAI employee count: linkedin.com
- Intuit employee count: sec.gov (page 11)
- PingCAP employee count: linkedin.com
- Palo Alto Networks employee count: sec.gov (page 12)
- Kitware employee count: linkedin.com (Retrieved March 2024)