Repository Analysis

nubjs/nub

The fast all-in-one Node.js toolkit

8.8 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of nubjs/nub, a Rust project with 4,131 GitHub stars. SynthScan v2.0 examined 258,477 lines of code across 805 source files, recording 1656 pattern matches distributed across 10 syntactic categories. The overall adjusted score of 8.8 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).

8.8
Adjusted Score
8.8
Raw Score
100%
Time Factor
2026-08-29
Last Push
4.1K
Stars
Rust
Language
258.5K
Lines of Code
805
Files
1.7K
Pattern Hits
2026-08-29
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 365LOW 1291

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 1656 distinct pattern matches across 10 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 Block1270 hits · 1119 pts
SeverityFileLineSnippetContext
LOWCargo.toml1[workspace]COMMENT
LOWCargo.toml21# `[profile.release] panic = "unwind"`, and is excluded here. It is built withCOMMENT
LOWCargo.toml41#COMMENT
LOWCargo.toml121# napi 3 (not 2): oxc_napi 0.140.0 and oxc_sourcemap[napi] are built againstCOMMENT
LOWCargo.toml141rustc-hash = "2"COMMENT
LOWCargo.toml161# unaffected: registries serve .tgz without Content-Encoding.COMMENT
LOWCargo.toml181# Workspace restriction lints, promoted to warn and inherited by every nub crateCOMMENT
LOWCross.toml1# cross-rs configuration.COMMENT
LOWinstall.sh201# makes this idempotent across reinstall/upgrade and harmless if a futureCOMMENT
LOWhawk.toml1# hawk (astral-sh/hawk) visibility-lint config.COMMENT
LOW.githooks/agents-symlink-check.sh1#!/bin/shCOMMENT
LOWtools/pnpm-workspace.yaml1# pnpm-side soak surface + catalog (pnpm reads minimumReleaseAge in MINUTESCOMMENT
LOWtools/pnpm-workspace.yaml21# lists, which the gate can't validate); `soak:fix` prunes expired ones.COMMENT
LOWcrates/nub-phantom-scan/src/classify.rs21 HardPhantom,COMMENT
LOWcrates/nub-phantom-scan/src/graph.rs1//! Walk the module graph reachable from a package's PUBLISHED entry points,COMMENT
LOWcrates/nub-phantom-scan/src/graph.rs41 pub(crate) raw: String,COMMENT
LOWcrates/nub-phantom-scan/src/graph.rs61 pub files_analyzed: usize,COMMENT
LOWcrates/nub-phantom-scan/src/graph.rs81 fn resolve_entry(&self, entry_path: &str, prefer_dts: bool) -> Option<Self::Key>;COMMENT
LOWcrates/nub-phantom-scan/src/graph.rs201/// back at itself (`"."`/`""`/`"./"`) or a mutual `main` cycle across dirs wouldCOMMENT
LOWcrates/nub-phantom-scan/src/lib.rs1//! nub-phantom-scan — scan an already-extracted package version's PUBLISHED,COMMENT
LOWcrates/nub-phantom-scan/src/lib.rs41}COMMENT
LOWcrates/nub-phantom-scan/src/lib.rs81/// Scan a package straight from its CAS-backed file index — the EXTRACT-TIMECOMMENT
LOWcrates/nub-phantom-scan/src/manifest.rs1//! Parse a package's `package.json` into (a) its DECLARED dependency surface —COMMENT
LOWcrates/nub-phantom-scan/src/manifest.rs21 /// Required peers (`peerDependencies` without an `optional` meta flag).COMMENT
LOWcrates/nub-phantom-scan/src/manifest.rs281/// Whether a `main`/`module`/`bin`/`exports` target should SEED the reachableCOMMENT
LOWcrates/nub-data-formats/Cargo.toml1# The YAML/TOML/JSON5/JSONC parsers behind Nub's data imports, factored out soCOMMENT
LOWcrates/nub-data-formats/src/lib.rs1//! The data formats Nub's runtime accepts as imports — YAML, TOML, JSON5, JSONC.COMMENT
LOWcrates/nub-data-formats/src/lib.rs21/// take arbitrary user data — a `.json5` fixture is not a `nub.jsonc` — but farCOMMENT
LOWcrates/nub-tsconfig/Cargo.toml1# tsconfig discovery / parse / `extends` resolution (the get-tsconfig@4.14.0 port),COMMENT
LOWcrates/nub-tsconfig/src/lib.rs1//! In-process tsconfig discovery / parse / `extends` resolution + a `paths`COMMENT
LOWcrates/nub-tsconfig/src/lib.rs21//! (the cache-key component) all match get-tsconfig's output so warm transpileCOMMENT
LOWcrates/nub-tsconfig/src/lib.rs61COMMENT
LOWcrates/nub-tsconfig/src/lib.rs161COMMENT
LOWcrates/nub-tsconfig/src/lib.rs181/// Problems found parsing the tsconfig governing `dir`, already rendered for aCOMMENT
LOWcrates/nub-tsconfig/src/lib.rs201/// Both processes parse the same tsconfig on an ordinary run, so without this theCOMMENT
LOWcrates/nub-tsconfig/src/lib.rs561 Value::Array(arr) => arrCOMMENT
LOWcrates/nub-tsconfig/src/lib.rs981 // The `Option` is the deserialization target, not a wrapper the parser adds.COMMENT
LOWcrates/nub-tsconfig/src/lib.rs1181 emit_decorator_metadata: map.get("emitDecoratorMetadata").and_then(Value::as_bool),COMMENT
LOWcrates/nub-phantom/Cargo.toml1# nub-phantom — an INTERNAL/eval tool, not part of the shipped `nub` binary.COMMENT
LOWcrates/nub-phantom/src/lib.rs1//! nub-phantom — detect UNDECLARED (phantom) dependencies of an npm package.COMMENT
LOWcrates/nub-phantom/src/main.rs241struct Totals {COMMENT
LOWcrates/nub-core/Cargo.toml1# SELF-CONTAINED MANIFEST (no `*.workspace = true`): nub-core is a member of theCOMMENT
LOWcrates/nub-core/Cargo.toml61semver = "1"COMMENT
LOWcrates/nub-core/Cargo.toml81# shipped binary; the one-time ~tens-of-ms decode is irrelevant. Encode happensCOMMENT
LOWcrates/nub-core/build.rs1//! Single-binary blob generation (the `embed-runtime` feature only).COMMENT
LOWcrates/nub-core/build.rs141 let mut hasher = Sha256::new();COMMENT
LOWcrates/nub-core/benches/cache_body_copy.rs1//! Bench for the warm-hit body-copy reduction in `crates/nub-native/src/cache.rs`.COMMENT
LOWcrates/nub-core/benches/cache_hash.rs1//! Benches for the transpile-cache hot path.COMMENT
LOWcrates/nub-core/benches/workspace_filter.rs1//! Baseline benches for the workspace topo-sort hot path.COMMENT
LOWcrates/nub-core/src/lib.rs21/// standard library exposes no constant for this — only `env::join_paths` /COMMENT
LOWcrates/nub-core/src/config_cache.rs1//! Per-process, mtime-validated cache for config-file reads.COMMENT
LOWcrates/nub-core/src/config_cache.rs21//! reports the very same mtime. `size` catches that only when the length alsoCOMMENT
LOWcrates/nub-core/src/config_cache.rs41COMMENT
LOWcrates/nub-core/src/config_cache.rs61/// freshness stamp — its `(mtime, size)` pair — changes. Stores `Arc<V>` so aCOMMENT
LOWcrates/nub-core/src/config_cache.rs81COMMENT
LOWcrates/nub-core/src/config_cache.rs121 /// stamp matches the cached one; otherwise run `read` to produce a freshCOMMENT
LOWcrates/nub-core/src/config_cache.rs281 std::fs::write(&path, "v2").unwrap();COMMENT
LOWcrates/nub-core/src/compile.rs1//! The `nub compile` payload container — the single source of truth for theCOMMENT
LOWcrates/nub-core/src/compile.rs21//! launcher trusts the payload mapped from its own executable; publisherCOMMENT
LOWcrates/nub-core/src/compile.rs61/// or provisions one at runtime.COMMENT
1210 more matches not shown…
Decorative Section Separators260 hits · 798 pts
SeverityFileLineSnippetContext
MEDIUMcrates/nub-tsconfig/src/lib.rs345// ── `${configDir}` (TS 5.5) ─────────────────────────────────────────COMMENT
MEDIUMcrates/nub-tsconfig/src/lib.rs1163// ── compilerOptions extraction + hash ───────────────────────────────COMMENT
MEDIUMcrates/nub-tsconfig/src/lib.rs1210// ── paths matcher (get-tsconfig's `createPathsMatcher`) ─────────────COMMENT
MEDIUMcrates/nub-core/src/workspace/shell_escape.rs203 // ── POSIX sh (the verified-against-npm path) ──────────────────────────COMMENT
MEDIUMcrates/nub-core/src/workspace/shell_escape.rs282 // ── splice_args (the body+args display/exec string) ───────────────────COMMENT
MEDIUMcrates/nub-core/src/version_management/manage.rs66// ── install ──────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/version_management/manage.rs201// ── ls ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/version_management/manage.rs230// ── uninstall ────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/version_management/manage.rs269// ── pin ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/version.rs452 // ── Tier boundary cases ────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs156 // ── vm.Module / vm.SourceTextModule ────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs191 // ── EventSource global ──────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs211 // ── node:sqlite ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs232 // ── Wasm ES-module imports (import of `.wasm`) ──────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs259 // ── addon-modules (ESM import of native .node addons) ────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs283 // ── import-text (importing source as text via import attributes) ─────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs319 // ── Deferred module evaluation (`import defer`) ──────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs372 // ── Module syntax detection (ambiguous ESM `.js`) ────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs399 // ── node:ffi (foreign function interface) ────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs418 // ── node:vfs (virtual file system) ───────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs432 // ── node:stream/iter (async-iterator stream adapters) ────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs446 // ── WebSocket global ────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs462 // ── Web Storage (localStorage / sessionStorage) ─────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs491 // ── reportError ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs506 // ── URLPattern ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs524 // ── RegExp.escape ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs540 // ── Error.isError ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs557 // ── Promise.try ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs573 // ── Stage 3+ library surfaces ───────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs714 // ── Shipped-standard builtins missing below their Node line ─────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs833 // ── Promise.withResolvers ───────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs852 // ── Promise.allKeyed / Promise.allSettledKeyed ──────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs879 // ── Float16Array ────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs897 // ── Uint8Array base64/hex ───────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs917 // ── DisposableStack / AsyncDisposableStack / SuppressedError ─────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs966 // ── Temporal ────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs982 // ── Worker (browser-shape global) ───────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs997 // ── navigator global ────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs1018 // ── navigator.locks (Web Locks API) ─────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/cli_grammar_parity.rs111// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/cli_grammar_parity.rs115// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/cli_grammar_parity.rs343// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/cli_grammar_parity.rs347// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/cli_grammar_parity.rs463// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/cli_grammar_parity.rs468// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs1293// ── Version-gated tests ─────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs1503// ── Project-source plain JS (.js/.mjs/.cjs) transpile ───────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs3697 // ── Parallel run ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs3738 // ── Serial control run (concurrency=1) ───────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs3978// ── Section 4: Missing integration tests (v0.1-quality) ──────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs7875// ── Section 7: pnpm workspace behavior tests ────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs8343// ── `nub run` full flag set (run.md) ────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs9155// ── PM-management verbs (A2 passthrough disabled) ────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs9489// ── `nub pm` / `nub node` UX-message fixes ───────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/project_config.rs85// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/project_config.rs87// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/project_config.rs197// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/project_config.rs199// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/project_config.rs1018// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/project_config.rs1022// ─────────────────────────────────────────────────────────────────────────────COMMENT
200 more matches not shown…
AI Slop Vocabulary74 hits · 229 pts
SeverityFileLineSnippetContext
MEDIUMCargo.toml108# Benchmark harness (dev-only). `harness = false` benches drive criterion's ownCOMMENT
MEDIUMcrates/nub-core/src/version_management/mod.rs182/// selector keys on Node's `glibcVersionRuntime` (the robust detect-libc signal),COMMENT
MEDIUMcrates/nub-cache-key/Cargo.toml3# resolved by the Node host at dlopen, so a `cargo test` harness for that crateCOMMENT
MEDIUMcrates/nub-json-guard/Cargo.toml4# `test = false` (a `cargo test` harness cannot link them) — a copy of thisCOMMENT
MEDIUMcrates/nub-native/Cargo.toml118# allowed), but a `cargo test` harness is a normal executable and CANNOT link thoseCOMMENT
MEDIUMcrates/nub-cli/tests/integration.rs2798 // Dual-channel doubling regression, tier-robust. On the `nub <file>` path theCOMMENT
MEDIUMcrates/nub-cli/tests/integration.rs8535/// fake shell that prints a marker before delegating to `/bin/sh` — robust acrossCOMMENT
MEDIUMcrates/nub-cli/tests/integration.rs8828 // loading is the robust augmentation discriminator here — flag/preloadCOMMENT
MEDIUMtests/bench/install/run-warm-gvs.sh106 # $$ here is the harness PID (constant); $RANDOM varies per --prepare eval.COMMENT
MEDIUMtests/bench/install/gen-fixtures.sh7# each bench harness installs from nub.lock — its native lockfile — not theCOMMENT
MEDIUMtests/bench/script-runner/run-vs-node.sh20# This is a canonical checked-in benchmark harness. By default, result JSON isCOMMENT
MEDIUMtests/bench/bin-runner/run-pure.sh10# bin-runner sibling of run-script-runner-pure.sh and uses the same harness.COMMENT
MEDIUMtests/launcher/make-fixture.sh59# (the harness exercises the RUNTIME heal, independent of postinstall).COMMENT
MEDIUMtests/launcher/make-fixture.sh185 # failure this harness exists to prevent.COMMENT
MEDIUMtests/pnpm-conformance/run.sh2# pnpm conformance harness — run pnpm's OWN black-box CLI test suite against nub.COMMENT
MEDIUMtests/pnpm-conformance/run.sh210# Substituting them into the file is the robust seam. `#` is the sed delimiterCOMMENT
MEDIUMtests/pnpm-conformance/run.sh258 # First integer run of `jest --version` (robust to a leading v / extra text).COMMENT
MEDIUMtests/brand-global/run.sh60# clean too, then print a single PASS/FAIL line the harness greps. A TS annotationCOMMENT
MEDIUMtests/aube-conformance/run.sh2# Lockfile conformance harness — nub's embedded aube engine writes eachCOMMENT
MEDIUMtests/mutation/run-mutations.sh2# Lockfile MUTATION differential harness — the write-path counterpart to theCOMMENT
MEDIUMtests/mutation/run-mutations.sh111 # spec file, which is harness metadata, not project content.COMMENT
MEDIUMtests/native-deps/run.sh2# Native-dependency floor end-to-end harness.COMMENT
MEDIUMtests/native-deps/run.sh76# Copy only the fixture files — not the harness scripts — to avoidCOMMENT
MEDIUMtests/parcel-gvs/make-fixture.sh7# over-split this harness regression-tests).COMMENT
MEDIUMtests/parcel-gvs/run.sh2# Regression harness for the GVS @parcel/core store-dir over-split.COMMENT
MEDIUMtests/daily-driver/run.sh2# Real-app daily-loop smoke harness.COMMENT
MEDIUMtests/registry-stall/run-stall-matrix.sh34# A binary that predates the stall bound is the failure mode this harness isCOMMENT
MEDIUMtests/vite-compat/driver.sh25# Fidelity note: this harness asserts at the HTTP layer — it fetches the REALCOMMENT
MEDIUMtests/vite-compat/driver.sh43# the next run then binds a DIFFERENT port while the harness curls the staleCOMMENT
MEDIUMtests/vite-compat/driver.sh44# (unpatched) server → false 403s. The robust fix is a process GROUP: the devCOMMENT
MEDIUMtests/conversion/run.sh2# Cross-format lockfile conversion harness — proves `nub pm use <target>` producesCOMMENT
MEDIUMtests/conversion/run.sh10# For each (source, target) pair the harness:COMMENT
MEDIUMtests/compile-corpus/layouts.sh185# defect for as long as the harness existed: the shared chunks were emitted asCOMMENT
MEDIUMtests/cross-runtime/pty-spawn.py7# exits with the child's status, because the harness reads exit codes; and itCOMMENT
MEDIUMtests/cross-runtime/pty-spawn.py8# resolves the command through PATH (execvpe, not execve), because the harnessCOMMENT
MEDIUMtests/global-install/run.sh49# fail, the harness is broken, not the code. `git worktree add` at theCOMMENT
MEDIUMtests/aube-bats/run.sh5# registry. This harness runs a CURATED subset of those suites with nub's PMCOMMENT
MEDIUMtests/aube-bats/run.sh9# that exec's nub — so the harness's own PATH prepend resolves straight toCOMMENT
MEDIUMtests/aube-bats/run.sh51# nothing else is guaranteed to survive the harness's env isolation);COMMENT
MEDIUMtests/aube-bats/run.sh52# 2. translate the harness's AUBE_* knobs to their npm_config_* spellings.COMMENT
MEDIUMtests/installer/run.sh6# Local end-to-end harness for install.sh. Each case runs the REAL installerCOMMENT
MEDIUMtests/conformance/run.sh2# Drop-in PM conformance harness — proves nub is a true drop-in package managerCOMMENT
MEDIUMtests/conformance/run-pnpm11.sh2# pnpm-11 conformance leg for the drop-in PM conformance harness.COMMENT
MEDIUMtests/conformance/frontdoor/run.sh9# DISTINCT from its two siblings (README.md): the lockfile harness verifiesCOMMENT
MEDIUMtests/conformance/frontdoor/run.sh10# round-trip fidelity; the cmdflag harness verifies every verb runs on one repo;COMMENT
MEDIUMtests/conformance/frontdoor/run.sh23set -uo pipefail # NOT -e: a failing cell is data, not a harness abort.CODE
MEDIUMtests/conformance/cmdflag/run.sh2# Command×flag conformance harness — exercise nub's FULL CLI surface against aCOMMENT
MEDIUMtests/conformance/cmdflag/run.sh8# DISTINCT from the lockfile harness one level up (tests/conformance/run.sh),COMMENT
MEDIUMtests/conformance/cmdflag/run.sh17# harness operates on COPIES — the fixture is neverCOMMENT
MEDIUMtests/conformance/cmdflag/run.sh32set -uo pipefail # NOT -e: a failing cell is data, not a harness abort.CODE
MEDIUMtests/conformance/cmdflag/run.sh68# point of the harness is to cover REAL machine state, not a pristine void.COMMENT
MEDIUMscripts/check-docs-links.ts144 // Markdown link target: ](...) — the simplest robust form; docs use plainCOMMENT
MEDIUMscripts/ci-watch.ts3// terminal, then exit with a status the orchestrator can trust. The robustCOMMENT
MEDIUMscripts/remote-build.ts850# why a run could not fit the driving harness's ceiling and the tool never completed a job.COMMENT
MEDIUM.github/workflows/release.yml561 # harness exercises the PM engine (install/add/pm use), not the data-formatCOMMENT
MEDIUM.github/workflows/verb-dispatch.yml8# harness in tests/launcher/ — the two platforms take different paths and only one ofCOMMENT
MEDIUM.github/workflows/native-deps.yml15# Why separate workflow: the harness does a real npm registry install of esbuildCOMMENT
MEDIUM.github/workflows/test-install.yml4# comprehensive battery the release pipeline runs post-publish, but decoupled from aCOMMENT
MEDIUM.github/workflows/compile-native.yml145 # Tree SHAPES, as opposed to the islands harness above, which varies theCOMMENT
MEDIUM.github/workflows/compile-native.yml151 # Linux only, and only because it is cheap: the whole harness is ~80s andCOMMENT
14 more matches not shown…
Modern AI Meta-Vocabulary29 hits · 92 pts
SeverityFileLineSnippetContext
MEDIUMcrates/nub-cli/tests/init_cmd.rs1//! `nub init` through the real binary — scaffold contents, refuse-don't-COMMENT
MEDIUMcrates/nub-cli/tests/init_cmd.rs3//! is offline by construction: scaffold-only cases use `--no-install`, whileCOMMENT
MEDIUMcrates/nub-cli/tests/init_cmd.rs394/// `git check-ignore` is the only honest test of a `.gitignore`: the scaffold'sCOMMENT
MEDIUMcrates/nub-cli/tests/pm_verbs.rs910/// The scaffold contract itself lives in tests/init_cmd.rs.COMMENT
MEDIUMcrates/nub-cli/src/init.rs1//! `nub init` — scaffold a minimal modern-TS project (nub's own project init,COMMENT
MEDIUMcrates/nub-cli/src/init.rs3//! from ENGINE_VERBS). Design record: internal/commands/init.md. The scaffold isCOMMENT
MEDIUMcrates/nub-cli/src/init.rs16/// `@types/node` range written into the scaffold. Tracks the docs' latest-majorCOMMENT
MEDIUMcrates/nub-cli/src/init.rs21/// Oldest declarations that cover the scaffold's `Worker`-era ambient surface.COMMENT
MEDIUMcrates/nub-cli/src/init.rs27/// `typescript` range written into the scaffold. Nub transpiles TS itself, soCOMMENT
MEDIUMcrates/nub-cli/src/init.rs361/// Best-effort `git init` — a missing/failing git degrades the scaffold, itCOMMENT
MEDIUMcrates/nub-cli/src/cli.rs2837 // Self-update, the scaffold, and the help pages consume no projectCOMMENT
MEDIUMcrates/nub-cli/src/cli.rs2841 // scaffold's final cwd.COMMENT
MEDIUMcrates/nub-cli/src/cli.rs9779 // (the same never-scaffold rule write_declared_pm enforces — but onlyCOMMENT
MEDIUMcrates/nub-cli/src/pm_engine/install_family.rs1400 // refuses to scaffold one); the install already succeeded, so this is aCOMMENT
MEDIUMcrates/nub-cli/src/pm_engine/install_family.rs2394 /// or scaffold one — the stamp is best-effort and silently no-ops (nub neverCOMMENT
MEDIUMcrates/nub-cli/src/pm_engine/mod.rs256 // own project scaffold (src/init.rs, a clap subcommand), not the engine'sCOMMENT
MEDIUMtests/daily-driver/README.md35# Reuse an existing fixture (skip the scaffold + install for iteration)COMMENT
MEDIUMtests/vite-compat/scaffold.sh2# scaffold.sh — non-interactively scaffold a real Vite-powered project for theCOMMENT
MEDIUMtests/vite-compat/scaffold.sh7# Usage: scaffold.sh <case> <dest-dir>COMMENT
MEDIUMtests/vite-compat/scaffold.sh8# Cases print, after scaffolding, two lines the runner consumes:COMMENT
MEDIUMtests/framework-matrix/frameworks.sh10# Usage: frameworks.sh scaffold <name> <dest> # scaffolds into <dest>, prints DEV=/BUILD=/PREVIEW=/PROBE=/GVS=COMMENT
MEDIUMtests/framework-matrix/matrix.sh3# scaffold it via its OFFICIAL create-* generator (frameworks.sh), then drive theCOMMENT
MEDIUMwiki/research/upstream-cpp-resolver-prs.md30- **#61548** (joyeecheung, merged Feb 2026) — "src: initial support for ESM in embedder API." Adds `ModuleData`, `ModuleCODE
MEDIUMwiki/research/gvs-in-ci.md52So the divergence question inverts: Nub is not diverging from the norm by gating GVS in CI — Nub diverged by making GVS CODE
MEDIUMwiki/research/workspace-discovery-walk-up.md19## (1) Test scaffoldCOMMENT
MEDIUMbenchmarks/README.md32# Script runner overhead (pure orchestration)COMMENT
MEDIUM.github/workflows/release.yml863 # writes both literals into the `nub init` scaffold, so they sit in everyCOMMENT
MEDIUMsite/public/skill.md76nub run --node test # nub's CLI orchestration, runtime augmentation offCODE
MEDIUMskills/nub/SKILL.md76nub run --node test # nub's CLI orchestration, runtime augmentation offCODE
Example Usage Blocks7 hits · 10 pts
SeverityFileLineSnippetContext
LOWtests/bench/install/cold-cas.sh34# Usage:COMMENT
LOWtests/bench/install/run.sh5# Usage:COMMENT
LOWtests/bench/install/run-4way.sh10# Usage:COMMENT
LOWtests/pnpm-conformance/run.sh11# Usage:COMMENT
LOWtests/vm/tart-vm.sh13# Usage:COMMENT
LOWtests/pnp/run-pnp-matrix.sh17# Usage:COMMENT
LOWtests/conformance/run-pnpm11.sh23# Usage:COMMENT
Hyper-Verbose Identifiers9 hits · 9 pts
SeverityFileLineSnippetContext
LOWtests/worker-wpt/wpt/resources/testharness.js338 function DedicatedWorkerTestEnvironment() {CODE
LOWtests/worker-wpt/wpt/resources/testharness.js361 function SharedWorkerTestEnvironment() {CODE
LOWtests/worker-wpt/wpt/resources/testharness.js387 function ServiceWorkerTestEnvironment() {CODE
LOWtests/worker-wpt/wpt/resources/testharness.js439 function ShadowRealmTestEnvironment() {CODE
LOWtests/worker-wpt/wpt/resources/testharness.js4839 function OptionalFeatureUnsupportedError(message)CODE
LOW…red-clone/structured-clone-battery-of-tests-harness.js16function runStructuredCloneBatteryOfTests(runner) {CODE
LOW…skills/cpu-reduction/scripts/clean-worktree-targets.py100def owns_installed_dev_binary(path: Path, binaries: list[Path]) -> bool:CODE
LOWwiki/research/store-marker-hardcoding.md18function getProjectRootDirectoryFromNodeModules(projectPath) {CODE
LOWwiki/research/node-strip-types-interaction.md29function initializeExtensionFormatMap() {CODE
Self-Referential Comments2 hits · 5 pts
SeverityFileLineSnippetContext
MEDIUMcrates/nub-core/src/pm/lockfile_version.rs256 let berry = "# This file is generated by running \"yarn install\".\n\n\CODE
MEDIUM.github/workflows/release.yml409 # This file is what makes the corpus DOWNLOAD-RANKED rather than theCOMMENT
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWinstall.sh328# Check if already in PATHCOMMENT
LOWsite/public/install.sh328# Check if already in PATHCOMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWscripts/remote-build.ts436[ -s runtime/addons/nub-native.node ] || printf 'placeholder' > runtime/addons/nub-native.nodeCODE
LOWscripts/remote-build.ts827mkdir -p runtime/addons && printf 'placeholder' > runtime/addons/nub-native.nodeCODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…skills/cpu-reduction/scripts/clean-worktree-targets.py4CODE