Files
poli0981andClaude Opus 5.5 ccae96dbeb chore: move to poli0981org — self-contained CI, Qodana, an npm licence gate, this week's dependencies (#119)
The repository now lives in the poli0981org organization, and this makes it at home there.

- main was red since 2026-11-18: RUSTSEC-2026-0543 (chrono), in Cargo.lock only through serde_with's weak features and compiled into nothing; ignored with its reason and exit condition.
- Supersedes #113–#118 (Rust 1.100.0, rusqlite 0.42.0, Tauri 2.12.6, code-health pins, actions, npm) plus jsdom 31.0.1; minimatch 11 closes GHSA-g3hv-75wg-m249. rfd 0.18 (#112) is held again until tauri-plugin-dialog moves.
- Dependabot's tauri groups never worked (it picks the most specific group); exclude-patterns on the catch-alls fix it.
- CI is self-contained: no workflow calls poli0981/.github; every action is pinned by commit; notify.yml vendors the Discord notifier.
- npm licences: scripts/check-licenses.mjs, deny.toml's allowlist for the npm half. Required, with cargo deny and tauri lockstep — eight required checks.
- Qodana in two parts (Rust, TS/JS), full scans, a triaged Rust baseline, fail on anything new. The Rust container needed its toolchain and CARGO_HOME pointed somewhere writable before it analysed anything.
- SonarQube Cloud analyses into poli0981org_pipdock; every npm ci runs with --ignore-scripts (S6505).
- Every repository URL points at the organization. README's attestation command for 1.4.0/1.5.0 had stopped working; it now says --owner poli0981 --signer-repo poli0981/pipdock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 21:50:41 +07:00

33 lines
1.5 KiB
Markdown

# Security Policy
## Supported versions
The latest release gets fixes. The previous minor gets security-only patches for 90 days. There is
no update channel — PipDock does not update itself, so a fix reaches you when you download the new
build from [Releases](https://github.com/poli0981org/pipdock/releases).
## Reporting a vulnerability
**Do not open a public issue.** Use either:
- [GitHub Security Advisories](https://github.com/poli0981org/pipdock/security/advisories/new) — preferred
- `code@poli0981.dev`
Target acknowledgment is 7 days. Coordinated disclosure is preferred; tell us if you have a
disclosure deadline and we will work to it.
Useful in a report: the PipDock version (it is on the **About** tab), the Windows version, the
engine (pip or uv) and its version, and the smallest sequence of steps that reproduces the issue.
## What is in scope
PipDock runs subprocesses against Python interpreters you point it at, so the interesting surface is
where untrusted input reaches a command line, a file path, or a URL handed to your browser.
[`docs/SECURITY.md`](../docs/SECURITY.md) is the full threat model — §2 (argv arrays, never a shell),
§3 (PEP 668), §4 (network and the opener allowlist) and §7 (supply chain) are the sections most
reports land in.
Out of scope: vulnerabilities in the packages PipDock installs on your behalf — report those to the
package's own maintainers — and in pip, uv, deptry, vulture or ruff, which PipDock invokes but does
not distribute.