Home / z-lab / dflash
AI Slop Code RIsk Monitor

z-lab/dflash

DFlash: Block Diffusion for Flash Speculative Decoding

11.3 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for z-lab/dflash, a Python project with 6,148 GitHub stars. SynthScan examined 2,487 lines of code across 9 source files, recording 16 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 11.3 (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.

11.3
Adjusted Signal
11.3
Raw Pattern Score
100%
Time Factor
2026-08-18
Last Push
6.1K
Stars
Python
Language
2.5K
Lines of Code
9
Files
16
Pattern Hits
2026-10-12
Scan Date
0.11
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 13.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 3.9/100 · LOW

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

Agent Over-Engineering Ratio 35.7/100 · MEDIUM

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

PR Review Velocity Impact 44.2/100 · MEDIUM

Which changes need focused human review? 16 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 1MEDIUM 4LOW 11

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 16 distinct pattern matches across 8 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.

Decorative Section Separators4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMdflash/model.py21# ---------------------------------------------------------------------------COMMENT
MEDIUMdflash/model.py23# ---------------------------------------------------------------------------COMMENT
MEDIUMdflash/model.py327# ---------------------------------------------------------------------------COMMENT
MEDIUMdflash/model.py329# ---------------------------------------------------------------------------COMMENT
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHdflash/benchmark.py405except (TypeError, ValueError):CODE
Deep Nesting4 hits · 4 pts
SeverityFileLineSnippetContext
LOWdflash/benchmark.py287CODE
LOWdflash/benchmark.py357CODE
LOWdflash/model.py180CODE
LOWdflash/model_mlx.py726CODE
Unused Imports2 hits · 2 pts
SeverityFileLineSnippetContext
LOWdflash/benchmark.py1CODE
LOWdflash/cli.py1CODE
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWdflash/model.py478def _grouped_dynamic_convolve(hidden, dynamic, base, group_size):CODE
LOWdflash/model_mlx.py223def _grouped_dynamic_convolve(hidden, dynamic, base, group_size):CODE
Modern Structural Boilerplate1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdflash/__init__.py1__all__ = [CODE
AI Structural Patterns1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdflash/model.py433CODE
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdflash/model_mlx.py550 except Exception:CODE