Large binary file committed
Part of Dependencies & Hygiene, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
Files over 5MB were found committed directly, which bloats repo size; consider Git LFS or external storage.
Why it matters
Git keeps every version of every file forever, so a 5MB+ binary makes each clone and CI checkout download it (and every past revision of it) permanently, even after you delete the file. Repos with committed binaries slowly grow until clones take minutes and shallow-clone tricks become mandatory. Large assets belong in Git LFS, object storage, or release artifacts, with only a pointer in the repo.
How to fix it
For assets that must live alongside the code (design files, model weights, fixtures), set up Git LFS: git lfs install, git lfs track "*.psd" (or the relevant extension), commit the .gitattributes, then re-add the files. For build outputs or downloadable data, remove them from the repo entirely and fetch them at build time from R2/S3 or a release URL instead. Note that already-committed copies stay in history until you rewrite it with git filter-repo, which is only worth doing on repos where clone size actually hurts.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo