Harden site build and search boundaries - #105
Merged
Merged
Conversation
Pin browser and build dependencies, constrain untrusted search URLs, and fail closed on local tooling errors. Restrict Actions tokens, move Pages credentials to deploy jobs, upgrade Ruby, and fix the affected UI and packaging regressions.
Add base64 and csv as explicit dependencies now that Ruby 3.4 no longer ships them as default gems. This keeps the pinned Jekyll build runnable locally and in CI.
Write the Pages archive to the explicit GitHub workspace path so tar and gzip agree across runners. Drop the unused GNU-only hard-link flag to keep local reproduction portable.
VatsalSy
marked this pull request as ready for review
July 29, 2026 07:56
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.
Summary
base64andcsvgems required by Jekyll on Ruby 3.4Why
The security scan surfaced a mix of actionable hardening gaps, stale assumptions, and false positives. The actionable cases were fixed; the remaining findings were reviewed and closed with a decision. Running the repository under its pinned Ruby version also exposed that Jekyll relied on standard-library gems that Ruby 3.4 no longer installs by default.
Impact
The public site keeps its existing behaviour while reducing unsafe search/rendering paths and making local and CI builds reproducible with the pinned toolchain.
Validation
npm audit --omit=dev: 0 vulnerabilities