Brave is Chromium-based and already has a brave-cache target, but it also accumulates a distinct Crashpad report folder and a Country Logs folder under Application Support that grow over time and are safe to clear:
~/Library/Application Support/BraveSoftware/Brave-Browser/Crashpad
This is a small extension to the existing brave-cache target (or a sibling target), scoped to the crashpad/reports subfolders only. The parent BraveSoftware/Brave-Browser holds real profile data and must never be deletable as a whole.
File: CleanerEngine/Sources/CleanerEngine/CleanupTargetRegistry.swift (see the brave-cache entry)
Level: Safe
- Add the Crashpad subfolder to the existing path templates, or add a
brave-crashpad target that reuses the App Cache category.
- Mirror the blocking assertions already in
AppCacheTargetTests.swift so the parent profile folder stays protected.
Acceptance: swift test passes, the new path validates against SafetyValidator, and the Brave profile root still does not.
Brave is Chromium-based and already has a
brave-cachetarget, but it also accumulates a distinct Crashpad report folder and a Country Logs folder under Application Support that grow over time and are safe to clear:This is a small extension to the existing
brave-cachetarget (or a sibling target), scoped to the crashpad/reports subfolders only. The parentBraveSoftware/Brave-Browserholds real profile data and must never be deletable as a whole.File:
CleanerEngine/Sources/CleanerEngine/CleanupTargetRegistry.swift(see thebrave-cacheentry)Level: Safe
brave-crashpadtarget that reuses the App Cache category.AppCacheTargetTests.swiftso the parent profile folder stays protected.Acceptance:
swift testpasses, the new path validates againstSafetyValidator, and the Brave profile root still does not.