Microsoft’s Repeated Open‑Source Code Misuse: Cases, Legal Implications, and Lessons for Developers

Recently, the Microsoft Edge team published a cloud‑gaming announcement that referenced a community‑maintained Edge Flatpak project without crediting its author, prompting the developer (TheEvilSkeleton) to publicly demand acknowledgment and proper maintenance support.

The author also highlighted a similar controversy surrounding Microsoft’s WinGet tool, which was accused of copying the AppGet project’s design and code after months of dialogue with the original creator, yet Microsoft only offered a vague apology without compensation.

Another case involved Microsoft’s Rush project, alleged to have duplicated the Lerna multi‑package manager’s code and structure shortly after Lerna’s release, with the original author noting that Microsoft failed to provide any substantive explanation or licensing clarification.

These three incidents illustrate a pattern of misattribution and potential license violations, underscoring widespread misunderstandings about open‑source licenses; many developers mistakenly believe that using open‑source code is unrestricted, ignoring the legal obligations to retain copyright notices and comply with license terms.

The article explains that open‑source software, like proprietary software, is protected by copyright and may also be subject to contract, patent, and trademark law; licenses such as MIT or Apache 2.0 allow modification and redistribution only when the original author’s attribution is preserved.

Because individual developers often lack the resources to enforce their rights against large corporations, the piece advises developers to thoroughly understand license terms, document infringements, and seek community or public support when defending their contributions.