OneNoughtOne VS git-sizer

• Creative Design Focus
  OneNoughtOne appears to position itself as a creative design agency, suggesting a strong emphasis on visual aesthetics and brand identity work for clients.
• Niche Specialization
  As a smaller, specialized agency, they may offer more personalized attention and tailored solutions compared to larger, more impersonal firms.
• Potentially Flexible Service Offering
  Boutique agencies like this often provide flexible, customizable service packages that can be adapted to different client needs and budgets.
• Direct Client Relationships
  Smaller agencies typically allow for more direct communication with the actual designers or team members working on projects, rather than going through multiple layers of account management.
• Portfolio-Driven Approach
  The website likely showcases a curated portfolio of work, allowing potential clients to directly evaluate the quality and style of previous projects before engaging.

Possible disadvantages

• Limited Public Information
  There is minimal publicly available information about this company, making it difficult to verify claims, reputation, client reviews, or long-term business stability.
• Potential Scale Limitations
  As a smaller or boutique operation, they may have limited capacity to handle very large-scale projects or high-volume client demands simultaneously.
• Uncertain Pricing Transparency
  Many boutique design agencies do not publish pricing information, requiring potential clients to go through inquiry processes before understanding cost structures.
• Limited Service Diversification
  Specialized or niche agencies may not offer the full range of services (e.g., development, marketing, SEO) that larger full-service agencies provide under one roof.
• Unclear Market Track Record
  Without extensive documented case studies, client testimonials, or industry recognition readily available, it can be challenging to assess their long-term track record and reliability.

• 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 OneNoughtOne since Mar 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