Revenge VS git-sizer

• Open-source and community-driven
  Revenge is an open-source Discord mobile client modification project, allowing community contributions, transparency in code, and collaborative development through GitHub.
• Customization and theming
  Revenge allows users to customize their Discord mobile experience with plugins and themes, offering a level of personalization not available in the stock Discord app.
• Plugin support
  The mod supports a plugin system that enables users to extend Discord's functionality with additional features that are not natively provided by the official client.
• Successor to Vendetta
  Revenge was created as a continuation and spiritual successor to the discontinued Vendetta mod, carrying forward its ideas with improvements and active maintenance.
• Lightweight modification approach
  Revenge aims to be a relatively lightweight client mod that patches the existing Discord app rather than requiring a completely separate application, making it easier to set up and use.

Possible disadvantages

• Against Discord's Terms of Service
  Using client modifications like Revenge violates Discord's Terms of Service, which means users risk account suspension or termination if detected by Discord.
• Potential instability and breakage
  Since Revenge relies on patching Discord's code, frequent Discord updates can break functionality, requiring constant maintenance and updates from developers to keep the mod working.
• Security risks
  Third-party plugins and modifications can introduce security vulnerabilities or malicious code, especially if users install plugins from untrusted sources without proper vetting.
• Limited documentation and steep learning curve
  As a relatively niche community project, Revenge may lack comprehensive documentation, making it challenging for less technical users to install, configure, and troubleshoot issues.
• Early development and potential incompleteness
  Revenge is still in active development, meaning some features may be incomplete, buggy, or missing compared to more mature client modification projects, and the project's long-term sustainability is uncertain.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

Tracking Revenge since Apr 2026.

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago