fix: resolve high-severity CodeQL findings - #54
Open
AjnasNB wants to merge 3 commits into
Open
Conversation
AjnasNB
enabled auto-merge (squash)
August 29, 2026 05:13
Owner
Author
|
Review-ready security fix: all four high CodeQL findings are fixed without dismissals, the PR merge ref reports zero open findings, all 10 required checks pass, and every commit is GitHub-verified. The changes cover structural HTML handling, linear path scanning, and salted scrypt tab locks with regression coverage. @cognifyrdotco, please review. |
Owner
Author
|
@cognifyrdotco All four reported high-severity CodeQL findings are fixed on |
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 changed
Authority impact
Evidence
npm run checkpasses (85 tests: 80 passed, 5 browser-dependent skips; typecheck/build/package/site/audit/dry-pack all passed).COCKROACH_BROWSER_E2E=1 node --test .test-dist/test/browser-smoke.test.jspassed with the wrong-token regression.<hex>placeholders rather than reconstructing markup.Release impact
No deployment migration is required. Existing in-memory locks are process-local and are not persisted across upgrades.
All three commits carry SSH signatures. All four open high-severity CodeQL findings are fixed; none was remotely dismissed.