AI Slop Code Risk Monitor

insin/control-panel-for-twitter

SlopCodeMonitor badge for insin/control-panel-for-twitter Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Browser extension which gives you more control over your Twitter timeline and adds missing features and UI improvements - for desktop and mobile

1.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for insin/control-panel-for-twitter, a JavaScript project with 2,652 GitHub stars. SynthScan examined 16,710 lines of code across 52 source files, recording 34 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 1.7 (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.7
Adjusted Signal
1.7
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
2.7K
Stars
JavaScript
Language
16.7K
Lines of Code
52
Files
34
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? 34 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 8.0/100 · LOW

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

PR Review Velocity Impact 9.7/100 · LOW

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

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 34 distinct pattern matches across 1 syntactic category. 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.

Hyper-Verbose Identifiers34 hits · 28 pts
SeverityFileLineSnippetContext
LOWoptions.js485function shouldDisplayHideQuotesFrom() {CODE
LOWoptions.js537function updateHideQuotesFromDisplay() {CODE
LOWscript.js2484function isOnAccessibilitySettingsPage() {CODE
LOWscript.js2508function isOnDiscoverCommunitiesPage() {CODE
LOWscript.js2580function isOnSeparatedTweetsTimeline() {CODE
LOWscript.js2592function shouldShowSeparatedTweetsTab() {CODE
LOWscript.js3078function observeBodyBackgroundColor() {CODE
LOWscript.js3208async function observeDesktopComposeTweetModal($popup) {CODE
LOWscript.js3271async function observeDesktopHomeTimelineTweetBox() {CODE
LOWscript.js3336async function observeDesktopModalTimeline($popup) {CODE
LOWscript.js3351 function observeModalTimelineItems($timeline) {CODE
LOWscript.js3787 return async function observeSideNavTweetButton() {CODE
LOWscript.js3962function observeDesktopTweetEditorPlaceholder($editorRoot, {CODE
LOWscript.js3981async function observeIndividualTweetTimeline(page) {CODE
LOWscript.js4030async function addAccountLocationToFocusedTweet($permalinkBar, screenName) {CODE
LOWscript.js4093function addCaretMenuListenerForQuoteTweet($tweet) {CODE
LOWscript.js4170async function addToggleListRetweetsMenuItem($switchMenuItem) {CODE
LOWscript.js4210function checkforDisabledHomeTimeline() {CODE
LOWscript.js4226function checkReactNativeStylesheet() {CODE
LOWscript.js5386function configureSeparatedTweetsTimelineTitle() {CODE
LOWscript.js6339function onIndividualTweetTimelineChange($timeline, options) {CODE
LOWscript.js6753function handleDesktopModalRouteChange(path) {CODE
LOWscript.js6918function removeMobileTimelineHeaderElements() {CODE
LOWscript.js6953function restoreTweetInteractionsLinks({$actionBar, $focusedTweet, tweetInfo, isOwnTweet, tweetPath}) {CODE
LOWscript.js7033 function shouldHideIndividualTweetTimelineItem(type) {CODE
LOWscript.js7052function shouldHideListTimelineItem(type) {CODE
LOWscript.js7071function shouldHideHomeTimelineItem(type, page) {CODE
LOWscript.js7099function shouldHideProfileTimelineItem(type) {CODE
LOWscript.js7120 function shouldHideOtherTimelineItem(type) {CODE
LOWscript.js7248function tweakCommunityMembersPage() {CODE
LOWscript.js7543 function updateSelectedHomeTabIndex() {CODE
LOWscript.js7587async function tweakMobileComposeTweetPage() {CODE
LOWscript.js7590 function observeUserTypeaheadDropdown($tweetTextareaContainer) {CODE
LOWscript.js7691async function tweakMobileMediaViewerPage() {CODE