When Microsoft announced it was acquiring GitHub in a $7.5 billion deal in 2018, developers were nervous. Many feared that Microsoft would tighten its grip on the open-source community, while others adopted a wait-and-see attitude. Nearly eight years later, those concerns have materialized in ways few anticipated. GitHub is now fighting for its survival, grappling with a surge of outages, security vulnerabilities, and mounting pressure from competitors that threatens its dominance in the developer ecosystem.
In the past few weeks alone, GitHub experienced multiple major outages, a critical remote code execution vulnerability disclosure, and a breach of its internal code repositories caused by a poisoned VS Code extension on an employee's device. Conversations with current and former GitHub employees reveal a company struggling under a lack of cohesive leadership and an accelerating talent drain. The once-proud independent platform now feels like a hollowed-out division of Microsoft, with morale at an all-time low.
Leadership Vacuum and Talent Exodus
Much of GitHub's current predicament can be traced back to last summer, when former CEO Thomas Dohmke resigned. Rather than appoint a successor, Microsoft's leadership team decided not to fill the CEO role, forcing GitHub's executives to report directly to Microsoft's CoreAI division, led by former Meta engineering chief Jay Parikh. Parikh, personally recruited by Microsoft CEO Satya Nadella to oversee the company's AI transformation, has reportedly made unpopular decisions, including the choice to leave GitHub without a CEO. This move alienated long-time GitHub employees—or Hubbers—who had prided themselves on the company's independent culture.
The leadership vacuum has triggered a wave of departures. Many former GitHub employees have followed Dohmke to his new startup, Entire, a developer platform that directly competes with GitHub. Of the 30 employees listed at Entire, at least 11 previously worked at GitHub. Other key figures have also left: Julia Liuson, a veteran Microsoft executive who oversaw GitHub after Dohmke's departure, announced her resignation after 34 years at the company. Jared Palmer, who joined GitHub as a senior vice president in October, left after only a few months to become VP of engineering at Xbox. Elizabeth Pemmerl, GitHub's chief revenue officer, also resigned, replaced by Dan Stein from Microsoft's Customer and Partner Solutions division. These departures have left GitHub with a fragmented leadership structure, with revenue reporting into Microsoft MCAPS and product work split into the Developer Division. One employee lamented, 'There's basically no more GitHub at all anymore. It's all Microsoft, and the company is collapsing.'
Outages and Infrastructure Woes
The technical challenges facing GitHub are equally dire. Over the past year, the platform has suffered an unusual number of outages, frustrating developers around the world. In response, GitHub CTO Vladimir Fedorov—who joined the company only a year ago after decades at Microsoft and Facebook—issued a public apology. He attributed the outages to a massive growth spike in pull requests, commits, and new repositories, coupled with the ongoing migration of GitHub's infrastructure to Azure servers. Fedorov acknowledged that the migration, which he initiated months after joining, has been fraught with complexity due to GitHub's intricate MySQL clusters. 'Our priorities are clear: availability first, then capacity, then new features,' he said, outlining steps to reduce unnecessary work, improve caching, and isolate critical services.
Despite these efforts, the outages have driven some high-profile projects away. Mitchell Hashimoto, creator of the Ghostty terminal, announced he was leaving GitHub after 18 years, citing daily failures that made it impossible to code. 'I want it to be better, but I also want to code. And I can't code with GitHub anymore,' he wrote. Such departures signal a growing erosion of trust among the developer community, which once saw GitHub as the gold standard for version control and collaboration.
Security Breaches and Copilot Controversies
Security concerns have compounded GitHub's troubles. In March, researchers from Wiz uncovered a critical vulnerability in GitHub's internal git infrastructure that could have exposed millions of public and private repositories. GitHub patched the flaw within six hours, but the incident highlighted the platform's vulnerability. Earlier this week, a separate breach saw 3,800 internal code repositories compromised after an employee installed a malicious VS Code extension. This incident underscores the risks of GitHub's deep integration with Microsoft's development tools, where extensions with hundreds of thousands of installs have been known to harbor cryptomining malware.
GitHub also faces backlash over its planned shift to usage-based billing for GitHub Copilot, its AI-powered coding assistant. Starting next month, all Copilot plans will include a monthly allotment of AI credits, after which users will be cut off unless they pay for additional usage. This marks a departure from the current system, where users are automatically downgraded to a less capable model once limits are reached. Developers have criticized the change as punitive, especially as competitors like Cursor and Claude Code offer more flexible pricing and advanced features.
Competitive Pressure from All Sides
The competitive landscape is intensifying. GitHub Copilot, which once led the AI coding race, has fallen behind rivals in recent months. Private warnings from Parikh suggest that GitHub faces a 'critical threat' from upstarts like Entire, Cursor, and Claude Code. Microsoft even considered acquiring Cursor to bridge the gap, and last week, it began canceling many Claude Code licenses to force internal developers to help improve Copilot. However, the talent drain and leadership instability make it difficult to mount a coherent response.
Beyond AI coding tools, GitHub's core platform is also under pressure. Entire, founded by former GitHub CEO Dohmke, aims to build a new developer platform that directly competes with GitHub. While still nascent, Entire has already attracted significant talent and funding. Meanwhile, traditional competitors like GitLab and Bitbucket continue to innovate, capitalizing on GitHub's outages and reputational damage.
Broader Implications for Microsoft
GitHub's struggles are part of a larger pattern of challenges within Microsoft's developer ecosystem. The company is simultaneously dealing with the retirement of Teams' Together Mode, a rebranding of Xbox to all caps, and the death of former Developer Division chief S. Somasegar. On the positive side, Microsoft is testing a resizable taskbar and Start menu in Windows 11, and it has appointed its first chief design officer, Jon Friedman. But these moves do little to address the immediate crisis at GitHub.
The departure of key executives to other parts of Microsoft, such as Jared Palmer's move to Xbox, suggests that many are eager to distance themselves from Parikh's leadership. Xbox chief Asha Sharma has been building her own team by hiring former CoreAI executives, further draining GitHub of experienced talent. The race is now on for competitors to build the next GitHub and take advantage of Microsoft's struggles. If Microsoft's CoreAI team cannot stabilize GitHub, the company risks losing the very developers that helped transform it into a software giant.
Source: The Verge News