AI Slop Code RIsk Monitor

ProvableHQ/snarkOS

A Decentralized Operating System for ZK Applications

5.6 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for ProvableHQ/snarkOS, a Rust project with 4,530 GitHub stars. SynthScan examined 90,102 lines of code across 321 source files, recording 409 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 5.6 (Moderate 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.

5.6
Adjusted Signal
5.6
Raw Pattern Score
100%
Time Factor
2026-10-09
Last Push
4.5K
Stars
Rust
Language
90.1K
Lines of Code
321
Files
409
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 23.7/100 · LOW

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

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

PR Review Velocity Impact 23.9/100 · LOW

Which changes need focused human review? 409 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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 1MEDIUM 39LOW 369

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

Over-Commented Block353 hits · 353 pts
SeverityFileLineSnippetContext
LOWbuild.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWsnarkos/main.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOW.ci/utils.sh1#!/bin/bashCOMMENT
LOW.ci/test_partial_upgrade.sh1#!/bin/bashCOMMENT
LOW.ci/test_full_upgrade.sh1#!/bin/bashCOMMENT
LOWcli/build.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/tests/e2e.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/lib.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/start.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/start.rs141COMMENT
LOWcli/src/commands/start.rs161COMMENT
LOWcli/src/commands/start.rs181 /// These peers will be set as "trusted", which means the node will not disconnect from them when performing peer roCOMMENT
LOWcli/src/commands/start.rs241COMMENT
LOWcli/src/commands/start.rs261 #[clap(long, group = "jwt_flags")]COMMENT
LOWcli/src/commands/start.rs281COMMENT
LOWcli/src/commands/start.rs301 #[clap(long)]COMMENT
LOWcli/src/commands/start.rs321 #[clap(long, verbatim_doc_comment)]COMMENT
LOWcli/src/commands/start.rs341 /// If you do not explicitly set the `--peers` flag, this will also populate the set of trusted peers, so that the nCOMMENT
LOWcli/src/commands/start.rs1081 Ok(())COMMENT
LOWcli/src/commands/clean.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/update.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/mod.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/account.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/account.rs41COMMENT
LOWcli/src/commands/account.rs61 /// Try until an address with the vanity string is foundCOMMENT
LOWcli/src/commands/account.rs81 discreet: bool,COMMENT
LOWcli/src/commands/developer/decrypt.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/developer/execute.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/developer/execute.rs61 private_key: Option<String>,COMMENT
LOWcli/src/commands/developer/execute.rs81 /// The record to spend the fee from.COMMENT
LOWcli/src/commands/developer/deploy.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/developer/deploy.rs61 /// Use a developer validator key tok generate the deployment.COMMENT
LOWcli/src/commands/developer/deploy.rs81 #[clap(short, long)]COMMENT
LOWcli/src/commands/developer/mod.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/developer/mod.rs101 /// [options: 0 = mainnet, 1 = testnet, 2 = canary]COMMENT
LOWcli/src/commands/developer/scan.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/developer/scan.rs61COMMENT
LOWcli/src/commands/developer/transfer_private.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/commands/developer/transfer_private.rs41pub struct TransferPrivate {COMMENT
LOWcli/src/commands/developer/transfer_private.rs61 ///COMMENT
LOWcli/src/commands/account/sign.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/updater.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/logger.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/logger.rs121///COMMENT
LOWcli/src/helpers/log_fields.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/mod.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/dynamic_format.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/bech32m.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/bech32m.rs21/// ```ignoreCOMMENT
LOWcli/src/helpers/dev.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/log_writer.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/args.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWcli/src/helpers/fd_check.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWutilities/src/callback_handle.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWutilities/src/node_data.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWutilities/src/lib.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWutilities/src/signals.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWdisplay/src/lib.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWdisplay/src/tabs.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
LOWdisplay/src/pages/mod.rs1// Copyright (c) 2019-2026 Provable Inc.COMMENT
293 more matches not shown…
Self-Referential Comments26 hits · 78 pts
SeverityFileLineSnippetContext
MEDIUM.ci/bench_cdn_sync.sh27# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/bench_cdn_sync.sh34# Define a trap handler that prints a message when an error occurs.COMMENT
MEDIUM.ci/test_restart_majority.sh49# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/test_restart_majority.sh52# Define a trap handler that prints a message when an error occursCOMMENT
MEDIUM.ci/test_partial_upgrade.sh42# Create the log directoryCOMMENT
MEDIUM.ci/bench_bft_sync.sh40# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/bench_bft_sync.sh47# Define a trap handler that prints a message when an error occursCOMMENT
MEDIUM.ci/bench_rest_api.sh32# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/bench_rest_api.sh35# Define a trap handler that prints a message when an error occurs.COMMENT
MEDIUM.ci/generate_ledger.sh41# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/generate_ledger.sh48# Define a trap handler that prints a message when an error occursCOMMENT
MEDIUM.ci/test_restart_all.sh39# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/test_restart_all.sh42# Define a trap handler that prints a message when an error occursCOMMENT
MEDIUM.ci/test_db_backup.sh32# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/test_db_backup.sh35# Define a trap handler that prints a message when an error occursCOMMENT
MEDIUM.ci/test_devnet.sh40# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/test_devnet.sh53# Define a trap handler that prints a message when an error occursCOMMENT
MEDIUM.ci/test_reset_minority.sh39# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/test_reset_minority.sh42# Define a trap handler that prints a message when an error occursCOMMENT
MEDIUM.ci/bench_p2p_sync.sh90# Define a trap handler that cleans up all processes on exit.COMMENT
MEDIUM.ci/bench_p2p_sync.sh93# Define a trap handler that prints a message when an error occurs.COMMENT
MEDIUMscripts/delay-network.sh83 # Create the Priority QueueCOMMENT
MEDIUMscripts/devnet.sh124 # Create an array to store background processesCOMMENT
MEDIUMscripts/devnet.sh141# Create a timestamp-based directory for log filesCOMMENT
MEDIUMscripts/devnet.sh145# Create a new tmux session named "devnet"COMMENT
MEDIUMscripts/devnet.sh193 # Create a new window with a unique nameCOMMENT
AI Slop Vocabulary7 hits · 21 pts
SeverityFileLineSnippetContext
MEDIUMnode/bft/src/gateway.rs1585 // Make the socket more robust; every other handshake in the node does this too.COMMENT
MEDIUMnode/bft/src/helpers/storage.rs585 // As for the `test_network` clause, a more robust approach would be to set theCOMMENT
MEDIUMnode/sync/src/ping.rs34/// Essentially, ping keeps an ordered map `next_ping` of time(rs) to peer IPs.COMMENT
MEDIUMnode/src/validator/router.rs54 // Make the socket more robust.COMMENT
MEDIUMnode/src/bootstrap_client/handshake.rs117 // Make the socket more robust.COMMENT
MEDIUMnode/src/prover/router.rs54 // Make the socket more robust.COMMENT
MEDIUMnode/src/client/router.rs57 // Make the socket more robust.COMMENT
Decorative Section Separators6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMscripts/chaotic-network-runner.sh3# ==========================================COMMENT
MEDIUMscripts/chaotic-network-runner.sh5# ==========================================COMMENT
MEDIUMscripts/chaotic-network-runner.sh36# ==========================================COMMENT
MEDIUMscripts/chaotic-network-runner.sh38# ==========================================COMMENT
MEDIUMscripts/chaotic-network-runner.sh72# ==========================================COMMENT
MEDIUMscripts/chaotic-network-runner.sh74# ==========================================COMMENT
Redundant / Tautological Comments7 hits · 10 pts
SeverityFileLineSnippetContext
LOW.ci/utils.sh33# Check if any tracked node process has exited.COMMENT
LOW.ci/utils.sh150 # Check if count is greater than max_index + 1 (impossible request)COMMENT
LOW.ci/utils.sh171 # Check if PID exists (is not empty) and is currently runningCOMMENT
LOWscripts/delay-network.sh18# Check if the a command this script depends on existCOMMENT
LOWscripts/devnet.sh163# Loop through the list of validator indices and create a new window for eachCOMMENT
LOWscripts/devnet.sh185 # Loop through the list of client indices and create a new window for eachCOMMENT
LOWscripts/chaotic-network-runner.sh20# Check if there is a command to run leftCOMMENT
Verbosity Indicators5 hits · 10 pts
SeverityFileLineSnippetContext
LOW⚡node/network/src/peering.rs678 // Step 1: insert as a candidate.COMMENT
LOW⚡node/network/src/peering.rs687 // Step 2: promote to connecting.COMMENT
LOW⚡node/network/src/peering.rs696 // Step 3: complete the handshake — upgrade to connected.COMMENT
LOWnode/bft/src/helpers/storage.rs964 // Note that the ledger does *not* store aborted transmissions, so we need to check if the solutionCOMMENT
LOWnode/bft/src/helpers/storage.rs988 // Note that the ledger does *not* store aborted transmissions, so we need to check if the transactiCOMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHnode/rest/src/routes.rs168/// maximum applies to the range as requested. A height missing at or below the tip is left in theCOMMENT
Structural Annotation Overuse3 hits · 7 pts
SeverityFileLineSnippetContext
LOW⚡node/network/src/peering.rs678 // Step 1: insert as a candidate.COMMENT
LOW⚡node/network/src/peering.rs687 // Step 2: promote to connecting.COMMENT
LOW⚡node/network/src/peering.rs696 // Step 3: complete the handshake — upgrade to connected.COMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.ci/rest_api_helper.py74 except Exception as err:CODE