Repository Analysis

valyala/fasthttp

Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http

3.0 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of valyala/fasthttp, a Go project with 23,414 GitHub stars. SynthScan v2.0 examined 57,243 lines of code across 162 source files, recording 197 pattern matches distributed across 3 syntactic categories. The overall adjusted score of 3.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).

3.0
Adjusted Score
3.0
Raw Score
100%
Time Factor
2026-07-11
Last Push
23.4K
Stars
Go
Language
57.2K
Lines of Code
162
Files
197
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 197

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 197 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 Block187 hits · 158 pts
SeverityFileLineSnippetContext
LOWheader.go401 h.SetContentTypeBytes(h.bufV)COMMENT
LOWheader.go421func (h *header) SetTrailer(trailer string) error {COMMENT
LOWheader.go441// Return ErrBadTrailer if contain any forbidden trailers.COMMENT
LOWheader.go481 ErrNeedMore = errors.New("fasthttp: need more data: cannot find trailing lf")COMMENT
LOWheader.go901COMMENT
LOWheader.go921 h.disableSpecialHeader = falseCOMMENT
LOWheader.go941 return origCOMMENT
LOWheader.go1141COMMENT
LOWheader.go1181//COMMENT
LOWheader.go1281// Deprecated: Use All instead.COMMENT
LOWheader.go1521//COMMENT
LOWheader.go1541// and Date headers can only be set once and will overwrite the previous value,COMMENT
LOWheader.go1561func (h *ResponseHeader) AddBytesV(key string, value []byte) {COMMENT
LOWheader.go1581COMMENT
LOWheader.go1601// Please note that the Set-Cookie header will not clear previous cookies,COMMENT
LOWheader.go1641COMMENT
LOWheader.go1681func (h *RequestHeader) SetCookieBytesKV(key, value []byte) {COMMENT
LOWheader.go1701 c := AcquireCookie()COMMENT
LOWheader.go1761}COMMENT
LOWheader.go1781func (h *RequestHeader) AddBytesK(key []byte, value string) {COMMENT
LOWheader.go1801// the Content-Type, Content-Length, Connection, Transfer-Encoding,COMMENT
LOWheader.go1821// If the header is set as a Trailer (forbidden trailers will not be set, see SetTrailer for more details),COMMENT
LOWheader.go1841 h.SetBytesKV(key, h.bufV)COMMENT
LOWheader.go1861// delete cookies before calling in order to reset cookies.COMMENT
LOWserver.go21COMMENT
LOWserver.go161 // By default standard logger from log package is used.COMMENT
LOWserver.go181 // HeaderReceived is called after receiving the header.COMMENT
LOWserver.go201 // ExpectHandler provides more control than ContinueHandler by allowingCOMMENT
LOWserver.go221COMMENT
LOWserver.go261 //COMMENT
LOWserver.go281 // the full request including body. The connection's readCOMMENT
LOWserver.go301 //COMMENT
LOWserver.go321 MaxIdleWorkerDuration time.DurationCOMMENT
LOWserver.go361 //COMMENT
LOWserver.go381 // Server accepts all the requests by default.COMMENT
LOWserver.go401COMMENT
LOWserver.go421 // Examples:COMMENT
LOWserver.go441 // set to true, the Date will not be present.COMMENT
LOWserver.go461 // StreamRequestBody enables request body streaming,COMMENT
LOWserver.go521 // ReadTimeout is the maximum duration for reading the entireCOMMENT
LOWserver.go541// CompressHandlerLevel returns RequestHandler that transparently compressesCOMMENT
LOWserver.go561 ctx.Response.zstdBody(level)COMMENT
LOWserver.go601//COMMENT
LOWserver.go641 //COMMENT
LOWserver.go721// The connection c must not be used after returning from the handler, if KeepHijackedConns is disabled.COMMENT
LOWserver.go741// Server limits such as Concurrency, ReadTimeout, WriteTimeout, etc.COMMENT
LOWserver.go761 ctx.hijackNoResponse = noResponseCOMMENT
LOWserver.go841 ConnectionState() tls.ConnectionStateCOMMENT
LOWserver.go1081// See also PostArgs, FormValue and FormFile.COMMENT
LOWserver.go1101// Returns ErrNoMultipartForm if request's content-typeCOMMENT
LOWserver.go1121// multipart body size to maxBodySize bytes.COMMENT
LOWserver.go1221// - POST or PUT body.COMMENT
LOWserver.go1421 ctx.SetContentType(contentType)COMMENT
LOWserver.go1441// strLocation = []byte("Location") // Put this with your top level var () declarations.COMMENT
LOWserver.go1461// - StatusPermanentRedirect (308)COMMENT
LOWserver.go1501 ctx.Response.SetBodyString(body)COMMENT
LOWserver.go1521// WARNING: do not pass any user supplied paths to this function!COMMENT
LOWserver.go1541 ServeFileLiteral(ctx, path)COMMENT
LOWserver.go1601// PostBody returns POST request body.COMMENT
LOWserver.go1621}COMMENT
127 more matches not shown…
Example Usage Blocks8 hits · 12 pts
SeverityFileLineSnippetContext
LOWfasthttpproxy/http.go13// Example usage:COMMENT
LOWfasthttpproxy/http.go26// Example usage:COMMENT
LOWfasthttpproxy/http.go40// Example usage:COMMENT
LOWfasthttpproxy/http.go53// Example usage:COMMENT
LOWfasthttpproxy/proxy_env.go17// Example usage:COMMENT
LOWfasthttpproxy/proxy_env.go30// Example usage:COMMENT
LOWfasthttpproxy/socks5.go11// Example usage:COMMENT
LOWfasthttpproxy/socks5.go25// Example usage:COMMENT
TODO Padding2 hits · 3 pts
SeverityFileLineSnippetContext
LOWtcplisten/tcplisten_other.go10 // TODO: implement SO_ACCEPTFILTER:dataready hereCOMMENT
LOWtcplisten/tcplisten_other.go15 // TODO: implement TCP_FASTOPEN when it will be readyCOMMENT