AI Slop Code Risk Monitor

go-resty/resty

SlopCodeMonitor badge for go-resty/resty Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Simple HTTP, REST, and SSE client library for Go

3.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for go-resty/resty, a Go project with 11,824 GitHub stars. SynthScan examined 30,634 lines of code across 48 source files, recording 114 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 3.0 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

3.0
Adjusted Signal
3.0
Raw Pattern Score
100%
Time Factor
2026-10-19
Last Push
11.8K
Stars
Go
Language
30.6K
Lines of Code
48
Files
114
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 14.0/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 114 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 17.0/100 · LOW

Which changes need focused human review? 114 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 0LOW 114

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 114 distinct pattern matches across 2 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block112 hits · 90 pts
SeverityFileLineSnippetContext
LOWhedging.go41// - 50ms delay between requestsCOMMENT
LOWhedging.go61 delay: 50 * time.Millisecond, // delay between requestsCOMMENT
LOWmultipart.go41 // Reader is the [io.Reader] source for multipart upload. It is optional ifCOMMENT
LOWsse.go101// SetURL("https://example.com/events").COMMENT
LOWsse.go281//COMMENT
LOWsse.go321//COMMENT
LOWsse.go461// },COMMENT
LOWsse.go481//COMMENT
LOWsse.go521// func(e any) {COMMENT
LOWstream.go21)COMMENT
LOWstream.go41 // See [Client.AddContentTypeEncoder].COMMENT
LOWresponse.go61 return ""COMMENT
LOWresponse.go81// fmt.Println(err, res)COMMENT
LOWresponse.go141COMMENT
LOWrequest.go181 return rrCOMMENT
LOWrequest.go201func (r *Request) SetHeader(header, value string) *Request {COMMENT
LOWrequest.go221 return rCOMMENT
LOWrequest.go241COMMENT
LOWrequest.go261//COMMENT
LOWrequest.go281//COMMENT
LOWrequest.go301//COMMENT
LOWrequest.go321//COMMENT
LOWrequest.go341func (r *Request) SetQueryParams(params map[string]string) *Request {COMMENT
LOWrequest.go381 }COMMENT
LOWrequest.go421 }COMMENT
LOWrequest.go441// Password: "welcome2resty",COMMENT
LOWrequest.go461// client.R().COMMENT
LOWrequest.go481//COMMENT
LOWrequest.go501// fmt.Println(response.Result().(*AuthToken))COMMENT
LOWrequest.go541 r.multipartFields = append(r.multipartFields, &MultipartField{COMMENT
LOWrequest.go621 })COMMENT
LOWrequest.go641// FileName: "upload-file-2.json",COMMENT
LOWrequest.go701// SetBasicAuth method sets the basic authentication header in the current HTTP request.COMMENT
LOWrequest.go721// For Example: To set auth token BC594900518B4F7EAC75BD37F019E08FBC594900518B4F7EAC75BD37F019E08FCOMMENT
LOWrequest.go741// // The outcome will be -COMMENT
LOWrequest.go761 r.HeaderAuthorizationKey = kCOMMENT
LOWrequest.go781 r.ResponseSaveFileName = fileCOMMENT
LOWrequest.go801COMMENT
LOWrequest.go821 return rCOMMENT
LOWrequest.go841// that provides an ability to do unlimited reads.COMMENT
LOWrequest.go861// URL - /v1/users/{userId}/detailsCOMMENT
LOWrequest.go881//COMMENT
LOWrequest.go901}COMMENT
LOWrequest.go921 for p, v := range params {COMMENT
LOWrequest.go941//COMMENT
LOWrequest.go961// Composed URL - /v1/users/12345/detailsCOMMENT
LOWrequest.go981// "path": "groups/developers",COMMENT
LOWrequest.go1041// SetCookies method sets an array of cookies in the current request instance.COMMENT
LOWrequest.go1061}COMMENT
LOWrequest.go1101// AddRetryConditions method adds one or more retry condition functions into the request.COMMENT
LOWrequest.go1121//COMMENT
LOWrequest.go1141}COMMENT
LOWrequest.go1221// SetTrace method is used to turn on/off the trace capability at the request level.COMMENT
LOWrequest.go1241// By default, Resty does not log the curl command in the debug log since it has the potentialCOMMENT
LOWrequest.go1301//COMMENT
LOWrequest.go1321}COMMENT
LOWrequest.go1461//COMMENT
LOWrequest.go1661 // Unblock Client.Do / RoundTrip waiting on the request body pipe.COMMENT
LOWrequest.go1741 rr.bodyBuf = acquireBuffer()COMMENT
LOWrate_limiter.go21// The limiters shipped with Resty wrap the context error alongside this sentinel,COMMENT
52 more matches not shown…
Structural Annotation Overuse2 hits · 3 pts
SeverityFileLineSnippetContext
LOWsse.go238// NOTE: This method overwrites existing [http.Transport.TLSClientConfig]COMMENT
LOWclient.go1637// NOTE: This method overwrites existing [http.Transport.TLSClientConfig]COMMENT