When Microsoft announced it was acquiring GitHub in a $7.5 billion deal in 2018, developers were nervous. Some feared Microsoft's control over the open-source platform, while others adopted a wait-and-see approach. Nearly eight years later, GitHub is now fighting for its survival, grappling with a surge of outages, security issues, and intense pressure from competitors.
A Perfect Storm of Challenges
In recent weeks, GitHub has experienced multiple major outages, a remote code execution vulnerability disclosure, and a breach of its internal code repositories due to a malicious VS Code extension installed on an employee's device. These incidents have eroded developer trust and highlighted systemic problems within the organization. Current and former employees paint a picture of a company struggling with a lack of leadership and mounting competitive threats.
The turmoil can be traced back to last summer when former GitHub CEO Thomas Dohmke resigned, triggering a significant shakeup in how GitHub operates under Microsoft control. Instead of appointing a new CEO, Microsoft folded GitHub's leadership into its CoreAI team, led by former Meta engineering chief Jay Parikh. This change has created friction, as Hubbers — GitHub employees — have struggled to adapt to the loss of independence.
Talent Exodus and Leadership Vacuum
Since Dohmke's departure, GitHub has experienced a notable talent drain. At least 11 former GitHub employees have joined Dohmke's new venture, Entire, a developer platform that directly competes with GitHub. Other key figures have also left: veteran Microsoft executive Julia Liuson departed after 34 years; Jared Palmer, who joined GitHub as a senior vice president in October, is moving to Xbox; and Elizabeth Pemmerl, GitHub's chief revenue officer, resigned last month. These departures have left GitHub with a diminished leadership team, raising concerns about direction and stability.
One employee described the situation starkly: "There's basically no more GitHub at all anymore. It's all Microsoft, and the company is collapsing, both in outages that are really bad and have torched the company reputation… and in an exodus of leadership."
Technical Failures and Security Breaches
The outages have been particularly damaging. GitHub CTO Vladimir Fedorov, who joined a year ago, has apologized for the incidents, attributing them to a huge growth spike in pull requests, commits, and new repositories. GitHub is in the midst of a complex migration to Azure servers, which has contributed to the instability. Fedorov promised that availability is the top priority, with efforts to reduce unnecessary work, improve caching, and isolate critical services.
Security issues have compounded the problem. In March, Wiz Research used AI models to uncover a critical vulnerability in GitHub's internal git infrastructure, which could have allowed attackers to access millions of code repositories. Earlier, 3,800 internal repositories were breached after an employee installed a malicious VS Code extension. These incidents highlight the challenges of maintaining security in a rapidly evolving environment.
Competitive Pressures Mount
GitHub's AI coding tool, Copilot, once an early leader, has fallen behind rivals like Cursor and Claude Code. Microsoft has reportedly considered acquiring Cursor to close the gap, and the company is canceling many Claude Code licenses to force developers to improve Copilot. The competitive landscape is intensifying, with upstarts like Entire threatening to lure away both talent and users.
Jay Parikh has privately warned colleagues that GitHub faces a critical threat. The press is on him and the CoreAI team to reverse the decline. If they fail, Microsoft risks losing the developer community that has been central to its resurgence as a software giant.
Migration to Azure and Infrastructure Struggles
GitHub's ongoing migration to Azure servers, a project initiated by Fedorov, is intended to address data center capacity issues. However, the complex MySQL clusters involved have led to significant outages. Developers like Mitchell Hashimoto, creator of Ghostty, have expressed frustration, with Hashimoto announcing he is leaving GitHub after 18 years. "GitHub is failing me, every single day," he wrote.
The outages and security breaches are driving some developers away, while the shift to usage-based billing for Copilot is adding to the discontent. Starting next month, Copilot plans will include a monthly allotment of AI credits, after which users will be cut off unless they pay for more. This change has angered developers who previously enjoyed unlimited experimentation.
Leadership Under Scrutiny
The lack of a dedicated CEO has left GitHub feeling rudderless. With revenue now reporting into Microsoft Customer and Partner Solutions (MCAPS) and product work split into Microsoft's Developer Division, many insiders feel the company's identity has been lost. The Xbox team has poached several CoreAI executives, suggesting even internal divisions are seeking to escape Parikh's leadership.
As GitHub fights for survival, the stakes are high. The platform that hosts millions of open-source projects must overcome its technical issues, rebuild trust, and fend off competitors. The next few months will be critical for Parikh and the CoreAI team to prove that they can meet the moment.
Source: The Verge News