Repository Analysis

chubin/wttr.in

:partly_sunny: The right way to check the weather

5.4 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of chubin/wttr.in, a Go project with 30,098 GitHub stars. SynthScan v2.0 examined 35,681 lines of code across 579 source files, recording 76 pattern matches distributed across 7 syntactic categories. The overall adjusted score of 5.4 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).

5.4
Adjusted Score
5.4
Raw Score
100%
Time Factor
2026-07-08
Last Push
30.1K
Stars
Go
Language
35.7K
Lines of Code
579
Files
76
Pattern Hits
2026-07-14
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

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

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

Decorative Section Separators41 hits · 141 pts
SeverityFileLineSnippetContext
MEDIUMbuild.sh4# ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMbuild.sh12# ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMbuild.sh14# ─── Configuration ───────────────────────────────────────────────────────────COMMENT
MEDIUMbuild.sh20# ─── Font configuration ───────────────────────────────────────────────────────COMMENT
MEDIUMbuild.sh31# ─── Asset roots (non-font) ───────────────────────────────────────────────────COMMENT
MEDIUMbuild.sh46# ─── Helper functions ────────────────────────────────────────────────────────COMMENT
MEDIUMbuild.sh110# ─── Actions ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMbuild.sh177# ─── Main dispatcher ─────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/render.go11// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/render.go13// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/render_solar.go133// ────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/render_solar.go136// ────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go17// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go19// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go44// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go46// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go83// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go86// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go113// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/oneline.go115// ──────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/data_parse.go55 // ── Parse numeric fields with safe defaults ────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/data_parse.go73 // ── Description (prefer translated lang_xx if present) ─────────────────────COMMENT
MEDIUMinternal/renderer/oneline/data_parse.go88 // ── Observation time ───────────────────────────────────────────────────────COMMENT
MEDIUMinternal/renderer/oneline/data_parse.go94 // ── Location fallback ──────────────────────────────────────────────────────COMMENT
MEDIUMinternal/location/cache.go61 // ── Persistent storage ───────────────────────────────COMMENT
MEDIUMinternal/location/cache.go66 // ── Fast in-memory cache ─────────────────────────────COMMENT
MEDIUMinternal/location/cache.go70 // ── Batch writer ─────────────────────────────────────COMMENT
MEDIUMinternal/location/cache.go76 // ── Synchronization ──────────────────────────────────COMMENT
MEDIUMinternal/location/cache.go141// ── Batch Writer ─────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/location/cache.go386// ── LRU helpers ────────────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/location/cache.go426// ── Utility functions ──────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/server/config.go79# ================================================COMMENT
MEDIUMinternal/server/config.go81# ================================================COMMENT
MEDIUMinternal/server/config.go88# ================================================COMMENT
MEDIUMinternal/server/config.go90# ================================================COMMENT
MEDIUMinternal/weather/weather.go260 // ── Determine location string ────────────────────────────────────────COMMENT
MEDIUMinternal/weather/weather.go323 // ── Geocode ───────────────────────────────────────────────────────────COMMENT
MEDIUMinternal/weather/weather.go345 // ── Build Query ───────────────────────────────────────────────────────COMMENT
MEDIUMinternal/weather/weather.go376 // ── Fetch weather ─────────────────────────────────────────────────────COMMENT
MEDIUMinternal/weather/weather.go398 // ── Filling up Query ───────────────────────────────────────────────────────COMMENT
MEDIUMinternal/weather/weather.go402 // ── Render + Format ───────────────────────────────────────────────────COMMENT
Verbosity Indicators9 hits · 15 pts
SeverityFileLineSnippetContext
LOWinternal/renderer/oneline/render.go183 // Step 1: Get symbolic name from code (e.g. "116" → "PartlyCloudy")COMMENT
LOWinternal/renderer/oneline/render.go189 // Step 2: Look up the plain ASCII-style symbolCOMMENT
LOWinternal/query/queryparser.go32 // Step 1: use the existing parser to get validated map[string]stringCOMMENT
LOWinternal/query/fromrequest.go20 // Step 1: Extract components from the URL pathCOMMENT
LOWinternal/query/fromrequest.go35 // Step 2: Process domain name for VIEW or LANGCOMMENT
LOWinternal/query/fromrequest.go50 // Step 3: Process the first path component for VIEW or LANG if not set by domainCOMMENT
LOWinternal/query/fromrequest.go61 // Step 4: Extract location and format from the pathCOMMENT
LOWinternal/query/fromrequest.go90 // Step 5: Set default language from header if not set by domain or URLCOMMENT
LOWinternal/query/fromrequest.go113 // Step 6: Set User-Agent from header. Output defaulting based on theCOMMENT
Structural Annotation Overuse9 hits · 15 pts
SeverityFileLineSnippetContext
LOWinternal/renderer/oneline/render.go183 // Step 1: Get symbolic name from code (e.g. "116" → "PartlyCloudy")COMMENT
LOWinternal/renderer/oneline/render.go189 // Step 2: Look up the plain ASCII-style symbolCOMMENT
LOWinternal/query/queryparser.go32 // Step 1: use the existing parser to get validated map[string]stringCOMMENT
LOWinternal/query/fromrequest.go20 // Step 1: Extract components from the URL pathCOMMENT
LOWinternal/query/fromrequest.go35 // Step 2: Process domain name for VIEW or LANGCOMMENT
LOWinternal/query/fromrequest.go50 // Step 3: Process the first path component for VIEW or LANG if not set by domainCOMMENT
LOWinternal/query/fromrequest.go61 // Step 4: Extract location and format from the pathCOMMENT
LOWinternal/query/fromrequest.go90 // Step 5: Set default language from header if not set by domain or URLCOMMENT
LOWinternal/query/fromrequest.go113 // Step 6: Set User-Agent from header. Output defaulting based on theCOMMENT
Over-Commented Block14 hits · 14 pts
SeverityFileLineSnippetContext
LOWbuild.sh1#!/usr/bin/env bashCOMMENT
LOWinternal/renderer/oneline/oneline.go21type RenderFunc func(ctx *RenderContext) stringCOMMENT
LOWinternal/renderer/oneline/oneline.go201// If a percent-encoded sequence is invalid (e.g., not a valid hex number or incomplete),COMMENT
LOWinternal/renderer/v2/block_temperature_colorized.go141 // lastT := data[len(data)-1]COMMENT
LOWinternal/cache/config.go1// internal/cache/config.goCOMMENT
LOWinternal/weather/weather.go41}COMMENT
LOWinternal/weather/cache.go21 // This should clear any in-progress state for the same key.COMMENT
LOWinternal/query/doc.go1// Package query provides configuration-driven parsing and validation ofCOMMENT
LOWinternal/query/doc.go21// parsed, err := query.ParseQueryString("lang=fr&format=3&T&0pq", config)COMMENT
LOWinternal/query/fromrequest.go201COMMENT
LOWinternal/ip/ip.go61 db.UseErrorParser()COMMENT
LOWinternal/domain/models.go1// Package domain contains the core domain models and data structuresCOMMENT
LOWinternal/domain/models.go81 // Useful for debugging and future cache policy decisions.COMMENT
LOWshare/defs/options/options.yaml1query_options:COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMinternal/renderer/v1/testdata/update_golden.sh24# Read test cases using jq (more robust than pure bash)COMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWbuild.sh6# Usage:COMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWinternal/renderer/v1/testdata/update_golden.sh17# Check if server is runningCOMMENT