Safety labels
What Safe, Check first and Your files mean, and which items DevSweep selects for you.
Every item has one of three labels, shown with an icon and a word so you don’t have to rely on colour.
Safe
Data your tools recreate on their own: caches, build output, downloaded dependencies. Removing it costs time on the next build or install, never work.
Examples: Xcode DerivedData, Gradle and Yarn caches, node_modules of a project you haven’t opened in a month, Metro bundler caches, Docker build cache.
Safe items are selected for you.
Check first
Reasonable to remove, but you might still want it.
Examples:
- an Android emulator, or a simulator with apps installed on it
- a simulator runtime you still test on
- older Android build-tools or NDK versions (a project may pin one)
- Xcode archives, which you need to symbolicate a crash from that build
node_modulesof a project you touched this month- files left behind by an app you uninstalled
Not selected. Tick what you’re sure about.
Your files
Things only you can judge: large downloads, apps, Docker volumes that may hold a database.
Never selected. The confirm sheet warns when your selection includes any.
How project folders are judged
For each node_modules, Pods, build and similar folder, DevSweep checks when the project around it last changed. If that’s more than 30 days ago, the folder is Safe; otherwise Check first. You can change the 30 days in Settings.
DevSweep only lists a build folder when it can tell what made it (a Gradle file, an iOS Podfile, a Flutter pubspec.yaml), and only lists target next to a Cargo.toml. Generic folders named build or dist are left alone.