Repository navigation
fix: recover safely from malformed search fragments - #6
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
A chapter URL such as
#find-%or#find-%GGcould throw during React rendering and blank the reader. Search fragments are now decoded once through a guarded helper; malformed encodings safely fall back to the first section, while valid Unicode searches still select matching commentary.Addresses Codex Security Cloud finding
csf_8bdfd647c3204be095674eacat41c6d1d.Validation: production build and 11 unit/compiler tests pass. All 14 existing browser cases pass; the four new malformed-fragment/direct/history/Unicode cases pass using installed Chrome. The new tests' initially ambiguous Original text locator was corrected and those cases rerun. npm install audit reports zero vulnerabilities on 5 October 2026. No new dependencies.
No merge, deployment, or cloud-finding closure performed. The fix handles the identified input boundary; a general application error boundary is outside this focused patch.