AI Slop Code Risk Monitor

tabler/tabler

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

Free and open source admin dashboard UI kit built on Bootstrap: 100+ pages, 6,000+ icons, dark mode, RTL.

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for tabler/tabler, a Astro project with 41,981 GitHub stars. SynthScan examined 103,202 lines of code across 586 source files, recording 49 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.5
Adjusted Signal
0.5
Raw Pattern Score
100%
Time Factor
2026-10-29
Last Push
42.0K
Stars
Astro
Language
103.2K
Lines of Code
586
Files
49
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 2.0/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.3/100 · LOW

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

Agent Over-Engineering Ratio 0.1/100 · LOW

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

PR Review Velocity Impact 2.4/100 · LOW

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

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 49 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 Block41 hits · 41 pts
SeverityFileLineSnippetContext
LOW.build/generate-sri.ts1#!/usr/bin/env nodeCOMMENT
LOW.build/release-main.ts1#!/usr/bin/env nodeCOMMENT
LOW.build/css-vars-baseline.txt1# Custom properties the css references but never defines. Each one makes theCOMMENT
LOW.build/css-var-prefix.ts1// The `--tblr-` custom-property prefix, applied at build time.COMMENT
LOW.build/build-css.ts1// Single-pass CSS pipeline shared by @tabler/core and @tabler/preview.COMMENT
LOW.build/build-css.ts101// All compile work is done before the first write: compiles take seconds whileCOMMENT
LOW.build/generate-agent-skills.ts1#!/usr/bin/env nodeCOMMENT
LOW.build/compat-baseline.txt1# What the working tree no longer ships compared with the last release ofCOMMENT
LOW.build/check-docs-links.ts1#!/usr/bin/env nodeCOMMENT
LOW.build/check-html.ts1// Renders every page of a built site (or a running dev server) in Chromium andCOMMENT
LOW.build/check-markup-classes.ts1// Fails when a rendered page uses a class that no shipped stylesheet defines.COMMENT
LOW.build/check-compat.ts1// Fails when the build drops something the last release shipped.COMMENT
LOW.build/check-compat.ts21// while any unaccepted line is left: the release runs it that way.COMMENT
LOW.build/check-css-vars.ts1// Fails when the css references a custom property that nothing defines.COMMENT
LOW.build/check-open-source.ts1#!/usr/bin/env nodeCOMMENT
LOW.build/copy-assets.ts1// Shared Astro integration that rebuilds a package's public/ directory fromCOMMENT
LOW.build/check-compat-fixture.ts1// Runs a project written for the last release against that release and againstCOMMENT
LOWscreenshots/.build/record.ts1// Records a short video of a screenshots page: `pnpm run record button`.COMMENT
LOWscreenshots/.build/capture.ts1#!/usr/bin/env nodeCOMMENT
LOWcore/.build/generate-sri.ts1// Writes SRI hashes for the built core files to shared/data/sri.json.COMMENT
LOWcore/js/src/datepicker.ts41const DATE_PATTERN = /^(\d{4})-(\d{2})-(\d{2})$/COMMENT
LOWcore/scss/_settings.scss1// Foundational settings used by both functions and variables.COMMENT
LOWcore/scss/_extends.scss1// Cross-module `@extend` rules, loaded last from `tabler.scss`.COMMENT
LOWcore/scss/_extends.scss81// (from `layout/_dark.scss`)COMMENT
LOWcore/scss/ui/_login.scss1//.col-login {COMMENT
LOWcore/scss/ui/_close.scss61 display: none;COMMENT
LOWcore/scss/ui/_close.scss81// }COMMENT
LOWcore/scss/bootstrap/_carousel.scss1// Notes on the classes:COMMENT
LOWcore/scss/bootstrap/_tables.scss81//COMMENT
LOWcore/scss/bootstrap/_list-group.scss181COMMENT
LOWcore/scss/bootstrap/forms/_form-control.scss81 // On Android Chrome, form-control's "width: 100%" makes the input width too smallCOMMENT
LOWcore/scss/bootstrap/forms/_validation.scss1// Form validationCOMMENT
LOWcore/scss/mixins/_functions.scss41}COMMENT
LOWcore/scss/layout/_navbar.scss641 // Folded sidebar: every geometry consumer (aside width, page paddings,COMMENT
LOWcore/scss/layout/_navbar.scss881// with an outline on every side instead of the single border line.COMMENT
LOWcore/scss/tests/_generate-utility.test.scss1// Output tests for the `generate-utility` mixin fromCOMMENT
LOWshared/lib/page-scripts.ts1// Snippets declared in page content render at the end of <body> (via PageScripts).COMMENT
LOWshared/lib/page-modals.ts1// Modals declared in page content render at the end of <body>, before theCOMMENT
LOWdocs/lib/llms.ts1// MDX → plain markdown, for the /llms.txt endpoints.COMMENT
LOWdocs/lib/markdown-url.ts1// The `.md` mirror of a docs page url; the mirror of `/` is `/index.md`.COMMENT
LOW.github/workflows/release.yml61 # changeset-release/dev via a short-lived changesets-ghcommit-temp/* branch,COMMENT
Fake / Example Data7 hits · 7 pts
SeverityFileLineSnippetContext
LOWcore/js/tests/unit/collapse.spec.ts48 fixtureEl.innerHTML = ['<div class="my-collapse">', ' <div class="item">', ' <a data-bs-toggle="collapse" hrefCODE
LOWcore/js/tests/unit/collapse.spec.ts58 fixtureEl.innerHTML = ['<div class="my-collapse">', ' <div class="item">', ' <a data-bs-toggle="collapse" hrefCODE
LOWcore/js/tests/unit/collapse.spec.ts97 ' <div id="collapse1" class="collapse show">Lorem ipsum 1</div>',CODE
LOWcore/js/tests/unit/collapse.spec.ts101 ' <div id="collapse2" class="collapse">Lorem ipsum 2</div>',CODE
LOWshared/data/real-estate.json4 "address": "123 Main Street",CODE
LOWshared/data/menu.json233 "placeholder": {CODE
LOWpreview/CHANGELOG.md217- da11f08: Replaced lorem ipsum with unique placeholder text on the Scroll spy demo page and fixed its menu highlight.CODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcore/js/src/bootstrap/dom/event-handler.ts112function bootstrapDelegationHandler(element: EventTarget, selector: string, fn: EventCallback): BootstrapHandler {CODE