- notify-ci-failure.yml lists its workflows by name. `workflows: ['*']` is not a wildcard to workflow_run: it matched nothing, so `main` was red from 2026-09-23 with no one told. - cargo audit runs a prebuilt cargo-audit (taiki-e/install-action, pinned by commit) with `--deny warnings`, replacing rustsec/audit-check@v2 - Node 20, a check-run write token, and on a pull request a failure only for "critical", which is how September's advisories passed every PR. .cargo/audit.toml's contract (a new informational advisory fails CI) is now what runs. - security-scan.yml: both audits daily against `main`, so an advisory against something already merged is reported the day it is published, not at the next PR. - cargo deny (licences, sources, bans) with deny.toml: the licence allowlist makes "every bundled licence is GPL-3.0-compatible" a test. The workspace declares `publish = false`, which it never had - and without which cargo-deny judged the app crates as published ones. - CodeQL analyses rust and actions as well as javascript-typescript. The comment saying CodeQL had no Rust support stopped being true in 2025. - ci-node.yml: Pages and id-token write move from the workflow to the one job that needs them (Sonar S8233); the audit installs with --ignore-scripts (S6505); a new `tauri lockstep` job fails when a Tauri crate and its npm package drift apart on Cargo.lock and package-lock.json. - release.yml: build (read-only token, no persisted credentials) and publish (attest + draft) are separate jobs; the tag must match all five version fields; SHA256SUMS.txt is LF, which `sha256sum -c` elsewhere needs; actions/attest-build-provenance attests the .exe and .msi; softprops/action-gh-release is pinned by commit; `workflow_dispatch` with `dry_run` builds any ref without attesting or drafting. - ci-integration.yml also runs for the CLI, exec, audit, release metadata, errors, store, index, Cargo.lock and rust-toolchain.toml - every one of which its end-to-end steps run through. - dependabot.yml: cooldowns, a group per ecosystem for Tauri packages and for actions and pip, TypeScript held below 6.1 (typescript-eslint's peer range), and the rust-toolchain ecosystem. A multi-ecosystem group would put both Tauri halves in one PR, but what it does to dependencies outside its patterns is undocumented; the lockstep job covers the gap instead. - Sonar: NOSONAR with reasons on the dev scripts' argv and PATH lookups; bundle-cli.mjs no longer claims to run from beforeBuildCommand. The dev CSP moves out of index.html into a Vite plugin that reads devCsp from tauri.conf.json, so a release build carries one policy, the strict one (S7039); checked in the dev server, where React Refresh's preamble still runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
45 lines
2.5 KiB
TOML
45 lines
2.5 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, 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
|
|
|
|
# --- 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
|
|
]
|