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>
3.9 KiB
PipDock — End User License Agreement (Terms of Use)
Version 1.1 · Effective 2026-08-14 · Governing language: English (bản Tiếng Việt tóm tắt ở cuối chỉ mang tính tham khảo).
1. License
PipDock is free software, licensed under the GNU General Public License, version 3 (GPL-3.0). The full license text is available in the repository (LICENSE) and at https://www.gnu.org/licenses/gpl-3.0.html. Your rights to use, study, modify, and redistribute PipDock come from the GPL-3.0, and nothing in this document adds restrictions to, or removes rights granted by, that license (per GPL-3.0 §7, any such added restriction would be void). This document only (a) restates the GPL's warranty and liability terms as they apply to you as a user, and (b) records acknowledgments the application asks for at first run.
2. What PipDock does (acknowledgment)
PipDock installs, upgrades, and removes packages in Python environments at your direction, by invoking third-party package managers (pip, uv) and analysis tools (deptry, vulture, ruff, and pip-audit for the Security tab). These operations modify software environments on your computer and can affect the behavior of your projects. You are responsible for reviewing each preview and confirmation the application presents before applying changes.
3. No warranty
As stated in GPL-3.0 §15: THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. THE PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
4. Limitation of liability
As stated in GPL-3.0 §16: IN NO EVENT, UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, WILL ANY COPYRIGHT HOLDER BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS).
5. Third-party software and services
Packages you choose to install come from the Python Package Index or other indexes you have configured; they are published by third parties under their own licenses, and installing them may execute their build code. PipDock does not review, endorse, or warrant any third-party package. Third-party components bundled with or invoked by PipDock are listed in THIRD-PARTY-NOTICES.md.
6. Trademarks
"Python", "pip", and "PyPI" are trademarks of the Python Software Foundation. "uv" and "ruff" are projects of Astral. PipDock is an independent project and is not affiliated with, sponsored, or endorsed by these organizations.
7. Acceptance record
The application records your acceptance of this document (together with the Disclaimer and Privacy Policy) locally on your device, keyed to the documents' version hash. If these documents change materially, the application will ask again. You can read them at any time from the About tab, which also shows the hash your acceptance was recorded against.
Tóm tắt Tiếng Việt (tham khảo)
PipDock là phần mềm tự do theo giấy phép GPL-3.0; tài liệu này không thêm bất kỳ hạn chế nào ngoài GPL. Ứng dụng thay đổi các môi trường Python theo lệnh của bạn thông qua pip/uv; phần mềm được cung cấp "nguyên trạng", không bảo hành, và các tác giả không chịu trách nhiệm cho thiệt hại phát sinh (theo GPL-3.0 §15–16). Gói bên thứ ba do bạn chọn cài thuộc trách nhiệm của nhà phát hành gói đó. Việc chấp thuận được lưu cục bộ trên máy bạn.