Home / Ataraxy-Labs / sem
Repository Analysis

Ataraxy-Labs/sem

Semantic version control => entity-level diffs, blame, and impact analysis on top of git. 28 languages via tree-sitter. Built for coding agents.

5.6 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of Ataraxy-Labs/sem, a Rust project with 3,321 GitHub stars. SynthScan v2.0 examined 133,740 lines of code across 223 source files, recording 645 pattern matches distributed across 13 syntactic categories. The overall adjusted score of 5.6 places this repository in the Low AI signal 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).

5.6
Adjusted Score
5.6
Raw Score
100%
Time Factor
2026-08-28
Last Push
3.3K
Stars
Rust
Language
133.7K
Lines of Code
223
Files
645
Pattern Hits
2026-08-29
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 90LOW 555

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 645 distinct pattern matches across 13 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 Block492 hits · 412 pts
SeverityFileLineSnippetContext
LOWcrates/sem-plugin/src/bindings.rs981 pub use alloc_crate::alloc;COMMENT
LOWcrates/sem-mcp/tests/mcp_protocol.rs1//! RED tests proving three MCP server gaps, run against the real `sem-mcp`COMMENT
LOWcrates/sem-mcp/src/cache.rs1//! Thin re-export of `sem_core::persist::disk_cache`.COMMENT
LOWcrates/sem-mcp/src/cache.rs21//! `DiskCache` implementation here used to.COMMENT
LOWcrates/sem-mcp/src/cache.rs41use rusqlite::{params, Connection, OptionalExtension, Transaction};COMMENT
LOWcrates/sem-mcp/src/cloud.rs1//! Cloud routing for the MCP tools.COMMENT
LOWcrates/sem-mcp/src/lib.rs41// production scale (the socket accepted connections and never answered),COMMENT
LOWcrates/sem-mcp/src/agent_review.rs1//! Client for the sem-cloud "agent review listener" API.COMMENT
LOWcrates/sem-mcp/src/agent_review.rs121 }COMMENT
LOWcrates/sem-mcp/src/agent_review.rs161/// existing `agent_review::unanswerable_result` / `agent_review::review_gone_result`COMMENT
LOWcrates/sem-mcp/src/agent_review.rs261 let truncated: String = text.chars().take(max_chars).collect();COMMENT
LOWcrates/sem-mcp/src/server.rs101/// [`CachedGraph`]) it's checked first and skips [`CachedGraph`]'sCOMMENT
LOWcrates/sem-mcp/src/server.rs121/// a `std::sync::Mutex`, not the atomic-UPDATE-claim idiom a job queue wouldCOMMENT
LOWcrates/sem-mcp/src/server.rs441 /// Answers "every entity under this directory" from the query index: noCOMMENT
LOWcrates/sem-mcp/src/server.rs3621 );COMMENT
LOWcrates/sem-mcp/src/watch.rs1//! Filesystem watcher that keeps the MCP server's in-memory entity graph hot.COMMENT
LOWcrates/sem-mcp/src/review_protocol.rs1//! Centralized "loop discipline" text for the review-listener toolsCOMMENT
LOWcrates/sem-cli/tests/impact_direct_deps.rs461 );COMMENT
LOWcrates/sem-cli/tests/review_listen_dry_run.rs1//! `sem review listen --dry-run` — drives the real `sem` binary against aCOMMENT
LOWcrates/sem-cli/tests/support/mod.rs1//! Shared stub-server plumbing for `sem`'s cloud-facing integration testsCOMMENT
LOWcrates/sem-cli/src/telemetry.rs1//! Anonymous command-usage telemetry — three modes, local by default.COMMENT
LOWcrates/sem-cli/src/build_cache.rs1//! The build plane's warm-cache tier, and `index.sem`'s writer (COMMENT
LOWcrates/sem-cli/src/build_cache.rs41// PartialCache` had here before moved its definition to `sem-core`.COMMENT
LOWcrates/sem-cli/src/build_cache.rs121/// experiment measured every other verb byte-identical and equally fast fromCOMMENT
LOWcrates/sem-cli/src/hyperlinks.rs1//! Optional OSC8 terminal hyperlinks for entity references.COMMENT
LOWcrates/sem-cli/src/main.rs181 #[arg(long)]COMMENT
LOWcrates/sem-cli/src/main.rs221 file: Option<String>,COMMENT
LOWcrates/sem-cli/src/main.rs281COMMENT
LOWcrates/sem-cli/src/main.rs341 /// List only entities of these kinds (repeatable), e.g. --only function --only struct.COMMENT
LOWcrates/sem-cli/src/main.rs401 /// Start the MCP server (stdin/stdout transport)COMMENT
LOWcrates/sem-cli/src/corpus_columns.rs1//! The build's **one** post-graph corpus read, and the columns derived fromCOMMENT
LOWcrates/sem-cli/src/corpus_columns.rs21//! `Xxh3::new().update(bytes).digest()` (`incremental.rs:440`) — the sameCOMMENT
LOWcrates/sem-cli/src/corpus_columns.rs41//! distinction, so a non-UTF-8 file still gets its `cache.db` row and stillCOMMENT
LOWcrates/sem-cli/src/corpus_columns.rs61/// order-sensitive by SQL statement order and the bit-identical gate coversCOMMENT
LOWcrates/sem-cli/src/corpus_columns.rs181 .map(|row| (row.path.as_str(), row.imports.clone()))COMMENT
LOWcrates/sem-cli/src/corpus_columns.rs201 /// incremental save path calls it), `read_to_string` +COMMENT
LOWcrates/sem-cli/src/commands/hook.rs1//! `sem hook prompt-submit` — the prompt-time prefetch, compiled.COMMENT
LOWcrates/sem-cli/src/commands/review.rs1//! `sem review listen <diff-id-or-url>` — the one-command agent attach.COMMENT
LOWcrates/sem-cli/src/commands/graph.rs141/// - `{"entities":[…],"edges":[…],"stats":{"entityCount":N,"edgeCount":M}}`COMMENT
LOWcrates/sem-cli/src/commands/graph.rs321 CacheSourceScope::CustomCOMMENT
LOWcrates/sem-cli/src/commands/graph.rs361COMMENT
LOWcrates/sem-cli/src/commands/graph.rs421}COMMENT
LOWcrates/sem-cli/src/commands/graph.rs461 }COMMENT
LOWcrates/sem-cli/src/commands/graph.rs681/// What a cold miss writes. The three variants are the three artifact sets aCOMMENT
LOWcrates/sem-cli/src/commands/graph.rs701/// incremental rebuild instead of a full one.COMMENT
LOWcrates/sem-cli/src/commands/graph.rs821 );COMMENT
LOWcrates/sem-cli/src/commands/cloud.rs61}COMMENT
LOWcrates/sem-cli/src/commands/cloud.rs581 /// How the server will handle caller/callee relations for this snapshot:COMMENT
LOWcrates/sem-cli/src/commands/query.rs1//! `sem find` / `sem callers` / `sem refs` — query verbs that answer directlyCOMMENT
LOWcrates/sem-cli/src/commands/query.rs141/// transitive walk, `sem graph`'s whole-repo dump, `sem context`'s subgraph).COMMENT
LOWcrates/sem-cli/src/commands/query.rs181 defs: Vec<EntityInfo>,COMMENT
LOWcrates/sem-cli/src/commands/mod.rs61COMMENT
LOWcrates/sem-cli/src/commands/mod.rs101 // an already-absolute `path` must be canonicalized the sameCOMMENT
LOWcrates/sem-cli/src/commands/mod.rs481COMMENT
LOWcrates/sem-cli/src/commands/impact.rs41 pub dependents: Vec<EntityInfo>,COMMENT
LOWcrates/sem-cli/src/commands/impact.rs101 }COMMENT
LOWcrates/sem-cli/src/commands/impact.rs361 timings.mark("cli_output_serialization");COMMENT
LOWcrates/sem-cli/src/commands/impact.rs381/// query from being answered against the wrong entity. For a name carryingCOMMENT
LOWcrates/sem-cli/src/commands/impact.rs441 };COMMENT
LOWcrates/sem-cli/src/commands/impact.rs521/// callers of an entity, via `callers_of` instead of `refs_of`. `Dependents`COMMENT
432 more matches not shown…
Decorative Section Separators83 hits · 246 pts
SeverityFileLineSnippetContext
MEDIUMbench/agent-accuracy.py28# ── Config ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMbench/agent-accuracy.py65# ── Helpers ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMbench/agent-accuracy.py130# ── Scoring ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMbench/agent-accuracy.py183# ── API ──────────────────────────────────────────────────────────────────────COMMENT
MEDIUMbench/agent-accuracy.py237# ── Main ─────────────────────────────────────────────────────────────────────COMMENT
MEDIUMbench/agent-accuracy.py320 # ── Summary ──────────────────────────────────────────────────────────────COMMENT
MEDIUMbench/agent-accuracy.py357 # ── Write results ────────────────────────────────────────────────────────COMMENT
MEDIUMbench/agent-accuracy.py373 # ── Update HTML ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cloud-client/src/lib.rs23// ─── Credentials ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cloud-client/src/lib.rs67// ─── Cloud API Response Types ────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cloud-client/src/lib.rs224// ─── Repo Cache ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cloud-client/src/lib.rs329// ─── URL Normalization ───────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cloud-client/src/lib.rs380// ─── CloudClient ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-mcp/src/agent_review.rs42// ─── Config ──────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-mcp/src/agent_review.rs90// ─── Errors ──────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-mcp/src/agent_review.rs165// ─── Wire types ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-mcp/src/agent_review.rs301// ─── Client ──────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs26// ─── Credentials ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs70// ─── Cloud conversion nudge ─────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs148// ─── sem login ────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs212// ─── sem login --github ──────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs365// ─── sem logout ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs413// ─── sem whoami ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs470// ─── Cloud API Response Types ────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs616// ─── Repo Cache ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs681// ─── URL Normalization ───────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs750// ─── CloudClient ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs1261// ─── try_cloud_* helpers ─────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/cloud.rs1750// ─── Helper to convert CloudEntityBrief to JSON ─────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/update.rs22// ─── Update notification ─────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/update.rs154// ─── sem update ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs22// ─── Consent state ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs108// ─── Public consent queries (used by the cloud routing path) ────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs146// ─── Outbound request ledger ────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs174// ─── Helpers ────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs228// ─── sem cloud enable ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs319// ─── sem cloud share ────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs404// ─── sem cloud list ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs470// ─── sem cloud status ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs524// ─── sem cloud preview ──────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs583// ─── sem cloud log ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs623// ─── sem cloud never ────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs645// ─── sem cloud forget ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/consent.rs688// ─── Passive discovery tip ──────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/repos.rs54// ─── Cloud section ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/repos.rs128// ─── Local section ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-cli/src/commands/repos.rs294// ─── Output helpers ──────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/tests/scope_resolve_bench.rs1493// ═══════════════════════════════════════════════════════════════════COMMENT
MEDIUMcrates/sem-core/tests/scope_resolve_bench.rs1495// ═══════════════════════════════════════════════════════════════════COMMENT
MEDIUMcrates/sem-core/tests/scope_resolve_bench.rs1837// ═══════════════════════════════════════════════════════════════════COMMENT
MEDIUMcrates/sem-core/tests/scope_resolve_bench.rs1839// ═══════════════════════════════════════════════════════════════════COMMENT
MEDIUMcrates/sem-core/src/parser/test_detect.rs84 // ── Built-in directory patterns ──────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/test_detect.rs126 // ── File-name patterns ───────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/test_detect.rs136 // ── Negative cases ───────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/test_detect.rs149 // ── Custom directories ───────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/graph.rs12134 // ── is_test_entity / filter_test_entities tests ─────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/plugins/json.rs777 // ─────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/plugins/json.rs779 // ─────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/plugins/json.rs809 // ─────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/sem-core/src/parser/plugins/json.rs811 // ─────────────────────────────────────────────────────────────────────────COMMENT
23 more matches not shown…
Excessive Try-Catch Wrapping24 hits · 30 pts
SeverityFileLineSnippetContext
LOWagent-skill/guard/sem-guard.py66 except Exception:CODE
LOWagent-skill/guard/sem-guard.py76 except Exception:CODE
LOWagent-skill/guard/sem-guard.py187 except Exception:CODE
LOWagent-skill/guard/sem-guard.py245 except Exception:CODE
MEDIUMagent-skill/guard/sem-guard.py62def load_state():CODE
MEDIUMagent-skill/guard/sem-guard.py70def save_state(s):CODE
LOWagent-skill/badge/statusline-sem.py49 except Exception:CODE
LOWagent-skill/badge/statusline-sem.py70 except Exception:CODE
LOWagent-skill/badge/statusline-sem.py85 except Exception:CODE
MEDIUMagent-skill/badge/statusline-sem.py46def read_lifetime():CODE
MEDIUMagent-skill/badge/statusline-sem.py67def main():CODE
LOWagent-skill/badge/sem-activity.py39 except Exception:CODE
LOWagent-skill/badge/sem-activity.py62 except Exception:CODE
LOWagent-skill/badge/sem-activity.py108 except Exception:CODE
LOWagent-skill/badge/sem-activity.py126 except Exception:CODE
LOWagent-skill/badge/sem-activity.py133 except Exception:CODE
MEDIUMagent-skill/badge/sem-activity.py36def main():CODE
LOWagent-skill/badge/sem-live.py59 except Exception:CODE
LOWagent-skill/badge/sem-live.py116 except Exception:CODE
LOWagent-skill/badge/sem-live.py138 except Exception:CODE
LOWagent-skill/badge/sem-live.py261 except Exception:CODE
LOWagent-skill/badge/sem-live.py297 except Exception:CODE
MEDIUMagent-skill/badge/sem-live.py258def term_width():CODE
LOW.claude/hooks/sem-first.sh20except Exception:CODE
Structural Annotation Overuse16 hits · 26 pts
SeverityFileLineSnippetContext
LOWCONTRIBUTING.md34### Step 1: Add the tree-sitter dependencyCOMMENT
LOWCONTRIBUTING.md45### Step 2: Add a getter functionCOMMENT
LOWCONTRIBUTING.md61### Step 3: Define the language configCOMMENT
LOWCONTRIBUTING.md85### Step 4: Register the configCOMMENT
LOWCONTRIBUTING.md96### Step 5: Register the extensionsCOMMENT
LOWCONTRIBUTING.md107### Step 6: Add a testCOMMENT
LOWCONTRIBUTING.md140### Step 7: Run testsCOMMENT
LOWcrates/sem-core/src/parser/graph.rs6520 // Step 1: every file's scan — reused from cache when eligible and its ownCOMMENT
LOWcrates/sem-core/src/parser/graph.rs6570 // Step 2: aggregate export-side data from *every* scan (green or red —COMMENT
LOWcrates/sem-core/src/parser/graph.rs6615 // Step 3: fingerprint every file that contributes to the export surface,COMMENT
LOWcrates/sem-core/src/parser/graph.rs6642 // Step 4: decide GREEN/RED per file, using the cache's *previous* readCOMMENT
LOWcrates/sem-core/src/parser/graph.rs6658 // Step 5: build entries for every RED file. GREEN files are untouched —COMMENT
LOWcrates/sem-core/src/parser/graph.rs6807 // Step 6: apply. Sequential — `HashMap::insert`/`remove` on the oneCOMMENT
LOW⚡benchmarks/dependency-accuracy/run_benchmark.py188 # Step 1: Index the project (may already be indexed, that's fine)COMMENT
LOW⚡benchmarks/dependency-accuracy/run_benchmark.py194 # Step 2: Parse all files to build entity map and call sitesCOMMENT
LOW⚡benchmarks/dependency-accuracy/run_benchmark.py213 # Step 3: For each call site, query stack-graphs and resolveCOMMENT
Verbosity Indicators9 hits · 16 pts
SeverityFileLineSnippetContext
LOWcrates/sem-core/src/parser/graph.rs6520 // Step 1: every file's scan — reused from cache when eligible and its ownCOMMENT
LOWcrates/sem-core/src/parser/graph.rs6570 // Step 2: aggregate export-side data from *every* scan (green or red —COMMENT
LOWcrates/sem-core/src/parser/graph.rs6615 // Step 3: fingerprint every file that contributes to the export surface,COMMENT
LOWcrates/sem-core/src/parser/graph.rs6642 // Step 4: decide GREEN/RED per file, using the cache's *previous* readCOMMENT
LOWcrates/sem-core/src/parser/graph.rs6658 // Step 5: build entries for every RED file. GREEN files are untouched —COMMENT
LOWcrates/sem-core/src/parser/graph.rs6807 // Step 6: apply. Sequential — `HashMap::insert`/`remove` on the oneCOMMENT
LOW⚡benchmarks/dependency-accuracy/run_benchmark.py188 # Step 1: Index the project (may already be indexed, that's fine)COMMENT
LOW⚡benchmarks/dependency-accuracy/run_benchmark.py194 # Step 2: Parse all files to build entity map and call sitesCOMMENT
LOW⚡benchmarks/dependency-accuracy/run_benchmark.py213 # Step 3: For each call site, query stack-graphs and resolveCOMMENT
Deep Nesting8 hits · 8 pts
SeverityFileLineSnippetContext
LOWagent-skill/guard/sem-guard.py173CODE
LOWagent-skill/badge/statusline-sem.py67CODE
LOWagent-skill/badge/sem-activity.py36CODE
LOWagent-skill/badge/sem-live.py51CODE
LOWbenchmarks/dependency-accuracy/run_benchmark.py186CODE
LOWbenchmarks/dependency-accuracy/run_benchmark.py236CODE
LOWbenchmarks/dependency-accuracy/run_benchmark.py275CODE
LOWbenchmarks/dependency-accuracy/run_benchmark.py343CODE
Fake / Example Data5 hits · 5 pts
SeverityFileLineSnippetContext
LOWcrates/sem-core/tests/graph_accuracy.rs30 .args(["config", "user.email", "test@test.com"])CODE
LOWcrates/sem-core/tests/graph_accuracy.rs125 .args(["config", "user.email", "test@test.com"])CODE
LOWcrates/sem-core/tests/graph_accuracy.rs218 vec!["config", "user.email", "test@test.com"],CODE
LOWcrates/sem-core/tests/scope_resolve_bench.rs28 .args(["config", "user.email", "test@test.com"])CODE
LOWcrates/sem-core/tests/stem_collision_ground_truth.rs31 vec!["config", "user.email", "test@test.com"],CODE
Redundant / Tautological Comments2 hits · 4 pts
SeverityFileLineSnippetContext
LOW⚡benchmarks/dependency-accuracy/run_benchmark.py220 # Check if definition points to an import bindingCOMMENT
LOWbenchmarks/dependency-accuracy/run_benchmark.py286 # Check if this is a top-level function (not inside a class)COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMcrates/sem-core/src/parser/facts_store.rs1288/// from `facts.path`'s extension — cheaper, and robust to a futureCOMMENT
Unused Imports2 hits · 2 pts
SeverityFileLineSnippetContext
LOWbenchmarks/dependency-accuracy/project/compat.py3CODE
LOWbenchmarks/dependency-accuracy/project/noise.py11CODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWinstall.sh6# Usage:COMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWbenchmarks/dependency-accuracy/run_benchmark.py442def pycg_normalize_constructors(edges, truth_edges):CODE
Overly Generic Function Names1 hit · 1 pts
SeverityFileLineSnippetContext
LOWbenchmarks/dependency-accuracy/project/api.py12def handle_request(request):CODE