Repository Analysis

go-echarts/go-echarts

🎨 The adorable charts library for Golang.

7.1 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of go-echarts/go-echarts, a Go project with 7,630 GitHub stars. SynthScan v2.0 examined 17,590 lines of code across 165 source files, recording 105 pattern matches distributed across 3 syntactic categories. The overall adjusted score of 7.1 places this repository in the Low AI signal 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).

7.1
Adjusted Score
7.1
Raw Score
100%
Time Factor
2026-07-12
Last Push
7.6K
Stars
Go
Language
17.6K
Lines of Code
165
Files
105
Pattern Hits
2026-07-14
Scan Date
0.01
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 2HIGH 0MEDIUM 0LOW 103

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 105 distinct pattern matches across 3 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 Block100 hits · 100 pts
SeverityFileLineSnippetContext
LOWdocs/en-us/options/title.md41 // 'blank' opening it in a new tabCOMMENT
LOWdocs/en-us/options/title.md61 // Distance between title component and the right side of the container.COMMENT
LOWdocs/en-us/options/title.md81COMMENT
LOWdocs/en-us/options/yAxis.md21 // 'end'COMMENT
LOWdocs/en-us/options/yAxis.md41COMMENT
LOWdocs/en-us/options/yAxis.md61COMMENT
LOWdocs/en-us/options/legend.md21 // Distance between legend component and the left side of the container.COMMENT
LOWdocs/en-us/options/legend.md41 // Distance between legend component and the bottom side of the container.COMMENT
LOWdocs/en-us/options/legend.md61 Align string `json:"align,omitempty"`COMMENT
LOWdocs/en-us/options/legend.md81 // Example:COMMENT
LOWdocs/en-us/options/legend.md101 // 'image://http://example.website/a/b.png'COMMENT
LOWdocs/en-us/options/xAxis.md21 // 'bottom'COMMENT
LOWdocs/en-us/options/xAxis.md41 // Name of axis.COMMENT
LOWdocs/en-us/options/xAxis.md61COMMENT
LOWdocs/en-us/options/xAxis.md81 // It will be automatically computed to make sure axis tick is equally distributed when not set.COMMENT
LOWdocs/en-us/options/xAxis.md121 // Settings related to axis pointer.COMMENT
LOWdocs/en-us/options/xAxis.md141COMMENT
LOWdocs/en-us/options/xAxis.md161 // var date = new Date(value);COMMENT
LOWdocs/en-us/options/xAxis.md221// AxisLine controls settings related to axis line.COMMENT
LOWopts/gl_3d.go21 // * 'time' The timeline. Suitable for the continuous timing data. The time axis has aCOMMENT
LOWopts/gl_3d.go61 Grid3DIndex int `json:"grid3DIndex,omitempty"`COMMENT
LOWopts/gl_3d.go81COMMENT
LOWopts/gl_3d.go101 // Whether to display the z-axis.COMMENT
LOWopts/gl_3d.go121 // The minimum value of axis.COMMENT
LOWopts/toolbox.go21 // left value can be instant pixel value like 20; it can also be a percentageCOMMENT
LOWopts/toolbox.go121 // Icon for the tool.COMMENT
LOWopts/toolbox.go161 // 'polygon': Enabling selecting with any shape.COMMENT
LOWopts/toolbox.go181 // Icon for the tool.COMMENT
LOWopts/data_zoom.go1package optsCOMMENT
LOWopts/data_zoom.go21 // Valid values:COMMENT
LOWopts/data_zoom.go41 // Specify which yAxis is/are controlled by the dataZoom-inside when Cartesian coordinate system is used.COMMENT
LOWopts/data_zoom.go61COMMENT
LOWopts/charts.go21 AnimationDuration int `json:"animationDuration,omitempty"`COMMENT
LOWopts/charts.go101// https://echarts.apache.org/en/option.html#series-graphCOMMENT
LOWopts/charts.go401type TreeChart struct {COMMENT
LOWopts/charts.go521 // Value for each item. If contains children, value can be left unset, and sum of children values will be used in this COMMENT
LOWopts/charts.go581 // Font styleCOMMENT
LOWopts/charts.go681 // The content formatter of valueCOMMENT
LOWopts/charts.go701 // Whether to show the pointer, default true.COMMENT
LOWopts/series_bar.go1package optsCOMMENT
LOWopts/series_bar.go41 // Set barGap as '-100%' can overlap bars that belong to different series,COMMENT
LOWopts/polar.go61 // TriggerEvent Set this to true to enable triggering events.COMMENT
LOWopts/geo.go1package optsCOMMENT
LOWopts/geo.go21 // Zoom rate of current viewport. The value less than 1 indicates zooming out,COMMENT
LOWopts/tooltip.go1package optsCOMMENT
LOWopts/tooltip.go21 // * 'mousemove': Trigger when mouse moves.COMMENT
LOWopts/tooltip.go41 // * Line (area) charts, bar (column) charts, K charts: {a} for series name,COMMENT
LOWopts/tooltip.go61 // name: string,COMMENT
LOWopts/tooltip.go81 // dimensionIndex: number,COMMENT
LOWopts/visual_map.go41 Show types.Bool `json:"show,omitempty"`COMMENT
LOWopts/series_scatter.go1package optsCOMMENT
LOWopts/legend.go1package optsCOMMENT
LOWopts/legend.go21 // If the left value is set to be 'left', 'center', or 'right', then the componentCOMMENT
LOWopts/legend.go61 // Default values for each position are 5.COMMENT
LOWopts/legend.go81 // formatter: 'Legend {name}'COMMENT
LOWopts/legend.go101 // 'image://data:image/gif;base64,KOY......'COMMENT
LOWopts/series.go61 // Border radius of the text fragment.COMMENT
LOWopts/series.go81 // "left"COMMENT
LOWopts/series.go141}COMMENT
LOWopts/series.go521 // Opacity of the component. Supports value from 0 to 1, and the component will not be drawn when set to 0.COMMENT
40 more matches not shown…
Hallucination Indicators2 hits · 20 pts
SeverityFileLineSnippetContext
CRITICALdocs/static/search.min.js7!function(){"use strict";function e(){let e,t,n=arguments.length>0&&void 0!==arguments[0]?arguments[0]:"";return/<!-- {dCODE
CRITICALdocs/static/docsify.min.js7!function(){"use strict";function e(e){const n=Object.create(null);return function(i){const o=t(i)?i:JSON.stringify(i);rCODE
Slop Phrases3 hits · 4 pts
SeverityFileLineSnippetContext
LOW.github/ISSUE_TEMPLATE/bug-report.yml2# Before you report a bug, make sure you alreadyCOMMENT
LOW.github/ISSUE_TEMPLATE/improvement.yml2# Before you request a feature/improvement, make sure you alreadyCOMMENT
LOW.github/ISSUE_TEMPLATE/question.yml2# Before you report a question, make sure you alreadyCOMMENT