Repository Analysis

stretchr/testify

A toolkit with common assertions and mocks that plays nicely with the standard library

3.2 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of stretchr/testify, a Go project with 26,182 GitHub stars. SynthScan v2.0 examined 30,460 lines of code across 77 source files, recording 98 pattern matches distributed across 2 syntactic categories. The overall adjusted score of 3.2 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.2
Adjusted Score
3.2
Raw Score
100%
Time Factor
2026-06-24
Last Push
26.2K
Stars
Go
Language
30.5K
Lines of Code
77
Files
98
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 0LOW 98

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 98 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 Block97 hits · 97 pts
SeverityFileLineSnippetContext
LOW.ci.ghactions.sh1#!/usr/bin/env bashCOMMENT
LOWdoc.go1// Module testify is a set of packages that provide many tools for testifying that your code will behave as you intend.COMMENT
LOWmock/doc.go1// Package mock provides a system by which it is possible to mock your objectsCOMMENT
LOWmock/doc.go21//COMMENT
LOWmock/doc.go41//COMMENT
LOWmock/mock.go201//COMMENT
LOWmock/mock.go281}COMMENT
LOWmock/mock.go781*/COMMENT
LOWmock/mock.go801// func anyString interface{} {COMMENT
LOWmock/mock.go821COMMENT
LOWmock/mock.go901 }COMMENT
LOWrequire/doc.go1// Package require implements the same assertions as the assert package butCOMMENT
LOWrequire/doc.go21//COMMENT
LOWrequire/require_forward.go101//COMMENT
LOWrequire/require_forward.go121//COMMENT
LOWrequire/require_forward.go161COMMENT
LOWrequire/require_forward.go181// }COMMENT
LOWrequire/require_forward.go341// The condition is considered "met" if no errors are raised in a tick.COMMENT
LOWrequire/require_forward.go361COMMENT
LOWrequire/require_forward.go501//COMMENT
LOWrequire/require_forward.go1161// NotElementsMatchf asserts that the specified listA(array, slice...) is NOT equal to specifiedCOMMENT
LOWrequire/require_forward.go1381// Both arguments must be pointer variables. Pointer variable sameness isCOMMENT
LOWrequire/require_forward.go1561// Samef asserts that two pointers reference the same object.COMMENT
LOWrequire/require_forward.go1581// a.Subset([1, 2, 3], {1: "one", 2: "two"})COMMENT
LOWrequire/require_forward.go1661 h.Helper()COMMENT
LOWrequire/require_forward.go1681 h.Helper()COMMENT
LOWrequire/require.go121//COMMENT
LOWrequire/require.go141}COMMENT
LOWrequire/require.go421// function can use the CollectT to call other assertions.COMMENT
LOWrequire/require.go441 returnCOMMENT
LOWrequire/require.go2101 if h, ok := t.(tHelper); ok {COMMENT
LOWinternal/difflib/difflib.go1// Package difflib is a partial port of Python difflib module.COMMENT
LOWinternal/difflib/difflib.go61// the longest contiguous matching subsequence that contains no "junk"COMMENT
LOWinternal/difflib/difflib.go181 _, ok := m.bJunk[s]COMMENT
LOWinternal/difflib/difflib.go201// starts earliest in a, and of all those maximal matching blocks thatCOMMENT
LOWinternal/difflib/difflib.go281COMMENT
LOWinternal/difflib/difflib.go341 nonAdjacent = append(nonAdjacent, Match{i1, j1, k1})COMMENT
LOWinternal/difflib/difflib_test.go141 // and:COMMENT
LOWinternal/spew/config.go21 "fmt"COMMENT
LOWinternal/spew/config.go41 // set this to a tab with "\t" or perhaps two spaces with " ".COMMENT
LOWinternal/spew/config.go61 // with a pointer receiver could technically mutate the value, however,COMMENT
LOWinternal/spew/config.go81 // means it will print the results of invoking the custom error or StringerCOMMENT
LOWinternal/spew/config.go101}COMMENT
LOWinternal/spew/config.go121// the number of bytes written and any write error encountered. SeeCOMMENT
LOWinternal/spew/config.go141}COMMENT
LOWinternal/spew/config.go161// fmt.Print(c.NewFormatter(a), c.NewFormatter(b))COMMENT
LOWinternal/spew/config.go181// NewFormatter for formatting details.COMMENT
LOWinternal/spew/config.go201// Sprintf is a wrapper for fmt.Sprintf that treats each argument as if it wereCOMMENT
LOWinternal/spew/dumpnocgo_test.go1// Copyright (c) 2013 Dave Collins <dave@davec.name>COMMENT
LOWinternal/spew/dumpcgo_test.go1// Copyright (c) 2013-2016 Dave Collins <dave@davec.name>COMMENT
LOWinternal/spew/bypass.go1// Copyright (c) 2015-2016 Dave Collins <dave@davec.name>COMMENT
LOWinternal/spew/internalunsafe_test.go1// Copyright (c) 2013-2016 Dave Collins <dave@davec.name>COMMENT
LOWinternal/spew/common.go81// type the passed reflect.Value represents and outputes the result to Writer w.COMMENT
LOWinternal/spew/bypasssafe.go1// Copyright (c) 2015-2016 Dave Collins <dave@davec.name>COMMENT
LOWinternal/spew/dump.go181 // Try to use existing uint8 slices and fall back to convertingCOMMENT
LOWinternal/spew/spew.go21 "io"COMMENT
LOWinternal/spew/spew.go41// This function is shorthand for the following syntax:COMMENT
LOWinternal/spew/spew.go61// passed with a default Formatter interface returned by NewFormatter. SeeCOMMENT
LOWinternal/spew/spew.go81}COMMENT
LOWinternal/spew/spew.go101//COMMENT
37 more matches not shown…
Structural Annotation Overuse1 hit · 2 pts
SeverityFileLineSnippetContext
LOWREADME.md141// NOTE: This method is not being tested here, code that uses this object is.COMMENT