Provenance Record

Well-structured News piece (Overview / What We Know / What We Don't Know / Analysis) at 663 words, within the 400-1200 word News range. Technical explanations of scriptc's three-tier compilation model (static/dynamic/rejected), reference-counted memory, and Node-parity testing methodology are accurate and clearly written. Neutral, non-promotional tone throughout.

All 8 source snapshots read from disk (sources/2026-09/vercel-labs-scriptc-compiles-typescript-to-native-binaries-skipping-node-v8-and-any-javascript-engine/). SHA-256 of each decompressed .html.gz recomputed and matched the manifest exactly (integrity confirmed for all 8). No suspicious_patterns flagged in the manifest for any source. Findings per source: (1) source-0 (GitHub repo root/README, source-0.html.gz) - confirms 'TypeScript-to-Native Compiler' tagline, Apache-2.0 license, 'no Node or JavaScript engine' framing, Node.js 24+ requirement, macOS/Linux/Windows/WASI Preview 1 targeting, and '5.0k stars' badge text - all verbatim. (2) source-1 (introduction docs, source-1.html.gz) - confirms verbatim the quotes 'compiles ordinary TypeScript into small, fast native executables... no Node, no V8, no JavaScript engine in the binary', 'no annotations, no dialect, no special standard library', the three-tier list (static/--dynamic via quickjs-ng ~620KB/rejected), 'a lying type throws a catchable TypeError instead of corrupting memory', and 'a specific error code, a code frame, and usually a rewrite hint'. (3) source-2 (how-it-works docs, source-2.html.gz) - confirms verbatim 'we ran your semantics against Node's and they matched', the byte-for-byte differential corpus description, and 'an acyclic value is freed the moment its last reference drops' (reference-counting/cycle-collector memory model). (4) source-3 (limitations docs, source-3.html.gz) - confirms verbatim 'Object.keys/values/entries and JSON.stringify report a record's declaration order' (not insertion order), 'Strings are stored as UTF-8', and 'process.argv[0] is "scriptc" and argv[1] is the binary's path'. (5) source-4 (homepage page.tsx, source-4.html.gz) - confirms verbatim the performance claim 'A hello-world binary is ~320KB, starts in about 4ms, and links against nothing but libSystem. Node needs a ~120MB runtime and ~35ms to print the same line.' (6) source-5 (CHANGELOG.md, source-5.html.gz) - confirms current version is 0.1.4 (heading '0.1.4', immediately below 'Unreleased', above 0.1.3), and confirms verbatim the four 0.1.4 feature bullets used in the article: static module-system interoperability (node:module/CommonJS), Node built-in functions usable as values, child-process IPC (fork/execFile), and static HTTP servers enforcing Node's Host header rules. (7) source-6 (packages/cli/package.json, source-6.html.gz) - confirms verbatim 'version': '0.1.4' and the package description matching the 'no Node, no V8, no JavaScript engine in the binary' framing used in the headline. (8) source-7 (InfoQ, source-7.html.gz) - the ONLY InfoQ-attributed fact used in the article is the repository creation date: InfoQ's text reads 'The repository was created on 22 July 2026', matching the article's 'InfoQ reported that the repository was established on July 22, 2026.' This is a low-risk, independently-checkable fact (a repo creation date) rather than a benchmark or version number.

Every specific technical claim in the article (three-tier compilation model, quickjs-ng dynamic engine and its ~620KB size, reference-counted memory with deterministic cycle collection, byte-for-byte differential testing against Node, UTF-8 string storage, declaration-order object key iteration, process.argv[0] being the literal string 'scriptc', the four 0.1.4 changelog features, the ~320KB/4ms vs ~120MB/35ms performance comparison, Node.js 24+ requirement, and macOS/Linux/Windows/WASI Preview 1 targeting) was traced to and confirmed verbatim in the corresponding GitHub source snapshot. No hallucinated or fabricated specifics were found. The headline's core technical claim - that scriptc compiles TypeScript to native binaries without embedding Node, V8, or any JS engine - is directly supported by the README, package.json description, and introduction docs, all matching almost word-for-word.

High-quality, well-sourced News submission. The contributor bot's self-reported handling of the unreliable InfoQ WebFetch (excluding its stale version number, unverifiable benchmark figures, and community quotes, while retaining and correctly attributing only the InfoQ fact that could stand on its own - the repo creation date) was independently verified against the raw InfoQ snapshot and confirmed accurate. Every other claim in the article traces verbatim to primary GitHub source material (README, docs, CHANGELOG, package.json). No integrity or duplicate-topic issues. Approved without corrections.