Home / Fractal-Compute-Orchestrations / FractalWorkspace
AI Slop Code Risk Monitor

Fractal-Compute-Orchestrations/FractalWorkspace

SlopCodeMonitor badge for Fractal-Compute-Orchestrations/FractalWorkspace Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A unified ecosystem and workspace for large-scale federated learning of Large Models & LLMS. Store compute as Wifi

13.8 Moderate pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Fractal-Compute-Orchestrations/FractalWorkspace, a Python project with 9,227 GitHub stars. SynthScan examined 4,516 lines of code across 26 source files, recording 37 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 13.8 (Moderate 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.

13.8
Adjusted Signal
13.8
Raw Pattern Score
100%
Time Factor
2026-11-10
Last Push
9.2K
Stars
Python
Language
4.5K
Lines of Code
26
Files
37
Pattern Hits
2026-11-11
Scan Date
0.04
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-11-11.

Cognitive Ownership Risk 15.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.1/100 · LOW

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

Agent Over-Engineering Ratio 44.7/100 · MEDIUM

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

PR Review Velocity Impact 48.5/100 · MEDIUM

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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 1MEDIUM 9LOW 27

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

Excessive Try-Catch Wrapping26 hits · 46 pts
SeverityFileLineSnippetContext
LOW⚡scripts/verify_environment.py63 except Exception:CODE
LOW⚡scripts/generate_carousel_md.py108 except Exception as e:CODE
MEDIUM⚡scripts/generate_carousel_md.py109 print(f"Error parsing JSON: {e}")CODE
LOW⚡scripts/generate_carousel_md.py116except Exception as e:CODE
MEDIUM⚡scripts/generate_carousel_md.py117 print(f"Error: {e}")CODE
LOW⚡scripts/get_image_data.py43 except Exception as e:CODE
MEDIUM⚡scripts/get_image_data.py44 print(f"Error parsing JSON: {e}")CODE
LOW⚡scripts/get_image_data.py45except Exception:CODE
LOW⚡scripts/inspect_modules.py36 except Exception as e:CODE
MEDIUM⚡scripts/inspect_modules.py37 print(f"Error: {e}")CODE
LOW⚡scripts/inspect_modules.py38except Exception:CODE
LOWscripts/fetch_behance_images.py16except Exception as e:CODE
MEDIUMscripts/fetch_behance_images.py17 print(f'Error: {e}')CODE
LOWscripts/analyze_behance.py30except Exception as e:CODE
MEDIUMscripts/analyze_behance.py31 print(f"Error: {e}")CODE
LOW⚡scripts/inspect_project_details.py40 except Exception as e:CODE
MEDIUM⚡scripts/inspect_project_details.py41 print(f"Error parsing JSON: {e}")CODE
LOW⚡scripts/inspect_project_details.py42except Exception:CODE
LOWscripts/parse_behance_json.py52except Exception:CODE
LOWscripts/benchmark_evaluation.py765 except Exception as e:CODE
MEDIUMscripts/benchmark_evaluation.py766 print(f"Error loading {it['icon']}: {e}")CODE
LOW⚡scripts/get_image_sizes.py35 except Exception as e:CODE
MEDIUM⚡scripts/get_image_sizes.py36 print(f"Error parsing JSON: {e}")CODE
LOW⚡scripts/get_image_sizes.py37except Exception:CODE
LOWscripts/extract_project_modules.py70 except Exception as e:CODE
LOWscripts/extract_project_modules.py73except Exception:CODE
Hyper-Verbose Identifiers6 hits · 7 pts
SeverityFileLineSnippetContext
LOW⚡scripts/verify_environment.py56def check_huggingface_connection() -> bool:CODE
LOW⚡scripts/verify_environment.py68def check_firebase_credentials() -> bool:CODE
LOWscripts/benchmark_evaluation.py96def benchmark_tinyllama_layers():CODE
LOWscripts/benchmark_evaluation.py157def plot_exact_wire_compression():CODE
LOWscripts/benchmark_evaluation.py239def plot_measured_layer_fidelity(results):CODE
LOWscripts/benchmark_evaluation.py555def plot_distributed_edge_efficiency_index():CODE
Synthetic Comment Markers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHmodels/TinyLlama-1.1B/README.md31This is the chat model finetuned on top of [TinyLlama/TinyLlama-1.1B-intermediate-step-1431k-3T](https://huggingface.co/CODE
Over-Commented Block2 hits · 2 pts
SeverityFileLineSnippetContext
LOWmodels/TinyLlama-1.1B/README.md61# You are a friendly chatbot who always responds in the style of a pirate.</s>COMMENT
LOWscripts/verify_environment.py101# End of script verification.COMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/verify_environment.py12CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/extract_project_modules.py23CODE