AI Slop Code RIsk Monitor

nix-community/NUR

Nix User Repository: User contributed nix packages [maintainer=@Pandapip1]

4.4 Low pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for nix-community/NUR, a Python project with 1,965 GitHub stars. SynthScan examined 4,504 lines of code across 26 source files, recording 14 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 4.4 (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.

4.4
Adjusted Signal
4.4
Raw Pattern Score
100%
Time Factor
2026-10-11
Last Push
2.0K
Stars
Python
Language
4.5K
Lines of Code
26
Files
14
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 4.3/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 4 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 16.3/100 · LOW

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

PR Review Velocity Impact 19.9/100 · LOW

Which changes need focused human review? 14 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 3LOW 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 14 distinct pattern matches across 4 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 Separators3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMci/update-nur-search.sh13# ---------------------------------COMMENT
MEDIUMci/update-nur-search.sh41# -----------------------------------------COMMENT
MEDIUMci/lib/setup-git.sh2# ==================================================COMMENT
Modern Structural Boilerplate6 hits · 6 pts
SeverityFileLineSnippetContext
LOWci/nur/update.py12logger = logging.getLogger(__name__)CODE
LOWci/nur/combine.py15logger = logging.getLogger(__name__)CODE
LOWci/nur/combine.py113def update_manifest(repos: List[Repo], path: Path) -> None:CODE
LOWci/nur/combine.py121def update_combined(path: Path) -> None:CODE
LOWci/nur/manifest.py141def update_lock_file(repos: List[Repo], path: Path) -> None:CODE
LOWci/nur/eval.py14logger = logging.getLogger(__name__)CODE
Deep Nesting4 hits · 4 pts
SeverityFileLineSnippetContext
LOWci/nur/update.py40CODE
LOWci/nur/update.py51CODE
LOWci/nur/index.py11CODE
LOWci/nur/path.py12CODE
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWci/nur/combine.py139 except Exception:CODE