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.
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).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .github/workflows/dep_benchmarks.yml | 1 | # yaml-language-server: $schema=https://json.schemastore.org/github-workflow.json | COMMENT |
| LOW | .github/workflows/RegenSnapshotGoldens.yml | 1 | # yaml-language-server: $schema=https://json.schemastore.org/github-workflow.json | COMMENT |
| LOW | .github/workflows/ready-for-review-manage.yml | 1 | name: Ready-for-review (manage) | COMMENT |
| LOW | .github/workflows/ready-for-review-label.yml | 1 | name: Ready-for-review (collect) | COMMENT |
| LOW | .github/workflows/dep_update_guest_locks.yml | 61 | COMMENT | |
| LOW | dev/sync-project-board.sh | 1 | #!/bin/bash | COMMENT |
| LOW | dev/check-release-blockers.sh | 1 | #!/bin/bash | COMMENT |
| LOW | dev/notify-ci-failure.sh | 1 | #!/bin/bash | COMMENT |
| LOW | fuzz/fuzz_targets/virtq_packed_ring.rs | 141 | /// | COMMENT |
| LOW | src/hyperlight_component_util/src/resource.rs | 21 | use crate::etypes::{TypeBound, Tyvar}; | COMMENT |
| LOW | src/hyperlight_component_util/src/etypes.rs | 101 | #[derive(Debug, Clone, Copy, PartialEq)] | COMMENT |
| LOW | src/hyperlight_component_util/src/etypes.rs | 321 | COMMENT | |
| LOW | src/hyperlight_component_util/src/etypes.rs | 341 | /// element in the list, and later elements can depend on earlier | COMMENT |
| LOW | src/hyperlight_component_util/src/etypes.rs | 441 | /// gamma in the specification | COMMENT |
| LOW | src/hyperlight_component_util/src/wf.rs | 61 | } | COMMENT |
| LOW | src/hyperlight_component_util/src/rtypes.rs | 221 | /// Emit a token stream that references the given type variable in a | COMMENT |
| LOW | src/hyperlight_component_util/src/rtypes.rs | 801 | /// this instance type | COMMENT |
| LOW | src/hyperlight_component_util/src/substitute.rs | 21 | use crate::etypes::{ | COMMENT |
| LOW | src/hyperlight_component_util/src/substitute.rs | 41 | Self: Shiftable<'a>, | COMMENT |
| LOW | src/hyperlight_component_util/src/substitute.rs | 301 | /// fn shifted<'b>(&'b self) -> Shifted<'b, Self::Inner> { Shifted::new(self) } | COMMENT |
| LOW | src/hyperlight_component_util/src/substitute.rs | 561 | self.how_many += 1; | COMMENT |
| LOW | src/hyperlight_component_util/src/subtype.rs | 41 | MismatchedResources(ResourceId, ResourceId), | COMMENT |
| LOW | src/hyperlight_component_util/src/emit.rs | 321 | /// A resource-type index. Currently a resource-type index is | COMMENT |
| LOW | src/hyperlight_component_util/src/emit.rs | 341 | /// We use a "helper module" for auxiliary definitions: for | COMMENT |
| LOW | src/hyperlight_component_util/src/emit.rs | 361 | /// A path through instance import/export names from the root | COMMENT |
| LOW | src/hyperlight_component_util/src/emit.rs | 381 | /// interfaces, or just the types of the interface | COMMENT |
| LOW | src/hyperlight_component_util/src/component.rs | 61 | /// - a component, whose | COMMENT |
| LOW | src/hyperlight_component_util/src/hl.rs | 181 | let ResolvedBoundVar::Resource { rtidx } = s.resolve_bound_var(*vi) else { | COMMENT |
| LOW | src/hyperlight_component_util/src/elaborate.rs | 101 | /// Innerizing an outer alias failed; this usually means that the | COMMENT |
| LOW | src/hyperlight_host/build.rs | 21 | fn main() -> Result<()> { | COMMENT |
| LOW | src/hyperlight_host/build.rs | 121 | // the `gdb` cfg (gdb feature + debug build). | COMMENT |
| LOW | src/hyperlight_host/tests/integration_test.rs | 741 | // or it may impact other tests. | COMMENT |
| LOW | src/hyperlight_host/tests/integration_test.rs | 1361 | assert_eq!( | COMMENT |
| LOW | src/hyperlight_host/tests/integration_test.rs | 1781 | })); | COMMENT |
| LOW | src/hyperlight_host/tests/integration_test.rs | 1861 | host_region: host_base | COMMENT |
| LOW | src/hyperlight_host/examples/guest-debugging/main.rs | 121 | let out_file_path = format!("{out_dir}/{name}.output"); | COMMENT |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 21 | //! segment registers, XSAVE state) and guest memory (snapshot, scratch, | COMMENT |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 41 | //! [`MultiUseSandbox::generate_crashdump`] explicitly to capture the | COMMENT |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 61 | //! | COMMENT |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 121 | COMMENT | |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 281 | println!( | COMMENT |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 301 | /// # Find the thread running the guest | COMMENT |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 321 | } | COMMENT |
| LOW | src/hyperlight_host/examples/crashdump/main.rs | 501 | elf_files.len() | COMMENT |
| LOW | src/hyperlight_host/src/error.rs | 41 | pub enum HyperlightError { | COMMENT |
| LOW | src/hyperlight_host/src/error.rs | 121 | /// A Host function was called by the guest but it was not registered. | COMMENT |
| LOW | src/hyperlight_host/src/error.rs | 161 | /// Memory Protection Failed | COMMENT |
| LOW | src/hyperlight_host/src/error.rs | 201 | COMMENT | |
| LOW | src/hyperlight_host/src/error.rs | 221 | /// ## Recovery | COMMENT |
| LOW | src/hyperlight_host/src/lib.rs | 21 | //! The runtime manages sandbox creation, guest function calls, memory isolation, | COMMENT |
| LOW | src/hyperlight_host/src/lib.rs | 41 | COMMENT | |
| LOW | src/hyperlight_host/src/lib.rs | 61 | /// - Virtual Address | COMMENT |
| LOW | src/hyperlight_host/src/lib.rs | 81 | /// Utilities for testing including interacting with `simpleguest` testing guest binary | COMMENT |
| LOW | src/hyperlight_host/src/metrics/mod.rs | 21 | // Counter metric that counts the number of times a guest function was called due to timing out | COMMENT |
| LOW | …c/hyperlight_host/src/hyperlight_surrogate/src/main.rs | 21 | // which add ~200ms to CreateProcess on ARM64 Windows. The process never | COMMENT |
| LOW | src/hyperlight_host/src/signal_handlers/mod.rs | 21 | pub(crate) fn setup_signal_handlers(config: &SandboxConfiguration) -> crate::Result<()> { | COMMENT |
| LOW | src/hyperlight_host/src/sandbox/uninitialized_evolve.rs | 61 | let peb_addr = { | COMMENT |
| LOW | src/hyperlight_host/src/sandbox/config.rs | 41 | }, | COMMENT |
| LOW | src/hyperlight_host/src/sandbox/config.rs | 61 | input_data_size: usize, | COMMENT |
| LOW | src/hyperlight_host/src/sandbox/config.rs | 81 | /// | COMMENT |
| 280 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM⚡ | src/hyperlight_common/src/virtq/ring.rs | 30 | //! ┌─────────┐ (AVAIL=wrap) ┌───────────┐ | COMMENT |
| MEDIUM⚡ | src/hyperlight_common/src/virtq/ring.rs | 31 | //! │ Free │ ──────────────────> │ Available │ | COMMENT |
| MEDIUM⚡ | src/hyperlight_common/src/virtq/ring.rs | 32 | //! └─────────┘ └───────────┘ | COMMENT |
| MEDIUM⚡ | src/hyperlight_common/src/virtq/ring.rs | 38 | //! ┌─────────┐ ┌───────────┐ | COMMENT |
| MEDIUM⚡ | src/hyperlight_common/src/virtq/ring.rs | 39 | //! │Reclaimed│ <────────────────── │ Used │ | COMMENT |
| MEDIUM⚡ | src/hyperlight_common/src/virtq/ring.rs | 40 | //! └─────────┘ └───────────┘ | COMMENT |
| MEDIUM | src/hyperlight_common/src/virtq/ring.rs | 59 | //! ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ | COMMENT |
| MEDIUM | src/hyperlight_common/src/virtq/ring.rs | 64 | //! └──────────────┘ └──────────────┘ └──────────────┘ | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .github/workflows/ReleaseBlockerLabelCleanUp.yml | 22 | # Check if the issue has the release-blocker label | COMMENT |
| LOW | .github/workflows/dep_update_guest_locks.yml | 83 | # Check if there are any changes to the guest Cargo.lock file | COMMENT |
| LOW | dev/sync-project-board.sh | 65 | # Check if repo has 'hyperlight' in the name | COMMENT |
| LOW | dev/auto-approve-dependabot.sh | 9 | # Check if repository argument is provided | COMMENT |
| LOW | dev/auto-approve-dependabot.sh | 40 | # Check if PR only modifies allowed files | COMMENT |
| LOW | dev/auto-approve-dependabot.sh | 56 | # Check if all status checks have passed (regardless of required or not) | COMMENT |
| LOW | dev/auto-approve-dependabot.sh | 105 | # Check if PR has been modified by someone other than dependabot | COMMENT |
| LOW | dev/auto-approve-dependabot.sh | 114 | # Check if PR needs approval (i.e., hasn't been approved already) | COMMENT |
| LOW | dev/auto-approve-dependabot.sh | 125 | # Check if PR is up-to-date with base branch | COMMENT |
| LOW | dev/check-release-blockers.sh | 22 | # Check if repository argument is provided | COMMENT |
| LOW | dev/check-license-headers.sh | 46 | # Check if the file has the license header (allowing for multi-line matching) | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | docs/how-to-run-coverage.md | 16 | ### Step 1: Run tests with coverage instrumentation | COMMENT |
| LOW | docs/how-to-run-coverage.md | 32 | ### Step 2: Generate a report | COMMENT |
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 51 | // Step 1: Send abort code (typically 1 byte, but `code` allows flexibility) | COMMENT |
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 54 | // Step 2: Convert the C string to bytes | COMMENT |
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 57 | // Step 3: Send the message itself in chunks | COMMENT |
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 60 | // Step 4: Send abort terminator to signal completion (e.g., 0xFF) | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | .github/workflows/dep_update_guest_locks.yml | 113 | # Create a new tree with the updated files | COMMENT |
| MEDIUM | dev/check-license-headers.sh | 8 | # Define the license header pattern to look for | COMMENT |
| MEDIUM | dev/check-license-headers.sh | 11 | # Define the full license header for files that need it | COMMENT |
| MEDIUM | dev/check-license-headers.sh | 30 | # Initialize a variable to track missing headers | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | src/hyperlight_host/examples/guest-debugging/main.rs | 63 | // Note: This function is unused, it's just here for demonstration purposes | COMMENT |
| MEDIUM | src/hyperlight_host/examples/hello-world/main.rs | 32 | // Note: This function is unused, it's just here for demonstration purposes | COMMENT |
| MEDIUM | src/hyperlight_host/src/mem/shared_mem.rs | 1055 | /// racing loads in LLVM return `undef`, as discussed above, we would | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 51 | // Step 1: Send abort code (typically 1 byte, but `code` allows flexibility) | COMMENT |
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 54 | // Step 2: Convert the C string to bytes | COMMENT |
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 57 | // Step 3: Send the message itself in chunks | COMMENT |
| LOW⚡ | src/hyperlight_guest/src/exit.rs | 60 | // Step 4: Send abort terminator to signal completion (e.g., 0xFF) | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | src/hyperlight_host/Cargo.toml | 152 | # Custom harness (see main.rs). | STRING |
| MEDIUM | src/hyperlight_host/build.rs | 105 | // Essentially the kvm and mshv3 features are ignored on windows as long as you use #[cfg(kvm)] and not #[cfg(featur | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | src/hyperlight_host/tests/integration_test.rs | 426 | let abort_message = "Lorem ipsum dolor sit amet, \ | CODE |
| LOW | src/hyperlight_host/tests/integration_test.rs | 426 | let abort_message = "Lorem ipsum dolor sit amet, \ | CODE |
| LOW | src/hyperlight_host/tests/integration_test.rs | 442 | Dolor sit amet consectetur adipiscing elit pellentesque habitant morbi. \ | CODE |
| LOW | src/hyperlight_host/tests/integration_test.rs | 454 | Proin sagittis nisl rhoncus mattis rhoncus urna. Magna eget est lorem ipsum."; | CODE |