GitHub faces a fight for its survival at Microsoft

GitHub is experiencing multiple major outages, a remote code execution vulnerability disclosure, and internal repository compromises linked to a poisoned VS Code extension on an employee device. Developers have expressed long-standing concerns after Microsoft’s 2018 $7.5 billion acquisition, including fears of Microsoft control and uncertainty about GitHub’s future. In recent weeks, the company’s operational problems have intensified. The situation traces back to last summer when former CEO Thomas Dohmke resigned, triggering a shakeup in how GitHub operates under Microsoft. Microsoft did not replace the CEO role, and GitHub leadership began reporting directly to Microsoft’s CoreAI team, creating difficulties for employees accustomed to independence.

"In the last few weeks alone, GitHub had multiple major outages, a remote code execution vulnerability disclosure, and its internal code repositories hacked due to a "poisoned" VS Code extension on an employee's device. I've spoken to current and former GitHub employees who all paint a picture of a company that is struggling with a lack of leadership and pressure from competitors."

"When Microsoft announced it was acquiring GitHub in a $7.5 billion deal in 2018, developers were nervous. Some were concerned about Microsoft controlling GitHub, and others were taking a wait-and-see approach. Nearly eight years later, GitHub is now fighting for its survival, amid a surge of outages, security issues, and pressure from competitors."

"Former GitHub CEO Thomas Dohmke resigned and triggered a big shakeup to the way GitHub operates under Microsoft control. Microsoft didn't replace Dohmke's CEO position, so the rest of GitHub's leadership team had to report directly to Microsoft's CoreAI team instead. GitHub employees, who refer to themselves as Hubbers, have struggled to adapt after being proudly independent for so long"

Read at The Verge