🍺 BREW Explorer

← all formulae

git-sizer

brew install git-sizer v1.5.0 MIT

Compute various size metrics for a Git repository

67
30-day installs · #4097
178
90-day · #4397
981
365-day · #3872
4.0k
★ GitHub stars · updated 7mo ago

Build dependencies

go

GitHub topics

git github golang

Links

Raw metadata
{
  "aliases": [],
  "alternatives": [],
  "build_dependencies": [
    "go"
  ],
  "categories": [],
  "caveats": null,
  "conflicts_with": [],
  "dependencies": [],
  "deprecated": 0,
  "deprecation_reason": null,
  "desc": "Compute various size metrics for a Git repository",
  "disable_reason": null,
  "disabled": 0,
  "enrichment_fetched_at": "2026-06-20T23:38:05+00:00",
  "first_seen": "2026-06-20T23:34:18+00:00",
  "full_name": "git-sizer",
  "github_default_branch": "master",
  "github_last_commit_at": "2026-01-16T14:50:04Z",
  "github_readme_excerpt": "_Happy Git repositories are all alike; every unhappy Git repository is unhappy in its own way._ \u2014Linus Tolstoy\n\n# git-sizer\n\nIs your Git repository bursting at the seams?\n\n`git-sizer` computes various size metrics for a local Git repository, flagging those that might cause you problems or inconvenience. For example:\n\n* Is the repository too big overall? Ideally, Git repositories should be under 1 GiB, and (without special handling) they start to get unwieldy over 5 GiB. Big repositories take a long time to clone and repack, and take a lot of disk space. Suggestions:\n\n    * Avoid storing generated files (e.g., compiler output, JAR files) in Git. It would be better to regenerate them when necessary, or store them in a package registry or even a fileserver.\n\n    * Avoid storing large media assets in Git. You might want to look into [Git-LFS](https://git-lfs.github.com/) or [git-annex](http://git-annex.branchable.com/), which allow you to version your media assets in Git while actually storing them outside of your repository.\n\n    * Avoid storing file archives (e.g., ZIP files, tarballs) in Git, especially if compressed. Different versions of such files don\u0027t delta well against each other, so Git can\u0027t store them efficiently. It would be better to store the individual files in your repository, or store the archive elsewhere.\n\n* Does the repository have too many references (branches and/or tags)? They all have to be transferred to the client for every fetch, even if your clone is up-to-date. Try to limit them to a few tens of thousands at most. Suggestions:\n\n    * Delete unneeded tags and branches.\n\n    * Avoid pushing your \"remote-tracking\" branches to a shared repository.\n\n    * Consider using [\"git notes\"](https://git-scm.com/docs/git-notes) rather than tags to attach auxiliary information to commits (for example, CI build results).\n\n    * Perhaps store some of your rarely-needed tags and branches in a separate fork of your repository that is not fetched from by norma",
  "github_repo": "github/git-sizer",
  "github_stars": 4042,
  "github_topics": [
    "git",
    "github",
    "golang"
  ],
  "homepage": "https://github.com/github/git-sizer",
  "homepage_og_description": null,
  "homepage_og_image": null,
  "homepage_title": null,
  "installs_30d": 67,
  "installs_365d": 981,
  "installs_90d": 178,
  "keg_only": 0,
  "keg_only_reason": null,
  "last_seen": "2026-06-20T23:34:18+00:00",
  "license": "MIT",
  "llm_generated_at": null,
  "llm_model": null,
  "name": "git-sizer",
  "oldnames": [],
  "one_liner": null,
  "optional_dependencies": [],
  "rank_30d": 4097,
  "rank_365d": 3872,
  "rank_90d": 4397,
  "raw_hash": "cbb975115fff8c38",
  "recommended_dependencies": [],
  "revision": 0,
  "ruby_source_path": "Formula/g/git-sizer.rb",
  "tap": "homebrew/core",
  "test_dependencies": [],
  "uses_from_macos": [],
  "version_head": "HEAD",
  "version_stable": "1.5.0",
  "versioned_formulae": [],
  "why_use_this": null
}