Repository Analysis

rivo/tview

Terminal UI library with rich, interactive widgets — written in Golang

4.0 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of rivo/tview, a Go project with 14,025 GitHub stars. SynthScan v2.0 examined 19,019 lines of code across 90 source files, recording 77 pattern matches distributed across 2 syntactic categories. The overall adjusted score of 4.0 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).

4.0
Adjusted Score
4.0
Raw Score
100%
Time Factor
2026-08-07
Last Push
14.0K
Stars
Go
Language
19.0K
Lines of Code
90
Files
77
Pattern Hits
2026-08-09
Scan Date
0.00
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

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

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 0HIGH 0MEDIUM 0LOW 77

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 77 distinct pattern matches across 2 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.

Over-Commented Block75 hits · 75 pts
SeverityFileLineSnippetContext
LOWlist.go21// clicking on them with the mouse. The following key binds are available:COMMENT
LOWlist.go161 l.itemOffset = itemsCOMMENT
LOWlist.go321// SetWrapAround sets the flag that determines whether navigating the list willCOMMENT
LOWlist.go361 return lCOMMENT
LOWlist.go381//COMMENT
LOWtreeview.go261func (n *TreeNode) GetLevel() int {COMMENT
LOWtreeview.go281// - J: Move (the selection) up one level (if that node is selectable).COMMENT
LOWtreeview.go381// selections. Selected nodes must be visible and selectable, or else theCOMMENT
LOWtreeview.go501// is only updated after the tree view has been redrawn.COMMENT
LOWtextarea.go41)COMMENT
LOWtextarea.go61// (3-int array) and an ending position (3-int array). The starting positionCOMMENT
LOWtextarea.go101// keys can be used to move the cursor (subject to what the user's terminalCOMMENT
LOWtextarea.go121//COMMENT
LOWtextarea.go141// - Ctrl-U: Delete the current line, i.e. everything after the last newlineCOMMENT
LOWtextarea.go161// global Ctrl-C key and you want to bind it to the "copy to clipboard"COMMENT
LOWtextarea.go181//COMMENT
LOWtextarea.go241 length intCOMMENT
LOWtextarea.go281 // position (see [textAreaSpan]). Not all lines of the text may be containedCOMMENT
LOWtextarea.go621// positions refer to index positions within the entire text string (as aCOMMENT
LOWtextarea.go901// skipped during drawing at the top or on the left, respectively. Note that theCOMMENT
LOWtextarea.go981 t.textStyle = tcell.StyleDefault.Foreground(fieldTextColor).Background(fieldBgColor)COMMENT
LOWtextarea.go1441 if fromLine < len(t.lineStarts) {COMMENT
LOWtextarea.go1601func (t *TextArea) setTransform(transform func(cluster, rest string, boundaries int) (newCluster string, newBoundaries iCOMMENT
LOWbox.go1package tviewCOMMENT
LOWbox.go161// (and all primitives which extend it).COMMENT
LOWbox.go221 }COMMENT
LOWbox.go281 }COMMENT
LOWbox.go481 // Call custom draw function.COMMENT
LOWbox.go501//COMMENT
LOWgrid.go21// Grid is an implementation of a grid-based layout. It works by defining theCOMMENT
LOWgrid.go61// NewGrid returns a new grid-based layout container with no initial primitives.COMMENT
LOWgrid.go81// less than or equal to 0 represent proportional column widths or fractions ofCOMMENT
LOWgrid.go101//COMMENT
LOWgrid.go181// If rowSpan or colSpan is 0, the primitive will not be drawn.COMMENT
LOWtextview.go61// Write() method except that it does not acquire the lock.COMMENT
LOWtextview.go81// screen columns, but only if the text is left-aligned. If the text is centeredCOMMENT
LOWtextview.go101//COMMENT
LOWtextview.go121//COMMENT
LOWtextview.go141// text very far down only if really needed. For example, callCOMMENT
LOWtextview.go501 if t.regionTags != regions {COMMENT
LOWtextview.go621 t.text.Reset()COMMENT
LOWtextview.go721 }COMMENT
LOWtextview.go801}COMMENT
LOWtextview.go901// and [TextView.Clear] do. The lock will be acquired once when BatchWriter isCOMMENT
LOWtextview.go921COMMENT
LOWsemigraphics.go181// The matching will be sorted ascending by rune value, so you don't need toCOMMENT
LOWutil.go41// not exceeding that box. "align" is one of AlignLeft, AlignCenter, orCOMMENT
LOWprimitive.go21 //COMMENT
LOWprimitive.go41 Focus(delegate func(p Primitive))COMMENT
LOWprimitive.go61COMMENT
LOWprimitive.go81 // the primitive which newly received focus as well as on all of itsCOMMENT
LOWform.go41 // AllowExit returns true if the form may use the given key event to exitCOMMENT
LOWform.go221}COMMENT
LOWapplication.go61//COMMENT
LOWapplication.go141COMMENT
LOWapplication.go761 }}COMMENT
LOWapplication.go901 return nilCOMMENT
LOWimage.go41 BlockQuadrantUpperRight: 0b0000000000000000000000000000000011110000111100001111000011110000,COMMENT
LOWimage.go61// settings, none of which are under the control of this package. Results mayCOMMENT
LOWimage.go141 return iCOMMENT
15 more matches not shown…
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWdemos/table/main.go15 lorem := strings.Split("Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor inviduntCODE
LOWdemos/table/main.go15 lorem := strings.Split("Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor inviduntCODE