AI Slop Code Risk Monitor

bitnami/sealed-secrets

Name: bitnami/sealed-secrets — Go Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

A Kubernetes controller and tool for one-way encrypted Secrets

1.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for bitnami/sealed-secrets, a Go project with 9,325 GitHub stars. SynthScan examined 24,879 lines of code across 204 source files, recording 36 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.4

Adjusted Signal

1.4

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

9.3K

Stars

Language

24.9K

Lines of Code

204

Files

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 7.0/100 · LOW

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 0.0/100 · LOW

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

PR Review Velocity Impact 7.0/100 · LOW

Which changes need focused human review? 36 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 0LOW 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 36 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 Block33 hits · 32 pts

Severity	File	Line	Snippet	Context
LOW	site/data/docs/toc-mapping.yml	1	# This file can be used to explicitly map a release to a specific table-of-contents	COMMENT
LOW	helm/sealed-secrets/values.yaml	1	## @section Common parameters	COMMENT
LOW	helm/sealed-secrets/values.yaml	21	##	COMMENT
LOW	helm/sealed-secrets/values.yaml	41	repository: bitnami/sealed-secrets-controller	COMMENT
LOW	helm/sealed-secrets/values.yaml	61	createController: true	COMMENT
LOW	helm/sealed-secrets/values.yaml	81	## e.g for one year	COMMENT
LOW	helm/sealed-secrets/values.yaml	101	##	COMMENT
LOW	helm/sealed-secrets/values.yaml	121	## @param kubeClientQPS Kubeclient QPS (negative value disables ratelimiting)	COMMENT
LOW	helm/sealed-secrets/values.yaml	181	##	COMMENT
LOW	helm/sealed-secrets/values.yaml	221	capabilities:	COMMENT
LOW	helm/sealed-secrets/values.yaml	241	##	COMMENT
LOW	helm/sealed-secrets/values.yaml	261	##	COMMENT
LOW	helm/sealed-secrets/values.yaml	281		COMMENT
LOW	helm/sealed-secrets/values.yaml	301	## NOTE: choose port between <30000-32767>	COMMENT
LOW	helm/sealed-secrets/values.yaml	321	## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for	COMMENT
LOW	helm/sealed-secrets/values.yaml	341	## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`	COMMENT
LOW	helm/sealed-secrets/values.yaml	361	## - path: /*	COMMENT
LOW	helm/sealed-secrets/values.yaml	381	## It is also possible to create and manage the certificates outside of this helm chart	COMMENT
LOW	helm/sealed-secrets/values.yaml	401	##	COMMENT
LOW	helm/sealed-secrets/values.yaml	421	## @param serviceAccount.annotations [object] Annotations for Sealed Secret service account	COMMENT
LOW	helm/sealed-secrets/values.yaml	441	## @param rbac.clusterRole Specifies whether the Cluster Role resource should be created	COMMENT
LOW	helm/sealed-secrets/values.yaml	521	labels: {}	COMMENT
LOW	helm/sealed-secrets/values.yaml	541	## @param metrics.serviceMonitor.relabelings [array] Specify general relabeling	COMMENT
LOW	helm/sealed-secrets/values.yaml	561	## Sealed Secret Metrics service parameters	COMMENT
LOW	pkg/apis/sealedsecrets/v1alpha1/types.go	41	// when created from a template.	COMMENT
LOW	pkg/apis/sealedsecrets/v1alpha1/types.go	121	// ObservedGeneration reflects the generation most recently observed by the sealed-secrets controller.	COMMENT
LOW	pkg/pflagenv/flagenv.go	1	// Package pflagenv implements a simple way to expose all your pflag flags as environmental variables.	COMMENT
LOW	pkg/client/informers/externalversions/factory.go	241	// genericInformer := factory.ForResource(resource)	COMMENT
LOW	pkg/client/informers/externalversions/factory.go	261	// return fmt.Errorf("sync event handler: %w", context.Cause(ctx))	COMMENT
LOW	pkg/client/informers/externalversions/factory.go	281	StartWithContext(ctx context.Context)	COMMENT
LOW	pkg/client/clientset/versioned/scheme/register.go	21	// AddToScheme adds all types of this clientset into the given scheme. This allows composition	COMMENT
LOW	pkg/client/clientset/versioned/fake/register.go	21	// AddToScheme adds all types of this clientset into the given scheme. This allows composition	COMMENT
LOW	pkg/flagenv/flagenv.go	1	// Package flagenv implements a simple way to expose all your flags as environmental variables.	COMMENT

Structural Annotation Overuse2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	site/content/docs/latest/tutorials/getting-started.md	22	## Step 1: Install Sealed Secrets	COMMENT
LOW	site/content/docs/latest/tutorials/getting-started.md	129	## Step 2: Encrypt local secrets into Sealed Secrets	COMMENT

TODO Padding1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	cmd/kubeseal/main_test.go	256	// TODO: Add test cases.	COMMENT