Executive summary
webrtc/samples falls short of our standard for a template or a sample, in part because it has pages that don't say their language. It scores 48 out of 100 and is rated Adequate, and seven of its 75 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Accessibility, at 37, is the weakest lens and counts most in the score. The best first step is adding text alternatives, worth about 5 points. Adding type checking comes next, worth about 4 points. Raising Accessibility to 58 would lift the score to about 54.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and thirty-four form fields can't be read by a screen reader. Pinning each tool to an exact version, setting a waiting period for automatic updates and labelling the form fields would close these risks. The 14 pages that don't say their language need their language set.
The product code is 11,429 lines, about €11,000 to rebuild.
If Accessibility rose from 37 to 58, the lowest score rated Strong, the score would rise from 48 to about 54.
Fixed since the last survey: 217 findings
- Secrets (history) · High secret: WD-SECRET-0005 package-lock.json
- Code Duplication · Duplicated block (14 lines × 3 locations) src/content/peerconnection/negotiate-timing/js/main.js
- Code Duplication · Duplicated block (13 lines × 2 locations) src/content/insertable-streams/video-processing/js/video-mirror-helper.js
- Code Duplication · Duplicated block (12 lines × 2 locations) src/content/datachannel/basic/js/main.js
- Code Duplication · Duplicated block (11 lines × 2 locations) src/content/datachannel/datatransfer/js/main.js
- Code Duplication · Duplicated block (11 lines × 2 locations) src/content/datachannel/datatransfer/js/test.js
- Code Duplication · Duplicated block (11 lines × 3 locations) src/content/extensions/svc/js/main.js
- Code Duplication · Duplicated block (11 lines × 2 locations) src/content/insertable-streams/audio-processing/js/worker.js
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) src/content/insertable-streams/video-processing/js/canvas-transform.js
- Code Duplication · Duplicated block (11 lines × 3 locations) src/content/peerconnection/audio/js/main.js
- Code Duplication · Duplicated block (11 lines × 2 locations) src/content/peerconnection/dtmf/js/main.js
- Code Duplication · Duplicated block (11 lines × 2 locations) src/content/peerconnection/dtmf/js/main.js
- Code Duplication · Duplicated block (11 lines × 2 locations) src/content/peerconnection/munge-sdp/js/main.js
- Code Duplication · Duplicated block (10 lines × 2 locations) src/content/getusermedia/exposure/js/main.js
- Code Duplication · Duplicated block (10 lines × 4 locations) src/content/getusermedia/exposure/js/main.js
- Code Duplication · Duplicated block (10 lines × 2 locations) src/content/peerconnection/audio/js/main.js
- Code Duplication · Duplicated block (10 lines × 2 locations) src/content/peerconnection/audio/js/test.js
- Code Duplication · Duplicated block (10 lines × 2 locations) src/content/peerconnection/constraints/js/main.js
- Code Duplication · Duplicated block (10 lines × 2 locations) src/content/peerconnection/pr-answer/js/main.js
- Code Duplication · Duplicated block (9 lines × 2 locations) src/content/datachannel/channel/js/test.js
- Code Duplication · Duplicated block (9 lines × 2 locations) src/content/insertable-streams/endtoend-encryption/js/test.js
- Code Duplication · Duplicated block (9 lines × 2 locations) src/content/peerconnection/multiple/js/main.js
- Code Duplication · Duplicated block (9 lines × 2 locations) src/content/peerconnection/per-frame-callback/js/main.js
- Code Duplication · Duplicated block (8 lines × 2 locations) src/content/capture/canvas-pc/js/main.js
- Code Duplication · Duplicated block (8 lines × 3 locations) src/content/capture/video-pc/js/main.js
- Code Duplication · Duplicated block (8 lines × 2 locations) src/content/insertable-streams/video-processing/js/canvas-source.js
- Code Duplication · Duplicated block (8 lines × 3 locations) src/content/peerconnection/constraints/js/main.js
- Code Duplication · Duplicated block (8 lines × 4 locations) src/content/peerconnection/dtmf/js/test.js
- Code Duplication · Duplicated block (8 lines × 2 locations) src/content/peerconnection/pr-answer/js/main.js
- Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) src/content/capture/video-pc/js/main.js
- Code Duplication · Duplicated block (7 lines × 3 locations) src/content/datachannel/channel/js/test.js
- Code Duplication · Duplicated block (7 lines × 2 locations) src/content/datachannel/messaging/main.js
- Code Duplication · Duplicated block (7 lines × 4 locations) REDACTED
- Code Duplication · Duplicated block (7 lines × 3 locations) src/content/peerconnection/bandwidth/js/main.js
- Code Duplication · Duplicated block (7 lines × 2 locations) src/content/peerconnection/change-codecs/js/main.js
- Code Duplication · Duplicated block (7 lines × 2 locations) src/content/peerconnection/channel/js/test.js
- Code Duplication · Duplicated block (7 lines × 2 locations) src/content/peerconnection/states/js/test.js
- Code Duplication · Duplicated block (6 lines × 13 locations) src/content/capture/canvas-record/js/main.js
- Code Duplication · Duplicated block (6 lines × 2 locations) src/content/devices/multi/js/main.js
- Code Duplication · Duplicated block (6 lines × 2 locations) src/content/peerconnection/change-codecs/js/test.js
- Code Duplication · Duplicated block (6 lines × 2 locations) src/content/peerconnection/trickle-ice/js/test.js
- Code Duplication · Duplicated block (5 lines × 2 locations) src/content/datachannel/filetransfer/js/test.js
- Code Duplication · Duplicated block (5 lines × 2 locations) src/content/getusermedia/record/js/main.js
- Code Duplication · Duplicated block (5 lines × 2 locations) src/content/peerconnection/dtmf/js/main.js
- Code Duplication · Duplicated block (5 lines × 2 locations) src/content/peerconnection/negotiate-timing/js/test.js
- Text alternatives · <video> without a captions track src/content/capture/video-contenthint/index.html
- Text alternatives · <video> without a captions track src/content/capture/video-video/index.html
- Forms & labels · <select> without a programmatic label src/content/peerconnection/audio/index.html
- Forms & labels · <select> without a programmatic label src/content/peerconnection/audio/index.html
- Forms & labels · <label> that labels no control src/content/peerconnection/bandwidth/index.html
- Forms & labels · <select> without a programmatic label src/content/peerconnection/bandwidth/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/bandwidth/index.html
- Forms & labels · <select> without a programmatic label REDACTED
- Forms & labels · <label> that labels no control src/content/peerconnection/constraints/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/constraints/index.html
- Forms & labels · <label> that labels no control src/content/peerconnection/constraints/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/constraints/index.html
- Forms & labels · <label> that labels no control src/content/peerconnection/constraints/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/constraints/index.html
- Forms & labels · <label> that labels no control src/content/peerconnection/constraints/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/constraints/index.html
- Forms & labels · <label> that labels no control src/content/peerconnection/constraints/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/constraints/index.html
- Forms & labels · <label> that labels no control src/content/peerconnection/constraints/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/constraints/index.html
- Forms & labels · <label> that labels no control src/content/peerconnection/constraints/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/constraints/index.html
- Forms & labels · <textarea> without a programmatic label src/content/peerconnection/create-offer/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/dtmf/index.html
- Forms & labels · <textarea> without a programmatic label REDACTED
- Forms & labels · <textarea> without a programmatic label REDACTED
- Forms & labels · <input> without a programmatic label src/content/peerconnection/negotiate-timing/index.html
- Forms & labels · <select> without a programmatic label src/content/peerconnection/trickle-ice/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/trickle-ice/index.html
- Forms & labels · <input> without a programmatic label src/content/peerconnection/trickle-ice/index.html
- Page structure · Page without a main landmark REDACTED
- Page structure · Viewport restricts zoom REDACTED
- Page structure · <html> without a lang src/content/devices/input-output/index.html
- Page structure · Page without a main landmark src/content/devices/input-output/index.html
- Page structure · Viewport restricts zoom src/content/devices/input-output/index.html
- Page structure · <html> without a lang src/content/devices/multi/index.html
- Page structure · Page without a main landmark src/content/devices/multi/index.html
- Page structure · Viewport restricts zoom src/content/devices/multi/index.html
- Page structure · <html> without a lang src/content/extensions/multipleroutes/src/options.html
- Page structure · Document without a <title> src/content/extensions/multipleroutes/src/options.html
- Page structure · Page without a main landmark src/content/extensions/multipleroutes/src/options.html
- Page structure · <html> without a lang src/content/extensions/svc/index.html
- Page structure · Page without a main landmark src/content/extensions/svc/index.html
- Page structure · Viewport restricts zoom src/content/extensions/svc/index.html
- Page structure · <html> without a lang src/content/getusermedia/audio/index.html
- Page structure · Page without a main landmark src/content/getusermedia/audio/index.html
- Page structure · Viewport restricts zoom src/content/getusermedia/audio/index.html
- Page structure · <html> without a lang src/content/getusermedia/canvas/index.html
- Page structure · Page without a main landmark src/content/getusermedia/canvas/index.html
- Page structure · Viewport restricts zoom src/content/getusermedia/canvas/index.html
- Page structure · <html> without a lang src/content/getusermedia/exposure/index.html
- Page structure · Page without a main landmark src/content/getusermedia/exposure/index.html
- Page structure · Viewport restricts zoom src/content/getusermedia/exposure/index.html
- Page structure · <html> without a lang src/content/getusermedia/filter/index.html
- Page structure · Page without a main landmark src/content/getusermedia/filter/index.html
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,600 to €18,000, for 59 to 189 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.7 at a score of 48. 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: 11,429 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 — module dependency graph
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 | 32 | High / Critical |
Roadmap
Top priorities: Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +5.4 pts | Medium | Text alternatives |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +4.1 pts | Medium | Type Safety |
| 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. | +4.1 pts | Medium | Code Duplication |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +4.1 pts | Medium | Page structure |
| 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.0 pts | Medium | Security & performance tooling |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.7 pts | Medium | Forms & labels |
| 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. | +1.9 pts | Medium | Visual & motion safety |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +1.3 pts | Medium | Dead Code |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/content/insertable-streams/video-processing/js/main.js | 7.8 | Near-clean | Cyclomatic Complexity: main.initUI (cyclomatic 21) |
| src/content/peerconnection/constraints/js/main.js | 7.8 | Near-clean | Cyclomatic Complexity: main.showRemoteStats (cyclomatic 18) |
| test/interop/connection.test.js | 7.8 | Near-clean | Test Quality: No assertions: establishes a connection |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/content/getusermedia/exposure/js/main.js | 8.5 | Near-clean | Cognitive Complexity: loadProperties (cognitive 19) |
| src/content/extensions/svc/js/main.js | 8.5 | Near-clean | Cognitive Complexity: main.start (cognitive 17) |
| REDACTED | 9.0 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| src/content/insertable-streams/video-processing/js/webgl-transform.js | 9.3 | Near-clean | Comment Value: redundant comment |
| src/content/insertable-streams/webgpu/js/multi_video_main.js | 9.3 | Near-clean | Comment Value: redundant comment |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
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 51 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 — 51 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, 303 of 312 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
- 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 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository commits none — a package.json states version RANGES, and a range names no particular release to be behind. 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: no lockfile reader we could write would find anything here to read, so there is no capability behind this row to build.
- 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. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — 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 source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D26 Project Cohesion — 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. `(repository root)` (11429 LoC, 88 module-visible types across 56 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- 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.
- AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
- AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 137 further occurrence(s) are not listed individually; the score already reflects all 177.
- 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 start`) 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: "[Sun Nov 15 2026 05:06:43 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:46 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:50 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:53 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:56 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:59 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0"" 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 (start). the dev server (`npm run start`) 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: "[Sun Nov 15 2026 05:06:43 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:46 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:50 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:53 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:56 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:59 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0"" 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 no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- 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 and Rust 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.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- 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.
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was peer.peer at 23.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with peer.peer (cyclomatic 23), main.initUI (cyclomatic 21), main.showRemoteStats (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was main.showRemoteStats at 20.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with main.showRemoteStats (cognitive 20), loadProperties (cognitive 19), peer::onmessage (cognitive 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 11,429) are in a reported copy.
D5 · Coupling
2 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them, and main-sequence distance (abstractness) is not computed for these modules yet.
D6 · Cohesion (LCOM4)
0 of 15 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with connection.test.js. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with connection.test.js. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm install --ignore-scripts` (no lockfile) in the repository root (36 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/content/datachannel/basic/js/main.js. Counted over 54 of the 103 production source files in this repository: 43 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D21 · Naming Consistency
1 naming inconsistencies among 25 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `establishPC` spells `PC` where 24 names in the project spell it `Pc` finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
6 of 259 judged comments only repeat the code they sit on (2.3 %). 5 comment(s) in another language or script were not judged.
What to do
- Resolve the 6 redundant comment finding(s) in Comment Value — start with webgl-transform.js (2), multi_video_main.js (2), REDACTED (2). — One of this dimension's main actionable groups (6 recommendation-level).
D27 · Navigability
48 % 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)
32 finding(s): 0 critical, 7 high, 3 medium, 22 low. 6 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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
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 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
27 of 60 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/content/extensions/svc/js/main.js. Counted over 60 of the 103 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (17), multi_video_main.js, canvas-source.js. — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×17) — REDACTED:39, REDACTED:39, src/content/capture/canvas-video/index.html:39, …
- Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way). (×2) — REDACTED:39, src/content/devices/multi/index.html:62
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — REDACTED:49, REDACTED:48
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×32) — REDACTED:54, REDACTED:53, REDACTED:54, …
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×6) — src/content/devices/multi/index.html:46, src/content/devices/multi/index.html:53, src/content/devices/multi/index.html:68, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×14) — REDACTED:9, src/content/capture/canvas-filter/index.html:9, REDACTED:9, …
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×13) — REDACTED:9, src/content/capture/canvas-filter/index.html:9, REDACTED:9, …
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×13) — REDACTED:14, src/content/capture/canvas-filter/index.html:14, REDACTED:14, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `button` sets color: white on background-color: #d84a38 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/css/main.css:43
- `.file-upload` sets color: white on background-color: #d84a38 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/content/getusermedia/record/css/main.css:16
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
AX8 · Test isolation
- `src/content` (production) references the test project `test`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `hangup` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — src/content/datachannel/channel/js/main.js:75, src/content/peerconnection/channel/js/main.js:72
- `handleFileInputChange` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/content/datachannel/filetransfer/js/main.js:43
- `init` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×4) — src/content/insertable-streams/audio-processing/js/main.js:57, src/content/insertable-streams/video-processing/js/canvas-transform.js:31, src/content/insertable-streams/video-processing/js/webcodec-transform.js:23, …
- `stop` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/content/insertable-streams/audio-processing/js/main.js:99
- `transform` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×5) — src/content/insertable-streams/video-processing/js/canvas-transform.js:46, src/content/insertable-streams/video-processing/js/simple-transforms.js:19, src/content/insertable-streams/video-processing/js/simple-transforms.js:34, …
- `setMediaStream` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/content/insertable-streams/video-processing/js/video-sink.js:32
- `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/content/peerconnection/dtmf/js/main.js:41
- `swapOnBoth` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:98
- `noAction` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/js/videopipe.js:36
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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.
M3 · Folder & project structure
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
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 2 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:3
- `package.json` 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`. — package.json:29
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.
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 107 plain JS — the untyped files are src/content/capture/canvas-filter/js/main.js, src/content/capture/canvas-pc/js/main.js, src/content/capture/canvas-record/js/main.js, src/content/capture/canvas-video/js/main.js, src/content/capture/video-contenthint/js/main.js, src/content/capture/video-pc/js/main.js (+101 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- 35 duplicated blocks under src/content/peerconnection/ have copies in at least two of the sibling directories always-negotiate-datachannels, audio, bandwidth, change-codecs, constraints, create-offer (+12 more sibling(s) not listed) — 31 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 35 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 35 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 35 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/content/peerconnection/audio/js/main.js:12
- 29 duplicated blocks under src/content/ have copies in at least two of the sibling directories capture, datachannel, devices, extensions, getusermedia, insertable-streams (+1 more sibling(s) not listed) — 24 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 29 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 29 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 29 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/content/extensions/svc/js/main.js:11
- src/content/extensions/svc/js/main.js:11 · src/content/peerconnection/change-codecs/js/main.js:11 — the two spans are one implementation copied and then locally edited — 1324 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/extensions/svc/js/main.js:11
- src/content/insertable-streams/video-analyzer/js/main.js:55 · src/content/peerconnection/pc1/js/main.js:36 — the two spans are one implementation copied and then locally edited — 913 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/insertable-streams/video-analyzer/js/main.js:55
- src/content/peerconnection/audio/js/main.js:12 · src/content/peerconnection/bandwidth/js/main.js:14 — the two spans are one implementation copied and then locally edited — 668 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/peerconnection/audio/js/main.js:12
- src/content/datachannel/channel/js/main.js:25 · src/content/peerconnection/channel/js/main.js:27 — the two spans are one implementation copied and then locally edited — 437 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/datachannel/channel/js/main.js:25
- src/content/capture/canvas-pc/js/main.js:43 · src/content/capture/video-pc/js/main.js:67 — the two spans are one implementation copied and then locally edited — 647 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/capture/canvas-pc/js/main.js:43
- src/content/peerconnection/bandwidth/js/main.js:60 · src/content/peerconnection/per-frame-callback/js/main.js:96 — the two spans are one implementation copied and then locally edited — 462 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/peerconnection/bandwidth/js/main.js:60
- src/content/peerconnection/restart-ice/js/main.js:93 · src/content/peerconnection/webaudio-output/js/main.js:79 — the two spans are one implementation copied and then locally edited — 500 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/peerconnection/restart-ice/js/main.js:93
- src/content/datachannel/basic/js/main.js:82 · src/content/datachannel/channel/js/main.js:80 — the two spans are one implementation copied and then locally edited — 229 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/datachannel/basic/js/main.js:82
- src/content/extensions/svc/js/main.js:219 · src/content/insertable-streams/video-analyzer/js/main.js:115 · src/content/peerconnection/pc1/js/main.js:99 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/content/extensions/svc/js/main.js:219
- src/content/extensions/svc/js/main.js:359 · src/content/peerconnection/bandwidth/js/main.js:269 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/content/extensions/svc/js/main.js:359
- src/content/peerconnection/negotiate-timing/js/main.js:41 · src/content/peerconnection/upgrade/js/main.js:25 — the two spans are one implementation copied and then locally edited — 276 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/peerconnection/negotiate-timing/js/main.js:41
- src/content/peerconnection/restart-ice/js/main.js:51 · src/content/peerconnection/webaudio-output/js/main.js:45 — 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/content/peerconnection/restart-ice/js/main.js:51
- src/content/peerconnection/restart-ice/js/main.js:121 · src/content/peerconnection/upgrade/js/main.js:99 · src/content/peerconnection/webaudio-output/js/main.js:102 — 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/content/peerconnection/restart-ice/js/main.js:121
- src/content/getusermedia/exposure/js/main.js:79 · src/content/getusermedia/pan-tilt-zoom/js/main.js:51 — 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/content/getusermedia/exposure/js/main.js:79
- src/content/capture/video-pc/js/main.js:77 · src/content/peerconnection/upgrade/js/main.js:89 · src/content/peerconnection/webaudio-output/js/main.js:92 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/content/capture/video-pc/js/main.js:77
- src/content/datachannel/basic/js/test.js:11 · src/content/datachannel/datatransfer/js/test.js:14 — 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/content/datachannel/basic/js/test.js:11
- src/content/peerconnection/bandwidth/js/main.js:166 · src/content/peerconnection/per-frame-callback/js/main.js:187 — 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/content/peerconnection/bandwidth/js/main.js:166
- src/content/peerconnection/upgrade/js/main.js:150 · src/content/peerconnection/webaudio-output/js/main.js:154 — 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/content/peerconnection/upgrade/js/main.js:150
- src/content/peerconnection/restart-ice/js/test.js:14 · src/content/peerconnection/upgrade/js/test.js:14 — 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/content/peerconnection/restart-ice/js/test.js:14
- src/content/extensions/svc/js/main.js:180 · src/content/peerconnection/pc1/js/main.js:71 — 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/content/extensions/svc/js/main.js:180
- src/content/insertable-streams/endtoend-encryption/js/test.js:14 · src/content/peerconnection/multiple/js/test.js:14 · src/content/peerconnection/negotiate-timing/js/test.js:14 · src/content/peerconnection/pc1/js/test.js:14 · +3 more site(s) not listed — the 7 copies are spread across 7 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/content/insertable-streams/endtoend-encryption/js/test.js:14
- src/content/peerconnection/munge-sdp/js/main.js:116 · src/content/peerconnection/munge-sdp/js/main.js:172 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/peerconnection/munge-sdp/js/main.js:116
- src/content/peerconnection/restart-ice/js/main.js:11 · src/content/peerconnection/upgrade/js/main.js:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/content/peerconnection/restart-ice/js/main.js:11
- src/content/peerconnection/audio/js/main.js:211 · src/content/peerconnection/states/js/main.js:189 · src/content/peerconnection/webaudio-input/js/main.js:99 — 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/content/peerconnection/audio/js/main.js:211
- src/content/capture/canvas-filter/js/main.js:11 · src/content/capture/worker-process/js/main.js:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/content/capture/canvas-filter/js/main.js:11
- src/content/peerconnection/change-codecs/js/main.js:177 · src/content/peerconnection/pc1/js/main.js:157 — 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/content/peerconnection/change-codecs/js/main.js:177
- src/content/peerconnection/change-codecs/js/test.js:43 · src/content/peerconnection/negotiate-timing/js/test.js:37 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/content/peerconnection/change-codecs/js/test.js:43
- src/content/datachannel/filetransfer/js/test.js:11 · src/content/devices/input-output/js/test.js:9 · src/content/getusermedia/gum/js/test.js:11 · src/content/insertable-streams/endtoend-encryption/js/test.js:11 · +8 more site(s) not listed — the 12 copies are spread across 12 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 12 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/content/datachannel/filetransfer/js/test.js:11
- src/content/insertable-streams/video-processing/js/video-mirror-helper.js:60 · src/content/insertable-streams/video-processing/js/video-sink.js:34 — the two spans are one implementation copied and then locally edited — 80 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/insertable-streams/video-processing/js/video-mirror-helper.js:60
- src/content/peerconnection/pc1/js/main.js:142 · src/content/peerconnection/restart-ice/js/main.js:148 — 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/content/peerconnection/pc1/js/main.js:142
- src/content/peerconnection/states/js/main.js:137 · src/content/peerconnection/states/js/main.js:155 — 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/content/peerconnection/states/js/main.js:137
- src/content/datachannel/basic/js/test.js:8 · src/content/datachannel/datatransfer/js/test.js:11 · src/content/datachannel/filetransfer/js/test.js:11 · src/content/devices/input-output/js/test.js:9 · +13 more site(s) not listed — the 17 copies are spread across 17 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 17 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/content/datachannel/basic/js/test.js:8
- src/content/datachannel/channel/js/test.js:14 · src/content/peerconnection/channel/js/test.js:14 — 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/content/datachannel/channel/js/test.js:14
- src/content/datachannel/filetransfer/js/test.js:14 · src/content/getusermedia/gum/js/test.js:14 · src/content/insertable-streams/endtoend-encryption/js/test.js:14 · src/content/peerconnection/audio/js/test.js:13 · +7 more site(s) not listed — the 11 copies are spread across 11 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/content/datachannel/filetransfer/js/test.js:14
- src/content/getusermedia/canvas/js/main.js:21 · src/content/getusermedia/filter/js/main.js:26 — 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/content/getusermedia/canvas/js/main.js:21
- src/content/insertable-streams/video-processing/js/camera-source.js:18 · src/content/insertable-streams/video-processing/js/peer-connection-source.js:28 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/content/insertable-streams/video-processing/js/camera-source.js:18
- src/content/peerconnection/multiple/js/main.js:58 · src/content/peerconnection/munge-sdp/js/main.js:70 — 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/content/peerconnection/multiple/js/main.js:58
- src/content/peerconnection/munge-sdp/js/main.js:67 · src/content/peerconnection/states/js/main.js:56 — 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/content/peerconnection/munge-sdp/js/main.js:67
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
- onmessage has cyclomatic complexity 15 and cognitive complexity 19; 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. — REDACTED:84
- start has cyclomatic complexity 14 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 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/content/devices/input-output/js/main.js:117
- buildDriver has cyclomatic complexity 13 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/webdriver.js:50
- animate 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/content/insertable-streams/video-processing/js/canvas-source.js:103
- showRemoteStats has cyclomatic complexity 11 and cognitive complexity 11; 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/content/peerconnection/constraints/js/main.js:202
R3 · Large Files
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json 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 type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 78 application, 2 tooling and 5 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `npm test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
- no import path from any entry point (78 application, 2 tooling, 5 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×24) — src/content/insertable-streams/endtoend-encryption/js/worker.js, src/content/datachannel/channel/js/test.js, src/content/insertable-streams/endtoend-encryption/js/test.js, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
S1 · Web-Security Posture
- `https://webrtc.github.io/adapter/adapter-latest.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 50 such include(s) across the repository's markup. — REDACTED:77
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- ``Invalid value for MB to send: ${number}`` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/datachannel/datatransfer/js/main.js:42
- `chrome.i18n.getMessage(msg)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/extensions/multipleroutes/src/options.js:67
- `mode` is text this program did not author, and it is written into a quoted attribute value through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/getusermedia/exposure/js/main.js:53
- `msg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — src/content/getusermedia/exposure/js/main.js:93, src/content/getusermedia/getdisplaymedia/js/main.js:44, src/content/getusermedia/gum/js/main.js:38, …
- ``Exception while creating MediaRecorder: ${JSON.stringify(e)}`` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/getusermedia/record/js/main.js:140
- ``Source error: ${e.toString()}`` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/getusermedia/record/js/main.js:187
- `statsString` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/content/peerconnection/constraints/js/main.js:204, src/content/peerconnection/constraints/js/main.js:260
- `bitrate` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:221
- `remoteCandidate.address` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:248
- `remoteCandidate.ip` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:250
- `remoteCandidate.ipAddress` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:253
- `width` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:282
- `rWidth` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:287
- `report.id` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:299
- `report.timestamp` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/constraints/js/main.js:300
- `key` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/content/peerconnection/constraints/js/main.js:304, src/content/peerconnection/constraints/js/main.js:306
- `error` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/content/peerconnection/webaudio-input/js/main.js:136
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X3 · Exception handling
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| 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 | 41% | Weak — gated by R1, R10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 77% | Exemplary | Solid. |
| Readiness | 57% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 78% | Strong | Solid. |
| Accessibility | 37% | Weak — gated by AC1, AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 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.
- P12 CI test-gate honesty — 1 observation(s) recorded · 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'.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 70 check(s) not relevant to this codebase
- 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 — not applicable — JavaScript has no interface declaration, so there is no declared member list whose width this check could measure
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 start`) 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: "[Sun Nov 15 2026 05:06:43 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:46 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:50 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:53 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:56 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0" / [Sun Nov 15 2026 05:06:59 GMT+0000 (Coordinated Universal Time)] "GET /" "curl/8.5.0"" 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.
- D12 Dependency Hygiene — Dependency currency not established — this repository commits no lockfile to resolve
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
- 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 — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- 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 — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- 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
- 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
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (FAIL src/content/datachannel/channel/js/test.js), so the coverage report describes the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- 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
- M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
- M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (command argument 1); M4 checks only links and versions and artefact counts.
- P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 103 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 not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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 package.json, 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.
- R4 Test Coverage — 5 test file(s) reach none of 102 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- 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
- X18 Disposal-pattern correctness — 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
- X2 Cancellation propagation — 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
- 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.
- 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
- X25 Inert configuration knob — 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
- X29 Per-element action decided by a fixed element — 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 — 75 finding(s)
- <input> without a programmatic label REDACTED:54
- <input> without a programmatic label src/content/getusermedia/exposure/index.html:56
- <input> without a programmatic label src/content/getusermedia/exposure/index.html:61
- <input> without a programmatic label src/content/getusermedia/exposure/index.html:66
- <input> without a programmatic label src/content/getusermedia/pan-tilt-zoom/index.html:50
- <input> without a programmatic label src/content/getusermedia/pan-tilt-zoom/index.html:54
- <input> without a programmatic label src/content/getusermedia/pan-tilt-zoom/index.html:58
- <input> without a programmatic label REDACTED:60
- <input> without a programmatic label REDACTED:103
- <input> without a programmatic label REDACTED:105
- <input> without a programmatic label REDACTED:106
- <input> without a programmatic label REDACTED:107
- <input> without a programmatic label src/content/insertable-streams/endtoend-encryption/index.html:47
- <input> without a programmatic label src/content/insertable-streams/endtoend-encryption/index.html:48
- <input> without a programmatic label src/content/insertable-streams/endtoend-encryption/index.html:54
- <input> without a programmatic label src/content/insertable-streams/video-processing/index.html:56
- <select> without a programmatic label src/content/devices/multi/index.html:47
- <select> without a programmatic label src/content/devices/multi/index.html:54
- <select> without a programmatic label src/content/devices/multi/index.html:69
- <select> without a programmatic label src/content/devices/multi/index.html:79
- <select> without a programmatic label src/content/extensions/svc/index.html:54
- <select> without a programmatic label src/content/extensions/svc/index.html:59
- <select> without a programmatic label src/content/getusermedia/exposure/index.html:50
- <select> without a programmatic label src/content/getusermedia/exposure/index.html:71
- <select> without a programmatic label src/content/getusermedia/getdisplaymedia/index.html:40
- <select> without a programmatic label REDACTED:56
- <select> without a programmatic label src/content/insertable-streams/video-processing/index.html:49
- <select> without a programmatic label src/content/insertable-streams/video-processing/index.html:60
- <select> without a programmatic label src/content/insertable-streams/video-processing/index.html:71
- <select> without a programmatic label src/content/insertable-streams/webgpu/index.html:49
- <html> without a lang REDACTED:9
- <html> without a lang src/content/capture/canvas-filter/index.html:9
- <html> without a lang REDACTED:9
- <html> without a lang REDACTED:9
- <html> without a lang src/content/capture/canvas-video/index.html:9
- <html> without a lang src/content/capture/video-contenthint/index.html:9
- <html> without a lang REDACTED:9
- <html> without a lang src/content/capture/video-video/index.html:9
- <html> without a lang src/content/capture/worker-process/index.html:9
- <html> without a lang REDACTED:9
- <html> without a lang REDACTED:9
- <html> without a lang REDACTED:9
- <html> without a lang REDACTED:9
- <html> without a lang REDACTED:9
- Viewport restricts zoom REDACTED:14
- Viewport restricts zoom src/content/capture/canvas-filter/index.html:14
- Viewport restricts zoom REDACTED:14
- Viewport restricts zoom REDACTED:14
- Viewport restricts zoom src/content/capture/canvas-video/index.html:14
- Viewport restricts zoom src/content/capture/video-contenthint/index.html:14
- Viewport restricts zoom REDACTED:14
- Viewport restricts zoom src/content/capture/video-video/index.html:14
- Viewport restricts zoom src/content/capture/worker-process/index.html:14
- Viewport restricts zoom REDACTED:14
- Viewport restricts zoom REDACTED:14
- Viewport restricts zoom REDACTED:14
- Viewport restricts zoom REDACTED:14
- <label> that labels no control src/content/devices/multi/index.html:46
- <label> that labels no control src/content/devices/multi/index.html:53
- <label> that labels no control src/content/devices/multi/index.html:68
- <label> that labels no control src/content/devices/multi/index.html:78
- <label> that labels no control src/content/extensions/multipleroutes/src/options.html:41
- <label> that labels no control REDACTED:102
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <textarea> without a programmatic label REDACTED:49
- <textarea> without a programmatic label REDACTED:54
- <textarea> without a programmatic label REDACTED:48
- <textarea> without a programmatic label REDACTED:53
- Production project references a test project: src/content → test
- REDACTED
Serious — 162 finding(s)
- Untrusted text written into markup unescaped src/content/datachannel/datatransfer/js/main.js:42
- Untrusted text written into markup unescaped src/content/extensions/multipleroutes/src/options.js:67
- Untrusted text written into markup unescaped src/content/getusermedia/exposure/js/main.js:53
- Untrusted text written into markup unescaped src/content/getusermedia/exposure/js/main.js:93
- Untrusted text written into markup unescaped src/content/getusermedia/getdisplaymedia/js/main.js:44
- Untrusted text written into markup unescaped src/content/getusermedia/gum/js/main.js:38
- Untrusted text written into markup unescaped src/content/getusermedia/pan-tilt-zoom/js/main.js:65
- Untrusted text written into markup unescaped src/content/getusermedia/record/js/main.js:140
- Untrusted text written into markup unescaped src/content/getusermedia/record/js/main.js:187
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:204
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:221
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:248
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:250
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:253
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:260
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:282
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:287
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:299
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:300
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:304
- Untrusted text written into markup unescaped src/content/peerconnection/constraints/js/main.js:306
- Untrusted text written into markup unescaped src/content/peerconnection/webaudio-input/js/main.js:136
- <canvas> without a text alternative REDACTED:39
- <canvas> without a text alternative REDACTED:39
- <canvas> without a text alternative src/content/capture/canvas-video/index.html:39
- <canvas> without a text alternative src/content/extensions/svc/index.html:67
- <canvas> without a text alternative src/content/extensions/svc/index.html:71
- <canvas> without a text alternative src/content/getusermedia/canvas/index.html:40
- <canvas> without a text alternative src/content/getusermedia/filter/index.html:86
- <canvas> without a text alternative src/content/peerconnection/audio/index.html:68
- <canvas> without a text alternative src/content/peerconnection/audio/index.html:72
- <canvas> without a text alternative src/content/peerconnection/audio/index.html:76
- <canvas> without a text alternative src/content/peerconnection/bandwidth/index.html:61
- <canvas> without a text alternative src/content/peerconnection/bandwidth/index.html:65
- <canvas> without a text alternative src/content/peerconnection/per-frame-callback/index.html:53
- <canvas> without a text alternative src/content/peerconnection/per-frame-callback/index.html:57
- <canvas> without a text alternative src/content/peerconnection/per-frame-callback/index.html:62
- <canvas> without a text alternative src/content/peerconnection/per-frame-callback/index.html:66
- <canvas> without a text alternative REDACTED:42
- Fake-async — async method never awaits src/content/datachannel/channel/js/main.js:75
- Fake-async — async method never awaits src/content/datachannel/filetransfer/js/main.js:43
- Fake-async — async method never awaits src/content/insertable-streams/audio-processing/js/main.js:57
- Fake-async — async method never awaits src/content/insertable-streams/audio-processing/js/main.js:99
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/canvas-transform.js:31
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/canvas-transform.js:46
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/simple-transforms.js:19
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/simple-transforms.js:34
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/video-sink.js:32
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/webcodec-transform.js:23
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/webcodec-transform.js:38
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/webgl-transform.js:32
- Fake-async — async method never awaits src/content/insertable-streams/video-processing/js/webgl-transform.js:153
- Fake-async — async method never awaits src/content/peerconnection/channel/js/main.js:72
- Fake-async — async method never awaits src/content/peerconnection/dtmf/js/main.js:41
- Fake-async — async method never awaits REDACTED:98
- Page without a main landmark REDACTED:9
- Page without a main landmark src/content/capture/canvas-filter/index.html:9
- Page without a main landmark REDACTED:9
- Page without a main landmark REDACTED:9
- Page without a main landmark src/content/capture/canvas-video/index.html:9
- Page without a main landmark src/content/capture/video-contenthint/index.html:9
- Page without a main landmark REDACTED:9
- Page without a main landmark src/content/capture/video-video/index.html:9
- Page without a main landmark src/content/capture/worker-process/index.html:9
- Page without a main landmark REDACTED:9
- Page without a main landmark REDACTED:9
- Page without a main landmark REDACTED:9
- Page without a main landmark REDACTED:9
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (25 lines × 2 locations) src/content/datachannel/basic/js/test.js:11
- Duplicated block (25 lines × 2 locations) src/content/peerconnection/bandwidth/js/main.js:166
- Duplicated block (25 lines × 2 locations) src/content/peerconnection/upgrade/js/main.js:150
- Duplicated block (18 lines × 2 locations) src/content/capture/canvas-filter/js/main.js:11
- Duplicated block (18 lines × 2 locations) src/content/peerconnection/change-codecs/js/main.js:177
- Duplicated block (18 lines × 2 locations) src/content/peerconnection/change-codecs/js/test.js:43
- Duplicated block (14 lines × 2 locations) src/content/getusermedia/canvas/js/main.js:21
- Duplicated block (14 lines × 2 locations) src/content/peerconnection/multiple/js/main.js:58
- Duplicated block (14 lines × 2 locations) src/content/peerconnection/munge-sdp/js/main.js:67
- Dead file (~68 LoC) src/content/peerconnection/channel/js/test.js
- Dead file (~68 LoC) src/content/peerconnection/multiple/js/test.js
- Dead file (~68 LoC) src/content/peerconnection/negotiate-timing/js/test.js
- <video> without a captions track REDACTED:39
- <video> without a captions track src/content/devices/multi/index.html:62
- Low contrast colour pair in CSS (4.2:1) src/css/main.css:43
- Low contrast colour pair in CSS (4.2:1) src/content/getusermedia/record/css/main.css:16
- REDACTED
- REDACTED
- Duplicated block (16 lines × 2 locations) src/content/peerconnection/pc1/js/main.js:142
- Duplicated block (16 lines × 2 locations) src/content/peerconnection/states/js/main.js:137
- Dead file (~62 LoC) src/content/peerconnection/munge-sdp/js/test.js
- Dead file (~62 LoC) src/content/peerconnection/trickle-ice/js/test.js
- Dead file (~56 LoC) src/content/datachannel/datatransfer/js/test.js
- Dead file (~56 LoC) src/content/getusermedia/resolution/js/test.js
- peer.peer (cyclomatic 23) REDACTED:18
- main.initUI (cyclomatic 21) src/content/insertable-streams/video-processing/js/main.js:135
- main.showRemoteStats (cyclomatic 18) src/content/peerconnection/constraints/js/main.js:202
- No assertions: establishes a connection test/interop/connection.test.js:38
- Test project verifies nothing: the repository root test/interop/connection.test.js:38
- main.showRemoteStats (cognitive 20) src/content/peerconnection/constraints/js/main.js:202
- loadProperties (cognitive 19) src/content/getusermedia/exposure/js/main.js:31
- peer::onmessage (cognitive 19) REDACTED:84
- main.start (cognitive 17) src/content/extensions/svc/js/main.js:105
- FunctionTooLong: main.initUI src/content/insertable-streams/video-processing/js/main.js:135
- Coverage not measured — JavaScript/TypeScript suite
- Tests run only outside the merge gate REDACTED:22
- Type Safety
- Duplication concentrated across 18 sibling directories (35 clone groups) src/content/peerconnection/audio/js/main.js:12
- Duplication concentrated across 7 sibling directories (29 clone groups) src/content/extensions/svc/js/main.js:11
- Duplicated block with local edits (191 matched lines × 2 locations) src/content/extensions/svc/js/main.js:11
- Duplicated block with local edits (146 matched lines × 2 locations) src/content/insertable-streams/video-analyzer/js/main.js:55
- Duplicated block with local edits (129 matched lines × 2 locations) src/content/peerconnection/audio/js/main.js:12
- Duplicated block with local edits (93 matched lines × 2 locations) src/content/datachannel/channel/js/main.js:25
- Duplicated block with local edits (86 matched lines × 2 locations) src/content/capture/canvas-pc/js/main.js:43
- Duplicated block with local edits (75 matched lines × 2 locations) src/content/peerconnection/bandwidth/js/main.js:60
- Duplicated block with local edits (63 matched lines × 2 locations) src/content/peerconnection/restart-ice/js/main.js:93
- Duplicated block with local edits (46 matched lines × 2 locations) src/content/datachannel/basic/js/main.js:82
- Duplicated block (46 lines × 3 locations) src/content/extensions/svc/js/main.js:219
- Duplicated block (46 lines × 2 locations) src/content/extensions/svc/js/main.js:359
- Duplicated block with local edits (40 matched lines × 2 locations) src/content/peerconnection/negotiate-timing/js/main.js:41
- Duplicated block (34 lines × 2 locations) src/content/peerconnection/restart-ice/js/main.js:51
- Duplicated block (30 lines × 3 locations) src/content/peerconnection/restart-ice/js/main.js:121
- Duplicated block (27 lines × 2 locations) src/content/getusermedia/exposure/js/main.js:79
- Duplicated block (25 lines × 3 locations) src/content/capture/video-pc/js/main.js:77
- Duplicated block (24 lines × 2 locations) src/content/peerconnection/restart-ice/js/test.js:14
- Duplicated block (23 lines × 2 locations) src/content/extensions/svc/js/main.js:180
- Duplicated block (20 lines × 7 locations) src/content/insertable-streams/endtoend-encryption/js/test.js:14
- Duplicated block with local edits (20 matched lines × 2 locations) src/content/peerconnection/munge-sdp/js/main.js:116
- Duplicated block (20 lines × 2 locations) src/content/peerconnection/restart-ice/js/main.js:11
- Duplicated block (19 lines × 3 locations) src/content/peerconnection/audio/js/main.js:211
- Duplicated block (17 lines × 12 locations) src/content/datachannel/filetransfer/js/test.js:11
- Duplicated block with local edits (16 matched lines × 2 locations) src/content/insertable-streams/video-processing/js/video-mirror-helper.js:60
- Duplicated block (15 lines × 17 locations) src/content/datachannel/basic/js/test.js:8
- Duplicated block (15 lines × 2 locations) src/content/datachannel/channel/js/test.js:14
- Duplicated block (15 lines × 11 locations) src/content/datachannel/filetransfer/js/test.js:14
- Duplicated block with local edits (14 matched lines × 2 locations) src/content/insertable-streams/video-processing/js/camera-source.js:18
- Complex function onmessage (cyclomatic 15, cognitive 19) REDACTED:84
- Complex function start (cyclomatic 14, cognitive 13) src/content/devices/input-output/js/main.js:117
- Complex function buildDriver (cyclomatic 13, cognitive 16) test/webdriver.js:50
- Complex function animate (cyclomatic 12, cognitive 13) src/content/insertable-streams/video-processing/js/canvas-source.js:103
- Complex function showRemoteStats (cyclomatic 11, cognitive 11) src/content/peerconnection/constraints/js/main.js:202
- No typecheck script
- Dead file (~159 LoC) src/content/insertable-streams/endtoend-encryption/js/worker.js
- Dead file (~88 LoC) src/content/datachannel/channel/js/test.js
- Dead file (~78 LoC) src/content/insertable-streams/endtoend-encryption/js/test.js
- Dead file (~77 LoC) src/content/peerconnection/states/js/test.js
- Dead file (~75 LoC) src/content/insertable-streams/audio-processing/js/worker.js
- Dead file (~73 LoC) src/content/peerconnection/dtmf/js/test.js
- Dead file (~70 LoC) src/content/peerconnection/restart-ice/js/test.js
- Dead file (~66 LoC) src/content/peerconnection/change-codecs/js/test.js
- Dead file (~59 LoC) src/content/peerconnection/pc1/js/test.js
- Dead file (~54 LoC) src/content/peerconnection/upgrade/js/test.js
- Dead file (~51 LoC) src/content/datachannel/basic/js/test.js
- Dead file (~49 LoC) src/content/devices/input-output/js/test.js
- Dead file (~43 LoC) src/content/peerconnection/audio/js/test.js
- Dead file (~42 LoC) src/content/datachannel/filetransfer/js/test.js
- Dead file (~38 LoC) src/content/getusermedia/gum/js/test.js
- Dead file (~35 LoC) src/content/insertable-streams/video-crop/js/worker.js
- Dead file (~20 LoC) src/content/capture/worker-process/js/worker.js
- Third-party script without Subresource Integrity REDACTED:77
- JavaScript dependencies are not locked package.json:29
Minor — 74 finding(s)
- Orphaned file src/content/extensions/svc/js/main.js:1
- Orphaned file src/content/insertable-streams/video-processing/js/main.js:1
- Orphaned file src/content/peerconnection/negotiate-timing/js/main.js:1
- Orphaned file src/content/insertable-streams/video-analyzer/js/main.js:1
- Orphaned file src/content/datachannel/datatransfer/js/main.js:1
- Orphaned file src/content/insertable-streams/webgpu/js/multi_video_main.js:1
- Orphaned file src/content/insertable-streams/video-processing/js/canvas-source.js:1
- Orphaned file src/content/insertable-streams/video-processing/js/webgl-transform.js:1
- Orphaned file src/content/insertable-streams/video-processing/js/pipeline.js:1
- Orphaned file REDACTED:1
- Orphaned file src/content/datachannel/messaging/main.js:1
- Orphaned file src/content/capture/video-pc/js/main.js:1
- Orphaned file src/content/devices/input-output/js/main.js:1
- Orphaned file src/content/capture/canvas-pc/js/main.js:1
- Orphaned file REDACTED:1
- Orphaned file src/content/insertable-streams/video-processing/js/peer-connection-pipe.js:1
- Orphaned file src/content/capture/canvas-record/js/main.js:1
- Orphaned file src/content/capture/video-contenthint/js/main.js:1
- Orphaned file src/content/insertable-streams/video-processing/js/video-source.js:1
- Orphaned file src/content/devices/multi/js/main.js:1
- Orphaned file src/content/getusermedia/exposure/js/main.js:1
- Orphaned file src/content/insertable-streams/webgpu/js/main.js:1
- Orphaned file src/content/insertable-streams/video-processing/js/peer-connection-source.js:1
- Orphaned file src/content/getusermedia/volume/js/main.js:1
- Orphaned file src/content/extensions/multipleroutes/src/options.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate src/content/peerconnection/constraints/js/main.js:243
- Duplicated predicate src/content/extensions/svc/js/main.js:286
- Duplicated predicate src/content/datachannel/channel/js/test.js:47
- Duplicated predicate src/content/datachannel/basic/js/test.js:33
- Duplicated predicate src/content/datachannel/basic/js/test.js:36
- Duplicated predicate src/content/capture/canvas-filter/js/main.js:24
- Duplicated predicate src/content/extensions/svc/js/main.js:314
- Duplicated predicate REDACTED:164
- Duplicated predicate src/content/insertable-streams/audio-processing/js/main.js:12
- Duplicated predicate src/content/getusermedia/volume/js/main.js:66
- Duplicated predicate src/content/extensions/svc/js/main.js:45
- redundant comment src/content/insertable-streams/video-processing/js/webgl-transform.js:73
- redundant comment src/content/insertable-streams/video-processing/js/webgl-transform.js:126
- redundant comment src/content/insertable-streams/webgpu/js/multi_video_main.js:85
- redundant comment src/content/insertable-streams/webgpu/js/multi_video_main.js:91
- redundant comment src/content/peerconnection/audio/js/main.js:304
- redundant comment src/content/peerconnection/multiple/js/main.js:70
- Off-boarding risk: anonymized user #1
- `establishPC` spells `PC` where 24 names in the project spell it `Pc` src/content/capture/video-contenthint/js/main.js:77
- Orphaned files with no living knowledge
- REDACTED
- Empty method body src/js/videopipe.js:36
- CI build step not evidenced
- No SAST REDACTED:3
- No dependency-update automation package.json:29
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade)
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-4efa39fa42e4465d8fa14bcaee95d76c/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-4efa39fa42e4465d8fa14bcaee95d76c/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 . | 32 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | 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 |
| 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 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 |