AI Slop Code Risk Monitor

anacrolix/torrent

Name: anacrolix/torrent — Go Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Full-featured BitTorrent client package and utilities

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for anacrolix/torrent, a Go project with 6,131 GitHub stars. SynthScan examined 51,754 lines of code across 438 source files, recording 24 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.0

Adjusted Signal

1.0

Raw Pattern Score

100%

Time Factor

2026-10-28

Last Push

6.1K

Stars

Language

51.8K

Lines of Code

438

Files

Pattern Hits

2026-10-31

Scan Date

0.01

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 2.2/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 2.9/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 5.0/100 · LOW

Which changes need focused human review? 24 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 3HIGH 0MEDIUM 1LOW 20

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

Hallucination Indicators3 hits · 30 pts

Severity	File	Line	Snippet	Context
CRITICAL	peerconn.go	645	return c.PeerExtensionBytes.SupportsFast() && c.t.cl.config.Extensions.SupportsFast()	CODE
CRITICAL	peerconn.go	1229	res := c.t.cl.config.UploadRateLimiter.ReserveN(time.Now(), int(r.Length))	CODE
CRITICAL	peerconn.go	1360	return pc.t.cl.config.Extensions.GetBit(bit) && pc.PeerExtensionBytes.GetBit(bit)	CODE

Over-Commented Block20 hits · 20 pts

Severity	File	Line	Snippet	Context
LOW	config.go	121	// Upload even after there's nothing in it for us. By default uploading is	COMMENT
LOW	config.go	141	//	COMMENT
LOW	config.go	161	PeerID string	COMMENT
LOW	config.go	201	HTTPDialContext func(ctx context.Context, network, addr string) (net.Conn, error)	COMMENT
LOW	config.go	241		COMMENT
LOW	peerid_test.go	1	package torrent	COMMENT
LOW	steal-request-grace.go	1	package torrent	COMMENT
LOW	torrent.go	141	// Reserve of peers to connect to. A peer can be both here and in the	COMMENT
LOW	torrent.go	2021	// if t.haveInfo() {	COMMENT
LOW	torrent.go	2761	if t.pieceAllDirty(piece) {	COMMENT
LOW	reader.go	21	SetContext(context.Context)	COMMENT
LOW	testing.go	21	cfg.KeepAliveTimeout = time.Millisecond	COMMENT
LOW	types/peerid.go	21		COMMENT
LOW	internal/fast/fast.go	1	// Package fast implements the Allowed Fast Set generation algorithm from	COMMENT
LOW	internal/fast/fast.go	21	// small constant (mainline / libtorrent use 10).	COMMENT
LOW	internal/fast/fast_test.go	1	package fast	COMMENT
LOW	storage/interface.go	41	NewReader func() TorrentReader	COMMENT
LOW	metainfo/piece-length.go	1	// From https://github.com/jackpal/Taipei-Torrent	COMMENT
LOW	metainfo/piece-length.go	21	// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR	COMMENT
LOW	fs/torrentfs.go	1	//go:build !windows	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	torrent.go	1576	// Pending pieces is an old bitmap of stuff we want. I think it's more nuanced than that now with	COMMENT