Public report — FsToolkit.ErrorHandling, 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.
157findings with an exact file:lineof 167 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
25/95dimensions across the health lenses16511 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.
demystifyfp/FsToolkit.ErrorHandling is sound in substance but carries real gaps (58%). 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 (97%) — the structure is clean and changes stay contained.
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 Maturity (53%) — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent. Accessibility (57%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: 'Testing' section to the root README (Documentation (README)); Record significant decisions one document per decision (Architecture documentation); Declare <html lang>, a document <title> and a <main> landmark,… (Page structure).
For scale: Small (~16,511 production lines); rebuilding it from scratch would take roughly ~0.3 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (97%); the priorities above are the highest-leverage way to bring the rest up to that level.
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.
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 58% 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.3 person-years of build effort (about ~€44,000 to rebuild). Its weakest lens is Maturity at 53% — 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
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with CancellableValueTaskOptionCE.fs, CancellableTaskOptionBuilderBase.fs, TaskValidationCE.fs.
Value concentrated against a weak lens · Medium · Value at risk
This is a Small asset (~0.3 person-years to rebuild), and its weakest lens is Maturity at 53%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Maturity 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: Add a 'Testing' section to the root README — how to run the test suite. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a 'Testing' section to the root README — how to run the test suite.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 6.8/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 3–7% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D4 code quality: averaging 6.8/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
Architecture — module dependency matrix
71 modules, 33 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
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
15
High / Critical
A03:2021 — Injection
13
High / Critical
Roadmap
Begin by updating the root README to include a testing section that explains how to run the test suite. Next, establish a structured approach to architecture documentation by recording significant decisions in a dedicated directory, ensuring each entry captures the context, decision, and consequences. Simultaneously, improve the page structure by adding proper language attributes, titles, and landmarks, while ensuring headings are ordered correctly and accessibility features like zoom remain enabled. Finally, enforce accessibility standards by integrating automated checks into the test suite and CI pipeline, and resolve the identified orphaned knowledge items to ensure the codebase remains current and well-documented.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with CancellableValueTaskOptionCE.fs, CancellableTaskOptionBuilderBase.fs, TaskValidationCE.fs.
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).
Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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. 23 of 25 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 — 25 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, 157 of 167 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.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (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.
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.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
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.
Dimensions
D3 · God Classes7.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 5 TooManyMethods finding(s) in God Classes — start with AsyncResult.fs, TaskResult.fs, JobResult.fs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 FileTooLong finding(s) in God Classes — start with Benchmarks.fs, CancellableValueTaskOptionCE.fs, CancellableTaskResultBuilderBase.fs. — One of this dimension's main actionable groups (4 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 43 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with CancellableTaskValidationCE.fs (3), CancellableTaskOption.fs (2), TaskValidationCE.fs (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 8 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with CancellableTaskOption.fs (2), ValueTaskValueOptionCE.fs, CancellableTaskOptionBuilderBase.fs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with CancellableValueTaskOptionCE.fs, CancellableTaskResultBuilderBase.fs, CancellableTaskOptionCE.fs. — One of this dimension's main actionable groups (6 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 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.
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.
The FsToolkit.ErrorHandling README and gitbook are clear, complete, well-structured, and well-representative of the library's purpose. The main body is a thorough description of the utility functions (map, bind, apply, traverse, sequence), computation expressions, infix operators for Async<Result>, TaskResult, and Result<'a list>, plus an inspired-by-Chessie motivation and links to learning resources like Railway Oriented Programming and Don't Throw Exceptions, with NuGet badges. A separate FunctionMap README provides a cross-reference table of the 18 functions covered by the library's FsToolkit namespace (abort, apply, bind, catch, contains, count, delayWith, etc.) plus an example of how to use them in code.
The README mentions FsToolkit.ErrorHandling targets .NET Standard 2.0, but there is no local development or build target documentation (e.g. how to develop locally).README.md
What to do
Resolve the 1 The README mentions FsToolkit.ErrorHandling targets .NET Standard 2.0,… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
High: github-actions-mutable-action-tag · ×13.github/workflows/build.yml:27detected by semgrep finding
What to do
Resolve the 13 High finding(s) in Static Analysis (SAST) — start with build.yml (13). — One of this dimension's main actionable groups (13 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
14 of 50 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs.
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with CancellableValueTaskOptionCE.fs, CancellableTaskOptionBuilderBase.fs, TaskValidationCE.fs. — One of this dimension's main actionable groups (3 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] · ×7package-lock.jsondetected by osv-scanner finding
Critical CVE: [GHSA redacted]package-lock.jsondetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×2package-lock.jsondetected by osv-scanner finding
Low CVE: [GHSA redacted]package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 7 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC3 · Page structure4.8 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×11) — ApplicativeTests.Result_BindvsAndCEBenchmarks-report.html:2, FsToolkit.ErrorHandling.Benchmarks.AsyncResultCEExtensions.AsyncResult_BindCEBenchmarks-report.html:2, FsToolkit.ErrorHandling.Benchmarks.TaskResultCEExtensions.TaskResult_BindCEBenchmarks-report.html:2, …
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI.
What to do
Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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.
30 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
Review the README against recent changes; refresh the parts that drifted.
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 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.
What to do
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.
What to do
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
Not included — 70 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 — No image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — 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 — ~25793 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
D12 Dependency Hygiene — Dependency hygiene not measured — no packages were read
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.
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 — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
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 — The target did not build, so no IL was available to measure.
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 — analyzer environment
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): 4 strongly-typed id(s); 42 value object(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.
High: github-actions-mutable-action-tag .github/workflows/build.yml:27— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:29— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v3`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:61— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:64— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-node@<40-character SHA>`. This step references `actions/setup-node@v3`; resolve the SHA it points at today with `gh api repos/actions/setup-node/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:69— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v3`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:100— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:103— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-python@<40-character SHA>`. This step references `actions/setup-python@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-python/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:108— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v3`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:135— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:138— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: devcontainers/ci@<40-character SHA>`. This step references `devcontainers/ci@v0.3`; resolve the SHA it points at today with `gh api repos/devcontainers/ci/commits/v0.3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:147— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:149— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v3`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:163— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: github/codeql-action/upload-sarif@<40-character SHA>`. This step references `github/codeql-action/upload-sarif@v3`; resolve the SHA it points at today with `gh api repos/github/codeql-action/commits/v3 --jq .sha`. `github/codeql-action/upload-sarif` is hosted INSIDE the `github/codeql-action` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `github/codeql-action/upload-sarif` path in `uses:` and query only `github/codeql-action`.
D38 · OSV Dependency Vulnerabilities· High CVE · ×7
High CVE: [GHSA redacted] package-lock.json— @babel/plugin-transform-modules-systemjs 7.16.0: [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).
High CVE: [GHSA redacted] 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). 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. 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] package-lock.json— cross-spawn 6.0.5: [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 6.0.6 with an `overrides` entry).
High CVE: [GHSA redacted] package-lock.json— picomatch 2.3.0: [GHSA redacted] — picomatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin picomatch to 2.3.2 with an `overrides` entry). This one row stands for the 2 advisories this scan raises against picomatch 2.3.0: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] package-lock.json— semver 5.7.1: [GHSA redacted] — semver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin semver to 5.7.2 with an `overrides` entry).
High CVE: [GHSA redacted] package-lock.json— semver 6.3.0: [GHSA redacted] — semver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin semver to 6.3.1 with an `overrides` entry).
High CVE: [GHSA redacted] package-lock.json— semver 7.0.0: [GHSA redacted] — semver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin semver to 7.5.2 with an `overrides` entry).
Orphaned knowledge src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.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 src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.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 src/FsToolkit.ErrorHandling/TaskValidationCE.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.
High CVE: Microsoft.Build.Tasks.Core 16.10.0 — Microsoft.Build.Tasks.Core 16.10.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Formats.Asn1 5.0.0 — System.Formats.Asn1 5.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
Critical CVE: [GHSA redacted] package-lock.json— shell-quote 1.7.3: [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). This is 1 of 2 advisories with a published fix this scan raises against shell-quote 1.7.3, 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.7.3: [GHSA redacted], [GHSA redacted].
Duplicated block (10 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:3— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:3-12 | src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:8-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.
Duplicated block (10 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:125— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:125-134 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:70-79 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:125` 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:617— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:617-626 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:650-659 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:617` 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. 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:683— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:683-692 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:716-725 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:683` 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. 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:218— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:218-227 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:217-226 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:218` 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 (10 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:425— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:425-434 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:451-460 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:425` 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 (10 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:473— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:473-482 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:499-508 — 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. 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) src/FsToolkit.ErrorHandling/ValueOption.fs:44— src/FsToolkit.ErrorHandling/ValueOption.fs:44-53 | src/FsToolkit.ErrorHandling/Option.fs:148-157 — 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.
Duplicated block (10 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:480— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:480-489 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:497-506 — 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.
Duplicated block (10 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:554— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:554-563 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:573-582 — 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.
Duplicated block (10 lines × 2) src/FsToolkit.ErrorHandling/List.fs:280— src/FsToolkit.ErrorHandling/List.fs:280-289 | src/FsToolkit.ErrorHandling/Array.fs:252-261 — 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.
Duplicated block (10 lines × 2) src/FsToolkit.ErrorHandling/Array.fs:164— src/FsToolkit.ErrorHandling/Array.fs:164-173 | src/FsToolkit.ErrorHandling/Array.fs:220-229 — 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 (11 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:203— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:203-213 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:196-206 — 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. 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:277— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:277-287 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:597-607 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:277` 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 (11 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:240— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:240-250 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:290-300 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:240` 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 (11 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:459— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:459-469 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:485-495 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:459` 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) src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:182— src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:182-192 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:317-327 — 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 `src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:182` 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) src/FsToolkit.ErrorHandling/Seq.fs:512— src/FsToolkit.ErrorHandling/Seq.fs:512-522 | src/FsToolkit.ErrorHandling/Array.fs:253-263 — 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.
Duplicated block (11 lines × 2) src/FsToolkit.ErrorHandling/ResultOptionCE.fs:99— src/FsToolkit.ErrorHandling/ResultOptionCE.fs:99-109 | src/FsToolkit.ErrorHandling/ResultCE.fs:90-100 — 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. 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) src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:213— src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:213-223 | src/FsToolkit.ErrorHandling/AsyncValidationCE.fs:161-171 — 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.
Duplicated block (14 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:437— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:437-450 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:441-454 — 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.
Duplicated block (14 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:282— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:282-295 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:631-644 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:282` 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 (14 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:91— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:91-104 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:173-186 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:91` 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 (14 lines × 2) src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:389— src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:389-402 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:382-395 — 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 `src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:389` 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 (14 lines × 2) src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:189— src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:189-203 | src/FsToolkit.ErrorHandling/AsyncValidationCE.fs:136-149 — 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.
Duplicated block (14 lines × 2) src/FsToolkit.ErrorHandling/ParallelAsyncResultCE.fs:161— src/FsToolkit.ErrorHandling/ParallelAsyncResultCE.fs:161-174 | src/FsToolkit.ErrorHandling/AsyncResultCE.fs:161-175 — 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.
Duplicated block (12 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:345— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:345-356 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:471-482 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:345` 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:177— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:177-188 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:117-128 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:177` 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:711— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:711-722 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:881-892 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:711` 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 × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:195— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:195-206 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:190-201 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:195` 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. 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 (12 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:392— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:392-403 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:400-411 — 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 `src/FsToolkit.ErrorHandling/TaskValidationCE.fs:392` 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 × 2) src/FsToolkit.ErrorHandling/Array.fs:58— src/FsToolkit.ErrorHandling/Array.fs:58-69 | src/FsToolkit.ErrorHandling/Array.fs:91-102 — 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.
TooManyMethods: AsyncResult src/FsToolkit.ErrorHandling/AsyncResult.fs:9— TooManyMethods — 57 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TaskResult src/FsToolkit.ErrorHandling/TaskResult.fs:6— TooManyMethods — 55 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: JobResult src/FsToolkit.ErrorHandling.JobResult/JobResult.fs:7— TooManyMethods — 47 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Result src/FsToolkit.ErrorHandling/Result.fs:8— TooManyMethods — 47 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: List src/FsToolkit.ErrorHandling/List.fs:4— TooManyMethods — 31 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (13 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:36— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:36-48 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:40-52 — 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.
Duplicated block (13 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:8— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:8-20 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:8-20 — 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.
Duplicated block (13 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1120— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1120-1132 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1136-1148 — 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 (13 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:1044— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:1044-1056 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:1060-1072 — 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 (13 lines × 2) src/FsToolkit.ErrorHandling/TaskValidation.fs:145— src/FsToolkit.ErrorHandling/TaskValidation.fs:145-167 | src/FsToolkit.ErrorHandling/AsyncValidation.fs:89-101 — before extracting anything, compare `src/FsToolkit.ErrorHandling/TaskValidation.fs` and `src/FsToolkit.ErrorHandling/AsyncValidation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/FsToolkit.ErrorHandling/TaskValidation.fs:145` 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) src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:335— src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:335-339 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:387-391 — 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 `src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:335` 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) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:335— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:335-339 | src/FsToolkit.ErrorHandling/TaskValidationCE.fs:390-394 — 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 `src/FsToolkit.ErrorHandling/TaskValidationCE.fs:335` 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) src/FsToolkit.ErrorHandling/TaskResultCE.fs:341— src/FsToolkit.ErrorHandling/TaskResultCE.fs:341-345 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:398-402 — 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 `src/FsToolkit.ErrorHandling/TaskResultCE.fs:341` 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) src/FsToolkit.ErrorHandling/TaskOptionCE.fs:328— src/FsToolkit.ErrorHandling/TaskOptionCE.fs:328-332 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:380-384 — 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 `src/FsToolkit.ErrorHandling/TaskOptionCE.fs:328` 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) src/FsToolkit.ErrorHandling/AsyncResult.fs:33— src/FsToolkit.ErrorHandling/AsyncResult.fs:33-37 | src/FsToolkit.ErrorHandling/AsyncResult.fs:135-140 — 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.
FileTooLong: benchmarks/Benchmarks.fs benchmarks/Benchmarks.fs:0— FileTooLong — 996 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:0— FileTooLong — 815 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:0— FileTooLong — 652 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:0— FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (17 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:299— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:299-315 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:907-927 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:299` 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 (17 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:315— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:315-331 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:981-1001 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:315` 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 (17 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:304— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:304-320 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:907-927 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:304` 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 (17 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:525— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:525-541 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:544-560 — 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 `src/FsToolkit.ErrorHandling/TaskValidationCE.fs:525` 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 (16 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:276— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:276-291 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:339-354 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:332-347 — 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.
Duplicated block (16 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:524— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:524-539 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:552-567 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:528-543 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:524` 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 (16 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:714— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:714-729 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:775-790 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:718-733 — 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.
Duplicated block (16 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:888— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:888-903 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:962-977 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:888-903 — 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.
Duplicated block (16 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1232— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1232-1247 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:53-68 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1232` 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 (16 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:836— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:836-851 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:779-794 — 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.
Duplicated block (16 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:173— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:173-188 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:179-194 — 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 `src/FsToolkit.ErrorHandling/TaskValidationCE.fs:173` 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 (16 lines × 2) src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:104— src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:104-119 | src/FsToolkit.ErrorHandling/AsyncValidationCE.fs:102-117 — 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.
Duplicated block (15 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:227— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:227-241 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:550-564 — 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 (15 lines × 2) src/FsToolkit.ErrorHandling/ValidationCE.fs:77— src/FsToolkit.ErrorHandling/ValidationCE.fs:77-91 | src/FsToolkit.ErrorHandling/ResultCE.fs:74-88 — 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 `src/FsToolkit.ErrorHandling/ValidationCE.fs:77` 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 (15 lines × 2) src/FsToolkit.ErrorHandling/TaskValidation.fs:34— src/FsToolkit.ErrorHandling/TaskValidation.fs:34-66 | src/FsToolkit.ErrorHandling/AsyncValidation.fs:32-46 — before extracting anything, compare `src/FsToolkit.ErrorHandling/TaskValidation.fs` and `src/FsToolkit.ErrorHandling/AsyncValidation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/FsToolkit.ErrorHandling/TaskValidation.fs:34` 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 × 2) src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:225— src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:225-239 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:355-369 — 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 `src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:225` 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) src/FsToolkit.ErrorHandling/ValueOption.fs:57— src/FsToolkit.ErrorHandling/ValueOption.fs:57-65 | src/FsToolkit.ErrorHandling/Option.fs:171-179 — 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.
Duplicated block (9 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:149— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:149-157 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:152-160 — 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 `src/FsToolkit.ErrorHandling/TaskValidationCE.fs:149` 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 (9 lines × 2) src/FsToolkit.ErrorHandling/TaskValidation.fs:174— src/FsToolkit.ErrorHandling/TaskValidation.fs:174-182 | src/FsToolkit.ErrorHandling/AsyncValidation.fs:108-116 — before extracting anything, compare `src/FsToolkit.ErrorHandling/TaskValidation.fs` and `src/FsToolkit.ErrorHandling/AsyncValidation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (9 lines × 2) src/FsToolkit.ErrorHandling/TaskValidation.fs:283— src/FsToolkit.ErrorHandling/TaskValidation.fs:283-291 | src/FsToolkit.ErrorHandling/AsyncValidation.fs:176-184 — before extracting anything, compare `src/FsToolkit.ErrorHandling/TaskValidation.fs` and `src/FsToolkit.ErrorHandling/AsyncValidation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (8 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:327— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:327-334 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:417-424 — 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.
Duplicated block (8 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:504— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:504-511 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:530-537 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:504` 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) src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:416— src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:416-424 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:409-416 — 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 `src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:416` 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) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:546— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:546-553 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:565-572 — 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.
Duplicated block (19 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1197— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1197-1215 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:1119-1137 — 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.
Duplicated block (19 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:100— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:100-118 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:95-113 — 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 (19 lines × 2) src/FsToolkit.ErrorHandling/Seq.fs:144— src/FsToolkit.ErrorHandling/Seq.fs:144-162 | src/FsToolkit.ErrorHandling/Seq.fs:198-216 — 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 `src/FsToolkit.ErrorHandling/Seq.fs:144` 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:51— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:51-57 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:46-52 — 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 (7 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:61— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:61-67 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:56-62 — 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 (7 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:212— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:212-218 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:218-224 — 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.
Duplicated block (6 lines × 2) src/FsToolkit.ErrorHandling/TaskValidationCE.fs:570— src/FsToolkit.ErrorHandling/TaskValidationCE.fs:570-575 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:589-594 — 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.
Duplicated block (6 lines × 2) src/FsToolkit.ErrorHandling/ResultOption.fs:72— src/FsToolkit.ErrorHandling/ResultOption.fs:72-77 | src/FsToolkit.ErrorHandling/ResultOption.fs:95-100 — 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 (6 lines × 2) src/FsToolkit.ErrorHandling/AsyncResult.fs:307— src/FsToolkit.ErrorHandling/AsyncResult.fs:307-312 | src/FsToolkit.ErrorHandling/AsyncResult.fs:326-331 — 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.
Change coupling: TaskOptionCE.fs ↔ TaskResultCE.fs src/FsToolkit.ErrorHandling/TaskOptionCE.fs— `src/FsToolkit.ErrorHandling/TaskOptionCE.fs` and `src/FsToolkit.ErrorHandling/TaskResultCE.fs` change together 55% of the time (11 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Change coupling: AsyncResult.fs ↔ TaskResult.fs src/FsToolkit.ErrorHandling/AsyncResult.fs— `src/FsToolkit.ErrorHandling/AsyncResult.fs` and `src/FsToolkit.ErrorHandling/TaskResult.fs` change together 55% of the time (12 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×2
Medium CVE: [GHSA redacted] package-lock.json— @babel/helpers 7.16.3: [GHSA redacted] — @babel/helpers is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/helpers to 7.26.10 with an `overrides` entry).
Medium CVE: [GHSA redacted] package-lock.json— @babel/runtime 7.16.3: [GHSA redacted] — @babel/runtime is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/runtime to 7.26.10 with an `overrides` entry).
Duplicated block (29 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:618— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:618-647 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:731-759 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:618` 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 (29 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:851— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:851-879 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:851-879 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:851` 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 (28 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:244— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:244-271 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:249-276 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:244` 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 (28 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:698— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:698-725 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:881-908 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:698` 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 (25 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:662— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:662-691 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:792-816 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:662` 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 (25 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:622— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:622-651 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:735-759 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:622` 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 (21 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:396— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:396-416 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:483-503 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:396` 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 (21 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:173— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:173-193 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:168-188 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:173` 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 (20 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:654— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:654-673 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:824-843 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:654` 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 (20 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:658— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:658-677 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:824-843 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:658` 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 (19 lines × 4) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:182— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:182-200 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:175-193 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:175-193 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:170-188 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:182` 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 (19 lines × 4) src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:148— src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:148-166 | src/FsToolkit.ErrorHandling/ParallelAsyncResultCE.fs:56-74 | src/FsToolkit.ErrorHandling/AsyncResultCE.fs:58-76 | src/FsToolkit.ErrorHandling/AsyncOptionCE.fs:48-66 — 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 `src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:148` 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 (15 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:57— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:57-71 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:109-124 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:55-69 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:57` 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) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1274— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1274-1288 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1360-1374 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:95-109 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1274` 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 (14 lines × 4) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:1— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:1-14 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:1-14 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:1-14 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:1-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (14 lines × 4) src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:223— src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:223-236 | src/FsToolkit.ErrorHandling/TaskValidationCE.fs:219-232 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:225-238 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:218-231 — 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.
Duplicated block (14 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:460— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:460-473 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:547-560 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:587-600 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:460` 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 × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:798— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:798-811 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:855-868 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:798-811 — 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.
Duplicated block (12 lines × 3) src/FsToolkit.ErrorHandling/ValidationCE.fs:64— src/FsToolkit.ErrorHandling/ValidationCE.fs:64-75 | src/FsToolkit.ErrorHandling/ResultOptionCE.fs:64-75 | src/FsToolkit.ErrorHandling/ResultCE.fs:60-71 — 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 `src/FsToolkit.ErrorHandling/ValidationCE.fs:64` 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 (12 lines × 3) src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:61— src/FsToolkit.ErrorHandling/ParallelAsyncValidationCE.fs:61-72 | src/FsToolkit.ErrorHandling/AsyncValidationCE.fs:59-70 | src/FsToolkit.ErrorHandling/AsyncResultOptionCE.fs:85-100 — 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.
Medium CVE: System.Security.Cryptography.Xml 4.7.0 — System.Security.Cryptography.Xml 4.7.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Duplicated block (35 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:421— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:421-455 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:405-439 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:421` 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 (33 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:740— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:740-772 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:927-959 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:740` 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 (32 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:953— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:953-984 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1027-1058 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:953-984 — 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.
Duplicated block (29 lines × 6) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:564— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:564-592 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:677-705 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:602-630 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:731-760 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:568-596 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:681-709 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:564` 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 (27 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:793— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:793-819 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:985-1014 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:793` 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 (24 lines × 4) src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:242— src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:242-265 | src/FsToolkit.ErrorHandling/TaskValidationCE.fs:238-261 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:244-267 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:237-260 — 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 `src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:242` 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 (22 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:432— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:432-457 | src/FsToolkit.ErrorHandling/TaskValidation.fs:186-215 | src/FsToolkit.ErrorHandling/AsyncValidation.fs:120-141 — before extracting anything, compare `src/FsToolkit.ErrorHandling/TaskValidation.fs` and `src/FsToolkit.ErrorHandling/AsyncValidation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 104 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:432` 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 (22 lines × 2) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:222— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:222-243 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:574-595 — 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 (21 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:461— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:461-481 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:485-505 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:465-485 — 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.
Duplicated block (20 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1107— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1107-1126 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1166-1185 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:1088-1107 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1107` 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 (19 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:380— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:380-398 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:397-415 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:385-403 — 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.
Duplicated block (18 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1024— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:1024-1041 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:1101-1118 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:1025-1042 — 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.
Duplicated block (17 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:500— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:500-516 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:528-544 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:504-520 — 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 `src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:500` 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. 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 (15 lines × 4) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:484— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:484-498 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:611-625 | src/FsToolkit.ErrorHandling/TaskResultOptionCE.fs:104-119 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:597-611 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (13 lines × 5) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:105— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:105-117 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:193-205 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:159-172 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:100-112 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:182-194 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13 lines × 4) src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:196— src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:196-208 | src/FsToolkit.ErrorHandling/TaskValidationCE.fs:191-204 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:197-210 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:191-203 — 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 `src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:196` 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 (13 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:237— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:237-249 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:300-312 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:293-305 — 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.
Duplicated block (12 lines × 5) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:169— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:169-180 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:162-173 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:162-173 | src/FsToolkit.ErrorHandling/TaskValidationCE.fs:158-169 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:157-168 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (12 lines × 4) src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:542— src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:542-553 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:560-571 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:579-590 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:598-609 — all 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:542` 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. 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 × 7) src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:7— src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskResultCE.fs:7-16 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableValueTaskOptionCE.fs:7-16 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskValidationCE.fs:50-59 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultCE.fs:7-16 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskResultBuilderBase.fs:7-16 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionCE.fs:7-16 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOptionBuilderBase.fs:9-18 — 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. 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 × 4) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:315— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:315-324 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:441-450 | src/FsToolkit.ErrorHandling/TaskResultCE.fs:452-461 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:431-440 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (10 lines × 3) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:27— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:27-36 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:33-42 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:31-40 — 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.
Duplicated block (7 lines × 4) src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:424— src/FsToolkit.ErrorHandling.IcedTasks/ValueTaskValueOptionCE.fs:424-430 | src/FsToolkit.ErrorHandling.IcedTasks/CancellableTaskOption.fs:511-517 | src/FsToolkit.ErrorHandling/TaskValueOptionCE.fs:551-557 | src/FsToolkit.ErrorHandling/TaskOptionCE.fs:537-543 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Coverage not measured — analyzer environment — Coverage NOT MEASURED: the analyzer environment could not build/run this repository's test suite, whose production source is .fs. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, 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 and real coverage will be read.
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 (1416 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.
D19 · Documentation Quality· The README mentions FsToolkit.ErrorHandling targets .NET Standard 2.0, but there is no local development or build target documentation (e.g. how to develop locally). · ×1
The README mentions FsToolkit.ErrorHandling targets .NET Standard 2.0, but there is no local development or build target documentation (e.g. how to develop locally). README.md— Add a short Developing locally section describing the required SDK and how to run tests.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 11 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than listed individually (14 orphaned of 50 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).
Low CVE: [GHSA redacted] package-lock.json— @babel/core 7.16.0: [GHSA redacted] — this repo declares @babel/core ^7.15.4, a range that ALREADY admits the fixed 7.29.6, so there is no manifest edit to make here. Re-resolve the lock so @babel/core moves onto 7.29.6 or later; if the flagged 7.16.0 comes back, a dependency is pinning it — upgrade that dependent, or pin @babel/core with an `overrides` entry so only one copy resolves.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — no packages were read — This repository's projects (.fs) are MSBuild/NuGet projects and their `<PackageReference>` dependencies are exactly what this dimension assesses — but `dotnet list package` returned no packages for them, so there was nothing to assess. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED. This is a gap in the analysis run (restore or project-load failed for these projects), not a verdict about this repository.
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.
provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
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 019fd528-8b13-7f04-ad76-29fe72f85a10 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 27 · Warnings: 133 · Recommendations: 5 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 06-08-2026 @ 03:40 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.