Skip to content

fix: escape project name in generated HTML - #29

Open
johnjheejin wants to merge 1 commit into
companyjupiter:mainfrom
johnjheejin:fix/project-name-html-escaping
Open

fix: escape project name in generated HTML#29
johnjheejin wants to merge 1 commit into
companyjupiter:mainfrom
johnjheejin:fix/project-name-html-escaping

Conversation

@johnjheejin

@johnjheejin johnjheejin commented Jul 26, 2026

Copy link
Copy Markdown

Summary

  • escape the configured project name before inserting it into generated HTML
  • cover all HTML-sensitive characters used in text content
  • add CLI regression coverage for both project-name locations in the viewer

Root cause

CONFIG.name was interpolated directly into the generated document title and project-name element. A project name containing markup could therefore become executable HTML instead of displayed text.

User impact

Generated viewers now display project names as text, including names that contain HTML-sensitive characters, without creating injected elements or event handlers.

Latest-base update

  • rebased onto upstream main at f02a53e
  • preserved the current offline HTML viewer and executable-config protections while resolving conflicts

Validation

  • npm ci --ignore-scripts --no-audit --no-fund
  • npm test (21 tests: 20 passed, 1 skipped because symlink creation is unavailable on Windows)
  • node --check quarkify.mjs
  • git diff --check

@johnjheejin
johnjheejin force-pushed the fix/project-name-html-escaping branch from 27610f3 to 6a5fc84 Compare August 3, 2026 02:52
@johnjheejin
johnjheejin marked this pull request as ready for review August 3, 2026 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant