SiftMac
Features · Updated 21 November 2026

Developer files: what SiftMac clears, and how it knows it comes back

By Mohit Nippanikar, who makes SiftMac

The short answer
On this page
  1. How SiftMac finds them
  2. Why it waits for stale projects
  3. What it doesn’t touch
  4. Questions

1. How SiftMac finds them

SiftMac walks the visible folders in your home folder, up to 12 levels deep, skipping Library, Applications, Pictures, Music, Movies and Public. A folder holding .git, package.json, Cargo.toml, Package.swift, Podfile, pyproject.toml, build.gradle, pubspec.yaml or requirements.txt marks a project. In a monorepo the outermost project counts, so every package in it shares the repository’s activity. Toolchains that are git checkouts, like the Flutter SDK, are left alone.

FolderListed when this is next to itComes back with
node_modulespackage.jsonnpm install, or yarn, pnpm or bun
.next, .nuxt, .svelte-kit, .parcel-cache, .turbo, .angularpackage.jsonthe next build or dev run
targetCargo.tomlthe next Rust build
.buildPackage.swiftthe next swift build
PodsPodfilepod install
build, .gradlebuild.gradle or settings.gradle (or their .kts versions)the next Gradle build
build, .dart_toolpubspec.yamlthe next Flutter build
a Python environment: any folder with pyvenv.cfgrequirements*.txt, pyproject.toml, Pipfile, setup.py, environment.yml, uv.lock or poetry.lockpip install or uv sync

A project counts as untouched when none of its own files has changed for 3 months (1 or 6 if you change it in Settings › Developer files). Build folders don’t count towards that, and neither do folder dates, which change when Finder merely writes a .DS_Store. Git’s index and HEAD do, so a commit or a checkout marks a project as active.

Xcode

Docker, if you turn it on

With Include Docker on in Settings, SiftMac asks docker system df what Docker could give back, and lists unused images, build cache and stopped containers. They’re freed with Docker’s own commands, docker image prune --all --force, docker builder prune --all --force and docker container prune --force, which the panel on the right shows before you clean. Images and build cache come back with your next pull or build; stopped containers are marked You decide, since anything written inside them, outside a volume, goes with them. Volumes are never touched.

Package caches in ~/Library/Caches, such as Homebrew’s, pip’s, uv’s, Yarn’s, pnpm’s, bun’s, CocoaPods’, Swift packages’, Go’s build cache, JetBrains’ and Playwright’s browsers, are listed with the other app caches, marked Rebuilds.

2. Why it waits for stale projects

On a developer’s Mac, many of the biggest folders are ones that come back: every project carries its own node_modules or virtual environment, every Xcode project its DerivedData, and old simulators and device symbols stay behind after you’ve moved on. Clearing them costs nothing but time, the next time you need them.

That cost is why SiftMac only lists projects you’ve left alone for months: clearing the build folder of today’s project would just make your next build slow. Requiring the recipe file next to each folder means nothing is listed that your usual install or build can’t make again. And checking for running programs means a server or script running from inside an environment keeps it.

3. What it doesn’t touch

Questions

Will deleting node_modules break my project?

No. Running npm install (or yarn, pnpm or bun) in the project brings it back from package.json. SiftMac only lists a node_modules folder when that file sits next to it and the project hasn’t changed for 3 months.

Why isn’t my project’s build folder listed?

The project changed recently, the file that recreates the folder isn’t next to it, a program is running from inside it, or the project lives somewhere SiftMac doesn’t look, like Library or outside your home folder.

Does SiftMac delete Docker volumes?

Never. With Include Docker on, it lists unused images, build cache and stopped containers and frees them with Docker’s own prune commands. Volumes hold databases and other data, so they’re left alone.

How does SiftMac remove a simulator?

With xcrun simctl delete and the simulator’s ID, the same way Xcode does it. You can add it again in Xcode under Devices and Simulators; the apps and data on it go with it.

How SiftMac handles it. Developer files lists stale build folders, Python environments, Xcode data and, if you turn it on, Docker’s unused images and build cache, each with the project it belongs to and how it comes back. None is ticked until you tick it, and what you remove is deleted, since your next install or build makes it again.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works