Files
poli0981andClaude Opus 5 47b9bc9039 docs: the Security tab's spec and legal debt, including two claims that were false
SECURITY §6 has said since it was written that pip-audit "runs **from the tools venv**".
The code has refused that since P2, with three tests enforcing the refusal, because
`pip-audit`'s closure contains `msgpack` — no universal wheel, so a new CPython would
hard-fail the whole sync under `--only-binary=:all:` and take Code Health down with a
feature it does not use. §6 now describes the venv that exists.

**And neither §6 nor PRD P1-1 could have been implemented as written.** Both promised a
severity — §6 as "(CVE/GHSA id, severity, fixed-in)", the PRD as "severity-sorted" —
against a field pip-audit has never had under either vulnerability service. Running the
pinned 2.10.1 is what settled it: a finding carries `id`, `fix_versions`, `aliases` and
`description`, full stop. Both are corrected to the order that ships, which is package →
fixable → id, and both now say why a derived severity would be worse than none.

`osv.dev` joins the opener allowlist, which ROADMAP has flagged as owed since 1.1.0 —
without it every advisory link rejects and nothing opens, which is the silence SECURITY
§4 exists to name. The description records what makes this entry different from
`docs.astral.sh`: `PdHealthReport` hands over ruff's own `finding.url` verbatim, while
`audit::advisory_url` **builds** the URL from an id checked against a whitelist that
cannot contain a slash, colon, question mark, hash or percent. The tool chooses the id,
never the destination.

The three legal documents that said pip-audit is "not invoked in version 1.0" now say
what it does, and DISCLAIMER §4's forward-looking sentence is replaced by one about a
feature that exists: findings come from **PyPI's** advisory data, an advisory database
is a record of what has been reported rather than a guarantee, and PipDock assigns no
severity because pip-audit publishes none. **This re-shows the consent gate once** for
every existing user — the mechanism working, not a regression.

Also: UI-SPEC §4 gains the screen it has assumed since §3's diagram, §5 its click budget
counted in the running app, and §6's off-list inventory said *four* while naming five —
now six, plus the three from 1.1.0 it never named at all. CLI-SPEC §3 documents
`pipdock audit` and drops `doctor`'s promise of an audit summary it has never printed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 10:55:11 +07:00

3.5 KiB
Raw Permalink Blame History

PipDock — Disclaimer

Version 1.1 · Effective 2026-08-14 · Governing language: English.

1. Modifying environments carries inherent risk

PipDock installs, upgrades, and removes Python packages. Even with previews, dependency resolution, snapshots, and post-checks, any change to an environment can break projects that depend on it — including in ways no tool can predict (runtime behavior changes between package versions, compiled-extension ABI issues, packages with incorrect metadata). Use the preview step, keep snapshots, and test your projects after significant updates. Do not run bulk updates on environments backing production systems without your own backups and change process.

2. Forced operations are at your own risk

The "Force latest" and forced-uninstall options exist for expert use. When you choose them, PipDock shows which requirements will be violated; proceeding knowingly puts the environment into a state its own metadata declares broken. The resulting behavior of affected packages is undefined.

3. System Python

PipDock blocks modification of externally-managed (PEP 668) Python installations by default. If you enable the override, you accept that modifying an OS-managed or vendor-managed Python can damage tooling on your system beyond Python projects.

4. Information accuracy

Package metadata, latest-version information and code-health reports are derived from third-party sources (PyPI, and deptry/vulture/ruff output) and from heuristics such as reverse-dependency analysis. They may be incomplete, outdated, or wrong — for example, dead-code detection produces false positives on dynamically referenced code, and deptry reports a module name rather than the distribution that provides it. Review before acting; PipDock's reports are assistance, not authority. The Security tab reports known advisories against your installed packages. Those come from PyPI's advisory data, by way of pip-audit, and are covered by this paragraph too: an advisory database is a record of what has been reported, not a guarantee that a package is safe or that an absence of findings means there is nothing to find. Each finding links to its entry on osv.dev so you can read the original. PipDock assigns no severity and no risk score, because pip-audit publishes none.

5. Not professional advice; no affiliation

Nothing in PipDock constitutes professional, security, or legal advice. PipDock is an independent project, not affiliated with or endorsed by the Python Software Foundation (Python, pip, PyPI), Astral (uv, ruff), or the authors of deptry, vulture, pip-audit, or any package it manages.

6. Warranty and liability

The no-warranty and limitation-of-liability terms of the GPL-3.0 (§15–16), restated in the EULA, apply to all of the above.


Tóm tắt Tiếng Việt (tham khảo)

Mọi thay đổi lên môi trường Python đều có rủi ro làm hỏng dự án phụ thuộc vào nó, kể cả khi đã xem trước và có snapshot — hãy tự sao lưu và kiểm thử sau khi cập nhật lớn. Tùy chọn "Ép bản mới nhất" và gỡ cưỡng bức đặt môi trường vào trạng thái mà chính metadata của nó tuyên bố là hỏng — bạn tự chịu rủi ro. Thông tin phiên bản, lỗ hổng, dead code đến từ nguồn bên thứ ba và có thể sai — hãy xem xét trước khi hành động. PipDock độc lập, không liên kết với PSF hay Astral. Điều khoản miễn trừ bảo hành theo GPL-3.0 §15–16 áp dụng.