← Back to FAQ

Why did Clash delete the repository?

The Clash repository deletion (or project removal) incident is usually related to the developer's decisions, project maintenance policies, or other external factors. Specific reasons may involve:

• Developer's Personal Reasons: The developer may decide to stop maintaining or delete the project due to personal reasons, such as time constraints, reduced interest in the project, or adjustments in work arrangements.
• Legal or Policy Issues: Clash is a tool that provides network proxy functionality, and in some regions, such tools may violate laws or policies. To avoid legal risks, the developer may decide to delete the project.
• Security Issues: If serious security vulnerabilities are discovered during development or use, the developer may choose to temporarily remove or delete the code repository to conduct security fixes or avoid further risks.
• Community Disputes: Open source projects sometimes face development interruptions due to disagreements or disputes among community members. The developer may choose to delete the project to avoid continuing to engage with specific controversies.
• Project Update or Refactoring: Sometimes, developers choose to delete the original project, possibly to replace it with a brand new version, or to integrate functionality into other projects.

If Clash's deletion refers to a certain version or library being removed, it is recommended to check relevant community or developer announcements or notifications, which usually explain the specific reasons for the deletion and follow-up plans.