Home / onedr0p / cluster-template
AI Slop Code Risk Monitor

onedr0p/cluster-template

SlopCodeMonitor badge for onedr0p/cluster-template Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A template for deploying a Talos Kubernetes cluster including Flux for GitOps

25.1 Elevated pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for onedr0p/cluster-template, a YAML project with 2,833 GitHub stars. SynthScan examined 4,583 lines of code across 60 source files, recording 56 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 25.1 (Elevated 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.

25.1
Adjusted Signal
25.1
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
2.8K
Stars
YAML
Language
4.6K
Lines of Code
60
Files
56
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 34.3/100 · MEDIUM

Can maintainers explain intent, assumptions, and trade-offs? 36 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 68.7/100 · HIGH

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

PR Review Velocity Impact 64.9/100 · HIGH

Which changes need focused human review? 56 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 20LOW 36

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

Decorative Section Separators20 hits · 76 pts
SeverityFileLineSnippetContext
MEDIUM⚡cluster.sample.toml161# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml165# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml172# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml178# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml192# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml202# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml211# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml214# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml251# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml253# =============================================================================COMMENT
MEDIUM⚡cluster.sample.toml262# =============================================================================COMMENT
MEDIUMcluster.sample.toml2# =============================================================================COMMENT
MEDIUMcluster.sample.toml6# =============================================================================COMMENT
MEDIUMcluster.sample.toml45# =============================================================================COMMENT
MEDIUMcluster.sample.toml49# =============================================================================COMMENT
MEDIUMcluster.sample.toml87# =============================================================================COMMENT
MEDIUMcluster.sample.toml91# =============================================================================COMMENT
MEDIUMcluster.sample.toml113# =============================================================================COMMENT
MEDIUMcluster.sample.toml118# =============================================================================COMMENT
MEDIUMcluster.sample.toml276# =============================================================================COMMENT
Hyper-Verbose Identifiers20 hits · 30 pts
SeverityFileLineSnippetContext
LOW⚡template/scripts/test_validate.py84def test_valid_fixture_accepted(fixture: Path):CODE
LOW⚡template/scripts/test_validate.py88def test_every_invalid_fixture_has_an_expected_reason():CODE
LOW⚡template/scripts/test_validate.py93def test_invalid_fixture_rejected(fixture: Path):CODE
LOW⚡template/scripts/test_validate.py112def test_ssh_port_on_bundled_host_needs_no_known_hosts():CODE
LOW⚡template/scripts/test_validate.py117def test_cluster_issuer_follows_dns_provider():CODE
LOW⚡template/scripts/test_validate.py124def test_default_gateway_derived_from_node_cidr():CODE
LOW⚡template/scripts/test_validate.py131def test_coredns_addr_default_and_override():CODE
LOW⚡template/scripts/test_validate.py141def test_spegel_enabled_follows_node_count():CODE
LOW⚡template/scripts/test_validate.py153def test_controller_count_ignores_workers():CODE
LOW⚡template/scripts/test_validate.py161def test_derived_fields_are_not_settable():CODE
LOW⚡template/scripts/test_validate.py170def test_cert_sans_single_source():CODE
LOW⚡template/scripts/test_validate.py177def test_ingress_mode_follows_dns_provider():CODE
LOW⚡template/scripts/test_validate.py186def test_direct_mode_requires_cloudflare_dns():CODE
LOW⚡template/scripts/test_validate.py192def test_empty_string_means_unset():CODE
LOW⚡template/scripts/test_validate.py206def test_errors_omit_default_factory_noise():CODE
LOW⚡template/scripts/test_validate.py213def test_schematic_id_inherits_from_talos_section():CODE
LOW⚡template/scripts/test_validate.py220def test_node_defaults_exported():CODE
LOW⚡template/scripts/test_validate.py228def test_gateways_may_leave_node_cidr_only_with_bgp():CODE
LOW⚡template/scripts/test_validate.py236def test_schema_file_matches_model():CODE
LOW⚡template/scripts/test_validate.py241def test_schema_omits_computed_fields():CODE
Over-Commented Block16 hits · 8 pts
SeverityFileLineSnippetContext
LOWcluster.sample.toml1#:schema ./cluster.schema.jsonCOMMENT
LOWcluster.sample.toml21COMMENT
LOWcluster.sample.toml41COMMENT
LOWcluster.sample.toml61# pod_cidr.COMMENT
LOWcluster.sample.toml81# /etc/hosts entry) instead of the raw IP.COMMENT
LOWcluster.sample.toml101# at this IP to enable split-DNS resolution from your LAN.COMMENT
LOWcluster.sample.toml121# Full clone URL of the repository this cluster will pull from.COMMENT
LOWcluster.sample.toml141# "github" for them. Use "generic-hmac" for anything else that signs withCOMMENT
LOWcluster.sample.toml161# =============================================================================COMMENT
LOWcluster.sample.toml181# OPTIONAL. Default: "cloudflare". Allowed: "cloudflare" | "none"COMMENT
LOWcluster.sample.toml201# LAN via the internal gateway.COMMENT
LOWcluster.sample.toml221# REF: https://docs.cilium.io/en/stable/network/kubernetes/kubeproxy-free/COMMENT
LOWcluster.sample.toml241COMMENT
LOWcluster.sample.toml261COMMENT
LOWcluster.sample.toml281# controller = true # true = control-plane (etcd + API server), false = worker.COMMENT
LOW.github/template-tests/e2e/cluster.sh1#!/usr/bin/env bashCOMMENT