Repository navigation
ci: audit dependencies weekly; vite 6.4.5; drop a stale PyJWT exception - #15
Merged
Merged
Conversation
Twice in October an advisory was published while the repository sat idle, and nothing noticed until the next pull request failed on it. CI only audits on pull requests and pushes. .github/workflows/audit.yml runs the same audits every Monday: pip-audit over versions.lock and npm audit over the site. GitHub emails the owner when a scheduled run fails. It found one already: GHSA-8g5g-mxqh-grgj (published 2026-10-29) covers exactly the vite 6.4.4 the site pinned; vite 6.4.5 fixes it. It is a dev-server bypass (server.fs.deny with query strings), so it affected `npm run dev` on a contributor's machine, not the published site, but the docs workflow's audit would have failed the next site change. The pip-audit command moves into scripts/audit_pinned_deps.sh, which both CI and the weekly run call, so they cannot drift apart. It drops --ignore-vuln PYSEC-2026-4146: the advisory's record now covers PyJWT 2.11.0 to 2.13.0 only (modified 2026-10-01) and the lock pins 2.15.0, so the exception had stopped applying and would only have hidden a future finding under that ID. Checked locally: the script passes on the current lock and exits 1 with a vulnerable certifi pin swapped in; npm audit reports 0 on vite 6.4.5 and the site builds; both workflows parse. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Twice in October an advisory was published while the repository sat idle, and nothing noticed until the next pull request failed on it (#13). CI only audits on pull requests and pushes.
.github/workflows/audit.ymlruns the same audits every Monday (06:17 UTC) and on demand:pip-auditoverversions.lock, andnpm auditover the site. GitHub emails the owner when a scheduled run fails.server.fs.denywith query strings): it affectednpm run devon a contributor's machine, not the published site, but the docs workflow's audit would have failed the next site change.scripts/audit_pinned_deps.shholds the pip-audit command, called by both CI and the weekly run, so they cannot drift apart.--ignore-vuln PYSEC-2026-4146. The advisory's OSV record now covers PyJWT 2.11.0 to 2.13.0 only (modified 2026-10-01); the lock pins 2.15.0. The exception had stopped applying and would only have hidden a future finding under that ID.CONTRIBUTING and the changelog are updated.
Testing
npm audit: 0 vulnerabilities on vite 6.4.5; the site builds.main; I will run it once by hand after merging.Security invariants
src/changes. CI still fails a PR on any known vulnerability in the lock, now with no exceptions.🤖 Generated with Claude Code