Files
pipdock/.cargo/audit.toml
T
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

66 lines
4.1 KiB
TOML

# cargo-audit configuration.
#
# SECURITY §7 gates every PR on `cargo audit`. That gate is about **vulnerabilities**, and it is
# left at its default: any RUSTSEC vulnerability fails the build, and nothing below weakens that.
#
# What is ignored here are *informational* advisories — "unmaintained" and "unsound" — on
# transitive crates PipDock cannot influence and, in most cases, never compiles. They are listed
# individually rather than switched off as a class, so a new one still fails CI and has to be
# looked at rather than silently absorbed.
#
# Review obligation: when Tauri drops GTK3, its plugins move to zbus 6, or a `unic-*` dependent
# moves on, delete the corresponding lines. A stale ignore is how a real advisory eventually gets
# waved through.
[advisories]
ignore = [
# --- Tauri's GTK3 stack (Linux only) -------------------------------------
# gtk-rs archived its GTK3 bindings. Tauri 2 pulls them for its Linux target; PipDock v1
# ships Windows only (PRD, ARCHITECTURE §10), so none of these are compiled into anything we
# release. They will disappear when Tauri's Linux backend moves to GTK4, and the macOS/Linux
# builds in P2-1 are the point at which this block must be re-examined rather than extended.
"RUSTSEC-2024-0411", # gdkwayland-sys — unmaintained
"RUSTSEC-2024-0412", # gdk — unmaintained
"RUSTSEC-2024-0413", # atk — unmaintained
"RUSTSEC-2024-0414", # gdkx11-sys — unmaintained
"RUSTSEC-2024-0415", # gtk — unmaintained
"RUSTSEC-2024-0416", # atk-sys — unmaintained
"RUSTSEC-2024-0417", # gdkx11 — unmaintained
"RUSTSEC-2024-0418", # gdk-sys — unmaintained
"RUSTSEC-2024-0419", # gtk3-macros — unmaintained
"RUSTSEC-2024-0420", # gtk-sys — unmaintained
"RUSTSEC-2024-0429", # glib — unsound (VariantStrIter::impl_get); same GTK3 stack
# A proc-macro, reached through glib-macros: the same stack, not a build dependency of
# PipDock's as this file used to say (`cargo tree -i proc-macro-error --target all`).
"RUSTSEC-2024-0370", # proc-macro-error — unmaintained
# --- zbus 5's D-Bus stack (Linux only) -----------------------------------
# zbus 6 (2026-10-16) folded these three crates into itself, and the advisories were filed the
# same day. zbus reaches the tree only through tauri-plugin-opener and
# tauri-plugin-single-instance, which use D-Bus on Linux alone: `cargo tree -i zbus --target
# x86_64-pc-windows-msvc` prints nothing. Every release of both plugins — 2.x and the 3.0
# alphas alike — still requires zbus ^5.9, so there is no update to take. Delete these lines
# when the plugins move to zbus 6, or at P2-1 with the GTK3 block above.
"RUSTSEC-2026-0370", # zvariant — unmaintained, merged into zbus 6
"RUSTSEC-2026-0371", # zbus_names — unmaintained, merged into zbus 6
"RUSTSEC-2026-0372", # zvariant_derive — unmaintained, merged into zbus 6
# --- chrono, listed and never compiled ----------------------------------
# Cargo.lock names chrono only because serde_with 3.24's `std` feature carries the weak
# features `chrono_0_4?/clock` and `chrono_0_4?/std`, and Cargo's lock resolution records an
# optional dependency that a weak feature mentions even when nothing enables it. serde_with
# comes in through tauri-utils; `cargo tree -i chrono --target all` prints nothing, so no
# target — the shipped Windows one included — compiles it. PipDock's own dates are jiff, the
# advisory's first recommendation. Delete this line when Cargo.lock stops listing chrono.
"RUSTSEC-2026-0543", # chrono — unmaintained
# --- unic-* Unicode tables ----------------------------------------------
# Superseded upstream but functionally frozen data tables, reached transitively. Nothing here
# parses untrusted input on PipDock's behalf.
"RUSTSEC-2025-0075", # unic-char-range — unmaintained
"RUSTSEC-2025-0080", # unic-common — unmaintained
"RUSTSEC-2025-0081", # unic-char-property — unmaintained
"RUSTSEC-2025-0098", # unic-ucd-version — unmaintained
"RUSTSEC-2025-0100", # unic-ucd-ident — unmaintained
]