Executive summary
spite/ccapture.js falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 60.3 out of 100 and is rated Adequate, and both of its critical findings are security problems in the build pipeline.
Code Health, at 50.1, is the weakest lens and counts most in the score. The best first step is adding type checking, worth about 5.5 points. Adding tests for untested code comes next, worth about 4.8 points. Raising Code Health to 70 would lift the score to about 66.3.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 3,096 lines, about €5,200 to rebuild.
If Code Health rose from 50.1 to 70, the lowest score rated Strong, the score would rise from 60.3 to about 66.3.
Rebuild cost: about €5,200 · Estimate
| Cost to rebuild | €1,700 to €8,700, for 29 to 92 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,096 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 src | 2 src.CCapture | 3 src.FrameWrap | 4 src.GPUMotionBlur | 5 src.MotionBlur | 6 src.TimeWarp | 7 src.encoders.FrameEncoder | 8 src.third_party | 9 src.encoders.BatchEncoder | 10 src.encoders.GIFEncoder | 11 src.encoders.TarEncoder | 12 src.encoders.WebCodecsEncoder | 13 src.encoders.WebMEncoder | 14 src.encoders.GifskiEncoder | 15 src.encoders.ImageEncoder | 16 src.encoders.JPGEncoder | 17 src.encoders.PNGEncoder | 18 src.encoders.WebPEncoder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 src | ||||||||||||||||||
| 2 src.CCapture | ||||||||||||||||||
| 3 src.FrameWrap | ||||||||||||||||||
| 4 src.GPUMotionBlur | ||||||||||||||||||
| 5 src.MotionBlur | ||||||||||||||||||
| 6 src.TimeWarp | ||||||||||||||||||
| 7 src.encoders.FrameEncoder | ||||||||||||||||||
| 8 src.third_party | ||||||||||||||||||
| 9 src.encoders.BatchEncoder | 1 | |||||||||||||||||
| 10 src.encoders.GIFEncoder | 1 | |||||||||||||||||
| 11 src.encoders.TarEncoder | 1 | |||||||||||||||||
| 12 src.encoders.WebCodecsEncoder | 1 | |||||||||||||||||
| 13 src.encoders.WebMEncoder | 1 | |||||||||||||||||
| 14 src.encoders.GifskiEncoder | 1 | |||||||||||||||||
| 15 src.encoders.ImageEncoder | 1 | |||||||||||||||||
| 16 src.encoders.JPGEncoder | 1 | |||||||||||||||||
| 17 src.encoders.PNGEncoder | 1 | |||||||||||||||||
| 18 src.encoders.WebPEncoder | 1 |
9→7 src.encoders.BatchEncoder uses src.encoders.FrameEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.BatchEncoder uses a type in src.encoders.FrameEncoder.
- The types involved
src.encoders.BatchEncoder.BatchEncoder→src.encoders.FrameEncoder.FrameEncoder
- Direction
- src.encoders.BatchEncoder uses src.encoders.FrameEncoder, so a change to src.encoders.FrameEncoder can break src.encoders.BatchEncoder, while a change to src.encoders.BatchEncoder can't break src.encoders.FrameEncoder.
- Position
- Below the diagonal: src.encoders.BatchEncoder uses a module listed above it, which is the healthy direction.
10→7 src.encoders.GIFEncoder uses src.encoders.FrameEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.GIFEncoder uses a type in src.encoders.FrameEncoder.
- The types involved
src.encoders.GIFEncoder.GIFEncoder→src.encoders.FrameEncoder.FrameEncoder
- Direction
- src.encoders.GIFEncoder uses src.encoders.FrameEncoder, so a change to src.encoders.FrameEncoder can break src.encoders.GIFEncoder, while a change to src.encoders.GIFEncoder can't break src.encoders.FrameEncoder.
- Position
- Below the diagonal: src.encoders.GIFEncoder uses a module listed above it, which is the healthy direction.
11→7 src.encoders.TarEncoder uses src.encoders.FrameEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.TarEncoder uses a type in src.encoders.FrameEncoder.
- The types involved
src.encoders.TarEncoder.TarEncoder→src.encoders.FrameEncoder.FrameEncoder
- Direction
- src.encoders.TarEncoder uses src.encoders.FrameEncoder, so a change to src.encoders.FrameEncoder can break src.encoders.TarEncoder, while a change to src.encoders.TarEncoder can't break src.encoders.FrameEncoder.
- Position
- Below the diagonal: src.encoders.TarEncoder uses a module listed above it, which is the healthy direction.
12→7 src.encoders.WebCodecsEncoder uses src.encoders.FrameEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.WebCodecsEncoder uses a type in src.encoders.FrameEncoder.
- The types involved
src.encoders.WebCodecsEncoder.WebCodecsEncoder→src.encoders.FrameEncoder.FrameEncoder
- Direction
- src.encoders.WebCodecsEncoder uses src.encoders.FrameEncoder, so a change to src.encoders.FrameEncoder can break src.encoders.WebCodecsEncoder, while a change to src.encoders.WebCodecsEncoder can't break src.encoders.FrameEncoder.
- Position
- Below the diagonal: src.encoders.WebCodecsEncoder uses a module listed above it, which is the healthy direction.
13→7 src.encoders.WebMEncoder uses src.encoders.FrameEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.WebMEncoder uses a type in src.encoders.FrameEncoder.
- The types involved
src.encoders.WebMEncoder.WebMEncoder→src.encoders.FrameEncoder.FrameEncoder
- Direction
- src.encoders.WebMEncoder uses src.encoders.FrameEncoder, so a change to src.encoders.FrameEncoder can break src.encoders.WebMEncoder, while a change to src.encoders.WebMEncoder can't break src.encoders.FrameEncoder.
- Position
- Below the diagonal: src.encoders.WebMEncoder uses a module listed above it, which is the healthy direction.
14→9 src.encoders.GifskiEncoder uses src.encoders.BatchEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.GifskiEncoder uses a type in src.encoders.BatchEncoder.
- The types involved
src.encoders.GifskiEncoder.GifskiEncoder→src.encoders.BatchEncoder.BatchEncoder
- Direction
- src.encoders.GifskiEncoder uses src.encoders.BatchEncoder, so a change to src.encoders.BatchEncoder can break src.encoders.GifskiEncoder, while a change to src.encoders.GifskiEncoder can't break src.encoders.BatchEncoder.
- Position
- Below the diagonal: src.encoders.GifskiEncoder uses a module listed above it, which is the healthy direction.
15→11 src.encoders.ImageEncoder uses src.encoders.TarEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.ImageEncoder uses a type in src.encoders.TarEncoder.
- The types involved
src.encoders.ImageEncoder.ImageEncoder→src.encoders.TarEncoder.TarEncoder
- Direction
- src.encoders.ImageEncoder uses src.encoders.TarEncoder, so a change to src.encoders.TarEncoder can break src.encoders.ImageEncoder, while a change to src.encoders.ImageEncoder can't break src.encoders.TarEncoder.
- Position
- Below the diagonal: src.encoders.ImageEncoder uses a module listed above it, which is the healthy direction.
16→15 src.encoders.JPGEncoder uses src.encoders.ImageEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.JPGEncoder uses a type in src.encoders.ImageEncoder.
- The types involved
src.encoders.JPGEncoder.JPGEncoder→src.encoders.ImageEncoder.ImageEncoder
- Direction
- src.encoders.JPGEncoder uses src.encoders.ImageEncoder, so a change to src.encoders.ImageEncoder can break src.encoders.JPGEncoder, while a change to src.encoders.JPGEncoder can't break src.encoders.ImageEncoder.
- Position
- Below the diagonal: src.encoders.JPGEncoder uses a module listed above it, which is the healthy direction.
17→15 src.encoders.PNGEncoder uses src.encoders.ImageEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.PNGEncoder uses a type in src.encoders.ImageEncoder.
- The types involved
src.encoders.PNGEncoder.PNGEncoder→src.encoders.ImageEncoder.ImageEncoder
- Direction
- src.encoders.PNGEncoder uses src.encoders.ImageEncoder, so a change to src.encoders.ImageEncoder can break src.encoders.PNGEncoder, while a change to src.encoders.PNGEncoder can't break src.encoders.ImageEncoder.
- Position
- Below the diagonal: src.encoders.PNGEncoder uses a module listed above it, which is the healthy direction.
18→15 src.encoders.WebPEncoder uses src.encoders.ImageEncoder✕
- Connections
- 1 pair of types, where a type in src.encoders.WebPEncoder uses a type in src.encoders.ImageEncoder.
- The types involved
src.encoders.WebPEncoder.WebPEncoder→src.encoders.ImageEncoder.ImageEncoder
- Direction
- src.encoders.WebPEncoder uses src.encoders.ImageEncoder, so a change to src.encoders.ImageEncoder can break src.encoders.WebPEncoder, while a change to src.encoders.WebPEncoder can't break src.encoders.ImageEncoder.
- Position
- Below the diagonal: src.encoders.WebPEncoder uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 3 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 finding(s) in Type Safety; Resolve the 26 Low coverage finding(s) in Code Coverage — start with AudioTimeline.js, CCapture.js, FrameWrap.js; Swallowed exception (empty catch).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 finding(s) in Type Safety. | +5.5 pts | Medium | Type Safety |
| Resolve the 26 Low coverage finding(s) in Code Coverage — start with AudioTimeline.js, CCapture.js, FrameWrap.js. | +4.8 pts | Medium | Code Coverage |
| Swallowed exception (empty catch) | +3.5 pts | Medium | Exception handling |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +3.5 pts | Medium | Security & performance tooling |
| Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up. | +3.4 pts | Medium | Cancellation propagation |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.2 pts | Medium | Architecture documentation |
| Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with #configure (cognitive 50). | +2.2 pts | Medium | Cognitive Complexity |
| Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with WebCodecsEncoder.#configure (cyclomatic 29). | +1.3 pts | Medium | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/encoders/WebCodecsEncoder.js | 6.3 | Mixed | Cyclomatic Complexity: WebCodecsEncoder.#configure (cyclomatic 29) |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium vulnerability: REDACTED |
| src/AudioTimeline.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/AudioTimeline.js |
| src/CCapture.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/CCapture.js |
| src/FrameWrap.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/FrameWrap.js |
| src/GPUMotionBlur.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/GPUMotionBlur.js |
| src/MotionBlur.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/MotionBlur.js |
| src/createMotionBlur.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/createMotionBlur.js |
| src/encoders/BatchEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/BatchEncoder.js |
| src/encoders/FrameEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/FrameEncoder.js |
| src/encoders/GIFEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/GIFEncoder.js |
| src/encoders/GifskiEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/GifskiEncoder.js |
| src/encoders/ImageEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/ImageEncoder.js |
| src/encoders/JPGEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/JPGEncoder.js |
| src/encoders/PNGEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/PNGEncoder.js |
| src/encoders/TarEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/TarEncoder.js |
| src/encoders/WebMEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/WebMEncoder.js |
| src/encoders/WebPEncoder.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/encoders/WebPEncoder.js |
| src/index.js | 8.5 | Near-clean | Code Coverage: Low coverage: src/index.js |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 52 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 59 of 66 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D4 Code Duplication — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The language model for this repository listed its production source (.html) but exposed no token stream for any of it, so nothing reached the token comparison.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.ts, .js) and its test script runs a plain-node harness, which the reliability runner re-ran on its own: `node test/TimeWarp.test.js` in the repository root exited cleanly on 3 of 3 runs; `node test/FrameWrap.test.js` in the repository root exited cleanly on 3 of 3 runs; `node test/CCapture.test.js` in the repository root exited cleanly on 3 of 3 runs; `node test/WebCodecsEncoder.test.js` in the repository root exited cleanly on 3 of 3 runs; `node test/MotionBlur.test.js` in the repository root exited cleanly on 3 of 3 runs; `node test/Modular.test.js` in the repository root exited cleanly on 3 of 3 runs. The harness executes every test file inside its own process and starts none of them as a separate `node` process, so each run yields a single pass/fail for the whole suite — too coarse to tell which test is flaky. Not scored — this is a limit of what a one-process harness reports, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's 1 REDACTED manifest(s) and its 1 committed lockfile(s) WERE read; what went unanswered is the currency half, because it grades the production `dependencies` a lockfile resolves and these manifests declare none — only 3 devDependencies, which D12 does not grade. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: the lockfile was resolved, and no reader we could write would find a production dependency in it.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares no npm dependency a consumer installs, but 6 of the 31 code file(s) it ships carry a sign of vendored or bundled third-party code (for example `src/third_party/Tar.js` sits in a vendored-dependency directory; `src/third_party/download.js` sits in a vendored-dependency directory; `src/third_party/gifenc.mjs` sits in a vendored-dependency directory; `src/third_party/mp4-muxer.mjs` sits in a vendored-dependency directory; `src/third_party/webm-muxer.mjs` sits in a vendored-dependency directory). Code copied or bundled into a repository ships under its upstream licence, and this pass has no reader for it: it grades the licences of DECLARED packages only. So there is a licence to grade here and it was not graded — a missing collector, not a statement about this repository.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares no npm dependency a consumer installs, but 2 path(s) its REDACTED says it ships are not in the checkout (`build`, `build/ccapture.umd.min.js`) — they are built at publish time, and a bundler can inline `devDependencies` into them. What a package ships is not only what it declares: a devDependency bundled into build output ships under its own licence, and this pass has no reader for build output. So whether there is a licence to grade here was not established — a missing collector, not a statement about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (10 contributor(s) across 139 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 9 hold 1.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run serve`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> ccapture.js@2.0.0 serve / > node test/browser/serve.mjs / Serving <repo> / Test suite: http://localhost:8000/test/browser/ / Examples: http://localhost:8000/examples/ / On the same Wi-Fi (phone/tablet): / http://172.31.7.4:8000/test/browser/ / Open in Chrome / Firefox / Safari. Ctrl+C to stop." No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (serve). the dev server (`npm run serve`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> ccapture.js@2.0.0 serve / > node test/browser/serve.mjs / Serving <repo> / Test suite: http://localhost:8000/test/browser/ / Examples: http://localhost:8000/examples/ / On the same Wi-Fi (phone/tablet): / http://172.31.7.4:8000/test/browser/ / Open in Chrome / Firefox / Safari. Ctrl+C to stop." No runtime evidence was gathered.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 21 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WebCodecsEncoder.#configure at 29.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with WebCodecsEncoder.#configure (cyclomatic 29). — Refactoring it lifts Cyclomatic Complexity from 9.2 to about 10.0/10.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was #configure at 50.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with #configure (cognitive 50). — Refactoring it lifts Cognitive Complexity from 8.6 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 13 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 4.2% — 26 file(s) below 50%. Measured from the JavaScript/TypeScript suite (its `test` script (`node test/TimeWarp.test.js`) under node's V8 coverage via `npm ci --ignore-scripts` in the repository root).
What to do
- Resolve the 26 Low coverage finding(s) in Code Coverage — start with AudioTimeline.js, CCapture.js, FrameWrap.js. — One of this dimension's main actionable groups (26 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 60 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 0 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D24 · Comment Value
0 of 104 judged comments only repeat the code they sit on (0.0 %). 6 comment(s) in another language or script were not judged.
D27 · Navigability
20 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 2 high, 1 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 9 of the 21 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
AC6 · Visual & motion safety
- `.btn` moves (`transition: transform .12s ease, background .12s ease, border-color .12s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — index.html:43
- `.card` moves (`transition: transform .12s ease, border-color .12s ease, box-shadow .12s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — index.html:140
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:30
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
- Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
PF3 · Async & latency hygiene
R1 · Type Safety
- 2 typed · 31 plain JS — the untyped files are src/AudioTimeline.js, src/CCapture.js, src/FrameWrap.js, src/GPUMotionBlur.js, src/MotionBlur.js, src/TimeWarp.js (+25 more).
R10 · Code Duplication
- src/TimeWarp.js:139 · src/TimeWarp.js:153 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/TimeWarp.js:139
- src/CCapture.js:67 · src/FrameWrap.js:118 · src/encoders/FrameEncoder.js:38 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/CCapture.js:67
- src/GPUMotionBlur.js:115 · src/MotionBlur.js:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/GPUMotionBlur.js:115
- src/GPUMotionBlur.js:160 · src/GPUMotionBlur.js:180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/GPUMotionBlur.js:160
- src/encoders/BatchEncoder.js:44 · src/encoders/GIFEncoder.js:41 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/encoders/BatchEncoder.js:44
- src/encoders/WebCodecsEncoder.js:245 · src/encoders/WebCodecsEncoder.js:253 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/encoders/WebCodecsEncoder.js:245
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- #configure has cyclomatic complexity 29 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/encoders/WebCodecsEncoder.js:143
- main has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — test/browser/run.mjs:63
- blurCase has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — test/browser/cases.js:363
- #restore has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/TimeWarp.js:247
- constructor has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/encoders/WebCodecsEncoder.js:52
R3 · Large Files
- src/TimeWarp.js has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/TimeWarp.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. — src/umd.js:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as REDACTED scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `decodeToBuffer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/AudioTimeline.js:23
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X25 · Inert configuration knob
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — src/GPUMotionBlur.js:215, src/TimeWarp.js:326, src/createMotionBlur.js:45, …
- `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — src/TimeWarp.js:350
What to do
- Swallowed exception (empty catch)
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 50.1 | Adequate — gated by R1, X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100.0 | Exemplary | Strongest area. |
| Maturity | 63.3 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58.6 | Adequate — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 97.5 | Exemplary | Solid. |
| Accessibility | 82.6 | Strong | Solid. |
| Performance | 100.0 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run serve`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "> ccapture.js@2.0.0 serve / > node test/browser/serve.mjs / Serving <repo> / Test suite: http://localhost:8000/test/browser/ / Examples: http://localhost:8000/examples/ / On the same Wi-Fi (phone/tablet): / http://172.31.7.4:8000/test/browser/ / Open in Chrome / Firefox / Safari. Ctrl+C to stop." No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability not scored — the plain-node test harness runs every file in one process
- D12 Dependency Hygiene — Dependency currency not established — this repository declares no production dependency to grade
- D14 License Compliance — Vendored third-party code's licences not graded — D14 grades declared npm dependencies only
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (2413 LoC, 40 module-visible types across 19 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D4 Code Duplication — Duplication not measured — .html not exposed to the token comparison
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 12 claim(s) of kinds M4 does not check were not checked (path 1, command argument 3, install 1, setting 7); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 21 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 27 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: 21 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 2 finding(s)
- REDACTED
- REDACTED
Serious — 57 finding(s)
- Low coverage: src/AudioTimeline.js src/AudioTimeline.js:1
- Low coverage: src/CCapture.js src/CCapture.js:1
- Low coverage: src/FrameWrap.js src/FrameWrap.js:1
- Low coverage: src/GPUMotionBlur.js src/GPUMotionBlur.js:1
- Low coverage: src/MotionBlur.js src/MotionBlur.js:1
- Low coverage: src/createMotionBlur.js src/createMotionBlur.js:1
- Low coverage: src/encoders/BatchEncoder.js src/encoders/BatchEncoder.js:1
- Low coverage: src/encoders/FrameEncoder.js src/encoders/FrameEncoder.js:1
- Low coverage: src/encoders/GIFEncoder.js src/encoders/GIFEncoder.js:1
- Low coverage: src/encoders/GifskiEncoder.js src/encoders/GifskiEncoder.js:1
- Low coverage: src/encoders/ImageEncoder.js src/encoders/ImageEncoder.js:1
- Low coverage: src/encoders/JPGEncoder.js src/encoders/JPGEncoder.js:1
- Low coverage: src/encoders/PNGEncoder.js src/encoders/PNGEncoder.js:1
- Low coverage: src/encoders/TarEncoder.js src/encoders/TarEncoder.js:1
- Low coverage: src/encoders/WebCodecsEncoder.js src/encoders/WebCodecsEncoder.js:1
- Low coverage: src/encoders/WebMEncoder.js src/encoders/WebMEncoder.js:1
- Low coverage: src/encoders/WebPEncoder.js src/encoders/WebPEncoder.js:1
- Low coverage: src/index.js src/index.js:1
- Low coverage: src/third_party/Tar.js src/third_party/Tar.js:1
- Low coverage: src/third_party/download.js src/third_party/download.js:1
- Low coverage: src/third_party/gifenc.mjs src/third_party/gifenc.mjs:1
- Low coverage: src/third_party/mp4-muxer.mjs src/third_party/mp4-muxer.mjs:1
- Low coverage: src/third_party/webm-muxer.mjs src/third_party/webm-muxer.mjs:1
- Low coverage: src/third_party/webm-writer.js src/third_party/webm-writer.js:1
- Low coverage: src/umd.js src/umd.js:1
- Swallowed exception (empty catch) src/GPUMotionBlur.js:215
- Swallowed exception (empty catch) src/TimeWarp.js:326
- Swallowed exception (empty catch) src/createMotionBlur.js:45
- Swallowed exception (empty catch) src/encoders/WebCodecsEncoder.js:115
- Swallowed exception (empty catch) src/encoders/WebCodecsEncoder.js:191
- Swallowed exception (empty catch) src/encoders/WebCodecsEncoder.js:228
- Swallowed exception (empty catch) src/encoders/WebCodecsEncoder.js:388
- Animation without a prefers-reduced-motion guard index.html:43
- Animation without a prefers-reduced-motion guard index.html:140
- Duplicated block (7 lines × 2 locations) src/GPUMotionBlur.js:160
- Duplicated block (7 lines × 2 locations) src/encoders/BatchEncoder.js:44
- WebCodecsEncoder.#configure (cyclomatic 29) src/encoders/WebCodecsEncoder.js:143
- #configure (cognitive 50) src/encoders/WebCodecsEncoder.js:143
- REDACTED
- REDACTED
- REDACTED
- Type Safety
- Duplicated block (13 lines × 2 locations) src/TimeWarp.js:139
- Duplicated block (11 lines × 3 locations) src/CCapture.js:67
- Duplicated block (8 lines × 2 locations) src/GPUMotionBlur.js:115
- Duplicated block (6 lines × 2 locations) src/encoders/WebCodecsEncoder.js:245
- Complex function #configure (cyclomatic 29, cognitive 50) src/encoders/WebCodecsEncoder.js:143
- Complex function main (cyclomatic 12, cognitive 16) test/browser/run.mjs:63
- Complex function blurCase (cyclomatic 12, cognitive 14) test/browser/cases.js:363
- Complex function #restore (cyclomatic 12, cognitive 13) src/TimeWarp.js:247
- Complex function constructor (cyclomatic 11, cognitive 10) src/encoders/WebCodecsEncoder.js:52
- src/TimeWarp.js: 402 lines of code src/TimeWarp.js:1
- No test reaches this file src/umd.js:1
- No lint script
- Async function without AbortSignal: decodeToBuffer src/AudioTimeline.js:23
- Swallowed exception (caught, then discarded) src/TimeWarp.js:350
Minor — 6 finding(s)
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation REDACTED:30
- Changelog looks stale/thin
- Not all async functions that make a request accept an AbortSignal
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (the committed lockfile resolved no direct production dependency)
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-69b1de090d9e49af9535c5f28ce240c1/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-69b1de090d9e49af9535c5f28ce240c1/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |