npm (web/):
- undici 7.30.1 through a "miniflare" override (GHSA-xjj6-f33q-929c,
GHSA-4qv8-2p9j-2685, GHSA-f72v-6w45-q472). miniflare pins undici exactly
and wrangler 4.152.0, the newest, still ships 7.29.1. Local tooling only.
- zod 4.6.7 (GHSA-mrhx-c7xc-m3w5, via knip).
- Minor/patch: @lucide/svelte 1.61.0, @tanstack/svelte-virtual 3.13.48,
bits-ui 2.20.2, vite 8.3.5, wrangler 4.152.0, knip 6.43.0,
@tauri-apps/cli 2.12.4.
cargo (web/src-tauri/Cargo.lock, targeted updates only):
- rustls 0.23.46 (RUSTSEC-2026-0346..0349), rustls-webpki 0.103.16
(RUSTSEC-2026-0382), webpki-root-certs 1.0.11 (RUSTSEC-2026-0383),
tokio 1.54.1 (RUSTSEC-2026-0386), anyhow 1.0.104 (RUSTSEC-2026-0190),
event-listener 5.4.2 (RUSTSEC-2026-0221), plist 1.10.3 -> quick-xml
0.42.0 (RUSTSEC-2026-0194/0195). Dependabot had none of these.
- Left upstream: zip 4 (tauri-plugin-updater 2.14.0 asks for ^4), glib 0.18
(GTK 3), unmaintained proc-macro-error/zbus_names/zvariant.
pip: certifi 2026.10.23, coverage 7.17.0 (tests), with every file's hash.
CI: actions/checkout v4/v5 -> v6 and actions/setup-python v5 -> v6
everywhere (the Node 20 majors warned on every data job), rust-cache 2.9.3
by SHA. dependabot.yml says why those majors are taken by hand.
CLAUDE.md: the undici override and when to drop it; why SvelteKit stays on 2
(GHSA-27mw-82g8-phjj and GHSA-pfhg-q3qv-9q6r need setHeaders or use:enhance,
which the app does not have).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scan job now runs both suites with coverage before scanning:
pytest --cov (pyproject.toml: scripts/ without its tests, relative
paths, coverage.xml) and `npm run test:coverage` (vite.config.ts: v8,
lcov with projectRoot "..", so paths start web/). sonar-project.properties
names both reports and drops sonar.coverage.exclusions.
requirements-test.txt gains pytest-cov 7.1.0 and coverage 7.16.2 with
every file's hash (uv pip compile --universal --generate-hashes
--python-version 3.15; the existing pins are unchanged). web gains
@vitest/coverage-v8 5.0.5, matching vitest; none of its packages has an
install script. Coverage stays off for a plain `npm test`.
The token check is its own job, so the scan steps no longer each repeat
the condition; the workflow grants nothing at the top and the scan job
contents: read. `npm run build:admin` replaces the bare `svelte-kit
sync`: it syncs too, and writes the admin bundle the Worker's tests load.
Locally: 576 vitest tests at 58.35% of lines, 299 pytest tests at 57.7%.
Against main's new-code lines (SonarCloud's isNew), the reports cover
92 of 114 coverable lines, 80.7%: the 80% gate is borderline.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SonarCloud's GitHub Actions and shell findings, all supply-chain hardening
for jobs that hold a write token (and, in the release workflows, the
signing keys):
- The six third-party actions in release-desktop.yml and release-android.yml
are pinned to the commit their major tag points at today, with the version
in a comment for Dependabot. dtolnay/rust-toolchain is pinned to a master
commit and given `toolchain: stable`: its `stable` branch is regenerated
on top of master, so a commit of it can vanish.
- Every `npm ci` is `npm ci --ignore-scripts`. Only fsevents, workerd and
wrangler's esbuild have install scripts; the last two find their binary in
their optional platform package without them, and fsevents is only file
watching. `npx` is gone from the workflows (`npm run cf:check`,
`npm test -- <file>`).
- requirements.txt pins every runtime package, transitive ones included
(certifi, charset-normalizer, idna), with the sha256 of every file on
PyPI; every install is `--require-hashes --only-binary :all:`. The new
requirements-test.txt holds pytest the same way. python-tests.yml runs the
data jobs' exact install line first, so a Dependabot bump is proven before
a data job meets it.
- `[[ ]]` instead of `[ ]` in the bash wrappers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>