count-objects

Measure before you tune. git count-objects -vH reports loose and packed storage, and git repo structure (Git 2.52 1,932 ) summarizes what history contains:

git count-objects -vH
git repo structure

count: 0
...
packs: 1
size-pack: 56.81 KiB
prune-packable: 0
garbage: 0
...
| Repository structure      | Value      |
| ------------------------- | ---------- |
...
|   * Count                 |    240     |
|     * Commits             |     55     |
...
|   * Blobs                 |            |
|     * Maximum size    [5] |  72.17 KiB |
...

A large loose count means maintenance is not running, dozens of packs slow every lookup, and garbage should be zero. BookNest is healthy: one 57 KiB pack whose largest blob is package-lock.json (72 KiB), as the covers live in LFS (git lfs prune trims old local copies). For deeper audits, GitHub 29 's git-sizer 4,077 (github.com/github/git-sizer (https://github.com/github/git-sizer 4,077 ), MIT) rates oversized blobs, wide trees and deep histories by level of concern.