Repository Analysis

loov/lensm

Go assembly and source viewer

3.7 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of loov/lensm, a Go project with 3,694 GitHub stars. SynthScan v2.0 examined 23,811 lines of code across 224 source files, recording 83 pattern matches distributed across 3 syntactic categories. The overall adjusted score of 3.7 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.7
Adjusted Score
3.7
Raw Score
100%
Time Factor
2026-07-06
Last Push
3.7K
Stars
Go
Language
23.8K
Lines of Code
224
Files
83
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 2LOW 81

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 83 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 Block80 hits · 80 pts
SeverityFileLineSnippetContext
LOWinternal/go/src/buildcfg/exp.go41// It is not guaranteed to be canonical.COMMENT
LOWinternal/go/src/buildcfg/exp.go61 // regabiAlwaysOn is set to true on platforms where register ABI isCOMMENT
LOWinternal/go/src/goexperiment/flags.go1// Copyright 2021 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/goexperiment/flags.go21// boolean constant x and an integer constant xInt.COMMENT
LOWinternal/go/src/goexperiment/flags.go41// The code used in builds to interpret the GOEXPERIMENT variableCOMMENT
LOWinternal/go/src/goexperiment/flags.go61 BoringCrypto boolCOMMENT
LOWinternal/go/src/goexperiment/flags.go81 // This was originally reduced as part of PacerRedesign, butCOMMENT
LOWinternal/go/src/unsafeheader/unsafeheader.go1// Copyright 2020 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/archive/archive.go301 // 34:40 gidCOMMENT
LOWinternal/go/src/bisect/bisect.go1// Copyright 2023 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/bisect/bisect.go21// 3. Enable each change that the pattern says should be enabled.COMMENT
LOWinternal/go/src/bisect/bisect.go41// Then, each time a potential change is considered, the program computesCOMMENT
LOWinternal/go/src/bisect/bisect.go61// Finally, note that New returns a nil Matcher when there is no pattern,COMMENT
LOWinternal/go/src/bisect/bisect.go81// still exploring the space of possible changes and will not be showing theCOMMENT
LOWinternal/go/src/bisect/bisect.go101// provided by the [Matcher.FileLine] method.COMMENT
LOWinternal/go/src/bisect/bisect.go121// In the expression, all the + operators must appear before all the - operators.COMMENT
LOWinternal/go/src/bisect/bisect.go141// changes: the pattern specifies the changes to DISABLE and report. ThisCOMMENT
LOWinternal/go/src/bisect/bisect.go161// printed by the bisect tool to describe a change implicated in causingCOMMENT
LOWinternal/go/src/goarch/goarch.go1// Copyright 2021 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/objabi/autotype.go1// Derived from Inferno utils/6l/l.h and related files.COMMENT
LOWinternal/go/src/objabi/autotype.go21// all copies or substantial portions of the Software.COMMENT
LOWinternal/go/src/objabi/reloctype.go1// Derived from Inferno utils/6l/l.h and related files.COMMENT
LOWinternal/go/src/objabi/reloctype.go21// all copies or substantial portions of the Software.COMMENT
LOWinternal/go/src/objabi/reloctype.go81 // linker uses this as a signal that the pointed-to type informationCOMMENT
LOWinternal/go/src/objabi/reloctype.go101 // R_METHODOFF resolves to a 32-bit offset from the beginning of the sectionCOMMENT
LOWinternal/go/src/objabi/reloctype.go121 // Platform dependent relocations. Architectures with fixed width instructionsCOMMENT
LOWinternal/go/src/objabi/reloctype.go181 R_ARM64_LDST128COMMENT
LOWinternal/go/src/objabi/reloctype.go201 // simpler thread-pointer relative relocation. See table 3.26 and 3.28 in theCOMMENT
LOWinternal/go/src/objabi/reloctype.go221COMMENT
LOWinternal/go/src/objabi/reloctype.go241 // R_ADDRPOWER_DS but inserts the offset from the TOC to the address of theCOMMENT
LOWinternal/go/src/objabi/reloctype.go381 // address of a B instruction, by encoding it into the instruction.COMMENT
LOWinternal/go/src/objabi/reloctype.go401 R_XCOFFREFCOMMENT
LOWinternal/go/src/objabi/reloctype.go501 }COMMENT
LOWinternal/go/src/objabi/symkind.go1// Derived from Inferno utils/6l/l.h and related files.COMMENT
LOWinternal/go/src/objabi/symkind.go21// all copies or substantial portions of the Software.COMMENT
LOWinternal/go/src/objabi/flag.go41//COMMENT
LOWinternal/go/src/objabi/head.go1// Derived from Inferno utils/6l/l.h and related files.COMMENT
LOWinternal/go/src/objabi/pkgspecial.go1// Copyright 2023 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/objabi/pkgspecial.go21 // - Checkptr is always disabled.COMMENT
LOWinternal/go/src/abi/symtab.go1// Copyright 2023 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/abi/symtab.go21 // Entry PC of func data changed from address to offset (CL 351463).COMMENT
LOWinternal/go/src/abi/symtab.go41 // FuncFlagTopFrame indicates a function that appears at the top of its stack.COMMENT
LOWinternal/go/src/abi/escape.go1// Copyright 2024 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/abi/escape.go41// content, not the pointer.COMMENT
LOWinternal/go/src/abi/type.go1// Copyright 2023 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/abi/type.go21 Size_ uintptrCOMMENT
LOWinternal/go/src/abi/type.go81// TFlag is used by a Type to signal what extra type information isCOMMENT
LOWinternal/go/src/abi/type.go101 TFlagUncommon TFlag = 1 << 0COMMENT
LOWinternal/go/src/abi/type.go481 Elem *Type // slice element typeCOMMENT
LOWinternal/go/src/abi/type.go561 Fields []StructFieldCOMMENT
LOWinternal/go/src/abi/type.go581// methods that are defined in a different package than their type.COMMENT
LOWinternal/go/src/abi/type.go721 // and no more than one {, }, ... at each level (it cannot have both theCOMMENT
LOWinternal/go/src/abi/type.go741 TraceArgsStartAgg = 0xfeCOMMENT
LOWinternal/go/src/abi/type.go761// assume an aligned start and not use atomic operations. In the currentCOMMENT
LOWinternal/go/src/abi/abi.go1// Copyright 2020 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/abi/abi.go21type RegArgs struct {COMMENT
LOWinternal/go/src/abi/funcpc.go1// Copyright 2023 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/abi/funcpc.go21// Implemented as a compile intrinsic.COMMENT
LOWinternal/go/src/abi/stack.go1// Copyright 2023 The Go Authors. All rights reserved.COMMENT
LOWinternal/go/src/abi/stack.go21 //COMMENT
20 more matches not shown…
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMinternal/go/src/src/pos.go391// Depending on the debugger (gdb or delve) it may or may not be displayed.COMMENT
MEDIUMinternal/go/src/src/xpos.go71// gdb chooses not to display the bogus line; delve shows it with a complaint, but theCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWdata/download.sh7# Usage:COMMENT