Xv6 for RISC-V
This report summarizes scanner evidence for mit-pdos/xv6-riscv, a C project with 10,723 GitHub stars. SynthScan examined 12,519 lines of code across 68 source files, recording 41 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 3.3 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
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.
Can maintainers explain intent, assumptions, and trade-offs? 41 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 41 finding(s).
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.
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.
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.
The scanner identified 41 distinct pattern matches across 1 syntactic category. 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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | mkfs/mkfs.c | 1 | #include <stdio.h> | COMMENT |
| LOW | user/grind.c | 1 | // | COMMENT |
| LOW | user/sh.c | 1 | // Shell. | COMMENT |
| LOW | user/stressfs.c | 1 | // Demonstrate that moving the "acquire" in iderw after the loop that | COMMENT |
| LOW | user/usertests.c | 1 | #include "kernel/param.h" | COMMENT |
| LOW | kernel/log.c | 1 | #include "types.h" | COMMENT |
| LOW | kernel/log.c | 21 | // But if it thinks the log is close to running out, it | COMMENT |
| LOW | kernel/vm.c | 81 | COMMENT | |
| LOW | kernel/fcntl.h | 1 | #define O_RDONLY 0x000 | COMMENT |
| LOW | kernel/sysfile.c | 1 | // | COMMENT |
| LOW | kernel/printk.c | 1 | // | COMMENT |
| LOW | kernel/fs.c | 1 | // File system implementation. Five layers: | COMMENT |
| LOW | kernel/fs.c | 101 | m = 1 << (bi % 8); | COMMENT |
| LOW | kernel/fs.c | 121 | // to provide a place for synchronizing access | COMMENT |
| LOW | kernel/fs.c | 141 | // * Valid: the information (type, size, &c) in an inode | COMMENT |
| LOW | kernel/fs.c | 161 | // The separation also helps avoid deadlock and races during | COMMENT |
| LOW | kernel/fs.c | 641 | de.inum = inum; | COMMENT |
| LOW | kernel/memlayout.h | 1 | // Physical memory layout | COMMENT |
| LOW | kernel/memlayout.h | 21 | #define UART0 0x10000000L | COMMENT |
| LOW | kernel/memlayout.h | 41 | // for use by the kernel and user pages | COMMENT |
| LOW | kernel/memlayout.h | 61 | // TRAPFRAME (p->trapframe, used by the trampoline) | COMMENT |
| LOW | kernel/elf.h | 41 | #define ELF_PROG_FLAG_WRITE 2 | COMMENT |
| LOW | kernel/virtio.h | 1 | // | COMMENT |
| LOW | kernel/virtio.h | 21 | #define VIRTIO_MMIO_QUEUE_NUM 0x038 // size of current queue, write-only | COMMENT |
| LOW | kernel/virtio.h | 41 | // device feature bits | COMMENT |
| LOW | kernel/console.c | 1 | // | COMMENT |
| LOW | kernel/console.c | 21 | #include "riscv.h" | COMMENT |
| LOW | kernel/param.h | 1 | #define NPROC 64 // maximum number of processes | COMMENT |
| LOW | kernel/spinlock.c | 61 | // fence rw,w | COMMENT |
| LOW | kernel/bio.c | 1 | // Buffer cache. | COMMENT |
| LOW | kernel/proc.c | 421 | // Per-CPU process scheduler. | COMMENT |
| LOW | kernel/riscv.h | 401 | // shift a physical address to the right place for a PTE. | COMMENT |
| LOW | kernel/virtio_disk.c | 1 | // | COMMENT |
| LOW | kernel/virtio_disk.c | 21 | COMMENT | |
| LOW | kernel/file.c | 1 | // | COMMENT |
| LOW | kernel/vm.h | 1 | #define SBRK_EAGER 1 | COMMENT |
| LOW | kernel/syscall.h | 1 | // System call numbers | COMMENT |
| LOW | kernel/syscall.h | 21 | #define SYS_mkdir 20 | COMMENT |
| LOW | kernel/fs.h | 41 | // Inodes per block. | COMMENT |
| LOW | kernel/uart.c | 1 | // | COMMENT |
| LOW | kernel/uart.c | 21 | COMMENT |