2.5

Adjusted Signal

2.5

Raw Pattern Score

100%

Time Factor

2026-09-18

Last Push

32.0K

Stars

Rust

Language

419.1K

Lines of Code

1.3K

Files

982

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

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 0.5/100 · LOW

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

PR Review Velocity Impact 11.6/100 · LOW

Which changes need focused human review? 982 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 1MEDIUM 24LOW 957

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 982 distinct pattern matches across 11 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 Block879 hits · 839 pts

Severity	File	Line	Snippet	Context
LOW	spellcheck-cfg.toml	1	# cargo-spellcheck config	COMMENT
LOW	spellcheck-cfg.toml	21	# This must be in a directory in which hunspell looks for dictionaries.	COMMENT
LOW	spellcheck-cfg.toml	41	# Transforms words that are provided by the tokenizer	COMMENT
LOW	spellcheck-cfg.toml	61	[NlpRules]	COMMENT
LOW	…2e/tests/burn_completion_requires_on_chain_evidence.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/tests/e2e/tests/multi_tx_burn_chunking.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	…e/tests/multiple_burns_same_recipient_across_blocks.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/tests/e2e/tests/burns_per_evm_tx.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/tests/e2e/tests/burns_per_evm_tx.rs	41	/// constraint.	COMMENT
LOW	linera-bridge/tests/e2e/tests/auto_deposit_scan.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	…ra-bridge/tests/e2e/tests/multiple_burns_same_block.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/block_proof.rs	21	/// signatures. The header's hash is the value the validators signed and commits to the whole body	COMMENT
LOW	linera-bridge/src/lib.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/lib.rs	41		COMMENT
LOW	linera-bridge/src/main.rs	21	#[derive(Parser, Debug)]	COMMENT
LOW	linera-bridge/src/main.rs	161	/// Maximum number of retry attempts for pending deposits and burns.	COMMENT
LOW	linera-bridge/src/abi.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/abi.rs	21	#[derive(Clone, Debug, Deserialize, Eq, PartialEq, Serialize)]	COMMENT
LOW	linera-bridge/src/abi.rs	61	/// Replace the bridge's RPC endpoint. Chain-owner-only.	COMMENT
LOW	linera-bridge/src/abi.rs	81	},	COMMENT
LOW	linera-bridge/src/contracts.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/proof/gen.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/proof/gen.rs	41	/// All data needed to submit a `ProcessDeposit` operation to the evm-bridge app.	COMMENT
LOW	linera-bridge/src/proof/mod.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/proof/mod.rs	21	//! 3. `decode_receipt_logs` — Decode the receipt's RLP to extract its event logs.	COMMENT
LOW	linera-bridge/src/proof/mod.rs	41	//! // 1. Decode the block header to get the receipts root.	COMMENT
LOW	linera-bridge/src/proof/mod.rs	81		COMMENT
LOW	linera-bridge/src/monitor/linera.rs	181	/// Iterative LIFO binary search: keep halving slices that don't fit until	COMMENT
LOW	linera-bridge/src/monitor/linera.rs	241	/// keeps a single RPC hiccup from permanently failing a relayable burn — is	COMMENT
LOW	linera-bridge/src/monitor/db.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/monitor/mod.rs	81	/// Replay-protection key identifying this deposit `(source_chain_id, block_hash, tx_index, log_index)`.	COMMENT
LOW	linera-bridge/src/monitor/mod.rs	101	/// Height of the Linera block that produced this burn.	COMMENT
LOW	linera-bridge/src/monitor/mod.rs	121	/// Amount of tokens to release on the EVM side.	COMMENT
LOW	linera-bridge/src/monitor/mod.rs	161	/// (`event_indices` and `by_tx`) describe the same set of burns under one	COMMENT
LOW	linera-bridge/src/relay/settlement.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	linera-bridge/src/relay/settlement.rs	21	}	COMMENT
LOW	linera-bridge/src/relay/mod.rs	1	// Copyright (c) Zefchain Labs, Inc.	COMMENT
LOW	docker/docker-compose.bridge-mainnet.yml	1	# Long-running linera-bridge relayer.	COMMENT
LOW	docker/docker-compose.bridge-mainnet.yml	21	# 4. Ensure the tmpfs cache dir exists, owned root and mode 0700:	COMMENT
LOW	docker/docker-compose.alloy.yml	1	# Docker Compose override file to enable Grafana Alloy for central observability	COMMENT
LOW	linera-base/src/data_types.rs	41	vm::VmRuntime,	COMMENT
LOW	linera-base/src/data_types.rs	161	}	COMMENT
LOW	linera-base/src/data_types.rs	181	pub type CanonicalBTreeMap<K, V> = BTreeMap<K, V>;	COMMENT
LOW	linera-base/src/data_types.rs	661	/// A request to send a message.	COMMENT
LOW	linera-base/src/data_types.rs	1321	#[graphql(default)]	COMMENT
LOW	linera-base/src/data_types.rs	1421	/// A checkpoint of the chain's execution state was published. The execution-state	COMMENT
LOW	linera-base/src/data_types.rs	1561	}	COMMENT
LOW	linera-base/src/identifiers.rs	261	/// A generic data blob.	COMMENT
LOW	linera-base/src/identifiers.rs	521		COMMENT
LOW	linera-base/src/identifiers.rs	1481	// -> Hashable::write into a Keccak256 hasher	COMMENT
LOW	linera-base/src/lib.rs	61	/// # Examples	COMMENT
LOW	linera-base/src/lib.rs	81		COMMENT
LOW	linera-base/src/lib.rs	101	/// bytes: vec![0x12, 0x34, 0x56, 0x78],	COMMENT
LOW	linera-base/src/lib.rs	141	/// #[debug(with = "hex_vec_debug")]	COMMENT
LOW	linera-base/src/task.rs	21	///	COMMENT
LOW	linera-base/src/task.rs	41	/// Spawns `future` on the runtime and awaits its completion.	COMMENT
LOW	linera-base/src/unit_tests.rs	21	#[test_case(&AccountPublicKey::test_key(255); "of_public_key")]	COMMENT
LOW	linera-base/src/task_processor.rs	1	// Copyright (c) Facebook, Inc. and its affiliates.	COMMENT
LOW	linera-base/src/task_processor.rs	21	/// processTaskOutcome(outcome: TaskOutcome!)	COMMENT
LOW	linera-base/src/task_processor.rs	41		COMMENT
819 more matches not shown…

