This report summarizes scanner evidence for bashalarmistalt/decimen-optical-transfer, a TypeScript project with 6,976 GitHub stars. SynthScan examined 23,283 lines of code across 108 source files, recording 23 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 1.0 (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? 23 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 1 finding(s).
Which changes need focused human review? 23 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 23 distinct pattern matches across 2 syntactic categories. 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 | vite.config.ts | 21 | import { emitAs } from "./build/emit-as"; | COMMENT |
| LOW | vite.config.ts | 161 | injectRegister: false, | COMMENT |
| LOW | tests/transfer.test.ts | 1 | // Cross-layer transfer test: container → fountain → framed wire → back. | COMMENT |
| LOW | tests/fountain.test.ts | 1 | // fountain.ts IS the wire format. Sender and receiver derive every frame's | COMMENT |
| LOW | shared/progress.ts | 41 | if (uniqueFrames < minimumFrames) { | COMMENT |
| LOW | shared/send-settings.ts | 1 | // The sender's transmit tuning, in one place. The dropdowns in send/index.html | COMMENT |
| LOW | shared/fountain.ts | 1 | // Systematic-carousel fountain code (wire format v2) — the trick that makes | COMMENT |
| LOW | shared/protocol.ts | 1 | // Frame protocol: every QR frame is fully self-describing, so there is NO | COMMENT |
| LOW | shared/protocol.ts | 21 | // receiver silently did nothing, so a version-mismatched stream looked | COMMENT |
| LOW | shared/protocol.ts | 41 | // must-understand and ignorable halves (see CRITICAL_FLAGS). That split has | COMMENT |
| LOW | shared/apng.ts | 1 | // APNG assembly over the PNG primitives: acTL after IHDR, an fcTL before | COMMENT |
| LOW | shared/i18n/messages.ts | 1 | // The complete surface of user-facing text, as one typed interface. | COMMENT |
| LOW | shared/i18n/loaders.ts | 1 | // Hosted catalog loading: one dynamic import per locale, so each language is | COMMENT |
| LOW | shared/i18n/registry.ts | 1 | // The locale control panel: every language Decimen ships, in one table. | COMMENT |
| LOW | shared/i18n/index.ts | 1 | // The i18n runtime: resolve a locale, load its catalog, put it on screen. | COMMENT |
| LOW | receive/main.ts | 1 | // Receiver: camera → WASM QR decode in workers → fountain decoder → file. | COMMENT |
| LOW | receive/main.ts | 201 | // A grid sender shows several codes; when fewer regions are live than the | COMMENT |
| LOW | receive/worker-factory.ts | 1 | // Served builds: a module worker fetched by URL. The browser caches it, and the | COMMENT |
| LOW | receive/worker.ts | 1 | // QR decode worker: the decimen-codec engine (a custom zxing-cpp build) | COMMENT |
| LOW | send/main.ts | 1 | // Sender: turn a file into an endless fountain-coded QR stream. | COMMENT |
| LOW | send/main.ts | 721 | // cell rectangle; cells align to cell×scale boundaries, so the partial blit | COMMENT |
| LOW | send/export.ts | 1 | // Turn the armed payload into a downloadable animation: the same wire frames | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | shared/frame-capacity.ts | 41 | export function smallestSufficientFrameSize( | CODE |