1.4

Adjusted Signal

1.4

Raw Pattern Score

100%

Time Factor

2026-11-01

Last Push

1.7K

Stars

Language

87.8K

Lines of Code

179

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

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 3.7/100 · LOW

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

PR Review Velocity Impact 6.9/100 · LOW

Which changes need focused human review? 62 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 1MEDIUM 29LOW 32

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 62 distinct pattern matches across 8 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.

Decorative Section Separators24 hits · 66 pts

Severity	File	Line	Snippet	Context
MEDIUM	internal/modify/apply_test.go	431	// ─── BuildSnapshot ───────────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	477	// ─── BuildPlan ───────────────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	555	// ─── ApplyPlan: Drop ─────────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	623	// ─── ApplyPlan: FoldDown ─────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	693	// ─── ApplyPlan: FoldUp ───────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	766	// ─── ApplyPlan: Rename ───────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	823	// ─── ApplyPlan: Reorder ──────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	901	// ─── ApplyPlan: Mixed Drop and Fold ─────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	990	// ─── ApplyPlan: Conflict During Rebase ───────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1047	// ─── ApplyPlan: Conflict During CherryPick ───────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1107	// ─── ContinueApply: Multi-Stack Finds Correct Stack ─────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1179	// ─── Unwind ──────────────────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1274	// ─── ApplyPlan: No-op (empty plan) ──────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1331	// ─── ApplyPlan: Drop with no PR ─────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1376	// ─── ContinueApply ──────────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1504	// ─── Unwind with active rebase ──────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1558	// ─── Unwind with active cherry-pick ─────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1615	// ─── ContinueApply: subsequent conflict after fold-down is a rebase ─────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1862	// ─── Unwind restores renamed branch ─────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	1915	// ─── ApplyPlan: State file transitions for remote stack ─────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	2113	// ─── resolveCheckoutBranch ──────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	2445	// ─── ApplyPlan: Checkout behavior after drop ────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	2583	// ─── BuildPlan: Insert ──────────────────────────────────────────────────────	COMMENT
MEDIUM	internal/modify/apply_test.go	2632	// ─── ApplyPlan: Insert ──────────────────────────────────────────────────────	COMMENT

Over-Commented Block20 hits · 20 pts

Severity	File	Line	Snippet	Context
LOW	cmd/submit.go	581	func humanize(s string) string {	COMMENT
LOW	cmd/link.go	161	// Create/update mode: create a new stack or additively update the stack	COMMENT
LOW	cmd/checkout.go	361	return nil, "", ErrAPIFailure	COMMENT
LOW	cmd/utils.go	301	}	COMMENT
LOW	cmd/utils.go	521	// When the stack has a remote ID, the stack API is the source of truth: the	COMMENT
LOW	cmd/utils.go	2041		COMMENT
LOW	internal/tui/submitview/mousefilter.go	21	// run of real keystrokes. Real SGR mouse bodies are far shorter than this.	COMMENT
LOW	internal/tui/submitview/types.go	1	// Package submitview implements the interactive single-screen TUI used by	COMMENT
LOW	internal/tui/shared/header.go	41	IconStyle *lipgloss.Style // optional override; nil uses default HeaderInfoStyle (accent)	COMMENT
LOW	internal/tui/shared/logo.go	101	// graphics live in a layer the text renderer cannot clear, so callers must emit	COMMENT
LOW	internal/tui/mergeview/types.go	1	// Package mergeview implements the interactive wizard used by `gh stack merge`.	COMMENT
LOW	internal/tui/mergeview/types.go	81	// StackNumber is the repo-scoped stack number, shown in the header.	COMMENT
LOW	internal/github/merge_async.go	21		COMMENT
LOW	internal/github/merge_async.go	201	}	COMMENT
LOW	internal/theme/theme.go	1	// Package theme defines gh-stack's GitHub-branded, background-aware color	COMMENT
LOW	internal/theme/theme.go	41	// keys, the description scrollbar thumb. The full-screen TUIs paint it as	COMMENT
LOW	internal/theme/theme.go	141	}	COMMENT
LOW	internal/theme/canvas.go	61	// (tea.WithOutput) that paints the GitHub canvas while the program is on the	COMMENT
LOW	internal/git/git.go	361	// ClearRemote removes the gh-stack.remote git config entry.	COMMENT
LOW	docs/src/content/docs/guides/workflows.md	421		COMMENT

Structural Annotation Overuse6 hits · 11 pts

Severity	File	Line	Snippet	Context
LOW	cmd/checkout.go	326	// Step 1: Find the stack containing the target PR via the list endpoint's	COMMENT
LOW	cmd/checkout.go	342	// Step 2: Fetch PR details for every PR in the remote stack	COMMENT
LOW	internal/modify/apply.go	226	// Step 6: Replay each active branch's original commit range onto its new parent.	COMMENT
LOW⚡	docs/src/content/docs/guides/ui.md	26	### Step 1: Create the first PR normally	COMMENT
LOW⚡	docs/src/content/docs/guides/ui.md	32	### Step 2: Create subsequent PRs and add them to the stack	COMMENT
LOW⚡	docs/src/content/docs/guides/ui.md	38	### Step 3: Confirm the stack	COMMENT

Self-Referential Comments4 hits · 10 pts

Severity	File	Line	Snippet	Context
MEDIUM	cmd/alias.go	35	Example: ` # Create the default 'gs' alias	CODE
MEDIUM	cmd/alias.go	38	# Create a custom alias	COMMENT
MEDIUM	cmd/init.go	36	Example: ` # Create a stack with a new branch	CODE
MEDIUM	cmd/init.go	39	# Create a multi-layer stack at once	COMMENT

Synthetic Comment Markers1 hit · 8 pts

Severity	File	Line	Snippet	Context
HIGH	internal/tui/submitview/screen.go	565	// batch submit as requested and exits. If any included branch has an empty	COMMENT

Verbosity Indicators3 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	cmd/checkout.go	326	// Step 1: Find the stack containing the target PR via the list endpoint's	COMMENT
LOW	cmd/checkout.go	342	// Step 2: Fetch PR details for every PR in the remote stack	COMMENT
LOW	internal/modify/apply.go	226	// Step 6: Replay each active branch's original commit range onto its new parent.	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	internal/tui/mergeview/view.go	139	// seamless segmented bar without any Powerline glyph.	COMMENT

Fake / Example Data3 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	internal/git/gitops_test.go	720	gitExec(t, cloneDir, "config", "user.email", "test@test.com")	CODE
LOW	internal/git/gitops_test.go	767	gitExec(t, cloneDir, "config", "user.email", "test@test.com")	CODE
LOW	internal/git/gitops_test.go	800	gitExec(t, dir, "config", "user.email", "test@test.com")	CODE

github/gh-stack

Open-Source Code Quality, Security and Technical Debt Review