AI Slop Code Risk Monitor

prest/prest

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

Instant REST and MCP APIs for PostgreSQL and MySQL, on existing or new databases. CRUD, custom SQL routes, auth and ACL without writing a backend. Low-code, ⚡ realtime, high-performance. Native MySQL support since v2.5

2.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for prest/prest, a Go project with 4,632 GitHub stars. SynthScan examined 79,519 lines of code across 465 source files, recording 79 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 2.1 (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.

2.1
Adjusted Signal
2.1
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
4.6K
Stars
Go
Language
79.5K
Lines of Code
465
Files
79
Pattern Hits
2026-10-31
Scan Date
0.01
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 2.6/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.4/100 · LOW

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

Agent Over-Engineering Ratio 6.0/100 · LOW

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

PR Review Velocity Impact 9.2/100 · LOW

Which changes need focused human review? 79 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 3MEDIUM 30LOW 46

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 79 distinct pattern matches across 9 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 Separators28 hits · 99 pts
SeverityFileLineSnippetContext
MEDIUM⚡samples/prest.sample.toml52# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml54# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml61# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml67# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml74# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml76# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml107# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml109# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml115# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml122# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml221# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml228# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml236# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml238# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml243# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml245# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml253# ------------------------------------------------------------------------COMMENT
MEDIUM⚡samples/prest.sample.toml255# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml146# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml148# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml169# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml171# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml188# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml191# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml269# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml271# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml305# ------------------------------------------------------------------------COMMENT
MEDIUMsamples/prest.sample.toml307# ------------------------------------------------------------------------COMMENT
Over-Commented Block33 hits · 26 pts
SeverityFileLineSnippetContext
LOWdocker-compose.yml61 ports:COMMENT
LOWtestdata/prest_queries.toml61# Lifecycle template registered by integration/helpers.RunQueryRegistryLifecycle onCOMMENT
LOWapp/app.go41// Creates and registers adapters for each configured database. If cfg.Adapter is nilCOMMENT
LOWconfig/config.go161// setupLogger (level debug, overridable with PREST_LOG_LEVEL).COMMENT
LOWintegration/suites/controllers/scripts_test.go361COMMENT
LOWintegration/suites/controllers/scripts_test.go561COMMENT
LOWintegration/postgres/middlewares/config_test.go321COMMENT
LOWintegration/postgres/adapters/postgres/postgres_test.go2601 // SelectSQLCOMMENT
LOW…egration/postgres/controllers/queries_database_test.go21// testdata/queries contains, mirroring the filesystem-mode assertions inCOMMENT
LOWmiddlewares/cache.go21// different field permissions on the same table.COMMENT
LOWsamples/prest.sample.toml1# Sample pREST configuration file.COMMENT
LOWsamples/prest.sample.toml21# (host, port, user, pass, database, or url). Do not add a second [pg] table.COMMENT
LOWsamples/prest.sample.toml41# before request handling. Each entry is an array-of-tables item (note theCOMMENT
LOWsamples/prest.sample.toml101# rootcert fails startup when engine is mysql.COMMENT
LOWsamples/prest.sample.toml121# database.COMMENT
LOWsamples/prest.sample.toml141# alias = "shop"COMMENT
LOWsamples/prest.sample.toml161encrypt = "bcrypt" # bcrypt | md5COMMENT
LOWsamples/prest.sample.toml181# Alternative to `key`: a raw JWKS document, or a URL to fetch one from.COMMENT
LOWsamples/prest.sample.toml201allow_unscoped_writes = falseCOMMENT
LOWsamples/prest.sample.toml221# ------------------------------------------------------------------------COMMENT
LOWsamples/prest.sample.toml261COMMENT
LOWsamples/prest.sample.toml281# import_policy = "update" # skip | update | errorCOMMENT
LOWsamples/prest.sample.toml301# https://www.postgresql.org/docs/9.5/functions-aggregate.htmlCOMMENT
LOWsamples/prest.sample.toml321# metrics_interval = "15s" # PREST_OTEL_METRICS_INTERVAL; metric export periodCOMMENT
LOWadapters/compat_test.go1package adapters_testCOMMENT
LOWadapters/postgres/postgres.go1841}COMMENT
LOWadapters/postgres/otel.go21// own configuration regardless of construction order. database/sql drivers areCOMMENT
LOWdev/signoz/docker-compose.yaml1# Local SigNoz stack for viewing pREST OpenTelemetry signals (traces, metrics,COMMENT
LOWcontrollers/script.go101COMMENT
LOWcontrollers/script.go181 }COMMENT
LOWcontrollers/script.go241COMMENT
LOWcontrollers/script.go281//COMMENT
LOWcontrollers/script.go381COMMENT
Magic Placeholder Names3 hits · 15 pts
SeverityFileLineSnippetContext
HIGHstudio/README.md90- The "Connect an AI client" snippet uses a `<YOUR_TOKEN>` placeholder ratherCODE
HIGHstudio/src/features/mcp/McpExplorerPage.tsx409 headers: { Authorization: 'Bearer <YOUR_TOKEN>' },CODE
HIGHstudio/src/features/mcp/McpExplorerPage.tsx439 ? 'Replace <YOUR_TOKEN> with your bearer token (kept out of this snippet for safety).'CODE
Fake / Example Data8 hits · 8 pts
SeverityFileLineSnippetContext
LOWplugins/plugins_test.go167 require.NoError(t, os.WriteFile(soPath, []byte("placeholder"), 0o644))CODE
LOWplugins/plugins_test.go206 require.NoError(t, os.WriteFile(soPath, []byte("placeholder"), 0o644))CODE
LOWplugins/plugins_test.go237 require.NoError(t, os.WriteFile(soPath, []byte("placeholder"), 0o644))CODE
LOWplugins/plugins_test.go500 require.NoError(t, os.WriteFile(outside, []byte("placeholder"), 0o644))CODE
LOWintegration/suites/controllers/scripts_test.go529 {"email address", "user@example.com"},CODE
LOWcontrollers/script_test.go432 require.Equal(t, "user@example.com", sanitizeScriptParam("user@example.com"))CODE
LOWcontrollers/script_test.go465 safe := []string{"gopher", "42", "2024-01-01", "user@example.com", "John Doe", "a/b.c",CODE
LOWcontrollers/script_test.go465 safe := []string{"gopher", "42", "2024-01-01", "user@example.com", "John Doe", "a/b.c",CODE
Structural Annotation Overuse3 hits · 7 pts
SeverityFileLineSnippetContext
LOW⚡install-manifests/kubernetes/README.md3## Step 1: Edit deployment.yaml and set the right database urlCOMMENT
LOW⚡install-manifests/kubernetes/README.md13## Step 2: Create the kubernetes deployment, serviceCOMMENT
LOW⚡install-manifests/kubernetes/README.md20## Step 3: Access the consoleCOMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM…mescaledb/controllers/performance_optimization_test.go13 // Expected: pREST generates optimized queries that leverage TimescaleDB'sCOMMENT
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMadapters/postgres/postgres_test.go51// not use t.Parallel(); see agentic-loop serial test rules for shared globals.COMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWdev/signoz/docker-compose.yaml6# Usage:COMMENT
Slop Phrases1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdev/signoz/common/clickhouse/config.xml640 Regexps are not aligned: don't forget to add ^ and $. Also don't forget to escape dot (.) metacharacterCODE