Repository Analysis

Crosstalk-Solutions/project-nomad

Project N.O.M.A.D, is a self-contained, offline survival computer packed with critical tools, knowledge, and AI to keep you informed and empowered—anytime, anywhere.

3.3 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of Crosstalk-Solutions/project-nomad, a TypeScript project with 34,079 GitHub stars. SynthScan v2.0 examined 73,362 lines of code across 351 source files, recording 132 pattern matches distributed across 12 syntactic categories. The overall adjusted score of 3.3 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).

3.3
Adjusted Score
3.3
Raw Score
100%
Time Factor
2026-07-14
Last Push
34.1K
Stars
TypeScript
Language
73.4K
Lines of Code
351
Files
132
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 0MEDIUM 34LOW 98

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 132 distinct pattern matches across 12 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.

Decorative Section Separators26 hits · 78 pts
SeverityFileLineSnippetContext
MEDIUMadmin/database/seeders/service_seeder.ts32 // ── Core / original services ──────────────────────────────────────────────COMMENT
MEDIUMadmin/database/seeders/service_seeder.ts207 // ── Supply Depot — curated catalog (ports 8400–8499) ─────────────────────COMMENT
MEDIUMadmin/app/services/content_auto_update_service.ts434 // ── Per-window budget ─────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/app/services/content_auto_update_service.ts468 // ── Backoff + run recording ───────────────────────────────────────────────────COMMENT
MEDIUMadmin/app/services/content_auto_update_service.ts502 // ── Status snapshot ───────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/app/services/kiwix_catalog_service.ts132 // ── ZIM internals ───────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/app/services/kiwix_catalog_service.ts254 // ── Map internals ────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/app/services/kiwix_catalog_service.ts283 // ── Shared ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/content_auto_update_backoff.spec.ts29// ── Failure backoff ─────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/content_auto_update_backoff.spec.ts59// ── Success reset ───────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/custom_app_guard.spec.ts6// ── Bind mounts ──────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/custom_app_guard.spec.ts77// ── Image references ─────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/content_auto_update.spec.ts46// ── Per-resource eligibility ───────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/content_auto_update.spec.ts126// ── Cap-bounded selection ──────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/content_auto_update.spec.ts194// ── Window boundary math (per-window budget reset) ─────────────────────────────COMMENT
MEDIUMadmin/tests/unit/content_auto_update.spec.ts208// ── Shared update window ───────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/app_auto_update.spec.ts35// ── Per-app eligibility ───────────────────────────────────────────────────────COMMENT
MEDIUMadmin/tests/unit/app_auto_update.spec.ts133// ── Shared update window (reused from the core auto-update) ────────────────────COMMENT
MEDIUMadmin/inertia/components/CustomAppModal.tsx189 // ── Port row helpers ──────────────────────────────────────────────────────COMMENT
MEDIUMadmin/inertia/components/CustomAppModal.tsx201 // ── Volume row helpers ────────────────────────────────────────────────────COMMENT
MEDIUMadmin/inertia/components/CustomAppModal.tsx212 // ── Env var helpers ───────────────────────────────────────────────────────COMMENT
MEDIUMadmin/inertia/components/CustomAppModal.tsx223 // ── Submit ────────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/inertia/pages/supply-depot.tsx177 // ── Filtering ─────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/inertia/pages/supply-depot.tsx204 // ── Actions ───────────────────────────────────────────────────────────────COMMENT
MEDIUMadmin/inertia/pages/supply-depot.tsx355 // ── Install modal helpers ─────────────────────────────────────────────────COMMENT
MEDIUMadmin/inertia/pages/supply-depot.tsx824// ── App Card component ────────────────────────────────────────────────────────COMMENT
Structural Annotation Overuse28 hits · 46 pts
SeverityFileLineSnippetContext
LOWinstall/migrate-disk-collector.sh102# Step 1: Stop old host processCOMMENT
LOWinstall/migrate-disk-collector.sh121# Step 2: Backup compose.ymlCOMMENT
LOWinstall/migrate-disk-collector.sh133# Step 3: Remove old bind-mount from admin volumesCOMMENT
LOWinstall/migrate-disk-collector.sh152# Step 4: Add disk-collector service blockCOMMENT
LOWinstall/migrate-disk-collector.sh202# Step 6: VerifyCOMMENT
LOWadmin/app/jobs/run_download_job.ts182 // Step 1: delete the OUTDATED file if it differs from the new one.COMMENT
LOWadmin/app/services/rag_service.ts1432 // Step 2: is the knowledge base even installed? Short-circuits before anyCOMMENT
LOWadmin/app/services/rag_service.ts1447 // Step 5: only check liveness once we know we'd otherwise act. The healthCOMMENT
LOWadmin/app/services/docker_service.ts450 // Step 4: Mark service as uninstalledCOMMENT
LOWadmin/app/services/docker_service.ts456 // Step 5: Recreate the containerCOMMENT
LOWadmin/app/services/docker_service.ts1278 // Step 1: Build/update the XML from current disk stateCOMMENT
LOWadmin/app/services/docker_service.ts1284 // Step 2: Stop and remove old container (leave ZIM volumes intact)COMMENT
LOWadmin/app/services/docker_service.ts1624 // Step 1: Pull new image (runtimeImage diverges from newImage for AMD, see above)COMMENT
LOWadmin/app/services/docker_service.ts1628 // Step 2: Find and stop existing containerCOMMENT
LOWadmin/app/services/docker_service.ts380 // Step 1: Try to stop and remove the container if it existsCOMMENT
LOWadmin/app/services/docker_service.ts399 // Step 2: Remove the containerCOMMENT
LOWadmin/app/services/docker_service.ts416 // Step 3: Clear volumes/data if neededCOMMENT
LOWadmin/app/services/docker_service.ts1299 // Step 3: Read the service record and authoritatively set the correct command.COMMENT
LOWadmin/app/services/docker_service.ts1315 // Step 4: Recreate container directly (skipping _createContainer to avoid re-downloadingCOMMENT
LOWadmin/app/services/docker_service.ts1647 // Step 3: Rename old container as safety netCOMMENT
LOWadmin/app/services/docker_service.ts1679 // Step 4: Create new container with inspected config + new imageCOMMENT
LOWadmin/app/services/docker_service.ts1739 // Step 5: Start new container. If the start itself throws (bad device/GPU config,COMMENT
LOWadmin/app/services/docker_service.ts1764 // Step 6: Health check — verify container stays running for 5 secondsCOMMENT
LOWadmin/docs/use-cases.md170### Step 1: Identify Your NeedsCOMMENT
LOWadmin/docs/use-cases.md173### Step 2: Prioritize ContentCOMMENT
LOWadmin/docs/use-cases.md180### Step 3: Upload Relevant DocumentsCOMMENT
LOWadmin/docs/use-cases.md183### Step 4: Download While You CanCOMMENT
LOWadmin/docs/use-cases.md186### Step 5: PracticeCOMMENT
Verbosity Indicators23 hits · 35 pts
SeverityFileLineSnippetContext
LOWinstall/migrate-disk-collector.sh102# Step 1: Stop old host processCOMMENT
LOWinstall/migrate-disk-collector.sh121# Step 2: Backup compose.ymlCOMMENT
LOWinstall/migrate-disk-collector.sh133# Step 3: Remove old bind-mount from admin volumesCOMMENT
LOWinstall/migrate-disk-collector.sh152# Step 4: Add disk-collector service blockCOMMENT
LOWinstall/migrate-disk-collector.sh202# Step 6: VerifyCOMMENT
LOWadmin/app/jobs/run_download_job.ts182 // Step 1: delete the OUTDATED file if it differs from the new one.COMMENT
LOWadmin/app/services/rag_service.ts1432 // Step 2: is the knowledge base even installed? Short-circuits before anyCOMMENT
LOWadmin/app/services/rag_service.ts1447 // Step 5: only check liveness once we know we'd otherwise act. The healthCOMMENT
LOWadmin/app/services/docker_service.ts450 // Step 4: Mark service as uninstalledCOMMENT
LOWadmin/app/services/docker_service.ts456 // Step 5: Recreate the containerCOMMENT
LOWadmin/app/services/docker_service.ts1278 // Step 1: Build/update the XML from current disk stateCOMMENT
LOWadmin/app/services/docker_service.ts1284 // Step 2: Stop and remove old container (leave ZIM volumes intact)COMMENT
LOWadmin/app/services/docker_service.ts1624 // Step 1: Pull new image (runtimeImage diverges from newImage for AMD, see above)COMMENT
LOWadmin/app/services/docker_service.ts1628 // Step 2: Find and stop existing containerCOMMENT
LOWadmin/app/services/docker_service.ts380 // Step 1: Try to stop and remove the container if it existsCOMMENT
LOWadmin/app/services/docker_service.ts399 // Step 2: Remove the containerCOMMENT
LOWadmin/app/services/docker_service.ts416 // Step 3: Clear volumes/data if neededCOMMENT
LOWadmin/app/services/docker_service.ts1299 // Step 3: Read the service record and authoritatively set the correct command.COMMENT
LOWadmin/app/services/docker_service.ts1315 // Step 4: Recreate container directly (skipping _createContainer to avoid re-downloadingCOMMENT
LOWadmin/app/services/docker_service.ts1647 // Step 3: Rename old container as safety netCOMMENT
LOWadmin/app/services/docker_service.ts1679 // Step 4: Create new container with inspected config + new imageCOMMENT
LOWadmin/app/services/docker_service.ts1739 // Step 5: Start new container. If the start itself throws (bad device/GPU config,COMMENT
LOWadmin/app/services/docker_service.ts1764 // Step 6: Health check — verify container stays running for 5 secondsCOMMENT
Redundant / Tautological Comments12 hits · 18 pts
SeverityFileLineSnippetContext
LOWinstall/uninstall_nomad.sh79 # Check if 'docker compose' (v2 plugin) is availableCOMMENT
LOWinstall/install_nomad.sh141 # Check if the script is being run in debug modeCOMMENT
LOWinstall/install_nomad.sh194 # Check if Docker was installed successfullyCOMMENT
LOWinstall/install_nomad.sh204 # Check if Docker service is runningCOMMENT
LOWinstall/install_nomad.sh221 # Check if 'docker compose' (v2 plugin) is availableCOMMENT
LOWinstall/install_nomad.sh258 # Check if nvidia-container-toolkit is already installedCOMMENT
LOWinstall/install_nomad.sh305 # Check if nvidia runtime already existsCOMMENT
LOWinstall/install_nomad.sh495 # Check if NVIDIA GPU is presentCOMMENT
LOWinstall/install_nomad.sh506 # Check if NVIDIA Container Toolkit is installedCOMMENT
LOWinstall/install_nomad.sh513 # Check if Docker has NVIDIA runtimeCOMMENT
LOWinstall/update_nomad.sh98 # Check if 'docker compose' (v2 plugin) is availableCOMMENT
LOWinstall/sidecar-updater/update-watcher.sh123 # Check if an update request file existsCOMMENT
Over-Commented Block17 hits · 17 pts
SeverityFileLineSnippetContext
LOWinstall/uninstall_nomad.sh1#!/bin/bashCOMMENT
LOWinstall/install_nomad.sh1#!/bin/bashCOMMENT
LOWinstall/install_nomad.sh161 echo -e "${YELLOW}#${RESET} Docker not found. Installing Docker...\\n"COMMENT
LOWinstall/install_nomad.sh641# [Nn]*|"")COMMENT
LOWinstall/install_nomad.sh661# eus_database_moveCOMMENT
LOWinstall/run_updater_fixes.sh1#!/bin/bashCOMMENT
LOWinstall/run_updater_fixes.sh21# Downloads the updated sidecar Dockerfile (adds jq) and update-watcher.shCOMMENT
LOWinstall/update_nomad.sh1#!/bin/bashCOMMENT
LOWinstall/migrate-disk-collector.sh1#!/bin/bashCOMMENT
LOWadmin/app/jobs/embed_file_job.ts341 }COMMENT
LOWadmin/app/services/system_service.ts121 if (!ollamaContainer) return nullCOMMENT
LOWadmin/config/session.ts1// import env from '#start/env'COMMENT
LOWadmin/config/session.ts21// /**COMMENT
LOWadmin/config/session.ts41// * list of available stores and their config.COMMENT
LOWadmin/config/queue.ts1import env from '#start/env'COMMENT
LOW.github/workflows/release.yml81 GH_TOKEN: ${{ secrets.COSMISTACKBOT_ACCESS_TOKEN }}COMMENT
LOW.github/scripts/finalize-release-notes.sh1#!/usr/bin/env bashCOMMENT
Hyper-Verbose Identifiers12 hits · 12 pts
SeverityFileLineSnippetContext
LOWadmin/app/utils/zim_filename.ts17export function findReplacedWikipediaFiles(CODE
LOWadmin/app/utils/fs.ts47export async function listDirectoryContentsRecursive(path: string): Promise<FileEntry[]> {CODE
LOWadmin/app/utils/downloads.ts226export async function doResumableDownloadWithRetry({CODE
LOWadmin/app/utils/content_auto_update_backoff.ts25export async function recordResourceUpdateSuccess(resource: InstalledResource): Promise<void> {CODE
LOWadmin/app/utils/content_auto_update_backoff.ts35export async function recordResourceUpdateFailure(CODE
LOWadmin/app/validators/common.ts79export function assertNotCloudMetadataUrl(urlString: string): void {CODE
LOWadmin/app/services/kiwix_catalog_service.ts311export async function reconcileResourceUpdateState(CODE
LOWadmin/util/zim.ts3export function isRawListRemoteZimFilesResponse(obj: any): obj is RawListRemoteZimFilesResponse {CODE
LOWadmin/config/inertia.ts8export function invalidateAssistantNameCache() {CODE
LOWadmin/inertia/hooks/useServiceInstallationActivity.ts6export default function useServiceInstallationActivity() {CODE
LOWadmin/inertia/lib/collections.ts12function resolveTierResourcesInner(CODE
LOWadmin/inertia/lib/util.ts6export function setGlobalNotificationCallback(callback: (notification: Notification) => void) {CODE
Slop Phrases3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMinstall/management_compose.yaml29 # PORT is the port the admin server listens on *inside* the container and should not be changed. If you want to chCOMMENT
LOWinstall/management_compose.yaml39 # If you change the MySQL port, make sure to update this accordinglyCOMMENT
LOWinstall/management_compose.yaml48 # If you change the Redis port, make sure to update this accordinglyCOMMENT
Modern AI Meta-Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMadmin/app/controllers/system_controller.ts396 // Security guardrails: hard-block dangerous bind mounts / malformed images regardless ofCOMMENT
MEDIUMadmin/app/controllers/system_controller.ts621 // Security guardrails (same posture as create).COMMENT
MEDIUMadmin/docs/api-reference.md98## Knowledge Base (RAG)COMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMadmin/app/services/zim_extraction_service.ts184 // that we can leverage for better chunking. If not, we'll just chunk it as one big piece of text.COMMENT
MEDIUMadmin/app/services/kiwix_catalog_service.ts116 // 1. Exact-name lookup (the robust path).COMMENT
Excessive Try-Catch Wrapping3 hits · 4 pts
SeverityFileLineSnippetContext
LOWadmin/scripts/audit_catalog_ports.py61 except Exception:CODE
LOWadmin/scripts/audit_catalog_ports.py97 except Exception:CODE
MEDIUMadmin/scripts/audit_catalog_ports.py58def parse_config(raw):CODE
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMinstall/install_nomad.sh406 # Create a admin.log file in the logs directoryCOMMENT
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOWadmin/scripts/audit_catalog_ports.py77CODE
LOWadmin/scripts/audit_catalog_ports.py101CODE