Find large tracked files

Before you begin

Python 3.12 or later.
Git must be installed on PATH. --repo must be an existing non-bare repository.

What this script changesRead-only Git inspection with optional locking disabled. No fetch, checkout, reset, commit, merge, or push is performed. Metadata, author information, and filenames can be private.

Set up your example

Save as git-large-tracked-files.py.
Open a terminal in its folder.
Run python "git-large-tracked-files.py" --help and prepare the listed input files.

This recipe uses your own local input or creates its own example output. Follow the setup steps below.

Download the ZIP, extract it, and open a terminal inside the extracted folder. The source file is git-large-tracked-files.py.

Run the script

python "git-large-tracked-files.py" --minimum-mib 5

If your system uses python3 instead of python, use that command for Python examples. Keep paths containing spaces in quotes. Required inputs and optional settings are described in the code and setup steps.

What to expect

A tracked 12 MiB asset appears; missing tracked files are skipped.

The complete script

#!/usr/bin/env python3
"""Measure regular tracked working-tree files and report those above a selected size."""
import argparse
import sys
import json
from pathlib import Path
import os
import subprocess
from collections import Counter
from datetime import datetime, timezone

def git(repo,*arguments,allow=(0,)):
    env=dict(os.environ,GIT_OPTIONAL_LOCKS='0',GIT_PAGER='cat',GIT_TERMINAL_PROMPT='0')
    result=subprocess.run(['git','--no-pager','--no-optional-locks','-C',str(repo),*arguments],capture_output=True,timeout=60,env=env)
    if result.returncode not in allow:
        raise RuntimeError(result.stderr.decode('utf-8','replace').strip() or f'git exited {result.returncode}')
    return result.stdout

def text(repo,*arguments,allow=(0,)):
    return git(repo,*arguments,allow=allow).decode('utf-8','replace')

def main():
    parser = argparse.ArgumentParser(description='Measure regular tracked working-tree files and report those above a selected size.')
    parser.add_argument("--repo",type=Path,default=Path("."))
    parser.add_argument('--minimum-mib',type=float,default=5)
    args = parser.parse_args()
    repo=Path(text(args.repo,"rev-parse","--show-toplevel").strip())
    
    if args.minimum_mib<0:raise ValueError('--minimum-mib cannot be negative')
    rows=[]
    for raw in git(repo,'ls-files','-z').split(b'\0'):
        if not raw:continue
        name=os.fsdecode(raw);path=repo/name
        if path.is_file() and not path.is_symlink():
            size=path.stat().st_size
            if size>=args.minimum_mib*1024**2:rows.append({'path':name,'bytes':size})
    print(json.dumps(sorted(rows,key=lambda r:r['bytes'],reverse=True),indent=2))

if __name__ == '__main__':
    try:
        main()
    except (OSError, ValueError, RuntimeError) as exc:
        print(f'Error: {exc}', file=sys.stderr)
        sys.exit(1)

Open source as plain text · Download source and sample files

How it works

Measure regular tracked working-tree files and report those above a selected size.
Arguments are explicit and expected input errors produce a message with a nonzero exit code.
Results reflect your selected local data or the specific endpoint you choose; the example illustrates the result shape.

Make it your own

Adapt the task

Lower --minimum-mib to inspect smaller files; historical Git objects are not measured.

Adjust presentation

Edit final print statements or json.dumps indentation to adjust the report layout. Keep input validation and exclusive-create file modes intact.

Change one setting at a time, run it again on sample data, and compare the output. The customization guide walks through this process.

If something goes wrong

An input or dependency is unavailable.

Git must be installed on PATH. --repo must be an existing non-bare repository.

Actual results differ from the example.

Inputs and system state determine values. Review each finding in context; a report is not proof of system health or a complete security assessment.

Reference & next steps

Git git-ls-files documentation ↗

These official references explain the underlying tools. The Scriptage example and guide are original instructional content. See verification notes for what has been checked and the limits of those checks.

Copies a template for your own notes. It does not send anything.