sohanmanju

Fair point, yeet doesn't really decide what's safe. It just scans a hardcoded list of known cache locations and lets you pick what to delete. The assumption is that these are "caches" that can be regenerated, but you're right that some are more painful than others. For Docker specifically, we include paths like /var/lib/docker which is pretty aggressive, that's images, build cache, and volumes. Probably shouldn't be in there since `docker system prune handles` that way better. Good feedback, will tighten up what we scan for