Repository Analysis

nubjs/nub

The fast all-in-one Node.js toolkit

11.2 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of nubjs/nub, a Rust project with 2,903 GitHub stars. SynthScan v2.0 examined 145,143 lines of code across 609 source files, recording 1032 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 11.2 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).

11.2
Adjusted Score
11.2
Raw Score
100%
Time Factor
2026-07-14
Last Push
2.9K
Stars
Rust
Language
145.1K
Lines of Code
609
Files
1.0K
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

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.

No multi-scan history yet — run the scanner again to build trend data.

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 315LOW 717

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 1032 distinct pattern matches across 8 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 Separators239 hits · 742 pts
SeverityFileLineSnippetContext
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.rs209// ── ls ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/version_management/manage.rs238// ── uninstall ────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/version_management/manage.rs277// ── pin ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/version.rs408 // ── Tier boundary cases ────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs139 // ── vm.Module / vm.SourceTextModule ────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs174 // ── EventSource global ──────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs194 // ── node:sqlite ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs215 // ── Wasm ES-module imports (import of `.wasm`) ──────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs242 // ── addon-modules (ESM import of native .node addons) ────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs266 // ── import-text (importing source as text via import attributes) ─────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs292 // ── Module syntax detection (ambiguous ESM `.js`) ────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs319 // ── node:ffi (foreign function interface) ────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs338 // ── node:vfs (virtual file system) ───────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs352 // ── node:stream/iter (async-iterator stream adapters) ────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs366 // ── WebSocket global ────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs382 // ── Web Storage (localStorage / sessionStorage) ─────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs411 // ── reportError ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs426 // ── URLPattern ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs444 // ── RegExp.escape ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs460 // ── Error.isError ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs477 // ── Promise.try ─────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs493 // ── Float16Array ────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs511 // ── Uint8Array base64/hex ───────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs531 // ── DisposableStack / AsyncDisposableStack / SuppressedError ─────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs580 // ── Temporal ────────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs596 // ── Worker (browser-shape global) ───────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs611 // ── navigator global ────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-core/src/node/feature_matrix.rs632 // ── navigator.locks (Web Locks API) ─────────────────────────────────────COMMENT
MEDIUMcrates/nub-native/src/tsconfig.rs173// ── `${configDir}` (TS 5.5) ─────────────────────────────────────────COMMENT
MEDIUMcrates/nub-native/src/tsconfig.rs959// ── compilerOptions extraction + hash ───────────────────────────────COMMENT
MEDIUMcrates/nub-native/src/tsconfig.rs1006// ── paths matcher (get-tsconfig's `createPathsMatcher`) ─────────────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.rs135// ── Version-gated tests ─────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs311// ── Project-source plain JS (.js/.mjs/.cjs) transpile ───────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs2212 // ── Parallel run ──────────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs2253 // ── Serial control run (concurrency=1) ───────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs2493// ── Section 4: Missing integration tests (v0.1-quality) ──────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs5824// ── Section 7: pnpm workspace behavior tests ────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs6251// ── `nub run` full flag set (run.md) ────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs7004// ── PM-management verbs (A2 passthrough disabled) ────────────────────────────COMMENT
MEDIUMcrates/nub-cli/tests/integration.rs7338// ── `nub pm` / `nub node` UX-message fixes ───────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/cli.rs2612// ── Subcommand implementations ───────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/cli.rs7489// ── PM shims (`nub pm shim` / `unshim` + the argv0 dispatch) ──────────COMMENT
MEDIUMcrates/nub-cli/src/cli.rs9690 // ── nub pm verbs + PM-verb redirect ─────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/cli.rs10283 // ── PM shim: plan / provenance / dynamic default ─────────────────────COMMENT
MEDIUMcrates/nub-cli/src/cli.rs10665 // ── nubx argv0 dispatch ─────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/cli.rs10801 // ── .bin launcher resolution (the node-vs-shim decision) ─────────────COMMENT
MEDIUMcrates/nub-cli/src/nubx_consent.rs183// ─────────────────────────── ledger storage ───────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/nubx_consent.rs252// ─────────────────────────── classification ───────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/nubx_consent.rs313// ─────────────────────────── context probes ───────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/pm_engine/info_family.rs136// ── per-verb wrappers ───────────────────────────────────────────────────────COMMENT
MEDIUMcrates/nub-cli/src/pm_engine/info_family.rs292// ── wired verbs ─────────────────────────────────────────────────────────────COMMENT
179 more matches not shown…
Over-Commented Block702 hits · 620 pts
SeverityFileLineSnippetContext
LOWCargo.toml1[workspace]COMMENT
LOWCargo.toml21# `[profile.release] panic = "unwind"`, and is excluded here. It is builtCOMMENT
LOWCargo.toml41# reachable-graph phantom scanner, and crates/nub-phantom-core (also a MEMBER)COMMENT
LOWCargo.toml61panic = "abort"COMMENT
LOWCargo.toml101# Benchmark harness (dev-only). `harness = false` benches drive criterion's ownCOMMENT
LOWCargo.toml141serde_json = "1"COMMENT
LOWCargo.toml161# DEFLATE, so we skip bzip2/zstd/lzma/aes backends and their C deps. Keeps theCOMMENT
LOWCross.toml1# cross-rs configuration.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.rs61COMMENT
LOWcrates/nub-phantom-scan/src/graph.rs401/// Join `from_dir` + `spec` as POSIX relpaths and collapse `.`/`..`. ReturnsCOMMENT
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 pub from_subpath: bool,COMMENT
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/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.toml41# must not alphabetize the user's keys (a pin write that reorders the manifestCOMMENT
LOWcrates/nub-core/build.rs1//! Single-binary blob generation (the `embed-runtime` feature only).COMMENT
LOWcrates/nub-core/build.rs101 // `dlopen`s — as compile-time consts. `runtime_cache::verify_entrypoints`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/// Strip a leading UTF-8 BOM (U+FEFF, bytes `EF BB BF`) so `serde_json` acceptsCOMMENT
LOWcrates/nub-core/src/config_cache.rs1//! Per-process, mtime-validated cache for config-file reads.COMMENT
LOWcrates/nub-core/src/config_cache.rs21//! pre-cache code on those paths.COMMENT
LOWcrates/nub-core/src/pm/registry.rs1//! Registry metadata lookup for PM provisioning: dynamic version resolutionCOMMENT
LOWcrates/nub-core/src/pm/registry.rs41 Sha512(String),COMMENT
LOWcrates/nub-core/src/pm/registry.rs61}COMMENT
LOWcrates/nub-core/src/pm/registry.rs81/// `.npmrc` host auth).COMMENT
LOWcrates/nub-core/src/pm/registry.rs321 return tarball.to_string(); // already on the mirrorCOMMENT
LOWcrates/nub-core/src/pm/registry.rs361/// Resolve `spec` against an already-fetched packument. PURE — no network, no envCOMMENT
LOWcrates/nub-core/src/pm/registry.rs421 }COMMENT
LOWcrates/nub-core/src/pm/registry.rs521 }COMMENT
LOWcrates/nub-core/src/pm/resolve.rs1//! The single PM pin reader. Every consumer that needs to know "which packageCOMMENT
LOWcrates/nub-core/src/pm/resolve.rs21/// A resolved PM pin: which manager, and the version spec if one was stated.COMMENT
LOWcrates/nub-core/src/pm/resolve.rs41 /// Berry release, so the engine surfaces a clear error.COMMENT
LOWcrates/nub-core/src/pm/resolve.rs221}COMMENT
LOWcrates/nub-core/src/pm/resolve.rs401/// probe (wiki/commands/pm/identity-policy.md, Axiom 1: declaration outranksCOMMENT
LOWcrates/nub-core/src/pm/resolve.rs561///COMMENT
LOWcrates/nub-core/src/pm/resolve.rs601/// version bump behind `nub pm update`). Per the PM identity policyCOMMENT
LOWcrates/nub-core/src/pm/resolve.rs621/// they cannot drift. `onFail: "warn"` is load-bearing: npm 11 enforcesCOMMENT
LOWcrates/nub-core/src/pm/resolve.rs701/// itself writes — `^<exact>` (a caret over a full semver, e.g. `^9.1.0`,COMMENT
LOWcrates/nub-core/src/pm/resolve.rs741 crlf,COMMENT
LOWcrates/nub-core/src/pm/resolve.rs861 // A URL/git reference in place of a version (`pnpm@https://…`, `pnpm@git+…`)COMMENT
LOWcrates/nub-core/src/pm/resolve.rs921/// - no usable version → fall back to the `.yarnrc.yml` presence signalCOMMENT
LOWcrates/nub-core/src/pm/resolve.rs941/// leading run of digits before the first `.`, `+`, or `-`.COMMENT
LOWcrates/nub-core/src/pm/lockfile_version.rs1//! Lockfile-format-version → PM-version-range inference.COMMENT
LOWcrates/nub-core/src/pm/lockfile_version.rs21 pub pm: Pm,COMMENT
LOWcrates/nub-core/src/pm/extract.rs1//! PM tarball extraction. npm publishes `.tgz` (gzip + tar) with everything underCOMMENT
LOWcrates/nub-core/src/pm/extract.rs21};COMMENT
LOWcrates/nub-core/src/pm/shim.rs1//! The PM-shim library core: everything `nub pm shim` / `nub pm unshim` and theCOMMENT
LOWcrates/nub-core/src/pm/shim.rs101pub const TRANSPARENT_VERBS: [&str; 4] = ["init", "create", "dlx", "exec"];COMMENT
LOWcrates/nub-core/src/pm/shim.rs181 /// never provision a competing PM (the resolve layer can't classify `nub`COMMENT
LOWcrates/nub-core/src/pm/shim.rs201 Refuse {COMMENT
LOWcrates/nub-core/src/pm/shim.rs221/// - unpinned → fall through, always (transparency is irrelevant);COMMENT
LOWcrates/nub-core/src/pm/shim.rs301 match invoked {COMMENT
LOWcrates/nub-core/src/pm/shim.rs321COMMENT
LOWcrates/nub-core/src/pm/shim.rs341 Pm::Npm => false,COMMENT
642 more matches not shown…
AI Slop Vocabulary61 hits · 190 pts
SeverityFileLineSnippetContext
MEDIUMCargo.toml101# Benchmark harness (dev-only). `harness = false` benches drive criterion's ownCOMMENT
MEDIUMcrates/nub-cache-key/Cargo.toml3# resolved by the Node host at dlopen, so a `cargo test` harness for that crateCOMMENT
MEDIUMcrates/nub-native/Cargo.toml118# allowed), but a `cargo test` harness is a normal executable and CANNOT link thoseCOMMENT
MEDIUMcrates/nub-cli/tests/integration.rs1314 // Dual-channel doubling regression, tier-robust. On the `nub <file>` path theCOMMENT
MEDIUMcrates/nub-cli/tests/integration.rs6443/// fake shell that prints a marker before delegating to `/bin/sh` — robust acrossCOMMENT
MEDIUMcrates/nub-cli/tests/integration.rs6678 // 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/install/run-4way.sh97# CI=1 = off (the harness's existing GVS-pin mechanism).COMMENT
MEDIUMtests/bench/install/run-4way.sh104# Confirm the two nub modes take the paths we label them. The robust cross-platformCOMMENT
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.sh44# (the harness exercises the RUNTIME heal, independent of postinstall).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/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/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
MEDIUM.github/workflows/release.yml309 # harness exercises the PM engine (install/add/pm use), not the data-formatCOMMENT
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/verify-install.yml237 # The harness's install.sh authenticates the releases/latest API call toCOMMENT
MEDIUM.github/workflows/pnpm-conformance.yml7# pnpm/test/utils/execPnpm.ts). The harness (tests/pnpm-conformance/) clones pnpmCOMMENT
MEDIUM.github/workflows/pnpm-conformance.yml39 # keeps version-string assertions from false-failing — the harness README'sCOMMENT
MEDIUM.github/workflows/aube-parity.yml29 # tests/aube-bats/** is the nub-adapted harness (shim + skip lists) theCOMMENT
MEDIUM.github/workflows/aube-parity.yml31 # lockfile conformance harness the aube-conformance job runs.COMMENT
MEDIUM.github/workflows/aube-parity.yml142 # nub round-trip legs stay ubuntu-only; the harness itself runs underCOMMENT
MEDIUM.github/workflows/aube-parity.yml149 # bash harness and the committed fixtures at checkout. Must precedeCOMMENT
MEDIUM.github/workflows/lockfile-roundtrip.yml21# in sync with the tool/version matrices documented in each harness README andCOMMENT
MEDIUM.github/workflows/lockfile-roundtrip.yml25# per-PR — the conformance harness on a TIGHT, fast fixture set, so it doesn'tCOMMENT
MEDIUM.github/workflows/lockfile-roundtrip.yml32# each harness's expected-failures.txt and must shrink (a stale entry fails theCOMMENT
1 more matches not shown…
Modern AI Meta-Vocabulary14 hits · 44 pts
SeverityFileLineSnippetContext
MEDIUMcrates/nub-cli/src/cli.rs1684 // engine's npm-style manifest scaffold) — deliberately absentCOMMENT
MEDIUMcrates/nub-cli/src/cli.rs7020 // (the same never-scaffold rule write_declared_pm enforces — but onlyCOMMENT
MEDIUMcrates/nub-cli/src/pm_engine/install_family.rs1194 // refuses to scaffold one); the install already succeeded, so this is aCOMMENT
MEDIUMcrates/nub-cli/src/pm_engine/install_family.rs2125 /// or scaffold one — the stamp is best-effort and silently no-ops (nub neverCOMMENT
MEDIUMcrates/nub-cli/src/pm_engine/mod.rs253 // npm-style manifest scaffold. cli.rs answers `nub init` with aCOMMENT
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
MEDIUMbenchmarks/README.md32# Script runner overhead (pure orchestration)COMMENT
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.sh14# 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 Identifiers6 hits · 6 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
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWinstall.sh246# Check if already in PATHCOMMENT
LOWsite/public/install.sh246# Check if already in PATHCOMMENT
Self-Referential Comments1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMcrates/nub-core/src/pm/lockfile_version.rs256 let berry = "# This file is generated by running \"yarn install\".\n\n\CODE