Public report — Fable.Remoting, published 6 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
85findings with an exact file:lineof 187 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
21/95dimensions across the health lenses10761 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
Zaid-Ajaj/Fable.Remoting is sound in substance but carries real gaps (59%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (100%) — the structure is clean and changes stay contained. Code Health (87%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (46%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (56%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: Nothing pauses a release for a human (Deployment & Rollback); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped… (Release Hygiene); Record significant decisions one document per decision (Architecture documentation).
For scale: Small (~10,761 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/yarn.lock
D38 · High CVE: [GHSA redacted] documentation/yarn.lock
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
D38 · High CVE: [GHSA redacted] documentation/package-lock.json
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.8× (at 59% quality) — the last 20% of quality is most of the work
Size & shape
Small · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.1 person-years of build effort (about ~€17,000 to rebuild). Its weakest lens is Readiness at 46% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Value concentrated against a weak lens · Medium · Value at risk
This is a Small asset (~0.1 person-years to rebuild), and its weakest lens is Readiness at 46%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A06:2021 — Vulnerable & Outdated Components
50
High / Critical
Roadmap
First, implement draft releases or manual dispatch gates to prevent bad builds from reaching users. Next, maintain a changelog to track what is shipped in each release. Then, document significant architectural decisions in a dedicated folder to preserve context and consequences. After that, ensure the CI pipeline explicitly runs the test suite and blocks merges on failure. Finally, update the root README with a testing section to clarify how to run the test suite.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Watchdog 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. 19 of 21 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 21 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 85 of 187 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D4 Code Duplication: Duplication is token-similarity (jscpd) — 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
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").
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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 the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with App.fs (4), Patterns.fs (2), FableFalcoAdapter.fs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with App.fs (2), Middleware.fs, Patterns.fs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with TypeShape.fs (3), Middleware.fs. — One of this dimension's main actionable groups (4 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Fable.Remoting.MsgPack/TypeShape.fs.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
Fable.Remoting's documentation is clear and complete for a type-safe RPC library. The README gives an excellent one-page overview of the API (shared interface, server implementation as Remoting.createApi/fromValue, client typed proxy buildProxy) with concrete runnable code plus links to three real-world applications using it. A dedicated Getting Started document explains modeling the shared interface, implementing each field as Async<'T> or a function returning Async<'T>, and building the client proxy. The architecture docs cover server setups for Suave/Saturn/Falco/AspNetCore middleware with step-by-step code examples plus troubleshooting guidance (the internal diagnostics logger). There is no visible gap in content; every outlined section exists. The documentation is comprehensive and well-structured for a .NET remoting project: three README files cover client setup (Fable.Remoting.DotnetClient), integration testing with the dotnet client, using multiple protocols (Suave/Giraffe/Saturn), type-safe documentation generation from API definitions, raw HTTP communication for non-Fable clients, dependency injection, file upload/download, and error handling. The advanced topics are well illustrated with code examples and cross-project configuration notes.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
7 of 31 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Fable.Remoting.MsgPack/Write.fs.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with Write.fs, Read.fs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×26ClientTests/package-lock.jsondetected by osv-scanner finding
Critical CVE: [GHSA redacted] · ×23documentation/package-lock.jsondetected by osv-scanner finding
High vulnerability: [GHSA redacted]documentation/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 26 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (24), yarn.lock (2). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 23 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (18), yarn.lock (5). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 1 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 1 of 3 project(s) that lack one — worth up to 0.7 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Check the coverage dimensions first: if this repo has no test suite yet, that is the finding and this row follows from it. If a suite does exist, make the runner step explicit so the gate is unambiguous.
What to do
Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — 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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 74 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (6 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set 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
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
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 assessed — interface segregation is computed over a type surface 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
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.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D1 Cyclomatic Complexity — Most of this repository's production source (.fs) had no cyclomatic complexity computed for it, so cyclomatic complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
D10 Test Quality — ~5601 lines of test source are present (.fs) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D14 License Compliance — Not scored — this repository's projects are MSBuild/NuGet projects, whose package licenses are exactly what this dimension reads, but no license could be resolved for them (the .NET license collector did not run, or restore failed). A gap in the analysis run, NOT a finding that the repository's licenses are compliant.
D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
D2 Cognitive Complexity — Most of this repository's production source (.fs) had no cognitive complexity computed for it, so cognitive complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.fs) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. 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"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D3 God Classes — Most of this repository's production source (.fs) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. 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, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
D39 IL Efficiency — No first-party assembly was produced by the build.
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.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .fs, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
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
D9 Test Distribution — Test source is present (.fs) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 131 value object(s); 2 domain event(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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 check looks for
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — 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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — 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
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
X3 Exception handling — 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
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 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
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Issue — 52 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×26
High CVE: [GHSA redacted] ClientTests/package-lock.json— @babel/plugin-transform-modules-systemjs 7.23.3: [GHSA redacted] — @babel/plugin-transform-modules-systemjs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/plugin-transform-modules-systemjs to 7.29.4 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] documentation/package-lock.json— ansi-regex 3.0.0: [GHSA redacted] — ansi-regex is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ansi-regex to 3.0.1 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] documentation/package-lock.json— async 2.6.1: [GHSA redacted] — async is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin async to 2.6.4 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] documentation/package-lock.json— async 2.6.3: [GHSA redacted] — async is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin async to 2.6.4 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] ClientTests/package-lock.json— body-parser 1.20.1: [GHSA redacted] — body-parser is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin body-parser to 1.20.3 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against body-parser 1.20.1, and their fixed versions do not agree — anything below 1.20.6 still leaves at least one of them open. Take this package to 1.20.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against body-parser 1.20.1: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] ClientTests/package-lock.json— brace-expansion 1.1.11: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories with a published fix this scan raises against brace-expansion 1.1.11, and their fixed versions do not agree — anything below 1.1.18 still leaves at least one of them open. Take this package to 1.1.18 or later: that is the floor for the package, not this row's target alone. (in 3 dependency files: ClientTests/package-lock.json, documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 5 advisories this scan raises against brace-expansion 1.1.11: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— brace-expansion 1.1.6: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 6 advisories with a published fix this scan raises against brace-expansion 1.1.6, and their fixed versions do not agree — anything below 1.1.18 still leaves at least one of them open. Take this package to 1.1.18 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against brace-expansion 1.1.6: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— brace-expansion 1.1.8: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories with a published fix this scan raises against brace-expansion 1.1.8, and their fixed versions do not agree — anything below 1.1.18 still leaves at least one of them open. Take this package to 1.1.18 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against brace-expansion 1.1.8: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— braces 2.3.2: [GHSA redacted] — braces is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 3.0.3 is a MAJOR ahead of the resolved 2.3.2, so an `overrides` pin would force a breaking version under a dependent written against 2.3.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] ClientTests/package-lock.json— braces 3.0.2: [GHSA redacted] — braces is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin braces to 3.0.3 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] documentation/package-lock.json— cross-spawn 5.1.0: [GHSA redacted] — cross-spawn is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 6.0.6 is a MAJOR ahead of the resolved 5.1.0, so an `overrides` pin would force a breaking version under a dependent written against 5.1.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] ClientTests/package-lock.json— cross-spawn 7.0.3: [GHSA redacted] — cross-spawn is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin cross-spawn to 7.0.5 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] documentation/package-lock.json— debug 0.8.1: [GHSA redacted] — debug is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 2.6.9 is a MAJOR ahead of the resolved 0.8.1, so an `overrides` pin would force a breaking version under a dependent written against 0.8.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 2 advisories this scan raises against debug 0.8.1: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— debug 2.6.8: [GHSA redacted] — debug is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin debug to 2.6.9 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against debug 2.6.8: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— decode-uri-component 0.2.0: [GHSA redacted] — decode-uri-component is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin decode-uri-component to 0.2.1 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] documentation/package-lock.json— follow-redirects 1.12.1: [GHSA redacted] — follow-redirects is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin follow-redirects to 1.14.7 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories with a published fix this scan raises against follow-redirects 1.12.1, and their fixed versions do not agree — anything below 1.16.0 still leaves at least one of them open. Take this package to 1.16.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against follow-redirects 1.12.1: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/yarn.lock— follow-redirects 1.13.0: [GHSA redacted] — follow-redirects is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin follow-redirects to 1.14.7 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories with a published fix this scan raises against follow-redirects 1.13.0, and their fixed versions do not agree — anything below 1.16.0 still leaves at least one of them open. Take this package to 1.16.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against follow-redirects 1.13.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— fresh 0.2.0: [GHSA redacted] — fresh is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fresh to 0.5.2 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] documentation/package-lock.json— hawk 3.1.3: [GHSA redacted] — hawk is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 9.0.1 is a MAJOR ahead of the resolved 3.1.3, so an `overrides` pin would force a breaking version under a dependent written against 3.1.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
High CVE: [GHSA redacted] documentation/package-lock.json— hoek 2.16.3: [GHSA redacted] — no fixed version has been published yet. Track the advisory; hoek is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 2 advisories this scan raises against hoek 2.16.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— http-cache-semantics 3.7.3: [GHSA redacted] — http-cache-semantics is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.1.1 is a MAJOR ahead of the resolved 3.7.3, so an `overrides` pin would force a breaking version under a dependent written against 3.7.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] documentation/yarn.lock— http-cache-semantics 3.8.1: [GHSA redacted] — http-cache-semantics is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.1.1 is a MAJOR ahead of the resolved 3.8.1, so an `overrides` pin would force a breaking version under a dependent written against 3.8.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] ClientTests/package-lock.json— http-proxy-middleware 2.0.6: [GHSA redacted] — http-proxy-middleware is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin http-proxy-middleware to 2.0.7 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 4 advisories with a published fix this scan raises against http-proxy-middleware 2.0.6, and their fixed versions do not agree — anything below 2.0.10 still leaves at least one of them open. Take this package to 2.0.10 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against http-proxy-middleware 2.0.6: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— ini 1.3.4: [GHSA redacted] — ini is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ini to 1.3.6 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] documentation/package-lock.json— ini 1.3.5: [GHSA redacted] — ini is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ini to 1.3.6 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
Critical CVE: [GHSA redacted] documentation/package-lock.json— deep-extend 0.4.2: [GHSA redacted] — deep-extend is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin deep-extend to 0.5.1 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] documentation/package-lock.json— form-data 1.0.0-rc4: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 2.5.4 is a MAJOR ahead of the resolved 1.0.0-rc4, so an `overrides` pin would force a breaking version under a dependent written against 1.0.0-rc4; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories with a published fix this scan raises against form-data 1.0.0-rc4, and their fixed versions do not agree — anything below 2.5.6 still leaves at least one of them open. Take this package to 2.5.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against form-data 1.0.0-rc4: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/yarn.lock— form-data 1.0.1: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 2.5.4 is a MAJOR ahead of the resolved 1.0.1, so an `overrides` pin would force a breaking version under a dependent written against 1.0.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories with a published fix this scan raises against form-data 1.0.1, and their fixed versions do not agree — anything below 2.5.6 still leaves at least one of them open. Take this package to 2.5.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against form-data 1.0.1: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— form-data 2.1.4: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 2.5.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against form-data 2.1.4, and their fixed versions do not agree — anything below 2.5.6 still leaves at least one of them open. Take this package to 2.5.6 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 2 advisories this scan raises against form-data 2.1.4: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/yarn.lock— form-data 2.3.3: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 2.5.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against form-data 2.3.3, and their fixed versions do not agree — anything below 2.5.6 still leaves at least one of them open. Take this package to 2.5.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against form-data 2.3.3: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/yarn.lock— fsevents 1.2.4: [GHSA redacted] — fsevents is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fsevents to 1.2.11 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against fsevents 1.2.4: [GHSA redacted], MAL-2023-462.
Critical CVE: [GHSA redacted] documentation/package-lock.json— fsevents 1.2.7: [GHSA redacted] — fsevents is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fsevents to 1.2.11 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against fsevents 1.2.7: [GHSA redacted], MAL-2023-462.
Critical CVE: [GHSA redacted] documentation/package-lock.json— gh-pages 1.2.0: [GHSA redacted] — upgrade to 5.0.0 (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
Critical CVE: [GHSA redacted] documentation/package-lock.json— json-schema 0.2.2: [GHSA redacted] — json-schema is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin json-schema to 0.4.0 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] documentation/package-lock.json— json-schema 0.2.3: [GHSA redacted] — json-schema is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin json-schema to 0.4.0 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
Critical CVE: [GHSA redacted] documentation/package-lock.json— lodash 4.17.11: [GHSA redacted] — lodash is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash to 4.17.12 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories with a published fix this scan raises against lodash 4.17.11, and their fixed versions do not agree — anything below 4.18.0 still leaves at least one of them open. Take this package to 4.18.0 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 5 advisories this scan raises against lodash 4.17.11: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— lodash 4.17.4: [GHSA redacted] — lodash is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash to 4.17.12 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 8 advisories with a published fix this scan raises against lodash 4.17.4, and their fixed versions do not agree — anything below 4.18.0 still leaves at least one of them open. Take this package to 4.18.0 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 8 advisories this scan raises against lodash 4.17.4: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— minimist 0.0.10: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 0.2.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against minimist 0.0.10, and their fixed versions do not agree — anything below 0.2.4 still leaves at least one of them open. Take this package to 0.2.4 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 2 advisories this scan raises against minimist 0.0.10: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— minimist 0.0.8: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 0.2.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against minimist 0.0.8, and their fixed versions do not agree — anything below 0.2.4 still leaves at least one of them open. Take this package to 0.2.4 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 2 advisories this scan raises against minimist 0.0.8: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— minimist 1.2.0: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 1.2.6 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against minimist 1.2.0, and their fixed versions do not agree — anything below 1.2.6 still leaves at least one of them open. Take this package to 1.2.6 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 2 advisories this scan raises against minimist 1.2.0: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— minimist 1.2.5: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 1.2.6 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock)
Critical CVE: [GHSA redacted] documentation/yarn.lock— set-value 0.4.3: [GHSA redacted] — set-value is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 2.0.1 is a MAJOR ahead of the resolved 0.4.3, so an `overrides` pin would force a breaking version under a dependent written against 0.4.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This one row stands for the 2 advisories this scan raises against set-value 0.4.3: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/yarn.lock— set-value 2.0.0: [GHSA redacted] — set-value is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin set-value to 2.0.1 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against set-value 2.0.0: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] ClientTests/package-lock.json— shell-quote 1.8.1: [GHSA redacted] — shell-quote is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin shell-quote to 1.8.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against shell-quote 1.8.1, and their fixed versions do not agree — anything below 1.9.0 still leaves at least one of them open. Take this package to 1.9.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against shell-quote 1.8.1: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— tar 2.2.1: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.5.19 is a MAJOR ahead of the resolved 2.2.1, so an `overrides` pin would force a breaking version under a dependent written against 2.2.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 16 advisories this scan raises against tar 2.2.1: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— tar 4.4.8: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.5.19 is a MAJOR ahead of the resolved 4.4.8, so an `overrides` pin would force a breaking version under a dependent written against 4.4.8; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 18 advisories with a published fix this scan raises against tar 4.4.8, and their fixed versions do not agree — anything below 4.4.18 still leaves at least one of them open. Take this package to 4.4.18 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 18 advisories this scan raises against tar 4.4.8: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— websocket-driver 0.7.0: [GHSA redacted] — websocket-driver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin websocket-driver to 0.7.5 with an `overrides` entry (`resolutions` if you use Yarn)). (in 2 dependency files: documentation/package-lock.json, documentation/yarn.lock) This one row stands for the 2 advisories this scan raises against websocket-driver 0.7.0: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] ClientTests/package-lock.json— websocket-driver 0.7.4: [GHSA redacted] — websocket-driver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin websocket-driver to 0.7.5 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against websocket-driver 0.7.4: [GHSA redacted], [GHSA redacted].
Orphaned knowledge Fable.Remoting.MsgPack/Write.fs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge Fable.Remoting.MsgPack/Read.fs— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] documentation/package-lock.json— http-proxy-agent 2.0.0: [GHSA redacted] — http-proxy-agent is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin http-proxy-agent to 2.1.0 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against http-proxy-agent 2.0.0: [GHSA redacted], [GHSA redacted].
Duplicated block (7 lines × 2) Fable.Remoting.Server/Patterns.fs:41— Fable.Remoting.Server/Patterns.fs:41-47 | Fable.Remoting.DotnetClient/Patterns.fs:41-47 — `Fable.Remoting.Server/Patterns.fs` and `Fable.Remoting.DotnetClient/Patterns.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) Fable.Remoting.Server/Patterns.fs:78— Fable.Remoting.Server/Patterns.fs:78-84 | Fable.Remoting.DotnetClient/Patterns.fs:53-59 — `Fable.Remoting.Server/Patterns.fs` and `Fable.Remoting.DotnetClient/Patterns.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) Fable.Remoting.Falco/FableFalcoAdapter.fs:51— Fable.Remoting.Falco/FableFalcoAdapter.fs:51-58 | Fable.Remoting.Suave/FableSuaveAdapter.fs:64-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.Falco/FableFalcoAdapter.fs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) ClientTests/src/App.fs:427— ClientTests/src/App.fs:427-433 | ClientTests/src/App.fs:1098-1104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:427` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) ClientTests/src/App.fs:449— ClientTests/src/App.fs:449-455 | ClientTests/src/App.fs:1120-1126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:449` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) ClientTests/src/App.fs:755— ClientTests/src/App.fs:755-761 | ClientTests/src/App.fs:1491-1497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:755` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) ClientTests/src/App.fs:1098— ClientTests/src/App.fs:1098-1104 | ClientTests/src/App.fs:1120-1126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:1098` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Fable.Remoting.AspNetCore/Middleware.fs:116— Fable.Remoting.AspNetCore/Middleware.fs:116-127 | Fable.Remoting.Falco/FableFalcoAdapter.fs:92-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) Fable.Remoting.Server/Patterns.fs:154— Fable.Remoting.Server/Patterns.fs:154-165 | Fable.Remoting.DotnetClient/Patterns.fs:126-137 — `Fable.Remoting.Server/Patterns.fs` and `Fable.Remoting.DotnetClient/Patterns.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 2) ClientTests/src/App.fs:555— ClientTests/src/App.fs:555-566 | ClientTests/src/App.fs:1226-1237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:555` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) ClientTests/src/App.fs:607— ClientTests/src/App.fs:607-618 | ClientTests/src/App.fs:1278-1289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:607` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Fable.Remoting.AspNetCore/Middleware.fs:106— Fable.Remoting.AspNetCore/Middleware.fs:106-113 | Fable.Remoting.Giraffe/FableGiraffeAdapter.fs:53-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.AspNetCore/Middleware.fs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) Fable.Remoting.MsgPack/TypeShape.fs:877— Fable.Remoting.MsgPack/TypeShape.fs:877-884 | Fable.Remoting.MsgPack/TypeShape.fs:893-900 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) Fable.Remoting.MsgPack/TypeShape.fs:1363— Fable.Remoting.MsgPack/TypeShape.fs:1363-1370 | Fable.Remoting.MsgPack/TypeShape.fs:1416-1423 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) Fable.Remoting.MsgPack/TypeShape.fs:1372— Fable.Remoting.MsgPack/TypeShape.fs:1372-1379 | Fable.Remoting.MsgPack/TypeShape.fs:1425-1432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.MsgPack/TypeShape.fs:1372` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Fable.Remoting.Server/Documentation.fs:14— Fable.Remoting.Server/Documentation.fs:14-27 | Fable.Remoting.Server/Documentation.fs:28-41 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:116— Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:116-129 | Fable.Remoting.AwsLambda/FableLambdaApiGatewayAdapter.fs:120-133 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) Fable.Remoting.DotnetClient/Proxy.fs:172— Fable.Remoting.DotnetClient/Proxy.fs:172-188 | Fable.Remoting.DotnetClient/Proxy.fs:189-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) Fable.Remoting.Server/Patterns.fs:3— Fable.Remoting.Server/Patterns.fs:3-12 | Fable.Remoting.DotnetClient/Patterns.fs:3-12 — `Fable.Remoting.Server/Patterns.fs` and `Fable.Remoting.DotnetClient/Patterns.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) Fable.Remoting.MsgPack/TypeShape.fs:1382— Fable.Remoting.MsgPack/TypeShape.fs:1382-1391 | Fable.Remoting.MsgPack/TypeShape.fs:1435-1444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.MsgPack/TypeShape.fs:1382` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:36— Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:36-45 | Fable.Remoting.AwsLambda/FableLambdaApiGatewayAdapter.fs:40-49 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Fable.Remoting.Server/Patterns.fs:28— Fable.Remoting.Server/Patterns.fs:28-33 | Fable.Remoting.DotnetClient/Patterns.fs:28-33 — `Fable.Remoting.Server/Patterns.fs` and `Fable.Remoting.DotnetClient/Patterns.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) Fable.Remoting.Server/Proxy.fs:108— Fable.Remoting.Server/Proxy.fs:108-113 | Fable.Remoting.Server/Proxy.fs:121-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.Server/Proxy.fs:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Fable.Remoting.DotnetClient/Proxy.fs:114— Fable.Remoting.DotnetClient/Proxy.fs:114-119 | Fable.Remoting.DotnetClient/Proxy.fs:121-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) ClientTests/src/App.fs:87— ClientTests/src/App.fs:87-97 | ClientTests/src/App.fs:845-855 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) ClientTests/src/App.fs:593— ClientTests/src/App.fs:593-603 | ClientTests/src/App.fs:1264-1274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ClientTests/src/App.fs:593` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Fable.Remoting.AspNetCore/Middleware.fs:25— Fable.Remoting.AspNetCore/Middleware.fs:25-29 | Fable.Remoting.Falco/FableFalcoAdapter.fs:15-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.AspNetCore/Middleware.fs:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Fable.Remoting.MsgPack/Write.fs:419— Fable.Remoting.MsgPack/Write.fs:419-423 | Fable.Remoting.MsgPack/Write.fs:434-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.MsgPack/Write.fs:419` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) Fable.Remoting.Benchmarks/Serialization.fs:66— Fable.Remoting.Benchmarks/Serialization.fs:66-80 | Fable.Remoting.Benchmarks/Serialization.fs:118-132 | Fable.Remoting.Benchmarks/Serialization.fs:197-211 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 2) Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:74— Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:74-86 | Fable.Remoting.AwsLambda/FableLambdaApiGatewayAdapter.fs:78-90 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:137— Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:137-149 | Fable.Remoting.AwsLambda/FableLambdaApiGatewayAdapter.fs:141-153 | Fable.Remoting.AzureFunctions.Worker/FableAzureFunctionsAdapter.fs:102-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Fable.Remoting.AwsLambda/FableLambdaAdapter.fs:137` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Fable.Remoting.Server/Patterns.fs:140— Fable.Remoting.Server/Patterns.fs:140-148 | Fable.Remoting.DotnetClient/Patterns.fs:112-120 — `Fable.Remoting.Server/Patterns.fs` and `Fable.Remoting.DotnetClient/Patterns.fs` are the same file name in two sibling directories, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 3) Fable.Remoting.AspNetCore/Middleware.fs:96— Fable.Remoting.AspNetCore/Middleware.fs:96-100 | Fable.Remoting.Falco/FableFalcoAdapter.fs:70-74 | Fable.Remoting.Giraffe/FableGiraffeAdapter.fs:43-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Coverage not measured — The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. No coverage collector was found in your CI either, so there is no existing report to hand us: add a coverage collector to your test run and commit (or publish) its Cobertura/OpenCover/lcov output anywhere in the repo, or make the suite runnable in-image, and real coverage will be measured.
Recommendation — 5 finding(s)
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.fs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
complexity unreadable for .fs — churn × complexity hotspots could not be measured — A hotspot is churn × complexity. Churn was measured (78 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: Fable.Remoting.Server/Proxy.fs, Fable.Remoting.Client/Http.fs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (4 single-owned of 29 analysed files in total, counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 5 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than listed individually (7 orphaned of 31 analysed files in total, counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first).
Outdated: FSharp.Core — FSharp.Core 10.1.202 → 10.1.302 available (referenced by Fable.Remoting.Json).
Outdated: Newtonsoft.Json — Newtonsoft.Json 13.0.1 → 13.0.4 available (referenced by Fable.Remoting.Json).
Outdated: System.Diagnostics.DiagnosticSource — System.Diagnostics.DiagnosticSource 9.0.3 → 10.0.10 available (referenced by Fable.Remoting.Json).
Outdated: System.Formats.Asn1 — System.Formats.Asn1 6.0.1 → 10.0.10 available (referenced by Fable.Remoting.Json).
Outdated: Expecto — Expecto 9.0.2 → 11.1.0 available (referenced by Fable.Remoting.Json.Tests).
Outdated: Microsoft.AspNetCore.WebUtilities — Microsoft.AspNetCore.WebUtilities 2.3.0 → 10.0.10 available (referenced by Fable.Remoting.Server).
Outdated: Microsoft.Extensions.Primitives — Microsoft.Extensions.Primitives 9.0.3 → 10.0.10 available (referenced by Fable.Remoting.Server).
Outdated: Microsoft.Net.Http.Headers — Microsoft.Net.Http.Headers 2.3.0 → 10.0.10 available (referenced by Fable.Remoting.Server).
Outdated: System.Text.Encodings.Web — System.Text.Encodings.Web 10.0.6 → 10.0.10 available (referenced by Fable.Remoting.Server).
Outdated: Suave — Suave 2.6.0 → 3.4.4 available (referenced by Fable.Remoting.Suave).
Outdated: Giraffe — Giraffe 8.2.0 → 8.3.0 available (referenced by Fable.Remoting.Giraffe).
Outdated: Microsoft.Bcl.AsyncInterfaces — Microsoft.Bcl.AsyncInterfaces 10.0.6 → 10.0.10 available (referenced by Fable.Remoting.Giraffe).
Outdated: System.IO.Pipelines — System.IO.Pipelines 10.0.6 → 10.0.10 available (referenced by Fable.Remoting.Giraffe).
Outdated: System.Text.Json — System.Text.Json 10.0.6 → 10.0.10 available (referenced by Fable.Remoting.Giraffe).
Outdated: Microsoft.AspNetCore.Hosting — Microsoft.AspNetCore.Hosting 2.3.0 → 2.3.11 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.AspNetCore.Hosting.Abstractions — Microsoft.AspNetCore.Hosting.Abstractions 2.3.0 → 2.3.11 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.AspNetCore.Hosting.Server.Abstractions — Microsoft.AspNetCore.Hosting.Server.Abstractions 2.3.0 → 2.3.11 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.AspNetCore.Http — Microsoft.AspNetCore.Http 2.3.0 → 2.3.11 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.AspNetCore.Http.Abstractions — Microsoft.AspNetCore.Http.Abstractions 2.3.0 → 2.3.11 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.AspNetCore.Http.Extensions — Microsoft.AspNetCore.Http.Extensions 2.3.0 → 2.3.11 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.AspNetCore.TestHost — Microsoft.AspNetCore.TestHost 3.1.0 → 10.0.10 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 9.0.3 → 10.0.10 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.Extensions.Configuration.Abstractions — Microsoft.Extensions.Configuration.Abstractions 9.0.3 → 10.0.10 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables — Microsoft.Extensions.Configuration.EnvironmentVariables 9.0.3 → 10.0.10 available (referenced by Fable.Remoting.Giraffe.Tests).
Outdated: Microsoft.Extensions.Configuration.FileExtensions — Microsoft.Extensions.Configuration.FileExtensions 9.0.3 → 10.0.10 available (referenced by Fable.Remoting.Giraffe.Tests).
+ 70 more in this group — see findings.md.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
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.
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.
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
—
Run 019fd546-5efc-7a5e-a1a1-6c41347a092d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 52 · Warnings: 34 · Recommendations: 5 · Info: 96 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 06-08-2026 @ 04:13 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.