Repository Analysis

VSCodeVim/Vim

:star: Vim for Visual Studio Code

3.1 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of VSCodeVim/Vim, a TypeScript project with 15,170 GitHub stars. SynthScan v2.0 examined 75,206 lines of code across 303 source files, recording 157 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 3.1 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

3.1
Adjusted Score
3.1
Raw Score
100%
Time Factor
2026-07-13
Last Push
15.2K
Stars
TypeScript
Language
75.2K
Lines of Code
303
Files
157
Pattern Hits
2026-07-14
Scan Date
0.02
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 4HIGH 1MEDIUM 0LOW 152

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 157 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Verbosity Indicators77 hits · 91 pts
SeverityFileLineSnippetContext
LOWtest/macro.test.ts261 // Step 0:COMMENT
LOWtest/macro.test.ts276 // Step 0:COMMENT
LOWtest/macro.test.ts283 // Step 1:COMMENT
LOWtest/macro.test.ts298 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts59 // Step 1: Again we press the keys '<space>w' that remaps to 'w' and waits for timeout and we assertCOMMENT
LOWtest/configuration/remaps.test.ts67 // Step 2: Since we didn't wait for timeout on the previous step it is still waiting for timeout toCOMMENT
LOWtest/configuration/remaps.test.ts135 // Step 1: Again we press the keys '<space>w' and we assert that nothing has changed since theCOMMENT
LOWtest/configuration/remaps.test.ts143 // Step 2: Since we didn't wait for timeout on the previous step it is still waiting for timeout toCOMMENT
LOWtest/configuration/remaps.test.ts152 // Step 3: Press keys '<space>b' that remap to '0' but since there is the '<space>bb' potentialCOMMENT
LOWtest/configuration/remaps.test.ts162 // Step 4: Again we press the keys '<space>b' and we assert that nothing has changed since theCOMMENT
LOWtest/configuration/remaps.test.ts170 // Step 5: Since we didn't wait for timeout on the previous step it is still waiting for timeout toCOMMENT
LOWtest/configuration/remaps.test.ts179 // Step 6: '<space>ee' should be handled by the RecursiveRemapper after timeoutCOMMENT
LOWtest/configuration/remaps.test.ts187 // Step 7: '<space>eee' should be handled by the NonRecursiveRemapper without timeoutCOMMENT
LOWtest/configuration/remaps.test.ts194 // Step 8: '<space>ll' should be handled by the NonRecursiveRemapper after timeoutCOMMENT
LOWtest/configuration/remaps.test.ts202 // Step 9: '<space>lll' should be handled by the RecursiveRemapper without timeoutCOMMENT
LOWtest/configuration/remaps.test.ts319 // Step 1:COMMENT
LOWtest/configuration/remaps.test.ts329 // Step 2:COMMENT
LOWtest/configuration/remaps.test.ts339 // Step 3:COMMENT
LOWtest/configuration/remaps.test.ts371 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts381 // Step 1:COMMENT
LOWtest/configuration/remaps.test.ts390 // Step 2:COMMENT
LOWtest/configuration/remaps.test.ts450 // Step 3:COMMENT
LOWtest/configuration/remaps.test.ts460 // Step 4:COMMENT
LOWtest/configuration/remaps.test.ts470 // Step 5:COMMENT
LOWtest/configuration/remaps.test.ts480 // Step 6:COMMENT
LOWtest/configuration/remaps.test.ts490 // Step 7:COMMENT
LOWtest/configuration/remaps.test.ts500 // Step 8:COMMENT
LOWtest/configuration/remaps.test.ts560 // Step 3:COMMENT
LOWtest/configuration/remaps.test.ts570 // Step 4:COMMENT
LOWtest/configuration/remaps.test.ts580 // Step 5:COMMENT
LOWtest/configuration/remaps.test.ts590 // Step 6:COMMENT
LOWtest/configuration/remaps.test.ts600 // Step 7:COMMENT
LOWtest/configuration/remaps.test.ts610 // Step 8:COMMENT
LOWtest/configuration/remaps.test.ts921 // Step 0: there is no timeout because 'b' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts930 // Step 1: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts952 // Step 3: No timeout because 'x' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts961 // Step 4: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts1008 // Step 0: there is no timeout because 'b' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts1017 // Step 1: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts1039 // Step 3: No timeout because 'x' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts1048 // Step 4: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts1147 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts1157 // Step 1:COMMENT
LOWtest/configuration/remaps.test.ts1166 // Step 2:COMMENT
LOWtest/configuration/remaps.test.ts1175 // Step 3:COMMENT
LOWtest/configuration/remaps.test.ts1184 // Step 4:COMMENT
LOWtest/configuration/remaps.test.ts1193 // Step 5:COMMENT
LOWtest/configuration/remaps.test.ts48 // Step 0: Press keys '<space>w' that remap to 'w' but since 'w' is an ambiguous remap it waitsCOMMENT
LOWtest/configuration/remaps.test.ts121 // Step 0: Press keys '<space>w' that remap to '$' but since there is the '<space>ww' potentialCOMMENT
LOWtest/configuration/remaps.test.ts240 // Step 0: 'xxx' has no remapping and not actions so it does nothing but should stillCOMMENT
LOWtest/configuration/remaps.test.ts250 // Step 1: 'lll' has no remapping and not actions so it does nothing but should stillCOMMENT
LOWtest/configuration/remaps.test.ts268 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts284 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts308 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts351 // Step 4:COMMENT
LOWtest/configuration/remaps.test.ts415 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts427 // Step 1:COMMENT
LOWtest/configuration/remaps.test.ts438 // Step 2:COMMENT
LOWtest/configuration/remaps.test.ts525 // Step 0:COMMENT
LOWtest/configuration/remaps.test.ts537 // Step 1:COMMENT
17 more matches not shown…
Hallucination Indicators4 hits · 40 pts
SeverityFileLineSnippetContext
CRITICALextensionBase.ts549 vscode.window.activeTextEditor.document.uri.toString() === 'debug:input'CODE
CRITICALtest/testUtils.ts151 !vscode.window.activeTextEditor.document.fileName.endsWith(args.fileExtension)) ||CODE
CRITICALsrc/cmd_line/commands/bufferDelete.ts37 vscode.window.tabGroups.activeTabGroup.tabs.findIndex((t) => t.isActive) + 1;CODE
CRITICALsrc/cmd_line/commands/write.ts173 const matchingTab = vscode.window.tabGroups.activeTabGroup.tabs.find((tab: vscode.Tab) =>CODE
Fake / Example Data30 hits · 38 pts
SeverityFileLineSnippetContext
LOWtest/sentenceMotion.test.ts12 start: ['lorem ipsum. lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts14 end: ['lorem ipsum. |lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts19 start: ['lorem ipsum. lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts21 end: ['lorem ipsum. |lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts26 start: ['lorem ipsum. lorem ipsum. lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts28 end: ['lorem ipsum. |lorem ipsum. lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts33 start: ['lorem ipsum. |lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts35 end: ['|lorem ipsum. lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts40 start: ['lorem ipsum.lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts42 end: ['|lorem ipsum.lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts47 start: ['lorem ipsum.|lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts49 end: ['|lorem ipsum.lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts54 start: ['"lorem ipsum." lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts56 end: ['"lorem ipsum." |lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts61 start: ["'lorem ipsum.' lorem ipsum|"],CODE
LOWtest/sentenceMotion.test.ts63 end: ["'lorem ipsum.' |lorem ipsum"],CODE
LOWtest/sentenceMotion.test.ts68 start: ['(lorem ipsum.) lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts70 end: ['(lorem ipsum.) |lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts75 start: ['[lorem ipsum.] lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts77 end: ['[lorem ipsum.] |lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts82 start: ['lorem ipsum', 'lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts84 end: ['|lorem ipsum', 'lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts89 start: ['lorem ipsum.', 'lorem ipsum|'],CODE
LOWtest/sentenceMotion.test.ts91 end: ['lorem ipsum.', '|lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts96 start: ['lorem ipsum', '|lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts98 end: ['|lorem ipsum', 'lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts103 start: ['lorem ipsum.', '|lorem ipsum'],CODE
LOWtest/sentenceMotion.test.ts105 end: ['|lorem ipsum.', 'lorem ipsum'],CODE
LOWtest/configuration/remapper.test.ts226 const expectedDocumentContent = 'lorem ipsum';CODE
LOWtest/configuration/remapper.test.ts291 const expectedDocumentContent = 'lorem ipsum';CODE
Structural Annotation Overuse23 hits · 31 pts
SeverityFileLineSnippetContext
LOWtest/configuration/remaps.test.ts59 // Step 1: Again we press the keys '<space>w' that remaps to 'w' and waits for timeout and we assertCOMMENT
LOWtest/configuration/remaps.test.ts67 // Step 2: Since we didn't wait for timeout on the previous step it is still waiting for timeout toCOMMENT
LOWtest/configuration/remaps.test.ts135 // Step 1: Again we press the keys '<space>w' and we assert that nothing has changed since theCOMMENT
LOWtest/configuration/remaps.test.ts143 // Step 2: Since we didn't wait for timeout on the previous step it is still waiting for timeout toCOMMENT
LOWtest/configuration/remaps.test.ts152 // Step 3: Press keys '<space>b' that remap to '0' but since there is the '<space>bb' potentialCOMMENT
LOWtest/configuration/remaps.test.ts162 // Step 4: Again we press the keys '<space>b' and we assert that nothing has changed since theCOMMENT
LOWtest/configuration/remaps.test.ts170 // Step 5: Since we didn't wait for timeout on the previous step it is still waiting for timeout toCOMMENT
LOWtest/configuration/remaps.test.ts921 // Step 0: there is no timeout because 'b' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts930 // Step 1: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts952 // Step 3: No timeout because 'x' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts961 // Step 4: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts1008 // Step 0: there is no timeout because 'b' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts1017 // Step 1: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts1039 // Step 3: No timeout because 'x' breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts1048 // Step 4: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts48 // Step 0: Press keys '<space>w' that remap to 'w' but since 'w' is an ambiguous remap it waitsCOMMENT
LOWtest/configuration/remaps.test.ts121 // Step 0: Press keys '<space>w' that remap to '$' but since there is the '<space>ww' potentialCOMMENT
LOWtest/configuration/remaps.test.ts941 // Step 2: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts972 // Step 5: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts983 // Step 6: there will be no timeout because "x" breaks ambiguityCOMMENT
LOWtest/configuration/remaps.test.ts1028 // Step 2: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts1059 // Step 5: there will be timeoutCOMMENT
LOWtest/configuration/remaps.test.ts1070 // Step 6: there will be no timeout because "x" breaks ambiguityCOMMENT
Over-Commented Block13 hits · 13 pts
SeverityFileLineSnippetContext
LOWtest/index.ts1//COMMENT
LOWtest/testSimplifier.ts421 setTimeout(async () => {COMMENT
LOWtest/mode/normalModeTests/motions.test.ts501 // test('Remembers a forward search from another editor', async function() {COMMENT
LOWtest/mode/normalModeTests/motions.test.ts521 // });COMMENT
LOWtest/mode/normalModeTests/motions.test.ts581COMMENT
LOWtest/mode/normalModeTests/motions.test.ts601 // end: ['three four |two one'],COMMENT
LOWtest/actions/insertLine.test.ts61 await modeHandler.handleMultipleKeyEvents(['<Esc>']);COMMENT
LOWsrc/textobject/textobject.ts741 return configuration.argumentObjectSeparators;COMMENT
LOWsrc/textobject/textobject.ts761 //COMMENT
LOWsrc/configuration/remapper.ts161 if (this.hasAmbiguousRemap) {COMMENT
LOWsrc/configuration/remapper.ts181 // remap the 'a' should be handled.COMMENT
LOWsrc/common/number/numericString.ts101 const prefix = input.slice(0, coreBegin);COMMENT
LOWsrc/actions/commands/actions.ts81 // number so we need to multiply them.COMMENT
Hyper-Verbose Identifiers8 hits · 8 pts
SeverityFileLineSnippetContext
LOWextensionBase.ts30export async function getAndUpdateModeHandler(CODE
LOWsrc/textobject/paragraph.ts28export function getCurrentParagraphBeginning(pos: Position, trimWhite: boolean = false): Position {CODE
LOWsrc/textobject/sentence.ts73function getFirstNonWhitespaceInParagraph(CODE
LOWsrc/transformations/transformations.ts261export function overlappingTransformations(CODE
LOWsrc/mode/mode.ts84export function visualBlockGetTopLeftPosition(start: Position, stop: Position): Position {CODE
LOWsrc/mode/mode.ts88export function visualBlockGetBottomRightPosition(start: Position, stop: Position): Position {CODE
LOWsrc/util/decorationUtils.ts63export function getDecorationsForSearchMatchRanges(CODE
LOWsrc/actions/commands/search.ts89async function createSearchStateAndMoveToMatch(args: {CODE
AI Response Leakage1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHtest/plugins/surround.test.ts510 // I've added the '0' key press at the end because the test was behaving weirdly, if I ranCOMMENT
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWtest/cmd_line/normal.test.ts74 // TODO: implement to stop when operation failsCOMMENT