Fast math typesetting for the web.
This report summarizes scanner evidence for KaTeX/KaTeX, a TypeScript project with 20,482 GitHub stars. SynthScan examined 67,946 lines of code across 218 source files, recording 43 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 1.0 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.
Can maintainers explain intent, assumptions, and trade-offs? 35 finding(s).
Are imports declared and package/API names verified? 6 finding(s).
Are wrappers, guards, and repeated structures necessary? 4 finding(s).
Which changes need focused human review? 43 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 43 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | update-sri.js | 1 | // Update badge and CDN urls and subresource integrity hashes | COMMENT |
| LOW | test/screenshotter/ss_data.yaml | 1 | # List of test cases for which we create screenshots and other documents. | COMMENT |
| LOW | website/static/css/custom.css | 141 | #spacing-tbl td:nth-of-type(4)::before { content: "Produces:"; } | COMMENT |
| LOW | website/static/css/custom.css | 161 | #unit-blocks td:nth-of-type(2)::before { content: "textstyle:"; } | COMMENT |
| LOW | contrib/mhchem/mhchem.js | 101 | // | COMMENT |
| LOW | contrib/mhchem/mhchem.js | 121 | // buffer.rdt == arrow, script above, type | COMMENT |
| LOW | contrib/mhchem/mhchem.js | 181 | // | COMMENT |
| LOW | src/delimiter.ts | 821 | // exactly match TeX's calculation, we could do | COMMENT |
| LOW | src/buildCommon.ts | 461 | type VListParam = { | COMMENT |
| LOW | src/stretchy.ts | 81 | // distortion of arrowheads or brace corners. | COMMENT |
| LOW | src/unicodeScripts.ts | 41 | name: 'armenian', | COMMENT |
| LOW | src/macros.ts | 341 | ////////////////////////////////////////////////////////////////////// | COMMENT |
| LOW | src/macros.ts | 541 | // Spacing, based on amsmath.sty's override of LaTeX defaults | COMMENT |
| LOW | src/macros.ts | 561 | defineMacro("\\thickspace", "\\;"); | COMMENT |
| LOW | src/macros.ts | 621 | // TODO: Doesn't normally work in math mode because \@ fails. KaTeX doesn't | COMMENT |
| LOW | src/fontMetrics.ts | 21 | // provided in the arrays below, in that order. | COMMENT |
| LOW | src/svgGeometry.ts | 1 | /** | COMMENT |
| LOW | src/buildMathML.ts | 321 | COMMENT | |
| LOW | src/types/index.ts | 1 | export type Mode = "math" | "text"; | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | dockers/texcmp/texcmp.js | 95 | // Step 1: write key.tex file | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 97 | // Step 2: call "pdflatex key" to create key.pdf | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 103 | // Step 3: call "convert ... key.pdf key.png" to create key.png | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 110 | // Step 4: apply FFT to that | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 113 | // Step 5: apply FFT to reference image as well | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 118 | // Step 6: find alignment which maximizes overlap. | COMMENT |
| LOW | dockers/texcmp/texcmp.js | 166 | // Step 7: use these offsets to compute difference illustration | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | dockers/texcmp/texcmp.js | 95 | // Step 1: write key.tex file | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 97 | // Step 2: call "pdflatex key" to create key.pdf | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 103 | // Step 3: call "convert ... key.pdf key.png" to create key.png | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 110 | // Step 4: apply FFT to that | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 113 | // Step 5: apply FFT to reference image as well | COMMENT |
| LOW⚡ | dockers/texcmp/texcmp.js | 118 | // Step 6: find alignment which maximizes overlap. | COMMENT |
| LOW | dockers/texcmp/texcmp.js | 166 | // Step 7: use these offsets to compute difference illustration | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | src/functions/horizBrace.ts | 41 | // Generate the vlist, with the appropriate kerns ┏━━━━━━━━┓ | COMMENT |
| MEDIUM | src/functions/horizBrace.ts | 74 | // ┏━━━━━━━━┓ or ┏━━━┓ not ┏━━━━━━━━━┓ | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | test/setup.ts | 34 | print(val: unknown) { | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | contrib/auto-render/test/auto-render-spec.ts | 354 | const textNodes = ['Lorem ipsum dolor', | CODE |
| LOW | static/index.html | 73 | placeholder="Lorem ipsum" | CODE |
| LOW | static/index.html | 80 | placeholder="Lorem ipsum" | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | static/main.js | 86 | function getClampedMobileOptionsHeight(height) { | CODE |
| LOW | static/main.js | 129 | function getCurrentMobileOptionsHeight() { | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | src/fonts/generate_fonts.py | 5 | CODE | |
| LOW | src/fonts/generate_fonts.py | 8 | CODE |