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>
23 lines
1022 B
Plaintext
23 lines
1022 B
Plaintext
# Code Health tools — CODE-HEALTH-SPEC §2.
|
|
#
|
|
# These are installed into PipDock's own isolated environment at
|
|
# %LOCALAPPDATA%\PipDock\data\tools\.venv, NEVER into the user's environment. Exact `==` pins are
|
|
# resolved at PipDock release time; there are no floating versions at runtime, so a report is
|
|
# reproducible for a given PipDock build. Their dependencies are pinned too, by
|
|
# tools-constraints.txt beside this file — regenerate it whenever a pin here moves (the command is
|
|
# in its header).
|
|
#
|
|
# Dependabot bumps these in their own group (see .github/dependabot.yml) so a tool upgrade is
|
|
# never bundled with application dependencies — a ruff minor can change findings across every
|
|
# user's report, and that deserves its own review.
|
|
#
|
|
# Versions verified against PyPI 2026-11-04.
|
|
|
|
deptry==0.25.1
|
|
vulture==2.16
|
|
ruff==0.17.5
|
|
|
|
# The Security tab (PRD P1-1, shipped in 1.2.0). Installed into its own venv, not Code Health's
|
|
# (health::AUDIT_TOOLS), so a bump here never re-syncs the other one.
|
|
pip-audit==2.10.1
|