
Find and clean development dependencies, build artifacts, and caches
npkill is a Raycast extension that helps you find development dependencies, build artifacts, and caches. Review estimated sizes, project activity, and risk warnings with visual summaries, then clean the directories you choose.
This is an unofficial npkill integration for macOS. Scanning runs locally through the installed npkill CLI. No account, API key, background schedule, or filesystem analytics service is required.

Install the CLI yourself in a terminal:
npm install -g npkill@1
npkill --version
node --version
The extension uses the copy of npkill you install. It does not download or install packages.
~/Developer, or use Choose Directory. The filesystem root is rejected.node profile, or enter comma-separated profile names such as node,python,rust.command -v npkill in your terminal.Paths support spaces, Unicode, and ~ expansion. Setup is stored locally. Configure Scan changes the root, profiles, exclusions, executable, and custom configuration. Default Sort Order is an extension preference.
The executable's directory, Raycast's inherited PATH, Homebrew locations, ~/.volta/bin, and ~/.local/bin are searched for Node. With nvm, asdf, mise, or another version manager, use the installed executable's full path and make its Node runtime available on PATH. No login shell or user-supplied shell command is executed.
~/. The active scan root appears in the navigation title. Searching filters the current scan; use Configure Scan to scan another directory. The list shows paths relative to the selected root; full paths are available in details, tooltips, Finder, and Copy Path..npkillrc enables them. Cleaning them in the native command requires a second confirmation. AI cleanup uses one confirmation showing the exact paths, estimated sizes, and risk labels.⌘⌥S) preserves partial results. Refresh Scan starts a new scan and clears selection.Project activity is npkill's projectModificationTime: the newest eligible file it found in the parent project. The extension does not substitute directory modification time or infer activity independently. Sizes are estimates, not guaranteed recoverable disk space.
Artifact details include an SVG storage-share chart, a project-activity timeline, and a risk summary. Storage share compares the directory with measured results in the current scan, not your disk capacity; unknown sizes are excluded and partial scans are labeled. Cleanup reviews and reports show risk and outcome breakdowns. All graphics adapt to light and dark appearance, with the same information available as text.
All target definitions, project marker rules, default ignores, and risk analysis come from npkill. The extension does not maintain its own target catalog or filesystem scanner.
The CLI runs with the scan root as its working directory. npkill checks that directory for .npkillrc, then the home directory, unless Custom Configuration specifies a file. The selected root and profiles are passed explicitly and take precedence over config defaults. Custom profiles declared in .npkillrc can be entered by name.
Extra exclusions are comma-separated or newline-separated and are merged with config exclusions by npkill. Supported examples include work-in-progress, ./apps/active-project, absolute directory paths, and **/packages/keep. General glob patterns such as **/keep/** are unsupported by npkill 1.0.0 and produce a scan notice.
Upstream streaming output does not identify which profile matched a result. To change the ecosystem scope, use Configure Scan and change the profile names; the extension does not guess a result's profile from a common directory name.
See upstream's profile definitions and configuration documentation.
Review the exact paths, estimated sizes, and risk information before confirming Move to Trash. You can restore directories from Finder’s Trash until you empty it.

⌘↵) to mark results, or deselect with the same action.⌘⇧T) includes only selected results visible under the current search and filter. The header shows visible and total selected counts. Clear Selection removes all selections.
Some development artifacts contain local state that cannot be rebuilt. Stop processes using a directory and inspect it first. Identity checks detect changes observed between discovery and cleanup, but path-based Node and Raycast APIs cannot atomically lock an entire directory tree against a concurrent rename or write. This is not a security boundary against another process deliberately racing filesystem changes.
Mention @npkill in Raycast AI Chat, or open Ask Npkill. Example prompts:
Search Development Artifacts runs a fresh read-only scan using the same CLI adapter, saved root, profiles, exclusions, and sensitive-results setting as the native command. An explicitly supplied directory or profile list overrides those two settings for that search only. Executable paths, config files, and sensitive-result inclusion cannot be changed by the AI.
Search supports path text, minimum estimated size, minimum project inactivity, risk, sorting, and up to 100 returned results (30 by default). Scans stop after 20 seconds or 20,000 discovered candidates, then wait for the CLI to terminate. Reports distinguish incomplete discovery from a truncated result list and preserve unknown sizes, activity, and risk. They are snapshots, not a live monitor of a scan running in another view.
Check Npkill Setup checks CLI/Node compatibility and saved settings without scanning. When no directory has been saved or supplied, the search tool asks for one instead of assuming a root. Custom profiles and config contents are validated by npkill when scanning.
Move Artifacts to Trash performs cleanup directly from AI Chat. Search returns a scanId and exact candidate paths. When you request cleanup, Raycast shows the selected paths, estimated sizes, and risk labels for confirmation before moving them to Trash. The tool revalidates the original directory identities and reports each path as trashed, missing, or failed. It never permanently deletes files or empties Trash.
Scan snapshots are stored locally for up to 30 minutes of validity and can authorize one cleanup operation. Expired metadata is removed on later searches. Only returned paths from that scan can be selected; invented paths, overlapping directories, changed identities, and reused scan IDs are rejected. Search again before further cleanup. AI-returned estimates are never guaranteed reclaimed space.
Scanning itself remains local. When you invoke an AI tool, its returned paths, metadata, settings, and diagnostic messages are provided to your selected Raycast AI model. File contents are not returned. Use the native command if you want to keep those results outside AI conversations.
| Problem | What to do |
|---|---|
| CLI or Node not found | Install the requirements and set the full npkill executable path. Confirm that its Node runtime is available. |
| Unsupported version or output schema | Use a stable npkill 1.x release with schema 1. The adapter stops on malformed or incompatible stdout. |
| Profile or configuration error | Open View Scan Notices and correct the upstream configuration. |
| Permission denied | Review the affected path and macOS permissions. The extension never requests administrator privileges. |
| No results | Check the root, profiles, exclusions, and upstream marker rules. A .venv must contain pyvenv.cfg; an arbitrary directory named target is not necessarily a Rust artifact. |
| Directory changed or became a symlink | Refresh and review it again. The old discovery identity cannot authorize cleanup. |
| Move to Trash fails | Read the per-path cleanup report. The result is retained unless validation established it was already missing. |
| Scan canceled | Partial results remain. Refresh to start over. |
Find development dependencies, build artifacts, and caches using npkill profiles; review and clean selected directories.
~/. See the active scan root and reset filters when changing directories. Inspect directories in Finder or stop a scan and keep its partial results.