The report joins SCHEMA_TYPES; its seven sub-types do not, and do not need to — the bindings generator hoists every $defs entry into its own TS declaration, so DeptryIssue, VultureFinding, RuffFinding, RuffFindings, SourceLocation, ToolProblem, DeclaredSource and FixApplicability all arrive from one registration. Listing them would emit each twice. Skip-and-continue is the shape. PD-HLT-003 promises a "partial report shown", so a tool that fails lands in problems[] and the other two still report — the same rule plan::execute follows for a failed package, and the thing most likely to be built as a whole-run failure by accident. ToolProblem is deliberately PdError-shaped so the UI hands it to PdErrorRow rather than inventing a second error presentation. `ran` is what makes an empty tab readable: without it "no findings" and "never ran" are the same empty array. Two argv corrections found by reading `deptry --help` after asserting otherwise: --json-output takes a *location*, not a stream. `-` would have created a file literally named `-` in the CWD, which is the user's project — the exact §1 boundary the flag was chosen to respect. It now writes under the tools directory and is deleted on both paths. **deptry has no environment flag at all.** CODE-HEALTH-SPEC §3 says the env is "passed to deptry so 'installed vs declared vs imported' compares against reality"; deptry 0.25.1 ignores VIRTUAL_ENV and reads whatever its own interpreter can import. Verified by watching it report `click` — which exists only in the tools venv — as DEP003 transitive. Putting the tools venv on a user interpreter's PYTHONPATH does not help either: deptry's own deps come along. §2's isolation and §3's comparison are in conflict at this version. Kept all four codes rather than suppressing DEP003: deptry classifies an undeclared import as DEP003 *instead of* DEP001 when it can see the package, so --ignore DEP003 would turn a mislabelled finding into a missing one. The cost is bounded and named — the nine packages the tools venv holds — and both codes mean "you imported something you did not declare", which §6 already tells the user to fix the same way. A test pins the absence so a future deptry gaining the flag is noticed. Excludes are translated per tool, which is not cosmetic: deptry's are anchored regexes, so `.venv` unescaped also matches `avenv`; vulture takes one comma-separated glob list, not repeated flags. 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 · Platform: Windows 10/11 (v1) · Status: design phase
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.
Features (v1)
| 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; auto-suggest pinning heavily-depended-on packages |
| 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 |
| i18n | English + Tiếng Việt |
| Privacy | No telemetry. Network traffic goes only to PyPI (package data) and GitHub (app updates) |
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 binaries are not EV-code-signed. Verify the SHA-256 checksum published with each release.
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:
pipdock env list
pipdock update --all --env C:\proj\.venv --strategy compatible --yes
pipdock doctor
pipdock snapshot rollback latest
Documentation
| 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-SPEC.md | Commands, flags, exit codes, JSON contracts |
| 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) |
License
GPL-3.0. See LICENSE (add the standard GPL-3.0 text at repo creation). The legal documents in legal/ must be committed publicly so the in-app legal gate 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.