When Microsoft announced its $7.5 billion acquisition of GitHub in 2018, the developer community was skeptical. Nearly eight years later, GitHub is now fighting for its survival, facing a surge of outages, security vulnerabilities, and intense pressure from competitors. The platform that hosts over 100 million repositories is struggling to maintain its reputation as the home of open-source development.

The Current Crisis

In recent weeks alone, GitHub experienced multiple major outages, a remote code execution vulnerability disclosure, and a breach of its internal code repositories through a malicious VS Code extension installed on an employee's device. These incidents have shaken developer trust and raised questions about GitHub's operational stability under Microsoft's control. Current and former employees describe a company grappling with a lack of leadership and the pressure from emerging rivals.

The troubles trace back to last summer when former GitHub CEO Thomas Dohmke resigned. Microsoft did not replace the CEO position, instead requiring GitHub's leadership team to report directly to Microsoft's CoreAI division, led by former Meta engineering chief Jay Parikh. This restructuring has created friction among GitHub employees, who previously enjoyed a degree of independence.

The Talent Drain

Since Dohmke's departure, GitHub has suffered a significant talent exodus. A number of employees have followed Dohmke to his new startup, Entire, which is building a developer platform that directly competes with GitHub. Out of 30 employees listed at Entire, at least 11 are former GitHub staff. This brain drain is weakening GitHub's ability to innovate and respond to challenges.

Further departures include veteran Microsoft executive Julia Liuson after 34 years, and Jared Palmer, who joined GitHub as senior vice president in October but is leaving after just six months for a role at Xbox. Elizabeth Pemmerl, GitHub's former chief revenue officer, also resigned last month. The cumulative loss of key personnel has left many inside GitHub feeling that the company's identity is dissolving.

Competition Heats Up

GitHub is not only losing talent but also facing fierce competition. Parikh has reportedly warned colleagues that GitHub faces a critical threat from rivals such as Cursor and Claude Code. While GitHub Copilot initially led the AI coding assistant market, it has fallen behind over the past year. Microsoft reportedly considered acquiring Cursor to close the gap, and has canceled many of its own Claude Code licenses to push developers toward Copilot. This defensive move highlights the gravity of the competitive pressure.

Dohmke's startup Entire represents another direct challenge. Its platform aims to provide a modern developer experience that could lure users away from GitHub. With experienced GitHub veterans on board, Entire is well-positioned to capitalize on GitHub's misfortunes.

Security and Outages

GitHub's technical issues have compounded its strategic problems. A critical vulnerability in GitHub's internal git infrastructure was discovered by Wiz Research in March, allowing potential access to millions of repositories. The company rushed to patch it in under six hours, but the incident underscored systemic security weaknesses.

More recently, 3,800 internal code repositories were breached after an employee installed a malicious VS Code extension. This incident is particularly troubling because VS Code extensions are frequently updated, and even popular extensions have been found to contain malware. GitHub's own security practices—or lack thereof—are now under scrutiny.

Outages have become a recurring nightmare. GitHub CTO Vladimir Fedorov apologized for the latest incidents, acknowledging that the platform is struggling with capacity due to a surge in pull requests and commits. He outlined plans to prioritize availability and reduce unnecessary work, but the damage to reputation is already done. Developer Mitchell Hashimoto, creator of Ghostty terminal, announced he is leaving GitHub after 18 years, citing daily failures.

Leadership Shakeups

The leadership vacuum at GitHub has only worsened. Dan Stein, formerly head of software and digital platforms for Microsoft Customer and Partner Solutions, was appointed as new chief revenue officer. However, with revenue reporting into MCAPS and product work split into Microsoft's Developer Division, many employees feel the company has no cohesive leadership team anymore. One employee described the situation as "basically no more GitHub at all anymore."

Parikh's leadership is reportedly unpopular within Microsoft, and his decision not to appoint a new GitHub CEO has contributed to the instability. Meanwhile, the ongoing migration of GitHub infrastructure to Azure servers—a project initiated by Fedorov—has introduced additional outage risks due to the complexity of MySQL clusters.

GitHub is also facing backlash over its move to usage-based billing for Copilot. Starting next month, every Copilot plan will include monthly AI credits, with users cut off if they exceed their allotment unless they pay more. Developers accustomed to unlimited experimentation are now faced with potential interruptions, further eroding goodwill.

The convergence of technical failures, security breaches, talent loss, and competitive threats places GitHub at a crossroads. Microsoft's CoreAI team must urgently address these challenges or risk losing the developer community that helped make Microsoft a software giant.

Source: The Verge News