CodeRifts VS git-sizer

• Signed decision receipts
  Features and Specs Feature name and a short description :: Signed decision receipts Value or Description :: Policy Engine Breaking budgets, freeze windows, approval matrix :: Breaking Change Detection 10+ change types, OpenAPI schemas :: Economic Impact Cost and engineering effort estimation :: Offline Verification (OVSE) Value or Description :: MCP tool authorization Value or Description :: GitHub required check enforcement Value or Description :: Proof boundaries Value or Description
• Policy Engine
  Breaking budgets, freeze windows, approval matrix
• Breaking Change Detection
  10+ change types, OpenAPI schemas
• Economic Impact
  Cost and engineering effort estimation
• Offline Verification (OVSE)
  A public, MIT-licensed verifier checks any receipt with no API key, no account and no CodeRifts server in the loop.
• MCP server with three tools
  preflight_change_set, verify_receipt and get_decision_details, listed in the official MCP Registry; works with Claude Code, Cursor, Windsurf and custom hosts.
• Merge enforcement on GitHub
  A required, app-bound status check stays red until a grant exists; enforce_admins on, workflow pinned by SHA.
• Published proof boundaries
  Seven "does not prove" limits served live at /.well-known/coderifts.json — what a decision does not establish is a field in the output, not a footnote.
• Named-state verdicts
  CONTINUE, CONTINUE_WITH_MONITORING, REQUEST_APPROVAL or STOP — a state you can branch on, never a score or a boolean.
• Single-use grants
  One grant, one execution; an adapter that cannot prove atomic consumption cannot report the atomic success state.
• Guarded tool table for AI agents
  In the tool table handed to the agent, an ungranted mutation does not exist — nothing to call, not an error.
• Multi-protocol contract diff
  Breaking-change detection for OpenAPI, GraphQL, gRPC, AsyncAPI and MCP tool schemas, with the same signed verdict on every path.

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