Verbosity Indicators25 hits · 44 pts

Severity	File	Line	Snippet	Context
LOW⚡	linera-faucet/server/src/tests.rs	685	// Step 1: Daily claim should fail before initial claim.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	695	// Step 2: Do the initial claim to create a chain.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	703	// Step 3: Daily claim should fail in period 0 (same period as initial claim).	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	713	// Step 4: Advance clock by 25 hours to enter period 1.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	717	// Step 5: Daily claim should now succeed.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	734	// Step 6: Second daily claim in the same period should fail.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	744	// Step 7: Advance clock by another 24 hours to enter period 2.	COMMENT
LOW	examples/bridge-demo/index.html	558	// Step 1: Approve + Deposit on EVM	COMMENT
LOW	examples/bridge-demo/index.html	570	// Step 3: Wait for relay to auto-detect and process the deposit	COMMENT
LOW	examples/bridge-demo/index.html	599	// Step 1: Submit a Burn to the evm-bridge app. The bridge moves the	COMMENT
LOW⚡	examples/bridge-demo/index.html	614	// Step 2: Wait for relay to forward the burn to EVM	COMMENT
LOW⚡	examples/bridge-demo/index.html	617	// Step 3: Poll EVM balance	COMMENT
LOW⚡	linera-core/src/unit_tests/worker_tests.rs	4749	// Step 2: Process both certs on chain_1 (adds heights 0, 1 to outbox for chain_2).	COMMENT
LOW⚡	linera-core/src/unit_tests/worker_tests.rs	4757	// Step 3: Deliver height 0 to chain_2 and confirm it on chain_1.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4727	// Step 1: Create two transfer certificates from chain_1 to chain_2.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4768	// Step 4: Send a spurious ConfirmUpdatedRecipient that claims chain_2 already	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4789	// Step 5: Create cert_2 from chain_1 (height 2), process it on chain_1, and	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4834	// Step 7: Verify recovery — chain_2 received all three heights.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4885	// Step 1: Create and fully process block 0 (transfer from chain to target).	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4909	// Step 2: Plant a confirmed vote in the chain manager. After the reset, it must	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4920	// Step 3: Corrupt `previous_message_blocks` in storage. This directly affects	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4935	// Step 3: Create block 1 certificate.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4947	// Step 4: Verify that WITHOUT recovery, processing fails with CorruptedChainState.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	5007	// Step 5: Now create a worker WITH recovery enabled and a whitelist that	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	5051	// Step 6: Verify recovery — chain should be at height 2 with correct state.	COMMENT

