Repository navigation
[Project Support]: ant-design-blazor - repo disabled by GitHub #554
Description
Project
ant-design-blazor
Project Url
https://github.com/ant-design-blazor/ant-design-blazor
Description
Summary
ant-design-blazor, an official member project of the .NET Foundation, has had
its GitHub repository (https://github.com/ant-design-blazor/ant-design-blazor)
disabled by GitHub Staff due to an alleged violation of GitHub's Terms of
Service. We believe this was done in error and are requesting the Foundation's
support to help us restore access.
Background
- The repository is a well-known open-source project: a set of enterprise-class
UI components based on the Ant Design specification and Blazor
(WebAssembly / Server). It has been actively maintained since 2018 and is
MIT-licensed. - The project is an official member project of the .NET Foundation and follows
the Foundation's policies and code of conduct. - The project is maintained by a global community of contributors from all over
the world; it is not a personal project of any single country or region. - On 2026-09-25, access to the repository was disabled by GitHub Staff. We
received no prior notice and, after review, we are unable to identify any
content that violates GitHub's Terms of Service. - The disablement has also affected thousands of fork repositories created by
users, some of which contain their own production code. The impact is
extremely wide. - We received GitHub's notification email when the repository was disabled, but
it does not specify the content, report, or investigation that triggered the
action. We are attaching the email for reference.
Impact scope
- The repository is one of the most widely used .NET / Blazor UI component
libraries in the community (6,100+ GitHub stars, and 1,000+ forks), with the "AntDesign"
package distributed via NuGet and the official site https://antblazor.com/. - Thousands of fork repositories have been disabled together with the original
repository. Some of these forks contain their owners' own production code and
private work, and the owners have also lost access to them. The actual impact
therefore extends far beyond the original repository itself. - Ongoing development of the project has been halted, including the handling of
issues, pull requests, and releases, which affects the entire contributor and
user community. - As an official .NET Foundation member project maintained by a global
community, the disablement also affects the reputation and availability of an
open-source asset supported by the Foundation.
What we noticed
A few days before the disablement, we noticed bot-submitted code in several
recent pull requests. We believe this may have been a false positive from an
official bot, but it is also possible that a GitHub token was leaked and
misused. We take this very seriously and are willing to investigate and fix any
issue immediately once GitHub tells us what needs to be addressed.
Support needed
We are requesting the .NET Foundation's support in the following areas:
- Advocacy / official channels: Help us escalate this to the appropriate
GitHub / Microsoft channels to request a review of the decision and
restoration of the repository and the affected forks. - Legal and licensing guidance: Confirm whether any compliance issue with our
project could have triggered the action, and advise on next steps. - Technical guidance: Help us audit recent pull requests and commits for
suspicious bot activity, and advise on securing our GitHub tokens and
CI/CD pipelines.
Desired outcome
Restoration of access to https://github.com/ant-design-blazor/ant-design-blazor
and the affected fork repositories, once the review confirms there is no
genuine violation.
Contact
- GitHub username: ElderJames
- Email: shunjiey@hotmail.com
Due By
2026-10-15
Activity
WhyILoveSpringRoll commentedon Oct 12, 2026
I strongly support this request for help with the ant-design-blazor repository.
This is one of the most important and widely used Blazor UI component libraries in the .NET ecosystem (6k+ stars, extensive NuGet usage, and an official .NET Foundation member project). It has been actively maintained by a global community for years under the MIT license and follows the Foundation’s policies.
The sudden disablement by GitHub (with no clear prior notice or specific violation identified) has halted development, blocked issue/PR handling, and also affected thousands of forks—some of which contain users’ own production code. This has a broad negative impact on the Blazor community.
I hope the .NET Foundation can assist with escalation to GitHub/Microsoft, provide any necessary guidance on compliance or security review of recent activity, and help restore access as soon as possible if no genuine violation is found. Thank you for looking into this.
dashiell-zhang commentedon Oct 12, 2026
ant-design-blazor is one of the most valuable UI component libraries for the Blazor ecosystem. Many developers rely on it for building production applications with .NET. I hope the repository can be restored soon and that this excellent open-source project can continue to serve the community.
lijianxin520 commentedon Oct 12, 2026
It is strongly recommended to resume the use. If the project violates relevant regulations, it is necessary to promptly notify the person in charge and require them to make corrections within a specified time frame. Directly stopping access to the project is not advisable.
bxjg1987 commentedon Oct 12, 2026
I'm chiming in as a regular user and big fan of the ant-design-blazor project to voice my full support for this appeal.
ant-design-blazor is one of the most polished, production-ready UI component libraries available for Blazor. My team and I rely on it heavily across multiple production applications — it consistently delivers reliable, enterprise-grade components aligned with the Ant Design specification, and has been a cornerstone of the .NET Blazor open-source ecosystem for years. It operates transparently under the MIT license and follows all .NET Foundation policies as an official member project.
It is deeply concerning to see the repository disabled without prior notice or clear explanation. The impact extends far beyond the main repo: thousands of forks have also been affected, including many that hold teams' own production code and custom work. Given the project's strong track record of compliance and community-driven governance, this very much appears to be an erroneous enforcement action.
I strongly encourage the .NET Foundation to help escalate this matter through official GitHub and Microsoft channels, support a thorough review, and work to restore access to both the original repository and all impacted fork repositories as quickly as possible.
Thank you to the maintainers for all your outstanding work on this fantastic project, and thank you to the .NET Foundation for your assistance in resolving this.
MarvelTiter commentedon Oct 12, 2026
As a user of ant-design-blazor, I fully support this request.
ant-design-blazor is one of the UI component libraries I rely on most when building production applications with Blazor. Its components are high-quality, closely aligned with the Ant Design specification, and have been stable and reliable for years—making it an indispensable part of the .NET Blazor ecosystem. As an MIT-licensed, globally community-maintained official member project of the .NET Foundation, it has always operated transparently and in line with the Foundation's policies.
The repository was disabled without clear prior notice or any specific violation identified, which is deeply concerning. The impact extends far beyond the main repository—thousands of forks have also been disabled, some of which contain users' own production code and private work. Given the project's strong track record of compliance and community governance, this very much appears to be an erroneous enforcement action.
I strongly urge the .NET Foundation to help escalate this matter through official GitHub / Microsoft channels, support a thorough review, and work to restore access to both the original repository and all impacted fork repositories as quickly as possible.
Thank you to the maintainers for all your work on this excellent project, and thank you to the .NET Foundation for your assistance in resolving this.
xmu-Jiang commentedon Oct 12, 2026
As a long-time user of ant-design-blazor, I fully support this request.
ant-design-blazor is one of the most mature and production-ready UI component libraries in the Blazor ecosystem. My team and I have been using it in real projects for a long time, and it has consistently delivered reliable, enterprise-grade components that follow the Ant Design specification. It is an MIT-licensed, globally community-maintained official member project of the .NET Foundation, and has always operated transparently and in line with the Foundation's policies.
I strongly urge the .NET Foundation to help escalate this matter through official GitHub / Microsoft channels, support a thorough review, and work to restore access to both the original repository and all impacted fork repositories as soon as possible.
Thank you to the maintainers for your outstanding work on this excellent project, and thank you to the .NET Foundation for your help in resolving this.
shushu789 commentedon Oct 13, 2026
My project also uses ant-design-blazor, and I hope to restore access as soon as possible.
ChrisSfanos commentedon Oct 13, 2026
Thanks @ElderJames - I'll start checking on this today
ElderJames commentedon Oct 15, 2026
Thank you very much @ChrisSfanos , are there any progress?
ChrisSfanos commentedon Oct 15, 2026
Hey @ElderJames - yes some progress - I found folks who know about it, but I'm having trouble getting to the right folks to help get this unblocked. But I am working it for you
ChrisSfanos commentedon Oct 19, 2026
The repo is back - I'm going to resolve the issue
ElderJames commentedon Oct 20, 2026
Thank you @ChrisSfanos, but the pull request hasn’t fully restored everything.
ElderJames commentedon Oct 20, 2026
As well as the discussions.
ChrisSfanos commentedon Oct 20, 2026
Hey @ElderJames - you can definitely leave the issue open here in the DNF repo, but at this stage, I'll have to leave it in the hands of GH Support to help here as I have no control over the mechanics of the repo restore :-)