AI Slop Code Risk Monitor

asciimoo/hister

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

Your own search engine

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for asciimoo/hister, a Go project with 6,190 GitHub stars. SynthScan examined 172,854 lines of code across 735 source files, recording 64 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 0.4 (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.

0.4
Adjusted Signal
0.4
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
6.2K
Stars
Go
Language
172.9K
Lines of Code
735
Files
64
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 1.9/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.3/100 · LOW

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

PR Review Velocity Impact 1.8/100 · LOW

Which changes need focused human review? 64 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 64

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 64 distinct pattern matches across 6 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 Block43 hits · 42 pts
SeverityFileLineSnippetContext
LOWcmd/users.go281// r := bufio.NewReader(os.Stdin)COMMENT
LOWcmd/users.go301// return defCOMMENT
LOWcmd/users.go321// s = strings.TrimSpace(s)COMMENT
LOWserver/mcp.go1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWserver/oauth/providers.go1// Package oauth provides OAuth 2.0 authentication support for external providers.COMMENT
LOWserver/oauth/providers.go21// provider, ok := oauth.NewProvider("github", oauth.ProviderConfig{})COMMENT
LOWserver/crawler/validator.go21 URLSkipCOMMENT
LOW…/extractor/extractors/_extractor_template/extractor.go1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOW…/extractor/extractors/_extractor_template/extractor.go61COMMENT
LOW…/extractor/extractors/_extractor_template/extractor.go81// Optional features:COMMENT
LOW…/extractor/extractors/_extractor_template/extractor.go121 d.Metadata["author"] = authorCOMMENT
LOWserver/document/language.go161func NewLanguageDetector() LanguageDetector {COMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.h1#ifndef SQLITE_VEC_HCOMMENT
LOWserver/vectorstore/sqlitevec/vec.go1// SPDX-License-Identifier: AGPL-3.0-or-laterCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h81#ifndef SQLITE_APICALLCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h461#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h501#define SQLITE_ERROR_MISSING_COLLSEQ (SQLITE_ERROR | (1<<8))COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h521#define SQLITE_IOERR_LOCK (SQLITE_IOERR | (15<<8))COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h541#define SQLITE_IOERR_BADKEY (SQLITE_IOERR | (35<<8))COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h561#define SQLITE_READONLY_CANTINIT (SQLITE_READONLY | (5<<8))COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h601** [sqlite3_open_v2()] has historically been a no-op and might become anCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h1241** options are used to enable it.COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h1261#define SQLITE_FCNTL_TRACE 19COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h2201** setting unchanged. After changes, if any, the integer is written withCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h2221#define SQLITE_CONFIG_PCACHE 14 /* no-op */COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h2661** the integer to which the second argument points, depending on whether theCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h2681#define SQLITE_DBCONFIG_WRITABLE_SCHEMA 1011 /* int int* */COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h3481#define SQLITE_CREATE_VIEW 8 /* View Name NULL */COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h7801#define SQLITE_INDEX_CONSTRAINT_GT 4COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h8481#define SQLITE_MUTEX_STATIC_OPEN 4 /* sqlite3BtreeOpen() */COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h8581*/COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h8601#define SQLITE_TESTCTRL_EXPLAIN_STMT 19 /* NOT USED */COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h9081#define SQLITE_DBSTATUS_SCHEMA_USED 2COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h11201#define CARRAY_DOUBLE 2 /* Data is doubles */COMMENT
LOWserver/vectorstore/sqlitevec/sqlite3.h13961COMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c1#include "sqlite-vec.h"COMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c21#elseCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c41#define INT16_TYPE int16_tCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c81typedef uint32_t u32;COMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c101#define SQLITE_RESULT_SUBTYPE 0x001000000COMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c2901 // Clean up with sqlite3_free() once completeCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c3421#define VEC0_SHADOW_AUXILIARY_NAME "\"%w\".\"%w_auxiliary\""COMMENT
LOW…i/website/src/content/posts/data-indexing-in-golang.md281```goCOMMENT
Hyper-Verbose Identifiers12 hits · 12 pts
SeverityFileLineSnippetContext
LOWwebui/app/src/lib/preview.svelte.ts51export function getStoredPreviewDetailsOpen(): boolean {CODE
LOWwebui/app/src/lib/preview.svelte.ts56export function setStoredPreviewDetailsOpen(open: boolean): void {CODE
LOWwebui/app/src/lib/query-suggestions.ts150function contextualValueSuggestions(CODE
LOWwebui/app/src/lib/components/PreviewPanel.svelte141 function formatDocumentDetailValue(entry: DetailEntry): string {CODE
LOWwebui/app/src/routes/history/+page.svelte112 function replaceHistoryPageHistory(filterValue: string) {CODE
LOWwebui/app/src/routes/rules/+page.svelte364 async function confirmMatchingDocumentDeletion() {CODE
LOWwebui/app/src/routes/rules/+page.svelte382 function cancelMatchingDocumentDeletion() {CODE
LOWwebui/ext/src/background/background.ts41function setPreviouslyIndexedBadge(tabId: number) {CODE
LOWwebui/ext/src/background/background.ts293function getDocumentSubmissionHeaders(data): CustomHeader[] {CODE
LOWwebui/ext/src/background/background.ts686async function disableIndexingForCurrentTab(type: SkipRuleType): Promise<void> {CODE
LOWwebui/ext/src/options/Options.svelte116 function toggleSubmitPublicDocuments() {CODE
LOWwebui/ext/src/popup/Popup.svelte237 function toggleSubmitPublicDocuments() {CODE
Structural Annotation Overuse4 hits · 6 pts
SeverityFileLineSnippetContext
LOWserver/vectorstore/sqlitevec/README.md3## WARNING: This is required to be able to build sqlite-vec cross platform without dependenciesCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c4413 // Step 1: Insert a new row in _chunks, capture that new rowidCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c4472 // Step 2: Create new vector chunks for each vector column, withCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c4508 // Step 3: Create new metadata chunks for each metadata columnCOMMENT
Verbosity Indicators3 hits · 4 pts
SeverityFileLineSnippetContext
LOWserver/vectorstore/sqlitevec/sqlite-vec.c4413 // Step 1: Insert a new row in _chunks, capture that new rowidCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c4472 // Step 2: Create new vector chunks for each vector column, withCOMMENT
LOWserver/vectorstore/sqlitevec/sqlite-vec.c4508 // Step 3: Create new metadata chunks for each metadata columnCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWserver/vectorstore/sqlitevec/update.sh3# Usage:COMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWserver/session_test.go972 {"ál ice@example.org", "12345678", false},CODE