AI Slop Code Risk Monitor

HigherOrderCO/Bend

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

Bend 2: a fast language that blocks AI mistakes via proof. Install: curl -fsSL https://bend-lang.com/install.sh | sh

1.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for HigherOrderCO/Bend, a TypeScript project with 24,593 GitHub stars. SynthScan examined 46,956 lines of code across 323 source files, recording 73 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.8 (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.8
Adjusted Signal
1.8
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
24.6K
Stars
TypeScript
Language
47.0K
Lines of Code
323
Files
73
Pattern Hits
2026-10-31
Scan Date
0.01
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 7.2/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.6/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 9.1/100 · LOW

Which changes need focused human review? 73 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 3MEDIUM 1LOW 69

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 73 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 Block69 hits · 68 pts
SeverityFileLineSnippetContext
LOWgates/_lib.ts1// Shared by the gates: local and cluster exec (ssh through the bastion'sCOMMENT
LOWgates/ping.ts1#!/usr/bin/env bunCOMMENT
LOWgates/ping.ts21// the command's own; a dead origin costs one run under four seconds; bendCOMMENT
LOWgates/_run.ts1#!/usr/bin/env bunCOMMENT
LOWgates/repo.ts1#!/usr/bin/env bunCOMMENT
LOWgates/test.ts1#!/usr/bin/env bunCOMMENT
LOWgates/safe.ts1#!/usr/bin/env bunCOMMENT
LOWgates/perf.ts1#!/usr/bin/env bunCOMMENT
LOWbench/runtime/tree-matmul/main.c1// Native C twin of main.bend: recursive block matrix multiply overCOMMENT
LOWbench/runtime/nbody/main.c1// Native C translation of main.bend: chaotic three-body ensemble,COMMENT
LOWbench/runtime/raytrace/main.ts1// Single-threaded TypeScript twin of main.bend.COMMENT
LOWbench/runtime/raytrace/main.c1// Single-threaded C twin of main.bend. SameCOMMENT
LOWbench/runtime/lexer/main.c1// Native C twin of main.bend: same generator (the template expandedCOMMENT
LOWbench/runtime/tree-radix/main.c1// Native C twin of main.bend: same trie sort (gen -> to_map/mergeCOMMENT
LOWbench/runtime/symreg/main.c1// Single-threaded C twin of main.bend. SameCOMMENT
LOWbench/runtime/merkle/main.c1// Native C twin of main.bend: same Speck32/64 leaf stream, MerkleCOMMENT
LOWbench/runtime/hashmap/main.c1// Native C twin of main.bend: a hash table with separate chainingCOMMENT
LOWbench/runtime/bfs/main.c1// Native C twin of main.bend: breadth-first search over 2^DEPTHCOMMENT
LOWbench/runtime/editdist/main.c1// Native C twin of main.bend: Levenshtein edit distance by dynamicCOMMENT
LOWbench/runtime/tree-bitonic/main.c1// Native C twin of main.bend: same tree-shaped bitonic sortingCOMMENT
LOWbench/runtime/queens/main.c1// Single-threaded C twin of main.bend. Same algorithm, same shape:COMMENT
LOWbench/runtime/histogram/main.c1// Native C twin of main.bend: a histogram of R fresh batches of 2^D keysCOMMENT
LOWbend2/bend.ts1// NOTE: this file was 99% human-designed and audited.COMMENT
LOWbend2/bend.ts21// Term ::=COMMENT
LOWbend2/bend.ts41//COMMENT
LOWbend2/bend.ts61// Arrow | A "->" B | @_:A -> BCOMMENT
LOWbend2/bend.ts81// is, import, Type, Data, Kind, Quant ("as" reads only on an importCOMMENT
LOWbend2/bend.ts101// right-associative; the domain of a written @ or & binder stops at theCOMMENT
LOWbend2/bend.ts121// ">"-headed operator never fires -- space your comparisons andCOMMENT
LOWbend2/bend.ts141// Do-NotationCOMMENT
LOWbend2/bend.ts161// ------COMMENT
LOWbend2/bend.ts181// (Atkey scales the argument's measure by the binder's ω), and aCOMMENT
LOWbend2/bend.ts201// Data fits every kind, every kind fits Type and Kind(&0), and a meetCOMMENT
LOWbend2/bend.ts221// equality is intensional; elimination is the J axiom, %e@E : P; f,COMMENT
LOWbend2/bend.ts2641 continue;COMMENT
LOWbend2/bend.ts2841// field) becomes a share Var: index -1, its value the raw term; theCOMMENT
LOWbend2/bend.ts3101 }COMMENT
LOWbend2/bend.ts3261 }COMMENT
LOWbend2/bend.ts3341 return term_infer(book, lhs, term_force(tm), qt, ctx, d, sp);COMMENT
LOWbend2/bend.ts3441 // where a is dead if q is -, and consumed once otherwise: itsCOMMENT
LOWbend2/bend.ts3641 // as the constructor it isCOMMENT
LOWbend2/bend.ts3841// its event (a law: type checked at its law, defined at its fill), soCOMMENT
LOWbend2/safe.ts1// SafeCOMMENT
LOWbend2/safe.ts21// which ends in λ{(): ..; λ{}}. A default arm binds the tag and theCOMMENT
LOWbend2/safe.ts261 const ws = ns.flatMap(why);COMMENT
LOWbend2/safe.ts1201// GroupCOMMENT
LOWbend2/comp.ts3181#elif !BEND_RTCCOMMENT
LOWbend2/comp.ts3201#include <sys/select.h>COMMENT
LOWbend2/comp.ts3221// preserve_* attributes need clang 19+ and an optimized build. A segment isCOMMENT
LOWbend2/comp.ts3241#elseCOMMENT
LOWbend2/comp.ts3261#endifCOMMENT
LOWbend2/comp.ts3281#elseCOMMENT
LOWbend2/comp.ts3361COMMENT
LOWbend2/comp.ts3381#define CUBE_T 128COMMENT
LOWbend2/comp.ts3401#define H_BUMP 0COMMENT
LOWbend2/comp.ts3481#define fid_arity(x) FID_T[x].arCOMMENT
LOWbend2/comp.ts3541#endifCOMMENT
LOWbend2/comp.ts4341// WorkCOMMENT
LOWbend2/comp.ts5181}COMMENT
LOWbend2/comp.ts5361 return rv[0];COMMENT
9 more matches not shown…
Cross-Language Confusion (JS/TS)3 hits · 15 pts
SeverityFileLineSnippetContext
HIGHtools/bend-lint/rules/format.ts468 print(doc, opts.wrapAtWidth === "never" ? Infinity : opts.wrapAtWidth, indent, newline),CODE
HIGHbend2/bend.ts617 return None();CODE
HIGHbend2/bend.ts1725 return None();CODE
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMbend2/bend.ts3// It has a bit of AI slop, but it is the most robust file in the repo.COMMENT