Files
pipdock/.cargo/audit.toml
T
poli0981andClaude Opus 5.5 57ed5756c4 ci: unblock cargo audit on zbus 5, redact pip 26's finished progress bar, hold rfd at 0.16 (#84)
Three things have kept CI red since 2026-10-18; none touches the shipped program.

- **cargo audit** (required on every PR, and the daily Security scan) fails on
  RUSTSEC-2026-0370/0371/0372: zvariant, zbus_names and zvariant_derive were folded into
  zbus 6 on 2026-10-16 and marked unmaintained the same day. zbus reaches the tree only
  through tauri-plugin-opener and tauri-plugin-single-instance, for D-Bus on Linux;
  `cargo tree -i zbus --target x86_64-pc-windows-msvc` prints nothing. Every release of both
  plugins, the 3.0 alphas included, still requires zbus ^5.9, so there is no update to take.
  Ignored individually in .cargo/audit.toml with that reason and a removal condition.
  `cargo audit --deny warnings` is clean locally.

- **The Monday fixture-drift job** failed on pip/build-backend-failure/stdout.txt: pip 26
  ends a finished bar with the bare elapsed time, not `eta 0:00:00`, so `_is_progress` let
  the transfer rate through (15.1 MB/s committed, 75.1 MB/s on the next runner). The rule now
  keys on a trailing time token. Old vs new over every committed fixture line: exactly this
  one line changes verdict. The fixture is restored to `<PROGRESS>` in binary mode, 7 CRLF
  before and after; its blob is again b349d1f, the pre-pip-26 bytes.

- **rfd**: Dependabot's 0.17.2 bump (#83) adds a second rfd to the binary, because
  tauri-plugin-dialog 2.8.3 requires ^0.16 and src-tauri depends on rfd only because the
  plugin already compiles it. dependabot.yml now ignores rfd >= 0.17 until the plugin moves.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 06:37:19 +00:00

57 lines
3.4 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
# --- 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
]