1.6

Adjusted Signal

1.6

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

17.6K

Stars

Rust

Language

46.1K

Lines of Code

403

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

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

Hallucinated Dependency & Supply Chain Risk 0.8/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 6.8/100 · LOW

Which changes need focused human review? 63 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 1LOW 62

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 63 distinct pattern matches across 5 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 Block41 hits · 41 pts

Severity	File	Line	Snippet	Context
LOW	docs/content/documentation/content/page.md	101	# will not be rendered.	COMMENT
LOW	docs/content/documentation/content/page.md	121	# The section path will still be used.	COMMENT
LOW	docs/content/documentation/content/section.md	61	# Lower values have higher priority.	COMMENT
LOW	docs/content/documentation/content/section.md	81		COMMENT
LOW	docs/content/documentation/content/section.md	101	# Useful for the same reason as `render` but when you don't want a 404 when	COMMENT
LOW	…content/documentation/getting-started/configuration.md	81	# The filenames to use for the feeds. Used as the template filenames, too.	COMMENT
LOW	…content/documentation/getting-started/configuration.md	101	# taxonomies = [	COMMENT
LOW	…content/documentation/getting-started/configuration.md	161	# When set to "true", support for GitHub-style alerts, a.k.a. callouts or admonitions, is enabled in the Markdown parser	COMMENT
LOW	…content/documentation/getting-started/configuration.md	241	# Whether to remove date prefixes for page path slugs.	COMMENT
LOW	…content/documentation/getting-started/configuration.md	261	# Whether to produce the search index as a javascript file or as a JSON file	COMMENT
LOW	…content/documentation/getting-started/configuration.md	281	# For example	COMMENT
LOW	docs/content/documentation/templates/pages-sections.md	41	// earlier / heavier	COMMENT
LOW	docs/content/documentation/templates/pages-sections.md	101	assets: Array<String>;	COMMENT
LOW	docs/content/themes/linkita/index.md	321	# If you disable default favicons, you can use	COMMENT
LOW	docs/content/themes/linkita/index.md	341	# Default value: false	COMMENT
LOW	docs/content/themes/linkita/index.md	361	# Information shown on post pages.	COMMENT
LOW	docs/content/themes/linkita/index.md	461		COMMENT
LOW	docs/content/themes/linkita/index.md	541	[extra.languages.en]	COMMENT
LOW	docs/content/themes/coast/index.md	121	# Whether to automatically compile all Sass files in the sass directory	COMMENT
LOW	docs/content/themes/coffee/index.md	121	# When set to "true", the generated HTML files are minified.	COMMENT
LOW	docs/sass/site.scss	21	//@import url("syntax-theme-dark.css") (prefers-color-scheme: dark);	COMMENT
LOW	components/config/src/config/markup.rs	21	/// Emit an error for missing highlight languages. Defaults to false	COMMENT
LOW	components/config/src/config/markup.rs	141	/// Syntax highlighting option	COMMENT
LOW	components/content/src/page.rs	41	/// The HTML rendered of the page	COMMENT
LOW	components/content/src/page.rs	61	pub toc: Vec<Heading>,	COMMENT
LOW	components/content/src/section.rs	41	/// Not listed directly anywhere but we still render them in the queue	COMMENT
LOW	components/content/src/types.rs	1	use serde::{Deserialize, Serialize};	COMMENT
LOW	components/content/src/utils.rs	61	/// Eg if there is the following tree:	COMMENT
LOW	components/content/src/utils.rs	101	/// `unicode_words()`. Unlisted languages fall back to 200 wpm.	COMMENT
LOW	components/content/src/front_matter/page.rs	21	pub title: Option<String>,	COMMENT
LOW	components/content/src/front_matter/page.rs	41	pub datetime_tuple: Option<(i32, u8, u8)>,	COMMENT
LOW	components/content/src/front_matter/page.rs	61	/// redirect to this	COMMENT
LOW	components/content/src/front_matter/section.rs	21	/// Whether to sort by "date", "order", "weight" or "none". Defaults to `none`.	COMMENT
LOW	components/content/src/front_matter/section.rs	41	pub paginate_path: String,	COMMENT
LOW	components/content/src/front_matter/section.rs	61	/// sections for each year under a posts section.	COMMENT
LOW	components/imageproc/tests/resize_image.rs	461	// fn resize_image_png_avif_max_quality_min_speed() {	COMMENT
LOW	components/imageproc/src/ops.rs	1	use errors::{Result, anyhow};	COMMENT
LOW	components/templates/src/helpers.rs	1	use std::borrow::Cow;	COMMENT
LOW	components/templates/src/functions/load_data.rs	481	/// ```	COMMENT
LOW	components/templates/src/functions/load_data.rs	541	/// An example XML file `example.xml` could be:	COMMENT
LOW	src/cmd/serve.rs	1	// Contains an embedded version of livereload-js 3.2.4	COMMENT

Structural Annotation Overuse12 hits · 22 pts

Severity	File	Line	Snippet	Context
LOW	docs/content/documentation/deployment/zeabur.md	14	## Step 1: Create a Project on Zeabur	COMMENT
LOW	docs/content/documentation/deployment/zeabur.md	20	## Step 2: Push Your Zola Files to GitHub	COMMENT
LOW⚡	docs/content/documentation/deployment/zeabur.md	40	## Step 3: Create a Service on Zeabur	COMMENT
LOW⚡	docs/content/documentation/deployment/zeabur.md	45	## Step 4: Select Your Zola Repository	COMMENT
LOW⚡	docs/content/documentation/deployment/zeabur.md	49	## Step 5: Automatic Deployment	COMMENT
LOW⚡	docs/content/documentation/deployment/zeabur.md	56	## Step 6: Domain Binding	COMMENT
LOW⚡	docs/content/documentation/deployment/zeabur.md	62	## Step 7: Your Site is Live!	COMMENT
LOW	docs/content/themes/zola-hacker/index.md	51	### Step 1: Create a new zola site	COMMENT
LOW	docs/content/themes/zola-hacker/index.md	57	### Step 2: Install Zola Hacker Theme	COMMENT
LOW	docs/content/themes/zola-hacker/index.md	74	### Step 3: Configuration	COMMENT
LOW	docs/content/themes/zola-hacker/index.md	89	### Step 4: Add new content	COMMENT
LOW	docs/content/themes/zola-hacker/index.md	100	### Step 5: Run the project	COMMENT

Fake / Example Data7 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW	docs/content/documentation/templates/feeds/index.md	35	name, for example `"John Doe"`. While according to the	CODE
LOW	docs/content/themes/radion/index.md	205	authors = ["John Smith", "Joe Schmoe", "Jane Doe"]	CODE
LOW	docs/content/themes/zola-quiet/index.md	123	author = "Jane Doe"	CODE
LOW	docs/content/themes/zolarwind/index.md	307	authors = ["Jane Doe"]	CODE
LOW	docs/content/themes/zolarwind/index.md	327	- authors: an optional array of all the post's authors, e.g. `["Jane Doe"]`.	CODE
LOW	components/markdown/tests/markdown.rs	324	1. Lorem ipsum dolor sit amet	CODE
LOW	components/markdown/tests/markdown.rs	324	1. Lorem ipsum dolor sit amet	CODE

Slop Phrases2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	components/content/src/library.rs	448	// Don't forget to push the actual parent	COMMENT
LOW	components/site/tests/common.rs	330	// Don't forget to remove / because	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	src/cmd/serve.rs	573	// The first entry is ultimately to watch config.toml in a more robust manner on Linux when	COMMENT

getzola/zola

Open-Source Code Quality, Security and Technical Debt Review