Repository navigation
Fix HTML verification and bound API bearer-token parsing - #12
Merged
Merged
Conversation
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.
Repository verification now uses Python's standard HTMLParser instead of a tag-matching regex, resolving the new CodeQL bad-tag-filter finding while preserving JavaScript syntax and embedded-image checks.
The first full security scan also identified ambiguous bearer-header parsing in the existing experimental API. Accept only the issued 64-character hexadecimal token format, with separate whitespace handling. New API checks reject long whitespace-only and oversized token values within the request timeout.
Validation: 18 API checks and 5 archived tests pass locally; 25 Markdown files pass local-link/source checks; five JavaScript syntax checks and four embedded landing images pass; actionlint passed. GitHub CI checks iOS compilation, Linux tests, container health, dependency review and CodeQL. No production-readiness or full UI verification claim.
Follow-up to merged #11; refs #7. Wiki first-page initialization remains blocked by browser permission, with generated navigation available as an Actions artifact.