1.2

Adjusted Signal

1.2

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

7.7K

Stars

Rust

Language

77.0K

Lines of Code

469

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

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

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

PR Review Velocity Impact 6.0/100 · LOW

Which changes need focused human review? 95 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 0LOW 95

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 95 distinct pattern matches across 3 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 Block93 hits · 93 pts

Severity	File	Line	Snippet	Context
LOW	crates/youki/src/main.rs	21	pub systemd_log: bool,	COMMENT
LOW	crates/youki/src/main.rs	61	}	COMMENT
LOW	crates/youki/src/commands/foreground.rs	341	// the signal forwarding loops. There is no way to 100% sync	COMMENT
LOW	crates/libcgroups/src/lib.rs	1	//! Control groups provide a way of controlling groups of processes.	COMMENT
LOW	crates/libcgroups/src/v1/blkio.rs	21	// Upper limit on the number of write operations a device can perform specified in operations per second	COMMENT
LOW	crates/libcgroups/src/v1/blkio.rs	41	// to the cgroup. This overrides the the blkio.weight value for the specified device	COMMENT
LOW	crates/libcgroups/src/systemd/memory.rs	81	// positive value. Swap needs to be bigger than the memory limit (due to swap being memory + swap)	COMMENT
LOW	crates/libcgroups/src/systemd/manager.rs	41	/// Root path of the cgroup hierarchy e.g. /sys/fs/cgroup	COMMENT
LOW	crates/libcgroups/src/systemd/dbus_native/dbus.rs	21		COMMENT
LOW	crates/libcgroups/src/systemd/dbus_native/dbus.rs	341	}	COMMENT
LOW	crates/libcgroups/src/systemd/dbus_native/serialize.rs	1	use super::utils::{DbusError, Result, adjust_padding, align_counter};	COMMENT
LOW	crates/libcgroups/src/v2/devices/controller.rs	81		COMMENT
LOW	crates/libcgroups/src/v2/devices/emulator.rs	1	use oci_spec::runtime::{LinuxDeviceCgroup, LinuxDeviceType};	COMMENT
LOW	crates/liboci-cli/src/features.rs	1	use clap::Args;	COMMENT
LOW	crates/liboci-cli/src/exec.rs	1	use std::error::Error;	COMMENT
LOW	crates/liboci-cli/src/exec.rs	21	pub tty: bool,	COMMENT
LOW	crates/liboci-cli/src/exec.rs	41	#[arg(long)]	COMMENT
LOW	crates/liboci-cli/src/checkpoint.rs	1	use std::path::PathBuf;	COMMENT
LOW	crates/liboci-cli/src/checkpoint.rs	21	pub leave_running: bool,	COMMENT
LOW	crates/liboci-cli/src/checkpoint.rs	41	// #[arg(long)]	COMMENT
LOW	crates/liboci-cli/src/lib.rs	81	/// set the log file to write youki logs to (default is '/dev/stderr')	COMMENT
LOW	crates/liboci-cli/src/create.rs	1	//! Handles the creation of a new container	COMMENT
LOW	crates/liboci-cli/src/run.rs	1	use std::path::PathBuf;	COMMENT
LOW	crates/liboci-cli/src/run.rs	21	/// Do not use pivot root to jail process inside rootfs	COMMENT
LOW	crates/libcontainer/src/tty.rs	1	//! tty (teletype) for user-system interaction	COMMENT
LOW	crates/libcontainer/src/tty.rs	161	const PTY_SLAVE_MAJOR: u64 = 136;	COMMENT
LOW	crates/libcontainer/src/tty.rs	281	/// 1. Create PTY pair from /dev/pts/ptmx (we're already in the container),	COMMENT
LOW	crates/libcontainer/src/tty.rs	361	/// console-socket path the receiver of the master owns the termios, so it is	COMMENT
LOW	crates/libcontainer/src/hooks.rs	121	// Rust does not make it easy to handle executing a command and	COMMENT
LOW	crates/libcontainer/src/utils.rs	261	#[error("metadata doesn't match the expected attributes")]	COMMENT
LOW	crates/libcontainer/src/utils.rs	281	///	COMMENT
LOW	crates/libcontainer/src/rootfs/mount.rs	41	// runc has a retry interval of 100ms. We are following this.	COMMENT
LOW	crates/libcontainer/src/rootfs/mount.rs	981	mount_attr.attr_set \|= non_atime;	COMMENT
LOW	crates/libcontainer/src/rootfs/mount.rs	1001	/// let mount = SpecMountBuilder::default()	COMMENT
LOW	crates/libcontainer/src/rootfs/mount.rs	1021	/// let typ = "bind";	COMMENT
LOW	crates/libcontainer/src/network/cidr.rs	21	}	COMMENT
LOW	crates/libcontainer/src/network/address.rs	81	///	COMMENT
LOW	crates/libcontainer/src/network/address.rs	101	let mut req = NetlinkMessage::from(RouteNetlinkMessage::GetAddress(message));	COMMENT
LOW	crates/libcontainer/src/network/address.rs	141	///	COMMENT
LOW	crates/libcontainer/src/network/link.rs	141	req.header.flags = NLM_F_REQUEST \| NLM_F_ACK;	COMMENT
LOW	crates/libcontainer/src/network/traits.rs	1	use netlink_packet_core::{NetlinkMessage, NetlinkPayload};	COMMENT
LOW	crates/libcontainer/src/network/traits.rs	21	///	COMMENT
LOW	crates/libcontainer/src/network/traits.rs	41	/// A Result indicating success or failure of the send operation	COMMENT
LOW	crates/libcontainer/src/network/traits.rs	61	/// * `handler` - The handler to process the received messages	COMMENT
LOW	crates/libcontainer/src/container/container_events.rs	1	use std::thread;	COMMENT
LOW	crates/libcontainer/src/container/builder_impl.rs	121	let process = self	COMMENT
LOW	crates/libcontainer/src/container/container_pause.rs	1	use libcgroups::common::{CgroupManager, FreezerState};	COMMENT
LOW	crates/libcontainer/src/container/container_resume.rs	1	use libcgroups::common::{CgroupManager, FreezerState};	COMMENT
LOW	crates/libcontainer/src/container/container_delete.rs	21	///	COMMENT
LOW	crates/libcontainer/src/container/container_start.rs	1	use super::{Container, ContainerStatus};	COMMENT
LOW	crates/libcontainer/src/container/container_kill.rs	1	use libcgroups::common::{CgroupManager, get_cgroup_setup};	COMMENT
LOW	crates/libcontainer/src/container/container_criu.rs	61	ns.path().as_ref().map(\|p\| p.to_string_lossy().to_string())	COMMENT
LOW	crates/libcontainer/src/container/state.rs	101	pub oci_version: String,	COMMENT
LOW	crates/libcontainer/src/container/state.rs	241	/// ```	COMMENT
LOW	…tes/libcontainer/src/container/container_checkpoint.rs	181		COMMENT
LOW	crates/libcontainer/src/container/builder.rs	21	/// container process to the higher level runtime	COMMENT
LOW	crates/libcontainer/src/container/builder.rs	41	/// The format of valid ID was never formally defined, instead the code	COMMENT
LOW	crates/libcontainer/src/container/builder.rs	81	///	COMMENT
LOW	crates/libcontainer/src/container/builder.rs	121	}	COMMENT
LOW	crates/libcontainer/src/container/builder.rs	141	/// .as_tenant()	COMMENT
33 more matches not shown…

Example Usage Blocks1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	scripts/cargo.sh	4	# Usage:	COMMENT

Redundant / Tautological Comments1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	experiment/selinux/lima-setup.sh	222	# Check if the instance already exists	COMMENT

youki-dev/youki

Open-Source Code Quality, Security and Technical Debt Review