campaign 5: all packages — CI GREEN (run 88); batch A+B + campaign 2/3 first coverage; zizmor deferred #23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "campaign/candidates-5"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Candidate campaign 5 — verification PR
Purpose of this PR: the authoring session's sandbox cannot run verify.sh's FUSE smoke stage (no /dev/fuse, mknod EPERM) — so this PR exists partly to let CI be the authoritative verifier (bees runner: podman + FUSE + fusermount3 all proven). Both batches are now merged; CI re-runs per push.
Curated packages — batch A (committed)
-vbanner + offline schema validation of repo fixture → "Valid: 1"--version+ onlinescan sourcefixture (fixed after run 85:--offlinerequires a pre-seeded GB-scale DB, exit 127 without it); /persist for the vuln-DB cache--version+ offlinefilesystemscan of entropy-tuned synthetic key fixtureversion --client+ offlinehelpCurated packages — batch B (committed)
--version+config verifyon committed fixture (run/fmtneed a Go toolchain — not vendored)-V+--helphttp --version+--help(no offline real invocation exists; iperf3 precedent)--version+ two REAL headless SQL queries over a committed syslog fixtureAll fetches sha256-pinned (lnav is TOFU-over-HTTPS — upstream publishes no sums for the zips; nixpkgs package.nix noted as cross-check). One commit per package.
Also in this diff (pre-existing, first-ever CI coverage)
Campaign 2–3 delivered ten curated packages via PRs #21/#22 into
campaign/initial-backlog— but PR #20 merged that branch's older state to main, so main never received them. This branch carries them; CI verifies them here for the first time.zizmor DEFERRED (revert in this PR)
Run 85 exposed an upstream bug: zizmor 1.30.1 (the latest release) breaks whenever GITHUB_TOKEN is in the environment — which CI jobs always export.
--pedanticpanics (exit 101), default persona exits 2. Reproduced locally with a dummy token; absent = clean pass. No package-level fix exists (empty-string env trips clap; distroless = no shell shim). The package is reverted and returned to the backlog as blocked, with the reconsider trigger documented. Proposed follow-up (separate PR, not this one): strip CI job credentials (GITHUB_TOKEN/GH_TOKEN) from verify.sh smoke invocations — sandboxed tools shouldn't see job credentials at all, and it fixes this failure class for every package.Cautions for review
upstream-imageposture for AGPL).Upstream static Go release binary, fetched sha256-verified from the v3.97.9 release (trufflehog_3.97.9_linux_amd64.tar.gz): 40377e6572495412fb9ba0bc21c9401f73b72f1d2afd11b9931bc4a5ed622866 (from the release's trufflehog_3.97.9_checksums.txt asset). License AGPL-3.0 (upstream relicensed from the brief's assumed MIT in 2026-07; verified against the v3.97.9 LICENSE) — AGPL permits redistribution of the unmodified binary, redistribution ok. Smoke: --version banner + offline real invocation: filesystem scan over a repo fixture with a synthetic AWS key pair (--no-verification keeps the smoke offline; findings exit 0 by default, so the check asserts the 'Found unverified result' detection line). Fixture entropy tuned to clear the AWS detector's Shannon thresholds and its [a-f0-9]{40} false-positive filter. --no-same-owner on extraction: goreleaser ships uid-1001 members, chown fails in single-uid userns builds. Built via the real pipeline (39 MB footprint); smoke checks validated against the real image binary in a bwrap sandbox (session lacks /dev/fuse for the engine's FUSE mount stage — final verify.sh run pending on a FUSE-capable host).campaign 5: kubeconform osv-scanner trufflehog argocd (batch a) — CI verification; batch b incomingto campaign 5: all packages — CI GREEN (run 88); batch A+B + campaign 2/3 first coverage; zizmor deferred