AI Slop Code Risk Monitor

philc/vimium

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

The hacker's browser.

2.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for philc/vimium, a JavaScript project with 27,103 GitHub stars. SynthScan examined 24,465 lines of code across 115 source files, recording 48 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 2.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.

2.0
Adjusted Signal
2.0
Raw Pattern Score
100%
Time Factor
2026-07-25
Last Push
27.1K
Stars
JavaScript
Language
24.5K
Lines of Code
115
Files
48
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 8.0/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.8/100 · LOW

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

Agent Over-Engineering Ratio 1.8/100 · LOW

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

PR Review Velocity Impact 9.3/100 · LOW

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

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 48 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.

Over-Commented Block32 hits · 32 pts
SeverityFileLineSnippetContext
LOWtests/dom_tests/dom_tests.js201};COMMENT
LOWtests/dom_tests/dom_tests.js221// "month", "number", "password", "radio", "range", "reset", "search", "submit", "tel", "text",COMMENT
LOWtests/dom_tests/dom_tests.js241COMMENT
LOWtests/dom_tests/dom_tests.js961// disrepair, or we merged changes to master and neglected to update the tests. We should return toCOMMENT
LOWtests/dom_tests/dom_tests.js981// assert.isFalse(this.initialVisualMode.modeIsActive);COMMENT
LOWtests/dom_tests/dom_tests.js1001// assert.equal("i", getSelection());COMMENT
LOWtests/dom_tests/dom_tests.js1021COMMENT
LOWtests/dom_tests/dom_tests.js1041// // TODO(philc): Re-enableCOMMENT
LOWtests/dom_tests/dom_tests.js1061COMMENT
LOWtests/dom_tests/dom_tests.js1081COMMENT
LOWtests/dom_tests/dom_tests.js1101// assert.equal("a", getSelection());COMMENT
LOWtests/dom_tests/dom_utils_test.js121// document.getElementById("test-div").innerHTML = """COMMENT
LOWlib/utils.js241 // Logs a backtrace when an assertion fails, and also halts execution by throwing an error. We doCOMMENT
LOWlib/settings.js61# More examples.COMMENT
LOWpages/vomnibar_page.js281 // - If they've activated a custom search engine in the Vomnibar, launch that search using theCOMMENT
LOWcontent_scripts/scroller.js1// activatedElement is different from document.activeElement -- the latter seems to be reservedCOMMENT
LOWcontent_scripts/mode_visual.js41 /[_0-9\u0041-\u005A\u0061-\u007A\u00AA\u00B5\u00BA\u00C0-\u00D6\u00D8-\u00F6\u00F8-\u02C1\u02C6-\u02D1\u02E0-\u0COMMENT
LOWcontent_scripts/ui_component.js1// A UIComponent is an iframe containing a Vimium extension page, like the Vomnibar. This classCOMMENT
LOWcontent_scripts/ui_component.js21 shadowDOM;COMMENT
LOWcontent_scripts/mode_key_handler.js1// Example key mapping (@keyMapping):COMMENT
LOWcontent_scripts/link_hints.js1//COMMENT
LOWcontent_scripts/link_hints.js1401 // The order of elements here is important; they should appear in the order they are in the DOM,COMMENT
LOWcontent_scripts/mode.js1//COMMENT
LOWbackground_scripts/tab_recency.js1// TabRecency associates an integer with each tab id representing how recently it has been accessed.COMMENT
LOWbackground_scripts/reload.js21}COMMENT
LOWbackground_scripts/all_commands.js1// This is the order they will be shown in the help dialog.COMMENT
LOWbackground_scripts/completion/completers.js1// This file contains the definition of the completers used for the Vomnibar's suggestion UI. ACOMMENT
LOWbackground_scripts/completion/completers.js161 let textPosition = 0;COMMENT
LOWbackground_scripts/completion/completers.js241 }COMMENT
LOWbackground_scripts/completion/search_engines.js1// An engine provides search suggestions for a online search engine.COMMENT
LOWbackground_scripts/completion/search_engines.js21// "description" and an "explanation". This info is shown as documentation to the user.COMMENT
LOWbackground_scripts/completion/ranking.js141 // Get rexexp for `string` from cache, creating it if necessary.COMMENT
Hyper-Verbose Identifiers9 hits · 9 pts
SeverityFileLineSnippetContext
LOWmake.js98async function checkForCommonBuildIssues() {CODE
LOWmake.js118async function checkFilesFromManifestArePresent(manifest) {CODE
LOWmake.js275function setupPuppeteerPageForTests(page) {CODE
LOWpages/command_listing.js17function replaceBackticksWithCodeTags(str) {CODE
LOWpages/hud_page.js81function ensureClipboardIsAvailable() {CODE
LOWpages/ui_component_messenger.js8export async function registerPortWithOwnerPage(event) {CODE
LOWpages/ui_component_messenger.js57function dispatchReadyEventWhenReady() {CODE
LOWbackground_scripts/main.js820async function showUpgradeMessageIfNecessary(onInstalledDetails) {CODE
LOWbackground_scripts/main.js860async function injectContentScriptsAndCSSIntoExistingTabs() {CODE
Fake / Example Data7 hits · 9 pts
SeverityFileLineSnippetContext
LOWtests/dom_tests/dom_tests.js624<a href='#first'>lorem ipsum next</a>CODE
LOW⚡test_harnesses/vomnibar_harness.html16 Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt utCODE
LOW⚡test_harnesses/vomnibar_harness.html16 Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt utCODE
LOW⚡test_harnesses/vomnibar_harness.html25 Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt utCODE
LOW⚡test_harnesses/vomnibar_harness.html25 Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt utCODE
LOWpages/vomnibar_page.js88 this.input.setAttribute("placeholder", placeholder);CODE
LOWcontent_scripts/link_hints.js1521 if (!linkText && "placeholder" in element) {CODE