`audit::run` syncs nothing and freezes nothing: it takes the freeze document and the audit venv's directory, spawns pip-audit over the SP-4 argv, and returns a report. The freeze is the caller's for the reason `UpdateFlow::start` takes pins rather than a `&Store` — an engine here would mean settings, which means the store, whose guard cannot be held across an await at a command boundary. It also keeps the module testable without a subprocess. A failure does not propagate. It lands in `AuditReport.problems` and the report comes back anyway, so the Security tab renders an error row and an honest zero rather than a blank screen — the shape `PdHealthReport` proved and `PD-HLT-003`'s partial report depends on. `packages` is deliberately separate from `advisories.len()`, because "audited 145 and found nothing" and "audited nothing" are different answers and P4 already shipped the version of that lie once. **The watchdog was wrong, and only running it said so.** Written against Code Health's `TOOL_TIMEOUT`, the first real run hit 120 s and reported `PD-HLT-003` for a tool that was working. Measured by hand afterwards: | Run | Wall clock | |---|---| | cold cache, one package | 68 s | | warm cache, one package | 18.6 s | | warm cache, twelve packages | 20.0 s | Twelve packages cost 1.4 s more than one, so what dominates is a one-off advisory- database fetch, not the package count — a 352-package environment is not the risk, a cold fetch on a slow link is. 120 s is a linter's budget for walking a source tree and was simply the wrong unit. `AUDIT_TIMEOUT` is ten minutes, matching `exec::DEFAULT_TIMEOUT`, which is what every other network-bound subprocess gets. Three tests, plus one that is `#[ignore]`d the way `search_latency` is and takes `PIPDOCK_AUDIT_DIR`. That one was **run**, against a real synced venv: 16.8 s, no problems, and the same eight advisories live that the committed fixture carries — so it checks the parser against the tool rather than only against a capture. The missing- tool case is asserted to produce a *report* carrying `PD-HLT-001`, never an `Err`. Deliberately not done: cancellation. P4 deferred it for Code Health on a measurement of 1.3 s; this measures 18-68 s, which is a different answer to the same question, so it wants deciding rather than inheriting — and wiring the token alone would map a cancel to `PD-INT-001` and render "PipDock hit an internal error", which P4 also recorded. It belongs with the bridge command, where there is a session to cancel. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
PipDock
A friendly dock for your Python environments. Inspect, install, update, and clean up Python packages in bulk — through a keyboard-first GUI or a scriptable CLI — without ever hand-typing another pip install incantation or guessing why an upgrade broke your project.
Repo:
poli0981/pipdock· License: GPL-3.0-only · Platform: Windows 10/11 · Contact: contact@poli0981.dev · other channels
Why PipDock
pip is powerful but unforgiving: it does not preview what an upgrade will change, pip uninstall removes packages that other packages still need without a word of warning, and a failed bulk update leaves you guessing what state your environment is in. PipDock wraps the official resolvers (pip or uv — your choice) with:
- Preview before touch — every install/update runs a dry-run resolve first and shows you exactly what will change.
- Three-way conflict handling — when the latest version of a package would break another, choose compatible version (safe default), skip, or force latest with a clear "this will break X" warning.
- Snapshots & rollback — a
pip freezesnapshot is taken before every batch operation; one click restores it. - Reverse-dependency guard — uninstalling a package that others depend on triggers a warning listing exactly what would break.
- Skip-and-continue execution — one failed package never aborts the batch; you get a final report: "13 successful, 2 failed" with per-package reasons.
- Never touches itself — PipDock is a standalone binary that lives outside every environment it manages, so it can never break itself mid-update.
Screenshots
Features
| Area | What you get |
|---|---|
| Environments | Auto-discovery of venvs / uv venvs / system Pythons (PEP 514 + py launcher), manual add, PEP 668 guard |
| Installed | Full package list per env; up-to-date packages dimmed, outdated badged |
| Updates | Bulk update with group dry-run resolve, held-back explanations, 3-way conflict choices |
| Search & Install | Instant fuzzy search over a locally cached PyPI name index (PEP 691), metadata on demand, install queue |
| Uninstall | Bulk uninstall with reverse-dependency warnings |
| Pins | Exclude packages from bulk updates, with a reason. The Pins screen suggests packages a lot of your others depend on, and the threshold is configurable |
| Snapshots | Automatic pre-batch snapshots, diff view, one-click rollback |
| Engine | pip or uv, selectable in Settings (uv auto-detected on first run) |
| Code Health | deptry + vulture + ruff against a project folder — unused deps, dead code, style — run from PipDock's own isolated tools env |
| pip upkeep | Check & update pip itself per environment |
| CLI | pipdock — full parity for core operations, JSON output, CI-friendly exit codes |
| Requirements | Export an environment as requirements.txt; import one and preview what it would install, with every line it will not use reported by number |
| Disk usage | See and clear what PipDock has written — snapshots and the Code Health tools environment |
| Keyboard | Ctrl+K command palette, Ctrl+1–Ctrl+9 tabs, full keyboard traversal |
| i18n | English + Tiếng Việt |
| Privacy | No telemetry. PyPI is the only host PipDock connects to. It does not check for updates, so it never calls home — GitHub and the ruff docs are only ever handed to your browser as a link you clicked |
Install
Download the installer (NSIS .exe or .msi) from GitHub Releases.
PipDock does not update itself — grab a new build from the same page when you want one. That is deliberate: a self-updater is a standing remote-code-execution path into a tool that already runs subprocesses against your interpreters, and it is not worth the convenience (see docs/SECURITY.md §5).
Windows SmartScreen may warn on first run because the binaries are not EV-code-signed. Every release publishes
SHA256SUMS.txt; verify your download against it before running:(Get-FileHash .\PipDock_1.0.0_x64-setup.exe -Algorithm SHA256).Hash.ToLower()Compare that against the matching line in
SHA256SUMS.txt. If they differ, do not run the file.
Quick start
GUI: launch PipDock → accept the first-run legal gate → pick an environment (auto-discovered or Browse…) → the Updates tab shows what's outdated → Select all → Update → review the preview → Confirm. Four clicks.
CLI: the installer puts pipdock.exe next to the GUI, in %LOCALAPPDATA%\PipDock\.
PipDock does not edit your PATH; add that folder yourself if you want to type pipdock
from anywhere:
$dir = "$env:LOCALAPPDATA\PipDock"
[Environment]::SetEnvironmentVariable('Path', "$([Environment]::GetEnvironmentVariable('Path','User'));$dir", 'User')
pipdock env list
pipdock update --all --env C:\proj\.venv --strategy compatible --yes
pipdock doctor
pipdock snapshot rollback latest
Documentation
Using PipDock? The wiki is the user-facing set — Getting Started, Troubleshooting and an FAQ that explains the design decisions rather than just stating them. Everything below is for reading the code.
| Doc | Purpose |
|---|---|
| docs/PRD.md | Product goals, personas, feature matrix P0–P2, non-goals |
| docs/ARCHITECTURE.md | Crate layout, Engine trait, IPC surface, storage |
| docs/DATA-FLOW.md | State machines for update / install / uninstall, engine command mapping |
| docs/UI-SPEC.md | Terminal-tech design system, screens, click budgets |
| docs/CLI-GUIDE.md | Start here for the CLI — what to type, in the order you need it |
| docs/CLI-SPEC.md | The CLI contract: every flag, exit code and JSON shape |
| docs/AI-DISCLOSURE.md | Which AI model helped build this, what it did, and how it was reviewed |
| docs/CODE-HEALTH-SPEC.md | deptry / vulture / ruff integration |
| docs/ERROR-CATALOG.md | Error codes, stderr detection patterns, user guidance |
| docs/SECURITY.md | Threat model, PEP 668 policy, supply-chain hygiene |
| docs/TESTING.md | Test strategy incl. disposable-venv integration tests |
| docs/RELEASE-CI.md | CI callers into poli0981/.github, release pipeline |
| docs/I18N.md | EN/VI localization rules |
| docs/ROADMAP.md | Spike week, milestones, exit criteria |
| legal/ | EULA, Disclaimer, Privacy Policy, Third-Party Notices (linked by the in-app legal gate) |
How this was built
PipDock was written with substantial help from an AI coding assistant — Claude Opus 5, made by Anthropic, through Claude Code — under human review. It wrote source code, tests, debugging work and the Vietnamese translation. Every change reached main through a pull request the maintainer read and merged, main is protected and cannot be bypassed, and the built application was driven by hand on three machines before 1.0.0 shipped.
That review mattered: thirty-five defects reached or nearly reached main, and not one was caught by the test suite that was green at the time. They were found by running the thing.
Copyright and the GPL-3.0-only licence are unchanged. The full statement — model, vendor, what was and was not delegated, and how to verify any of it from git log — is in docs/AI-DISCLOSURE.md.
License
Copyright © 2026 Kokone (poli0981). PipDock is free software under GPL-3.0-only — see LICENSE. The legal documents in legal/ are committed publicly so the in-app legal gate and the About tab can link to them on GitHub.
PipDock is an independent project. It is not affiliated with or endorsed by the Python Software Foundation (Python, pip, PyPI) or Astral (uv, ruff).
Tiếng Việt (tóm tắt)
PipDock là ứng dụng Windows (GUI + CLI) giúp kiểm tra, cài đặt, cập nhật và gỡ hàng loạt gói thư viện Python một cách an toàn: luôn chạy dry-run xem trước thay đổi, xử lý xung đột phiên bản với 3 lựa chọn rõ ràng, tự chụp snapshot trước mỗi lần chạy để rollback một chạm, cảnh báo khi gỡ gói mà gói khác đang phụ thuộc, và tổng kết "13 thành công, 2 thất bại" kèm lý do từng gói. Hỗ trợ engine pip hoặc uv (chọn trong Settings), tìm gói tức thì nhờ cache chỉ mục PyPI, kèm module Code Health (deptry/vulture/ruff) để dọn dependency thừa và dead code. Không thu thập dữ liệu. Giấy phép GPL-3.0.