Structural Annotation Overuse25 hits · 44 pts

Severity	File	Line	Snippet	Context
LOW⚡	linera-faucet/server/src/tests.rs	685	// Step 1: Daily claim should fail before initial claim.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	695	// Step 2: Do the initial claim to create a chain.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	703	// Step 3: Daily claim should fail in period 0 (same period as initial claim).	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	713	// Step 4: Advance clock by 25 hours to enter period 1.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	717	// Step 5: Daily claim should now succeed.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	734	// Step 6: Second daily claim in the same period should fail.	COMMENT
LOW⚡	linera-faucet/server/src/tests.rs	744	// Step 7: Advance clock by another 24 hours to enter period 2.	COMMENT
LOW	examples/bridge-demo/index.html	558	// Step 1: Approve + Deposit on EVM	COMMENT
LOW	examples/bridge-demo/index.html	570	// Step 3: Wait for relay to auto-detect and process the deposit	COMMENT
LOW	examples/bridge-demo/index.html	599	// Step 1: Submit a Burn to the evm-bridge app. The bridge moves the	COMMENT
LOW⚡	examples/bridge-demo/index.html	614	// Step 2: Wait for relay to forward the burn to EVM	COMMENT
LOW⚡	examples/bridge-demo/index.html	617	// Step 3: Poll EVM balance	COMMENT
LOW⚡	linera-core/src/unit_tests/worker_tests.rs	4749	// Step 2: Process both certs on chain_1 (adds heights 0, 1 to outbox for chain_2).	COMMENT
LOW⚡	linera-core/src/unit_tests/worker_tests.rs	4757	// Step 3: Deliver height 0 to chain_2 and confirm it on chain_1.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4727	// Step 1: Create two transfer certificates from chain_1 to chain_2.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4768	// Step 4: Send a spurious ConfirmUpdatedRecipient that claims chain_2 already	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4789	// Step 5: Create cert_2 from chain_1 (height 2), process it on chain_1, and	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4834	// Step 7: Verify recovery — chain_2 received all three heights.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4885	// Step 1: Create and fully process block 0 (transfer from chain to target).	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4909	// Step 2: Plant a confirmed vote in the chain manager. After the reset, it must	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4920	// Step 3: Corrupt `previous_message_blocks` in storage. This directly affects	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4935	// Step 3: Create block 1 certificate.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	4947	// Step 4: Verify that WITHOUT recovery, processing fails with CorruptedChainState.	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	5007	// Step 5: Now create a worker WITH recovery enabled and a whitelist that	COMMENT
LOW	linera-core/src/unit_tests/worker_tests.rs	5051	// Step 6: Verify recovery — chain should be at height 2 with correct state.	COMMENT

Decorative Section Separators13 hits · 39 pts

Severity	File	Line	Snippet	Context
MEDIUM	linera-bridge/tests/e2e/tests/auto_deposit_scan.rs	341	// ══════════════════════════════════════════════════════════════════	COMMENT
MEDIUM	linera-bridge/tests/e2e/tests/auto_deposit_scan.rs	343	// ══════════════════════════════════════════════════════════════════	COMMENT
MEDIUM	linera-bridge/tests/e2e/tests/auto_deposit_scan.rs	432	// ══════════════════════════════════════════════════════════════════	COMMENT
MEDIUM	linera-bridge/tests/e2e/tests/auto_deposit_scan.rs	434	// ══════════════════════════════════════════════════════════════════	COMMENT
MEDIUM	scripts/deploy-validator.sh	52	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	scripts/deploy-validator.sh	54	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	scripts/deploy-validator.sh	80	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	scripts/deploy-validator.sh	82	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	scripts/deploy-validator.sh	746	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	scripts/deploy-validator.sh	748	# -----------------------------------------------------------------------------	COMMENT
MEDIUM	.github/scripts/format-bench-results.sh	28	# ── Formatting helpers ───────────────────────────────────────────────────────	COMMENT
MEDIUM	.github/scripts/format-bench-results.sh	86	# ── Read benchmark data from JSON files ──────────────────────────────────────	COMMENT
MEDIUM	.github/scripts/format-bench-results.sh	159	# ── Markdown output ──────────────────────────────────────────────────────────	COMMENT

AI Slop Vocabulary7 hits · 21 pts

