Repository Analysis

asterinas/asterinas

Asterinas aims to be a production-grade Linux alternative—memory safe, high-performance, and more.

5.1 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of asterinas/asterinas, a Rust project with 4,761 GitHub stars. SynthScan v2.0 examined 303,036 lines of code across 2173 source files, recording 1343 pattern matches distributed across 14 syntactic categories. The overall adjusted score of 5.1 places this repository in the Low AI signal 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).

5.1
Adjusted Score
5.1
Raw Score
100%
Time Factor
2026-07-13
Last Push
4.8K
Stars
Rust
Language
303.0K
Lines of Code
2.2K
Files
1.3K
Pattern Hits
2026-07-14
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

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

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 4MEDIUM 50LOW 1289

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 1343 distinct pattern matches across 14 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 Block1197 hits · 1182 pts
SeverityFileLineSnippetContext
LOWclippy.toml1# This file configures some Clippy lints.COMMENT
LOWostd/libs/padding-struct/src/lib.rs41///COMMENT
LOWostd/libs/padding-struct/src/lib.rs61/// #[repr(C)]COMMENT
LOWostd/libs/padding-struct/src/lib.rs81/// struct MyStruct {COMMENT
LOWostd/libs/ostd-pod/macros/src/lib.rs21///COMMENT
LOWostd/libs/ostd-pod/macros/src/lib.rs41/// use ostd_pod::array_helper::{ArrayFactory, ArrayManufacture, U64Array};COMMENT
LOWostd/libs/ostd-pod/macros/src/lib.rs61/// // Field accessor methodsCOMMENT
LOWostd/libs/ostd-pod/macros/src/lib.rs81/// pub fn new_bytes(bytes: [u8; 4]) -> Self {COMMENT
LOWostd/libs/ostd-pod/src/array_helper.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/ostd-pod/src/array_helper.rs41COMMENT
LOWostd/libs/ostd-pod/src/lib.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/ostd-pod/src/lib.rs21 /// Creates a new instance from the given bytes.COMMENT
LOWostd/libs/linux-bzimage/setup/src/main.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/linux-bzimage/setup/src/x86/amd64_efi/efi.rs141}COMMENT
LOWostd/libs/linux-bzimage/boot-params/src/lib.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/linux-bzimage/builder/src/lib.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/align_ext/src/lib.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/align_ext/src/lib.rs21 /// assert_eq!(12usize.align_up(4), 12);COMMENT
LOWostd/libs/ostd-test/src/lib.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/ostd-test/src/lib.rs21//! To write a unit test for any crates, it is recommended to create a new testCOMMENT
LOWostd/libs/ostd-test/src/lib.rs41//! panic!("expected panic message");COMMENT
LOWostd/libs/ostd-test/src/lib.rs241/// Get the whitelist of the tests.COMMENT
LOWostd/libs/ostd-macros/src/lib.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/libs/ostd-macros/src/lib.rs21/// perform all sorts of necessary initialization stepsCOMMENT
LOWostd/libs/ostd-macros/src/lib.rs41///COMMENT
LOWostd/libs/ostd-macros/src/lib.rs61/// }COMMENT
LOWostd/libs/ostd-macros/src/lib.rs81COMMENT
LOWostd/libs/ostd-macros/src/lib.rs121 let _: () = #main_fn_name();COMMENT
LOWostd/libs/ostd-macros/src/lib.rs141/// use core::alloc::Layout;COMMENT
LOWostd/libs/ostd-macros/src/lib.rs181/// [`global_allocator`] attribute, which applies to a static variableCOMMENT
LOWostd/libs/ostd-macros/src/lib.rs221 .into()COMMENT
LOWostd/libs/ostd-macros/src/lib.rs261COMMENT
LOWostd/libs/ostd-macros/src/lib.rs301COMMENT
LOWostd/libs/ostd-macros/src/lib.rs341 }COMMENT
LOWostd/libs/ostd-macros/src/lib.rs361/// }COMMENT
LOWostd/src/ex_table.rs21/// the following statements:COMMENT
LOWostd/src/ex_table.rs41/// ```COMMENT
LOWostd/src/lib.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/src/lib.rs61 global_heap_allocator_slot_map, main, panic_handler,COMMENT
LOWostd/src/smp.rs21///COMMENT
LOWostd/src/user.rs41/// Code execution in the user mode.COMMENT
LOWostd/src/power.rs21COMMENT
LOWostd/src/boot/memory_region.rs21 /// Reserved by BIOS or bootloader, do not use.COMMENT
LOWostd/src/boot/memory_region.rs221 /// usability will be its type.COMMENT
LOWostd/src/boot/smp.rs61COMMENT
LOWostd/src/boot/smp.rs121///COMMENT
LOWostd/src/boot/mod.rs41/// Gets the boot information.COMMENT
LOWostd/src/boot/mod.rs121///COMMENT
LOWostd/src/boot/mod.rs161 let kernel_cmdline = EARLY_INFO.get().unwrap().kernel_cmdline;COMMENT
LOWostd/src/util/id_set.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/src/util/id_set.rs41/// if one invokes `Into::<u32>::into()` for an `Id` value,COMMENT
LOWostd/src/util/id_set.rs81 }COMMENT
LOWostd/src/util/id_set.rs101/// ```COMMENT
LOWostd/src/util/macros.rs1// SPDX-License-Identifier: MPL-2.0COMMENT
LOWostd/src/util/macros.rs21///COMMENT
LOWostd/src/cpu/id.rs101 }COMMENT
LOWostd/src/cpu/id.rs141 /// This function is safe to call, but is vulnerable to races. The returned CPUCOMMENT
LOWostd/src/cpu/id.rs161 ///COMMENT
LOWostd/src/cpu/id.rs181 }COMMENT
LOWostd/src/cpu/id.rs201 // 2. The number of CPUs is correct.COMMENT
1137 more matches not shown…
Structural Annotation Overuse46 hits · 87 pts
SeverityFileLineSnippetContext
LOWostd/libs/ostd-pod/README.md37### Step 1: Edit your `Cargo.toml`COMMENT
LOWostd/libs/ostd-pod/README.md52### Step 2: Edit your `lib.rs` (or `main.rs`)COMMENT
LOWostd/libs/ostd-pod/README.md67### Step 3: Define your first POD typeCOMMENT
LOW…/github_workflows/prepare_for_docker_build_and_push.sh16# Step 1: Login to Docker HubCOMMENT
LOW…/github_workflows/prepare_for_docker_build_and_push.sh23# Step 2: Fetch versionsCOMMENT
LOW…/github_workflows/prepare_for_docker_build_and_push.sh31# Step 3: Check whether each target image already exists.COMMENT
LOWtest/nixos/README.md24### Step 1: Copy the TemplateCOMMENT
LOWtest/nixos/README.md31### Step 2: Update `Cargo.toml`COMMENT
LOWtest/nixos/README.md35### Step 3: Implement Your TestsCOMMENT
LOWtest/initramfs/src/benchmark/README.md97### Step 1: Add the Directory StructureCOMMENT
LOWtest/initramfs/src/benchmark/README.md111### Step 2: Create Necessary FilesCOMMENT
LOWtest/initramfs/src/benchmark/README.md181### Step 3: Update Suite's `summary.json`COMMENT
LOWtest/initramfs/src/benchmark/README.md199### Step 4: Update the CI ConfigurationCOMMENT
LOWtest/initramfs/src/benchmark/README.md212### Step 5: Test, Validate and CommitCOMMENT
LOW…/initramfs/src/regression/io/epoll/test_epoll_pwait.sh12# Step 2: Run epoll_pwait in the backgroundCOMMENT
LOW…/initramfs/src/regression/io/epoll/test_epoll_pwait.sh18# Step 3: Wait for 1 seconds to let epoll_pwait initialize and block SIGUSR1COMMENT
LOW…/initramfs/src/regression/io/epoll/test_epoll_pwait.sh21# Step 4: Send SIGUSR1 to epoll_pwaitCOMMENT
LOWdistro/etc_nixos/modules/xfce/start_xfce.sh7# Step 1: run dbusCOMMENT
LOWdistro/etc_nixos/modules/xfce/start_xfce.sh15# Step 2: run XorgCOMMENT
LOWdistro/etc_nixos/modules/xfce/start_xfce.sh31# Step 3: run xfce4COMMENT
LOW…tro/popular-applications/nix-and-nixos-tools/README.md20# Step 1: Create a clean workspaceCOMMENT
LOW…tro/popular-applications/nix-and-nixos-tools/README.md23# Step 2: Write a C programCOMMENT
LOW…tro/popular-applications/nix-and-nixos-tools/README.md33# Step 3: Write a default.nixCOMMENT
LOW…tro/popular-applications/nix-and-nixos-tools/README.md55# Step 4: Build and runCOMMENT
LOWbook/src/kernel/vm-based-containers/coco.md25## Step 1: Prepare the host kernelCOMMENT
LOWbook/src/kernel/vm-based-containers/coco.md53## Step 2: Enter the CoCo environmentCOMMENT
LOWbook/src/kernel/vm-based-containers/coco.md129## Step 3: Start a CoCo workloadCOMMENT
LOWbook/src/kernel/vm-based-containers/coco.md230## Step 4: Use a local kernel (optional)COMMENT
LOWbook/src/kernel/vm-based-containers/kata.md24## Step 1: Prepare the host kernelCOMMENT
LOWbook/src/kernel/vm-based-containers/kata.md50## Step 2: Enter the Kata-ready environmentCOMMENT
LOWbook/src/kernel/vm-based-containers/kata.md138## Step 3: Start a Kata workloadCOMMENT
LOWbook/src/kernel/vm-based-containers/kata.md230## Step 4: Use a local kernel (optional)COMMENT
LOWkernel/comps/cmdline/src/dispatch.rs111 // Step 1: Build lookup from registered param name to handler.COMMENT
LOWkernel/comps/cmdline/src/dispatch.rs122 // Step 2: Tokenize the kernel command line and group recognized param by normalized name.COMMENT
LOWkernel/comps/cmdline/src/dispatch.rs174 // Step 3: Dispatch each group to its handler.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs19 // Step 1: flush the xattr.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs24 // Step 2: flush dirty data pages.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs29 // Step 3: flush inode-local indirect metadata before inode-table state.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs32 // Step 4: persist inode metadata to the inode-table page cache.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs45 // Step 1: flush dirty data pages.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs48 // Step 2: flush inode-local indirect metadata before inode-table state.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs51 // Step 3: persist inode metadata to the inode-table page cache.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs245 // Step 1: read inode numbers without write locks so we know whichCOMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs266 // Step 2: lock all participating inodes in global ino order.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs275 // Step 3: validate invariants under lock.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs278 // Step 4: apply directory mutations and metadata updates.COMMENT
Decorative Section Separators21 hits · 80 pts
SeverityFileLineSnippetContext
MEDIUMkernel/comps/mlsdisk/src/layers/1-crypto/crypto_blob.rs24/// ┌─────────┬─────────┬─────────┬──────────────────────────────┐COMMENT
MEDIUMkernel/comps/mlsdisk/src/layers/1-crypto/crypto_blob.rs27/// └─────────┴─────────┴─────────┴──────────────────────────────┘COMMENT
MEDIUM…rnel/comps/mlsdisk/src/layers/1-crypto/crypto_chain.rs28/// ┌─────────────────────┬───────┬──────────┬──────────┬──────────┬─────────┐COMMENT
MEDIUM…rnel/comps/mlsdisk/src/layers/1-crypto/crypto_chain.rs31/// └─────────────────────┴───────┴──────────┴──────────┴──────────┴─────────┘COMMENT
MEDIUM…rnel/comps/mlsdisk/src/layers/1-crypto/crypto_chain.rs33/// ◄─────────────────────────── Block size (4KB) ──────────────────────────►COMMENT
MEDIUM…el/src/net/socket/netlink/route/message/segment/mod.rs28//! ┌────────┬─────────┬──────┬─────────┬──────┬──────┬──────┐COMMENT
MEDIUM…el/src/net/socket/netlink/route/message/segment/mod.rs30//! └────────┴─────────┴──────┴─────────┴──────┴──────┴──────┘COMMENT
MEDIUMkernel/src/net/socket/netlink/message/attr/mod.rs21//! ┌────────┬─────────┬─────────┬─────────┐COMMENT
MEDIUMkernel/src/net/socket/netlink/message/attr/mod.rs23//! └────────┴─────────┴─────────┴─────────┘COMMENT
MEDIUMkernel/src/net/socket/netlink/message/attr/mod.rs42// ┌────────┬───────────────┬──────────┐COMMENT
MEDIUMkernel/src/net/socket/netlink/message/attr/mod.rs44// └────────┴───────────────┴──────────┘COMMENT
MEDIUMkernel/src/security/tsm.rs90/// ┌────────────────┐COMMENT
MEDIUMkernel/src/security/tsm.rs93/// └────────┬───────┘COMMENT
MEDIUMkernel/src/security/tsm.rs96/// ┌────────▼───────┐COMMENT
MEDIUMkernel/src/security/tsm.rs97/// │InblobProvided ◄─────────┐COMMENT
MEDIUMkernel/src/security/tsm.rs98/// └────────┬───────┘ │COMMENT
MEDIUMkernel/src/security/tsm.rs101/// ┌────────▼───────┐ │COMMENT
MEDIUMkernel/src/security/tsm.rs102/// │OutblobGenerated├─────────┘COMMENT
MEDIUMkernel/src/security/tsm.rs103/// └────────────────┘COMMENT
MEDIUMkernel/src/fs/fs_impls/ext2/inode/dir/dir_entry.rs18//! ┌──────────────────────────────────────────────────────────┐COMMENT
MEDIUMkernel/src/fs/fs_impls/ext2/inode/dir/dir_entry.rs20//! └──────────────────────────────────────────────────────────┘COMMENT
AI Slop Vocabulary23 hits · 69 pts
SeverityFileLineSnippetContext
MEDIUMCargo.toml207# FIXME: to utilize `AES-NI` and `CLMUL` intrinsics, some specific flags must be added to `RUSTFLAGS`,COMMENT
MEDIUMostd/src/arch/x86/kernel/tsc.rs29/// leverage the PIT to calculate the TSC frequency.COMMENT
MEDIUMostd/src/arch/riscv/boot/smp.rs73 // FIXME: We should find a robust method to identify the managementCOMMENT
MEDIUMostd/src/arch/riscv/cpu/extension.rs18 // FIXME: We should find a robust method to identify the managementCOMMENT
MEDIUMostd/src/mm/frame/meta.rs83 /// - the subsequent fields can utilize the padding of theCOMMENT
MEDIUMostd/src/sync/wait.rs67 /// more efficient and robust.COMMENT
MEDIUM…nitramfs/src/regression/process/pthread/pthread_test.c117// The test case of robust mutexCOMMENT
MEDIUM…nitramfs/src/regression/process/pthread/pthread_test.c158 // Init robust mutexCOMMENT
MEDIUM…s/aster-code-review/benchmark/validate_problem_yaml.sh48 # The numeric part is the stable id the harness/CLI select by (slugs get reworded),COMMENT
MEDIUM…gents/skills/aster-code-review/benchmark/problems.yaml23# the harness never shows them to the review agent.COMMENT
MEDIUM.agents/skills/aster-code-review/benchmark/run.sh6# run.sh — benchmark harness for aster-code-review.COMMENT
MEDIUM.agents/skills/aster-code-review/benchmark/run.sh12# do the launching, so this harness names no agentCOMMENT
MEDIUM.agents/skills/aster-code-review/benchmark/run.sh57# so this harness names no agent.COMMENT
MEDIUM.agents/skills/aster-code-review/benchmark/run.sh284 # Pass iff every attempted problem produced a review (no harness errors) and at least one ranCOMMENT
MEDIUM.agents/skills/aster-code-review/benchmark/run.sh293 # every negative clean, no harness error, >=1 defect measured.COMMENT
MEDIUM…nts/skills/aster-code-review/scripts/resolve_target.sh34# --- parse: quote-aware tokenizer + grammar (in python for a robust parse) ----COMMENT
MEDIUM.github/workflows/test_nixos_full.yml1# A comprehensive test for NixOS.COMMENT
MEDIUMkernel/src/thread/work_queue/mod.rs48//! Certainly, users can also create a dedicated WorkQueue and WorkerPool.COMMENT
MEDIUMkernel/src/process/execve.rs176 // is initialized. Hence, it is necessary to clear the previously recorded robust list.COMMENT
MEDIUMkernel/src/process/posix_thread/robust_list.rs3//! The implementation of robust list is from occlum.COMMENT
MEDIUMkernel/src/process/posix_thread/robust_list.rs38 /// Return an iterator for all futexes in the robust list.COMMENT
MEDIUMkernel/src/process/posix_thread/robust_list.rs132/// Attempts to wake a robust futex owned by the given thread.COMMENT
MEDIUMkernel/src/process/posix_thread/exit.rs161/// Walks the robust futex list, marking futex dead and waking waiters.COMMENT
Verbosity Indicators23 hits · 48 pts
SeverityFileLineSnippetContext
LOW…/github_workflows/prepare_for_docker_build_and_push.sh16# Step 1: Login to Docker HubCOMMENT
LOW…/github_workflows/prepare_for_docker_build_and_push.sh23# Step 2: Fetch versionsCOMMENT
LOW…/github_workflows/prepare_for_docker_build_and_push.sh31# Step 3: Check whether each target image already exists.COMMENT
LOW…/initramfs/src/regression/io/epoll/test_epoll_pwait.sh12# Step 2: Run epoll_pwait in the backgroundCOMMENT
LOW…/initramfs/src/regression/io/epoll/test_epoll_pwait.sh18# Step 3: Wait for 1 seconds to let epoll_pwait initialize and block SIGUSR1COMMENT
LOW…/initramfs/src/regression/io/epoll/test_epoll_pwait.sh21# Step 4: Send SIGUSR1 to epoll_pwaitCOMMENT
LOWdistro/etc_nixos/modules/xfce/start_xfce.sh7# Step 1: run dbusCOMMENT
LOWdistro/etc_nixos/modules/xfce/start_xfce.sh15# Step 2: run XorgCOMMENT
LOWdistro/etc_nixos/modules/xfce/start_xfce.sh31# Step 3: run xfce4COMMENT
LOWkernel/comps/cmdline/src/dispatch.rs111 // Step 1: Build lookup from registered param name to handler.COMMENT
LOWkernel/comps/cmdline/src/dispatch.rs122 // Step 2: Tokenize the kernel command line and group recognized param by normalized name.COMMENT
LOWkernel/comps/cmdline/src/dispatch.rs174 // Step 3: Dispatch each group to its handler.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs19 // Step 1: flush the xattr.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs24 // Step 2: flush dirty data pages.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs29 // Step 3: flush inode-local indirect metadata before inode-table state.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs32 // Step 4: persist inode metadata to the inode-table page cache.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs45 // Step 1: flush dirty data pages.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs48 // Step 2: flush inode-local indirect metadata before inode-table state.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/sync.rs51 // Step 3: persist inode metadata to the inode-table page cache.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs245 // Step 1: read inode numbers without write locks so we know whichCOMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs266 // Step 2: lock all participating inodes in global ino order.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs275 // Step 3: validate invariants under lock.COMMENT
LOWkernel/src/fs/fs_impls/ext2/inode/dir/mod.rs278 // Step 4: apply directory mutations and metadata updates.COMMENT
Synthetic Comment Markers4 hits · 28 pts
SeverityFileLineSnippetContext
HIGH…ls/aster-code-review/scripts/post_reviews_to_github.sh126 f"> These comments were generated by AI using the [`aster-code-review`]({url}) "CODE
HIGHkernel/src/net/socket/netlink/message/segment/header.rs61 /// Dump was filtered as requestedCOMMENT
HIGHkernel/src/vm/perms.rs46 /// Parses `bits` as requested permissions from user programs and returns errorsCOMMENT
HIGHkernel/src/vm/perms.rs58 /// Parses `bits` as requested permissions from user programs and ignores anyCOMMENT
Self-Referential Comments4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUM.typos.toml1# This file is to help typos avoid false-positives.COMMENT
MEDIUMtools/net/qemu-ifup.sh5# Create a TAP interface.COMMENT
MEDIUMtest/nixos/common/merge_nixos_config.sh66# This file is generated by merge_nixos_config.shCOMMENT
MEDIUMosdk/rustfmt.toml1# This file contains the same content as the rustfmt.toml in the root directory,COMMENT
Redundant / Tautological Comments8 hits · 12 pts
SeverityFileLineSnippetContext
LOWtools/bump_version.sh175 # Check if versions are equalCOMMENT
LOWtools/nixos/run.sh91# Check if the execution was successful:COMMENT
LOWtools/github_workflows/publish_api_docs.sh125# Check if help message should be printedCOMMENT
LOWtest/nixos/common/merge_nixos_config.sh36# Check if input files existCOMMENT
LOWtest/initramfs/src/benchmark/bench_linux_and_aster.sh251 # Check if runtime_config was actually found and non-emptyCOMMENT
LOWtest/initramfs/src/benchmark/common/prepare_host.sh8# Set BENCHMARK_ROOT to the parent directory of the current directory if it is not setCOMMENT
LOWtest/initramfs/src/benchmark/common/bench_runner.sh63 # Check if the benchmark name is validCOMMENT
LOWtest/initramfs/src/regression/fs/run_test.sh76 # Check if file_a's content is updatedCOMMENT
Slop Phrases4 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMkernel/libs/aster-util/src/coeff.rs25/// Here is a simple example of such calculation:COMMENT
MEDIUMkernel/comps/mlsdisk/src/util/lazy_delete.rs26/// Here is a simple example.COMMENT
LOWkernel/comps/i8042/src/mouse.rs333 // Currently, this method can generate at most 7 events. Don't forget to update this whenCOMMENT
LOWkernel/src/arch/x86/cpu.rs495 // latest Linux implementation. Please don't forget to update the commit hash after youCOMMENT
Hyper-Verbose Identifiers6 hits · 6 pts
SeverityFileLineSnippetContext
LOW…pplications/ai-and-machine-learning/test_tensorflow.py16 def test_gpu_available_flag_type(self):CODE
LOW…pplications/ai-and-machine-learning/test_tensorflow.py23 def test_basic_autograd_linear(self):CODE
LOW…pplications/ai-and-machine-learning/test_tensorflow.py44 def test_linear_regression_training(self):CODE
LOW…r-applications/ai-and-machine-learning/test_pytorch.py16 def test_cuda_available_flag_type(self):CODE
LOW…r-applications/ai-and-machine-learning/test_pytorch.py23 def test_basic_autograd_linear(self):CODE
LOW…r-applications/ai-and-machine-learning/test_pytorch.py47 def test_linear_regression_training(self):CODE
Excessive Try-Catch Wrapping3 hits · 3 pts
SeverityFileLineSnippetContext
LOW…s/aster-code-review/benchmark/validate_problem_yaml.sh29except Exception as e:CODE
LOW.agents/skills/aster-code-review/scripts/run_agent.sh69 except Exception as e: sys.stderr.write(f"invalid JSON {p}: {e}\n"); sys.exit(3)CODE
LOW…ts/skills/aster-code-review/scripts/assemble_review.sh79 except Exception as e:CODE
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWtest/nixos/tests/development-tools/src/main.rs224 nixos_shell.run_cmd("cd /tmp/git_test2 && git config user.email 'test@test.com'")?;CODE
LOWtest/nixos/tests/development-tools/src/main.rs238 nixos_shell.run_cmd("cd /tmp/git_test3 && git config user.email 'test@test.com'")?;CODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWkernel/libs/typeflags/src/lib.rs20//! // Usage example:COMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…gents/skills/aster-code-review/scripts/parse_review.py58CODE