AI Slop Code Risk Monitor

cerbos/cerbos

Name: cerbos/cerbos — 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).

Cerbos is an open-core authorization management platform for authorizing every identity and governing every action across applications, gateways, workloads, and AI agents.

0.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cerbos/cerbos, a Go project with 4,639 GitHub stars. SynthScan examined 344,990 lines of code across 1828 source files, recording 46 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 0.2 (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.

0.2

Adjusted Signal

0.2

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

4.6K

Stars

Language

345.0K

Lines of Code

1.8K

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

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

Hallucinated Dependency & Supply Chain Risk 0.3/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 1.0/100 · LOW

Which changes need focused human review? 46 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 2HIGH 0MEDIUM 3LOW 41

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

Over-Commented Block38 hits · 38 pts

Severity	File	Line	Snippet	Context
LOW	deploy/charts/cerbos/values.yaml	1	# Default values for cerbos.	COMMENT
LOW	deploy/charts/cerbos/values.yaml	21		COMMENT
LOW	deploy/charts/cerbos/values.yaml	41	# Image digest to use. Takes precedence over tag if specified.	COMMENT
LOW	deploy/charts/cerbos/values.yaml	61	# type: [array, null]	COMMENT
LOW	deploy/charts/cerbos/values.yaml	81	# additionalProperties: true	COMMENT
LOW	deploy/charts/cerbos/values.yaml	101	# additionalProperties: true	COMMENT
LOW	deploy/charts/cerbos/values.yaml	121	# @schema	COMMENT
LOW	deploy/charts/cerbos/values.yaml	141	# limits:	COMMENT
LOW	deploy/charts/cerbos/values.yaml	161	# default: false	COMMENT
LOW	deploy/charts/cerbos/values.yaml	181		COMMENT
LOW	deploy/charts/cerbos/values.yaml	201	# @schema	COMMENT
LOW	deploy/charts/cerbos/values.yaml	221	# type: object	COMMENT
LOW	deploy/charts/cerbos/values.yaml	241	# name:	COMMENT
LOW	deploy/charts/cerbos/values.yaml	261	# properties:	COMMENT
LOW	deploy/charts/cerbos/values.yaml	281	# @schema	COMMENT
LOW	deploy/charts/cerbos/values.yaml	301	# @schema	COMMENT
LOW	deploy/charts/cerbos/values.yaml	321	annotations: {}	COMMENT
LOW	deploy/charts/cerbos/values.yaml	341	trafficDistribution: ""	COMMENT
LOW	deploy/charts/cerbos/values.yaml	361	tlsSecretName: ""	COMMENT
LOW	internal/test/test.go	141	Want map[string][]byte	COMMENT
LOW	…ata/policy_formats/single_policy_others_commented.yaml	21	# - actions:	COMMENT
LOW	internal/server/memlimit.go	21	// soft limit: the hard cap equals GOMEMLIMIT + offset + safety, where safety	COMMENT
LOW	internal/storage/db/internal/db.go	661	// Rather than writing a proper recursive query (which is pretty much impossible to do in a database-agnostic way), we'	COMMENT
LOW	internal/storage/db/internal/db.go	761	return err	COMMENT
LOW	internal/audit/conf.go	61	// Consider the following:	COMMENT
LOW	internal/audit/hub/filter.go	381	// - or bracket-notation: `['foo']['bar']['baz]`	COMMENT
LOW	hack/copyright_header.txt	1	// Copyright 2021-2026 Zenauth Ltd.	COMMENT
LOW	hack/loadtest/analyse_latency.sh	1	#!/usr/bin/env bash	COMMENT
LOW	hack/loadtest/gcp/sweep.sh	1	#!/usr/bin/env bash	COMMENT
LOW	…s/modules/deployment/examples/cerbos-sidecar-demo.yaml	21	---	COMMENT
LOW	api/genpb/cerbos/runtime/v1/runtime.pb.go	621	}	COMMENT
LOW	api/genpb/cerbos/svc/v1/svcv1connect/svc.connect.go	21	// This is a compile-time assertion to ensure that this generated file and the connect package are	COMMENT
LOW	api/genpb/cerbos/svc/v1/svcv1connect/svc.connect.go	41	// google.golang.org/protobuf/reflect/protoreflect. To convert from these constants to	COMMENT
LOW	api/genpb/cerbos/svc/v1/svcv1connect/svc.connect.go	61	// CerbosAdminService's AddOrUpdatePolicy RPC.	COMMENT
LOW	api/genpb/cerbos/svc/v1/svcv1connect/svc.connect.go	81	// CerbosAdminServiceListAuditLogEntriesProcedure is the fully-qualified name of the	COMMENT
LOW	api/genpb/cerbos/private/v1/test.pb.go	461	WantError bool `protobuf:"varint,3,opt,name=want_error,json=wantError,proto3" json:"want_error,omit	COMMENT
LOW	api/genpb/authzen/authorization/v1/svc_grpc.pb.go	81		COMMENT
LOW	…authorization/v1/authorizationv1connect/svc.connect.go	21	// generated with a version of connect newer than the one compiled into your binary. You can fix the	COMMENT

Hallucination Indicators2 hits · 20 pts

Severity	File	Line	Snippet	Context
CRITICAL	api/genpb/cerbos/response/v1/response.pb.go	3397	"\tvariables\x18\x02 \x03(\v24.cerbos.response.v1.InspectPoliciesResponse.VariableB(\x92A%2#Variables referenced in the	CODE
CRITICAL	api/genpb/cerbos/response/v1/response.pb.go	3403	"\tconstants\x18\x06 \x03(\v24.cerbos.response.v1.InspectPoliciesResponse.ConstantB(\x92A%2#Constants referenced in the	CODE

Self-Referential Comments2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	deploy/charts/cerbos/values-git-storage.yaml	30	# Create an environment variable from the GitHub PAT stored in a secret.	COMMENT
MEDIUM	hack/scripts/prep-release.sh	88	# Create a release branch	COMMENT

Slop Phrases1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	…s/modules/deployment/examples/cerbos-sidecar-demo.yaml	25	# sidecar (`cerbos` container) for demonstration purposes. In a real	COMMENT

Excessive Try-Catch Wrapping2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	docs/modules/policies/examples/example.py	46	except Exception:	CODE
LOW	docs/modules/ROOT/examples/quickstart/example.py	49	except Exception:	CODE

Example Usage Blocks1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	hack/loadtest/analyse_latency.sh	11	# Usage:	COMMENT