Repository navigation
Remove vulnerable publisher and request the existing gated deployment - #20
Merged
systemslibrarian merged 1 commit intoOct 9, 2026
Merged
Conversation
systemslibrarian
deleted the
repair/remove-vulnerable-publisher-20261009
branch
October 12, 2026 11:47
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.
Current npm audit flags the unpatched Braces3.0.3 publisher chain. The authoritative Pages workflow already performs the application gates and does not use gh-pages. This removes that redundant development publisher, preserving every remaining installed package version and the existing workflow.
npm run deploynow requestspages.ymlon remote main. Real npm positive/refused-request controls replace only the external GitHub command, retain failure73, and never dispatch a workflow. The existing build runs these controls before its original compile/build command, so current CI judges them. All cryptographic implementation, teaching claims, binary/compiler provenance and application assertions are preserved.Validation on final
61d06cdeb4242173158ad8d70f4a007699a14f32:npm ci— passednpm audit --json— passednpm run type-check— passednpm run test— passednpm run build— passednpm run test:a11y -- --workers=1— passedNpm audit0 after publisher-chain removal. This addresses locked development-tooling exposure; no live-site exploit or vendor/compiler reproduction is inferred. Required PR checks and default-branch deployment/live verification are collected separately before closure.
Fleet work item: d0db4cd4-325f-4caa-be78-ae74b05b80c2.