Severity	File	Line	Snippet	Context
MEDIUM	docker/compose-scylla-setup.sh	69	# Based on ScyllaDB documentation and best practices	COMMENT
MEDIUM	linera-service/src/cli/validator_benchmark/tip_lag.rs	52	// chain, so this is the robust source. NOTE: it is the genesis committee;	COMMENT
MEDIUM	.github/workflows/instruction-count-benchmarks.yml	7	# (author-date vs artifact-creation-date mismatch), the bench harness spawns a	COMMENT
MEDIUM	.github/workflows/docker_image.yml	138	# tool used by the test harness and does not need a DB backend,	COMMENT
MEDIUM	.github/workflows/docker_image.yml	140	# does not require --metrics-port, which the test harness does not pass.	COMMENT
MEDIUM	linera-core/src/chain_worker/state.rs	785	// Verify the certificate. Returns a catch-all error to make client code more robust.	COMMENT
MEDIUM	linera-core/src/chain_worker/state.rs	879	// Verify the certificate. Returns a catch-all error to make client code more robust.	COMMENT

Redundant / Tautological Comments13 hits · 20 pts

Severity	File	Line	Snippet	Context
LOW	docker/compose-scylla-setup.sh	25	# Check if running with sufficient privileges	COMMENT
LOW	docker/compose-scylla-setup.sh	243	# Check if config already exists	COMMENT
LOW	scripts/deploy-validator.sh	217	# Check if a command exists	COMMENT
LOW	scripts/deploy-validator.sh	222	# Check if Docker Compose plugin is installed	COMMENT
LOW	scripts/deploy-validator.sh	395	# Check if we should skip genesis download	COMMENT
LOW	scripts/deploy-validator.sh	432	# Check if wget is available	COMMENT
LOW	scripts/deploy-validator.sh	460	# Check if genesis configuration already exists	COMMENT
LOW	scripts/deploy-validator.sh	638	# Check if path exists	COMMENT
LOW	scripts/deploy-validator.sh	645	# Check if path is mounted	COMMENT
LOW	scripts/deploy-validator.sh	913	# Check if XFS is configured (optional - just for information)	COMMENT
LOW	scripts/check_chain_loads.sh	3	# Check if there aren't any unexpected chain load operations	COMMENT
LOW	scripts/backup-validator-keys.sh	29	# Check if container exists and is running	COMMENT
LOW	scripts/backup-validator-keys.sh	40	# Check if path exists in container	COMMENT

Fake / Example Data9 hits · 14 pts

Severity	File	Line	Snippet	Context
LOW⚡	linera-views/src/test_utils/test_views.rs	62	let dummy_value = 82;	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	63	self.byte.set(dummy_value);	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	64	Ok(dummy_value)	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	68	let dummy_value = 209;	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	69	self.byte.set(dummy_value);	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	70	Ok(dummy_value)	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	74	let dummy_value = 15;	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	75	self.byte.set(dummy_value);	CODE
LOW⚡	linera-views/src/test_utils/test_views.rs	76	Ok(dummy_value)	CODE

Self-Referential Comments3 hits · 9 pts

Severity	File	Line	Snippet	Context
MEDIUM	docker/compose-scylla-setup.sh	304	# Create a flag file to indicate setup is complete	COMMENT
MEDIUM	scripts/deploy-validator.sh	1066	# This file is the source of truth for Docker Compose configuration	COMMENT
MEDIUM	scripts/fix-validator-env.sh	61	# This file is now the source of truth for Docker Compose configuration	COMMENT

Example Usage Blocks5 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	docker/docker-compose.alloy.yml	3	# Usage:	COMMENT
LOW	examples/bridge-demo/setup.sh	8	# Usage:	COMMENT
LOW	examples/bridge-demo/spawn-relayer.sh	9	# Usage:	COMMENT
LOW	scripts/test_publish.sh	10	# Usage:	COMMENT
LOW	scripts/memleak_translate.sh	9	# Usage:	COMMENT

Synthetic Comment Markers1 hit · 8 pts

Severity	File	Line	Snippet	Context
HIGH	linera-views/src/batch.rs	37	/// A write operation as requested by a view when it needs to persist staged changes.	COMMENT

Slop Phrases2 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	linera-execution/build.rs	17	// If you change this, don't forget to update `WasmRuntime` and	COMMENT
MEDIUM	examples/counter-no-graphql/src/service.rs	44	// Check that they are equal (for demonstration purposes)	COMMENT

linera-io/linera-protocol

Open-Source Code Quality, Security and Technical Debt Review