SecretHub VS git-sizer

• Enhanced Security
  SecretHub centralizes secrets management, reducing the risk of accidentally exposing sensitive information in codebases.
• Ease of Use
  With its user-friendly interfaces and integration support, developers can easily deploy and manage secrets without extensive learning curves.
• Access Control
  Offers fine-grained access controls to ensure only authorized users can access specific secrets, enhancing security.
• Audit Logging
  Provides detailed logging of secret access and changes, enabling better tracking and compliance.
• Integration Capabilities
  Supports integration with various CI/CD pipelines and cloud providers, allowing seamless incorporation into existing workflows.

Possible disadvantages

• Cost
  May be expensive for small teams or individual developers compared to self-hosted solutions.
• Dependency Risk
  Reliance on a third-party service means potential downtime or vendor lock-in, which can impact operations.
• Learning Curve
  Despite ease of use, new users might still face a learning curve in understanding best practices for secrets management.
• Performance Overhead
  Integrating with SecretHub may introduce some performance overhead due to the extra layer of security checks.
• Limited Offline Support
  If internet connectivity is required for accessing secrets, it might be limiting in environments with restricted access.

• 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.

No analysis of SecretHub yet.

• How can I store a password properly so that it is not visible in source code.

  A simpler solution is sercrethub https://secrethub.io (who just got purchased by 1password). I’ve used it on my personal project and it worked great and has nice features - and is free for some small number of secrets, but with much... Source: about 5 years ago

• 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