scan,{' '}
+ analyze, and{' '}
+ explain never delete
+ anything. When you do run clean,
+ it moves items to your system trash — and anything ≥ 1 GiB requires typing{' '}
+ DELETE. See the Safety Net
+ above for the full picture.
+
+ ),
+ },
+ {
+ q: 'Can I control which folders it looks at?',
+ a: (
+ <>
+ Yes — through config, not a CLI flag. Add a project{' '}
+ .devklean.toml (found by
+ walking up from your current directory) or a global{' '}
+ ~/.config/devklean/config.toml,
+ and set exclude = [...] or{' '}
+ an [ignore] section with{' '}
+ paths /{' '}
+ directories.
+
+ ),
+ },
+ {
+ q: 'How do I install it?',
+ a: (
+ <>
+ devklean is on PyPI — pure Python, no compiled binary.{' '}
+ pipx install devklean is
+ recommended (isolated), or{' '}
+ pip install devklean into the
+ current environment.
+
+ ),
+ },
+ {
+ q: 'Does it work on Windows?',
+ a: (
+ <>
+ Yes. Every core command — scan,{' '}
+ clean,{' '}
+ analyze, and the rest — works
+ on Linux, macOS, and Windows. The only exception is interactive mode (
+ -i), which is Linux/macOS only.
+
+ ),
+ },
+];
+
+export default function App() {
+ return (
+ {faq.a}
++ Compatibility Layer +
+
+ Three commands that only ever read your disk. Each one tells you more about what’s there — so the one
+ command that does delete, clean, is never a guess.
+
{feature.description}
+{feature.sampleOutput}
+
+ The only command that removes anything is devklean clean — and even
+ that moves files to your system trash, never a hard delete.
+
analyze, explain, and{' '}
+ --compress are here
+
+ + A CLI that finds regenerable build artifacts from Node.js, Python, and Next.js, tells you exactly what each + one is, and moves them to your system trash — never a hard delete. +
+ + {/* CTAs and Copy Segment */} ++ The same workspace, seen through three read-only commands. Pick one — nothing here deletes anything. +
+portfolio (−10). Every
+ verdict comes from a fixed registry — never an inference.
+ + When you compress before trashing, devklean removes the original last. If anything goes wrong + before that, your directory is left exactly where it was. +
+{body}
++ Estimate your local project counts below. Build artifacts add up fast — and every one of them is + regenerable from source. +
+node_modules
+
+ .next
+
+ .venv / __pycache__
+
+ + Of regenerable build artifacts — dependency trees, virtual environments, and compiled output — sitting + on your drive. +
+ + {/* Truthful facts about how devklean handles it */} +rm -rf.
+ DELETE.
+ scan and analyze never delete a thing.
+
+ Run devklean analyze --verbose to see the workspace-health
+ score and the exact formula behind it — no deletions, just the report.
+
+ {beat.body} +
++ The risk and confidence scores are a hand-maintained, deterministic + registry — not a model call and not a heuristic, as stated outright in the tool’s own source. And + everything else shown on this page — commands, flags, sizes, the health formula — is{' '} + real tool output, not marketing copy. +
+