The CLI starts cleanup automatically, and its collector can recursively delete stale user files under its configured roots. The README documents the behavior and safety filters, so this is a warning-level destructive-action risk rather than evidence of malware.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Running a `wb` command starts GC automatically, at most once per daily local or hourly CI interval.
Impact
Stale files or workspaces can be lost without an explicit `wb gc` request; the documented filters and directory protections reduce the risk.
Mechanism
GC removes selected stale temporary entries, worktrees, build artifacts, and caches under its configured roots.
Evidence
bin/index.jsdist/index.jsdist/gc-tj8rtIiF.jsREADME.md$GHQ_ROOT/**/.tmp$GHQ_ROOT/**/node_modules$GHQ_ROOT/**/CACHEDIR.TAG$RUNNER_WORKSPACE sibling workspaces~/.cache/wb/gc.log