You can fork the code, but you cannot claim to be the official version
For twenty years, Mac users sought Notepad++ through workarounds, and when a native port finally arrived, it brought not celebration but legal tension. The creator of the beloved text editor does not contest the code itself — open-source licensing permits such work — but argues that the port's branding blurs the line between derivative and official, a distinction that trademark law holds sacred. At the intersection of open-source freedom and identity rights, this dispute asks a question the software world has long deferred: who owns the name when anyone may carry the flame?
- A macOS port of Notepad++ — assembled through AI rather than hand-crafted by a seasoned developer — appeared without the original creator's blessing, presenting itself in ways that reportedly suggest official status.
- The creator is preparing legal action, not against the act of porting, but against the branding that he believes impersonates his project and misleads users about its origin.
- The port developer defends the technical soundness of the work, pointing to the genuine value of giving Mac users a native option after two decades of absence.
- The core tension is a collision between open-source licensing — which grants broad freedoms over code — and trademark law, which does not extend those freedoms to names and identity.
- The outcome hinges on whether the port developer rebrands, withdraws, or fights, and either path could set lasting precedent for how open-source maintainers protect their project's identity against derivative works on unsupported platforms.
For twenty years, Notepad++ never officially landed on macOS — available only through workarounds and patience. That changed recently when someone released a native port, finally bridging the gap. The creator of Notepad++, however, is preparing legal action rather than offering thanks.
The dispute is not about code. Open-source licensing permits exactly this kind of derivative work, and the creator has acknowledged as much. What troubles him is the presentation: the port reportedly identifies itself in ways that could lead users to believe they are installing the official Notepad++ for Mac, when in fact it is an unauthorized derivative. That distinction is the heart of trademark law — confusion about origin is the violation.
The port was generated using artificial intelligence, which may explain why its branding received less careful scrutiny than a human developer might have applied. The technical result may be sound, but the way it faces the user apparently was not.
The port developer has defended the work on its merits, and those merits are real — a native Mac option after two decades is a genuine contribution. The creator's position, however, is that technical legitimacy and branding legitimacy are separate questions entirely: fork the code, port it anywhere, but do not call yourself the official version.
What happens next — litigation, rebranding, or withdrawal — may determine how open-source projects can protect their identity against derivative works on platforms they have never officially supported. For now, Mac users who waited twenty years find themselves caught between a working solution and an unresolved legal question.
For two decades, Notepad++ existed in a peculiar limbo on Apple's platform—available to Mac users only through workarounds and third-party solutions, never as a native application. That changed recently when someone released a macOS port of the lightweight text editor, finally bringing the tool to the operating system where it had never officially landed. The creator of Notepad++, however, is not celebrating. Instead, he is preparing legal action against the port's developer, arguing that while the technical work may be legitimate, the way it is being presented to users crosses a line.
The dispute centers on branding and identity rather than code. The original Notepad++ creator has made clear that he does not object to the existence of a macOS version built from his open-source codebase—that is, after all, what open-source licensing permits. What troubles him is how the port is being marketed and labeled. According to reports, the port appears to present itself in ways that could mislead users into thinking it is the official Notepad++ application for Mac, when in fact it is an unauthorized derivative work. This distinction matters legally. A trademark violation occurs when a product uses branding that confuses consumers about its origin or official status, and the Notepad++ creator believes that is exactly what has happened here.
The port itself was apparently generated using artificial intelligence, which adds another layer to the dispute. Rather than being hand-coded by a developer with deep knowledge of both the original application and macOS architecture, the port was assembled through automated means. This technical approach may explain why the branding question became so central—if the code was machine-generated, the presentation to users may not have received the same careful attention that a human developer would have applied.
What makes this case notable is that it sits at the intersection of open-source rights and trademark law, two areas that do not always align neatly. Open-source licenses like the one Notepad++ uses grant broad freedoms to modify and redistribute code. They do not, however, grant the right to use someone else's trademark or to impersonate their official project. The creator's position is that these are separate questions: you can fork the code, you can port it to new platforms, but you cannot do so while claiming to be the official version or using branding that suggests you are.
The port developer has reportedly defended the technical legitimacy of the work, arguing that the implementation is sound and that users benefit from having a native macOS option. This is not wrong. From a purely functional standpoint, bringing Notepad++ to Mac after twenty years of absence is a genuine contribution. The creator's complaint is not about the existence of the port but about its presentation—the way it appears in app stores, how it identifies itself, what promises it makes to users about its official status.
What happens next will likely depend on how aggressively the original creator pursues the matter and whether the port developer is willing to rebrand or remove the application. If the case goes to litigation, it could establish precedent for how open-source projects can enforce trademark rights against derivative works, particularly those created for platforms the original project does not officially support. For now, the port exists in legal limbo, and Mac users who have waited two decades for an official Notepad++ experience find themselves caught between a technical solution and a branding dispute.
Notable Quotes
The port developer argues the technical implementation is valid, but the creator contends the branding impersonates the official application— Dispute summary
The Hearth Conversation Another angle on the story
Why does the branding matter so much if the code itself is legitimate and open-source?
Because trademark exists to tell users where something actually comes from. If I see "Notepad++" on the Mac App Store, I assume it's the official version. If it's not, I've been misled about what I'm installing—even if the code works fine.
But the creator didn't make a macOS version himself. Shouldn't he be grateful someone did?
Gratitude and legal rights are different things. He can appreciate the work while still saying: don't use my name to do it. Call it something else, make clear it's unofficial, and there's no problem.
What's the actual harm to users if they install this port thinking it's official?
They might expect official support, security updates, or compatibility guarantees they won't get. They might report bugs to the wrong place. They might trust it more than they should. The branding creates false expectations.
Is this a common problem in open-source?
It's becoming more common as AI makes it easier to port code without understanding the ecosystem around it. The legal question—can you use someone's trademark on a derivative work—is old. But the scale and speed are new.
What would a fair resolution look like?
The port developer rebrand it clearly as unofficial, add disclaimers, maybe call it "Notepad++ for Mac (Community Port)" or something that signals it's not the original creator's work. Then everyone wins—Mac users get the tool, the creator's trademark stays protected.