Kinnek VS git-sizer

• Free to use for buyers
  Kinnek is free for buyers to use, allowing businesses to submit requests for quotes from suppliers without any upfront costs, making it accessible for small and medium-sized businesses looking to source products.
• Streamlined supplier discovery
  The platform aggregates multiple suppliers in one place, making it easier for businesses to discover and compare vendors for equipment, raw materials, and other supplies rather than searching individually.
• Competitive quoting process
  By allowing buyers to receive multiple quotes from different suppliers, Kinnek fosters competition among vendors, which can lead to better pricing and terms for the buyer.
• Wide range of industries covered
  Kinnek supports a broad range of industries including food and beverage, beauty, packaging, and more, making it a versatile sourcing platform for various types of businesses.
• Simplified procurement workflow
  The platform provides a structured process for requesting quotes, communicating with suppliers, and managing procurement, which can save businesses significant time compared to traditional sourcing methods.

Possible disadvantages

• Limited supplier pool in niche categories
  For highly specialized or niche products, the number of available suppliers on Kinnek may be limited, meaning buyers might not always find the best or most relevant vendors for their specific needs.
• Quality of supplier responses can vary
  Not all supplier responses are equally detailed or timely, and some buyers have reported receiving quotes that don't fully match their requirements, requiring additional back-and-forth communication.
• Less control over supplier vetting
  While Kinnek connects buyers with suppliers, the platform may not provide deep vetting or verification of every supplier's quality, reliability, or financial stability, placing that responsibility on the buyer.
• Potential for unsolicited communications
  After submitting a quote request, some users have reported receiving follow-up emails or calls from suppliers that can feel excessive or unsolicited, which may be an annoyance for some buyers.
• Platform activity may have declined
  There are indications that Kinnek's platform activity and development have slowed in recent years, which could mean fewer active suppliers and less robust support compared to its earlier days.

• 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 Kinnek since Mar 2021.

• 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