Has the GrapheneOS core developer team changed since 2023–2025?

Checked on December 17, 2025
Disclaimer: Factually can make mistakes. Please verify important information or breaking news. Learn more.

This fact-check may be outdated. Consider refreshing it to get the most current information.

Executive summary

GrapheneOS's public leadership picture shifted in 2023 when lead developer Daniel Micay announced he was stepping down as lead developer and a Foundation director amid harassment and swatting incidents [1] [2], yet official Canadian federal corporation records still list him as a director as of December 2025 [3]. Over 2023–2025 the project describes a transition from a single prominent lead to a small, distributed core team with multiple full‑time and part‑time developers paid by donations and corporate collaborators, and the project continued active development through 2025 [4] [5].

1. The headline: a public resignation that didn't erase Micay from corporate records

In May 2023 Micay publicly stated he was stepping down as GrapheneOS's lead developer and said he would be replaced as a Foundation director, citing escalating harassment and swatting attacks as the reason for leaving public leadership roles [1] [2]. That public announcement is recorded in multiple contemporaneous reports and project histories [6] [1], yet the project's Wikipedia entry notes that as of December 2025 the GrapheneOS Foundation's federal corporate filings still list Micay as a director, creating a discrepancy between public statements and corporate paperwork [3].

2. From single-leader narrative to a distributed core team

GrapheneOS's own history and FAQ indicate the project now operates with “multiple full‑time and part‑time developers” supported by donations and some company collaborations, signaling an organizational shift away from a one‑person public face toward a small distributed development team model [4]. That same institutional framing appears in secondary summaries, which note Micay stepped down in 2023 “while remaining involved in other capacities,” implying the formal contributor base and day‑to‑day development roles evolved rather than the project collapsing [6].

3. Operational continuity: releases and development through 2025

Technical outputs show continued, active engineering: GrapheneOS published security preview releases in late 2025 that bundle Android 16 security patches and a raft of CVE fixes, demonstrating the core developers remained operational and releasing security updates through 2025 [5]. Public communications in 2025 also show the project discussing device strategy and OEM talks, indicating an ongoing roadmap and functioning engineering team beyond the 2023 leadership change [7].

4. Disruptions and personnel shocks during 2023–2025

Reporting and project summaries document further disruptions: in April 2025 one of the two senior developers was reportedly conscripted into an ongoing war, which prompted temporary revocation of repository access and illustrates that personnel availability—not only governance—changed during this period [6]. The project also warns that a former sponsor engaged in misinformation and harassment campaigns against contributors, an implicit pressure factor likely influencing both public leadership choices and internal team arrangements [4].

5. Interpreting ‘change’ — leadership, governance, and practical authorship

Change since 2023 is real but layered: the public leadership role held by Micay ended by his account, corporate records suggest lingering formal ties, and the operational core diversified into multiple paid contributors and collaborations with companies, which sustained product releases and roadmap work [1] [3] [4] [5]. Sources differ on emphasis—project pages and grokipedia stress a deliberate team expansion, while news items highlighted a dramatic singular resignation—so assessing “the team changed” depends on whether one measures public leadership, corporate governance listings, or the functional engineering roster [6] [1] [3].

6. Limits of the available reporting and outstanding questions

The sources document public statements, corporate filings, published releases, and summaries of internal events, but they do not provide a complete roster of core contributors, nor do they reconcile why corporate filings still list Micay as a director despite his announced resignation—those gaps leave room for alternative administrative explanations or delays in filings that the available reporting does not resolve [3] [1] [4]. Given those limits, the most supported conclusion is that the GrapheneOS core developer team did change in composition and governance style from 2023 to 2025: public leadership stepped back, the project formalized a multi‑person core team, and it weathered further personnel and harassment disruptions while continuing active releases [1] [4] [5] [6].

Want to dive deeper?
Who are the current core contributors to GrapheneOS and how are development responsibilities divided?
What legal or bureaucratic reasons could explain a corporate filing listing a director after a public resignation?
How have harassment and misinformation campaigns impacted open‑source security projects historically?