Repository Analysis

hyperlight-dev/hyperlight

Hyperlight is a lightweight Virtual Machine Manager (VMM) designed to be embedded within applications. It enables safe execution of untrusted code within micro virtual machines with very low latency and minimal overhead.

4.6 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of hyperlight-dev/hyperlight, a Rust project with 4,581 GitHub stars. SynthScan v2.0 examined 94,594 lines of code across 353 source files, recording 382 pattern matches distributed across 9 syntactic categories. The overall adjusted score of 4.6 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

4.6
Adjusted Score
4.6
Raw Score
100%
Time Factor
2026-08-13
Last Push
4.6K
Stars
Rust
Language
94.6K
Lines of Code
353
Files
382
Pattern Hits
2026-08-13
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

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

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 17LOW 365

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 382 distinct pattern matches across 9 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block340 hits · 335 pts
SeverityFileLineSnippetContext
LOW.github/workflows/dep_benchmarks.yml1# yaml-language-server: $schema=https://json.schemastore.org/github-workflow.jsonCOMMENT
LOW.github/workflows/RegenSnapshotGoldens.yml1# yaml-language-server: $schema=https://json.schemastore.org/github-workflow.jsonCOMMENT
LOW.github/workflows/ready-for-review-manage.yml1name: Ready-for-review (manage)COMMENT
LOW.github/workflows/ready-for-review-label.yml1name: Ready-for-review (collect)COMMENT
LOW.github/workflows/dep_update_guest_locks.yml61COMMENT
LOWdev/sync-project-board.sh1#!/bin/bashCOMMENT
LOWdev/check-release-blockers.sh1#!/bin/bashCOMMENT
LOWdev/notify-ci-failure.sh1#!/bin/bashCOMMENT
LOWfuzz/fuzz_targets/virtq_packed_ring.rs141///COMMENT
LOWsrc/hyperlight_component_util/src/resource.rs21use crate::etypes::{TypeBound, Tyvar};COMMENT
LOWsrc/hyperlight_component_util/src/etypes.rs101#[derive(Debug, Clone, Copy, PartialEq)]COMMENT
LOWsrc/hyperlight_component_util/src/etypes.rs321COMMENT
LOWsrc/hyperlight_component_util/src/etypes.rs341 /// element in the list, and later elements can depend on earlierCOMMENT
LOWsrc/hyperlight_component_util/src/etypes.rs441/// gamma in the specificationCOMMENT
LOWsrc/hyperlight_component_util/src/wf.rs61}COMMENT
LOWsrc/hyperlight_component_util/src/rtypes.rs221/// Emit a token stream that references the given type variable in aCOMMENT
LOWsrc/hyperlight_component_util/src/rtypes.rs801/// this instance typeCOMMENT
LOWsrc/hyperlight_component_util/src/substitute.rs21use crate::etypes::{COMMENT
LOWsrc/hyperlight_component_util/src/substitute.rs41 Self: Shiftable<'a>,COMMENT
LOWsrc/hyperlight_component_util/src/substitute.rs301/// fn shifted<'b>(&'b self) -> Shifted<'b, Self::Inner> { Shifted::new(self) }COMMENT
LOWsrc/hyperlight_component_util/src/substitute.rs561 self.how_many += 1;COMMENT
LOWsrc/hyperlight_component_util/src/subtype.rs41 MismatchedResources(ResourceId, ResourceId),COMMENT
LOWsrc/hyperlight_component_util/src/emit.rs321 /// A resource-type index. Currently a resource-type index isCOMMENT
LOWsrc/hyperlight_component_util/src/emit.rs341 /// We use a "helper module" for auxiliary definitions: forCOMMENT
LOWsrc/hyperlight_component_util/src/emit.rs361 /// A path through instance import/export names from the rootCOMMENT
LOWsrc/hyperlight_component_util/src/emit.rs381 /// interfaces, or just the types of the interfaceCOMMENT
LOWsrc/hyperlight_component_util/src/component.rs61/// - a component, whoseCOMMENT
LOWsrc/hyperlight_component_util/src/hl.rs181 let ResolvedBoundVar::Resource { rtidx } = s.resolve_bound_var(*vi) else {COMMENT
LOWsrc/hyperlight_component_util/src/elaborate.rs101 /// Innerizing an outer alias failed; this usually means that theCOMMENT
LOWsrc/hyperlight_host/build.rs21fn main() -> Result<()> {COMMENT
LOWsrc/hyperlight_host/build.rs121 // the `gdb` cfg (gdb feature + debug build).COMMENT
LOWsrc/hyperlight_host/tests/integration_test.rs741// or it may impact other tests.COMMENT
LOWsrc/hyperlight_host/tests/integration_test.rs1361 assert_eq!(COMMENT
LOWsrc/hyperlight_host/tests/integration_test.rs1781 }));COMMENT
LOWsrc/hyperlight_host/tests/integration_test.rs1861 host_region: host_baseCOMMENT
LOWsrc/hyperlight_host/examples/guest-debugging/main.rs121 let out_file_path = format!("{out_dir}/{name}.output");COMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs21//! segment registers, XSAVE state) and guest memory (snapshot, scratch,COMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs41//! [`MultiUseSandbox::generate_crashdump`] explicitly to capture theCOMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs61//!COMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs121COMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs281 println!(COMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs301/// # Find the thread running the guestCOMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs321}COMMENT
LOWsrc/hyperlight_host/examples/crashdump/main.rs501 elf_files.len()COMMENT
LOWsrc/hyperlight_host/src/error.rs41pub enum HyperlightError {COMMENT
LOWsrc/hyperlight_host/src/error.rs121 /// A Host function was called by the guest but it was not registered.COMMENT
LOWsrc/hyperlight_host/src/error.rs161 /// Memory Protection FailedCOMMENT
LOWsrc/hyperlight_host/src/error.rs201COMMENT
LOWsrc/hyperlight_host/src/error.rs221 /// ## RecoveryCOMMENT
LOWsrc/hyperlight_host/src/lib.rs21//! The runtime manages sandbox creation, guest function calls, memory isolation,COMMENT
LOWsrc/hyperlight_host/src/lib.rs41COMMENT
LOWsrc/hyperlight_host/src/lib.rs61/// - Virtual AddressCOMMENT
LOWsrc/hyperlight_host/src/lib.rs81/// Utilities for testing including interacting with `simpleguest` testing guest binaryCOMMENT
LOWsrc/hyperlight_host/src/metrics/mod.rs21// Counter metric that counts the number of times a guest function was called due to timing outCOMMENT
LOW…c/hyperlight_host/src/hyperlight_surrogate/src/main.rs21// which add ~200ms to CreateProcess on ARM64 Windows. The process neverCOMMENT
LOWsrc/hyperlight_host/src/signal_handlers/mod.rs21pub(crate) fn setup_signal_handlers(config: &SandboxConfiguration) -> crate::Result<()> {COMMENT
LOWsrc/hyperlight_host/src/sandbox/uninitialized_evolve.rs61 let peb_addr = {COMMENT
LOWsrc/hyperlight_host/src/sandbox/config.rs41 },COMMENT
LOWsrc/hyperlight_host/src/sandbox/config.rs61 input_data_size: usize,COMMENT
LOWsrc/hyperlight_host/src/sandbox/config.rs81 ///COMMENT
280 more matches not shown…
Decorative Section Separators8 hits · 33 pts
SeverityFileLineSnippetContext
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs30//! ┌─────────┐ (AVAIL=wrap) ┌───────────┐COMMENT
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs31//! │ Free │ ──────────────────> │ Available │COMMENT
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs32//! └─────────┘ └───────────┘COMMENT
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs38//! ┌─────────┐ ┌───────────┐COMMENT
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs39//! │Reclaimed│ <────────────────── │ Used │COMMENT
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs40//! └─────────┘ └───────────┘COMMENT
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs59//! ┌──────────────┐ ┌──────────────┐ ┌──────────────┐COMMENT
MEDIUMsrc/hyperlight_common/src/virtq/ring.rs64//! └──────────────┘ └──────────────┘ └──────────────┘COMMENT
Redundant / Tautological Comments11 hits · 16 pts
SeverityFileLineSnippetContext
LOW.github/workflows/ReleaseBlockerLabelCleanUp.yml22 # Check if the issue has the release-blocker labelCOMMENT
LOW.github/workflows/dep_update_guest_locks.yml83 # Check if there are any changes to the guest Cargo.lock fileCOMMENT
LOWdev/sync-project-board.sh65 # Check if repo has 'hyperlight' in the nameCOMMENT
LOWdev/auto-approve-dependabot.sh9# Check if repository argument is providedCOMMENT
LOWdev/auto-approve-dependabot.sh40 # Check if PR only modifies allowed filesCOMMENT
LOWdev/auto-approve-dependabot.sh56 # Check if all status checks have passed (regardless of required or not)COMMENT
LOWdev/auto-approve-dependabot.sh105 # Check if PR has been modified by someone other than dependabotCOMMENT
LOWdev/auto-approve-dependabot.sh114 # Check if PR needs approval (i.e., hasn't been approved already)COMMENT
LOWdev/auto-approve-dependabot.sh125 # Check if PR is up-to-date with base branchCOMMENT
LOWdev/check-release-blockers.sh22# Check if repository argument is providedCOMMENT
LOWdev/check-license-headers.sh46 # Check if the file has the license header (allowing for multi-line matching)COMMENT
Structural Annotation Overuse6 hits · 12 pts
SeverityFileLineSnippetContext
LOWdocs/how-to-run-coverage.md16### Step 1: Run tests with coverage instrumentationCOMMENT
LOWdocs/how-to-run-coverage.md32### Step 2: Generate a reportCOMMENT
LOWsrc/hyperlight_guest/src/exit.rs51 // Step 1: Send abort code (typically 1 byte, but `code` allows flexibility)COMMENT
LOWsrc/hyperlight_guest/src/exit.rs54 // Step 2: Convert the C string to bytesCOMMENT
LOWsrc/hyperlight_guest/src/exit.rs57 // Step 3: Send the message itself in chunksCOMMENT
LOWsrc/hyperlight_guest/src/exit.rs60 // Step 4: Send abort terminator to signal completion (e.g., 0xFF)COMMENT
Self-Referential Comments4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/dep_update_guest_locks.yml113 # Create a new tree with the updated filesCOMMENT
MEDIUMdev/check-license-headers.sh8# Define the license header pattern to look forCOMMENT
MEDIUMdev/check-license-headers.sh11# Define the full license header for files that need itCOMMENT
MEDIUMdev/check-license-headers.sh30# Initialize a variable to track missing headersCOMMENT
Slop Phrases3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMsrc/hyperlight_host/examples/guest-debugging/main.rs63 // Note: This function is unused, it's just here for demonstration purposesCOMMENT
MEDIUMsrc/hyperlight_host/examples/hello-world/main.rs32 // Note: This function is unused, it's just here for demonstration purposesCOMMENT
MEDIUMsrc/hyperlight_host/src/mem/shared_mem.rs1055/// racing loads in LLVM return `undef`, as discussed above, we wouldCOMMENT
Verbosity Indicators4 hits · 9 pts
SeverityFileLineSnippetContext
LOWsrc/hyperlight_guest/src/exit.rs51 // Step 1: Send abort code (typically 1 byte, but `code` allows flexibility)COMMENT
LOWsrc/hyperlight_guest/src/exit.rs54 // Step 2: Convert the C string to bytesCOMMENT
LOWsrc/hyperlight_guest/src/exit.rs57 // Step 3: Send the message itself in chunksCOMMENT
LOWsrc/hyperlight_guest/src/exit.rs60 // Step 4: Send abort terminator to signal completion (e.g., 0xFF)COMMENT
AI Slop Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMsrc/hyperlight_host/Cargo.toml152# Custom harness (see main.rs).STRING
MEDIUMsrc/hyperlight_host/build.rs105 // Essentially the kvm and mshv3 features are ignored on windows as long as you use #[cfg(kvm)] and not #[cfg(featurCOMMENT
Fake / Example Data4 hits · 4 pts
SeverityFileLineSnippetContext
LOWsrc/hyperlight_host/tests/integration_test.rs426 let abort_message = "Lorem ipsum dolor sit amet, \CODE
LOWsrc/hyperlight_host/tests/integration_test.rs426 let abort_message = "Lorem ipsum dolor sit amet, \CODE
LOWsrc/hyperlight_host/tests/integration_test.rs442 Dolor sit amet consectetur adipiscing elit pellentesque habitant morbi. \CODE
LOWsrc/hyperlight_host/tests/integration_test.rs454 Proin sagittis nisl rhoncus mattis rhoncus urna. Magna eget est lorem ipsum.";CODE