Public report — ailab, published 5 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
148findings 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
60/108dimensions across the health lenses19379 LoC · 1 projects — 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.
microsoft/ailab carries serious gaps (43%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
The area that most needs attention is Readiness (20%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (58%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Run what this repository's stack ships (Security & performance tooling); tests that import the unreached modules (directly or through… (Test Coverage).
For scale: Small (~19,379 production lines); rebuilding it from scratch would take roughly ~0.2 person-years (~1 engineer). Approximate, ±~30%.
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.
~42 LoC unreachable (3 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~0.2 person-years of build effort (about ~€24,000 to rebuild). Its weakest lens is Readiness at 20% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.1) — desktop/game × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. 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
Add a CI workflow that builds and runs the test suite on every push/PR.
Run what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Value concentrated against a weak lens · High · Value at risk
This is a Small asset (~0.2 person-years to rebuild), and its weakest lens is Readiness at 20%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture — module dependency matrix
52 modules, 27 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
30
High / Critical
A03:2021 — Injection
26
High / Critical
A05:2021 — Security Misconfiguration
14
High / Critical
Roadmap
First, establish a continuous integration pipeline to build the code and run the test suite on every push or pull request. Next, integrate a security analyzer, such as Semgrep or CodeQL, into this workflow to ensure security regressions fail the build. Then, expand test coverage by adding tests for all currently unreached production modules. After that, configure tooling scripts for testing, linting, and type checking to run automatically in CI. Finally, implement a deployment gate, such as a draft release or manual approval step, to prevent bad builds from reaching users.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a CI workflow that builds and runs the test suite on every push/PR.
Run what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
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.
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. 58 of 60 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.7 — 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 — 60 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, 148 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
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D24 Comment Value — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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): D20, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AppManager.DeleteAsync at 22. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being KeyCombo.IsValidPrimaryKey at 20 — they are counted neither in the figure above nor in this dimension's score.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 AppManager.DeleteAsync (cognitive 35) finding(s) in Cognitive Complexity — start with AppManager.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 (anonymous) (cognitive 23) finding(s) in Cognitive Complexity — start with RichMessageLimitationsManager.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 OCRViewModel.GetLUISInsights (cognitive 22) finding(s) in Cognitive Complexity — start with OCRViewModel.cs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 10Exemplary✓ 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.
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.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with MainWindow.xaml.cs, AIPanelViewModel.cs, ToolWindow.xaml.cs. — One of this dimension's main actionable groups (6 warning-level).
Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
23 test methods: 23 unit, 0 integration, 0 BDD, 0 e2e.
Tests co-located / outside the solution
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality8.0 / 10Strong✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 23 tests.
No assertions: ShouldGetLayoutBorders · ×3Sketch2Code/Sketch2Code.Tests/ApplicationTests.cs:68
What to do
Resolve the 3 No assertions finding(s) in Test Quality — start with AITests.cs (2), ApplicationTests.cs. — One of this dimension's main actionable groups (3 warning-level).
Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
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 the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 EmptyCatchBlock finding(s) in Explicit Debt — start with RegistrySettings.cs (6), OCRViewModel.cs (2), AppManager.cs. — One of this dimension's main actionable groups (11 issue-level).
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with SnipInsight.Forms.csproj, SnipInsight.Forms.Tests.csproj. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 NoWarnInCsproj repeated 10 times in 2 files finding(s) in Explicit Debt — start with Speaker.Recorder.UWP.csproj. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
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: eval-detected · ×5Pix2Story/source/generation/skipthoughts.py:98detected by semgrep finding
Medium: react-dangerouslysetinnerhtml · ×18BuildAnIntelligentBot/src/ChatBot/wwwroot/built/FormattedText.js:56detected by semgrep finding
Low: httpsconnection-detected · ×3Pix2Story/source/preprocessing/text_moderator.py:19detected by semgrep finding
What to do
Resolve the 18 Medium finding(s) in Static Analysis (SAST) — start with tools.py (4), utils.py (3), vocab.py (3). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 5 High finding(s) in Static Analysis (SAST) — start with train.py (2), layers.py (2), skipthoughts.py. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 Low finding(s) in Static Analysis (SAST) — start with text_moderator.py, authadal.py, segmentation_deeplab.py. — One of this dimension's main actionable groups (3 recommendation-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.
High IaC: DS-0002 · ×3Pix2Story/source/config_deploy/Dockerfiledetected by trivy finding
Medium IaC: DS-0013 · ×7Pix2Story/source/config_deploy/Dockerfiledetected by trivy finding
Low IaC: KSV-0011 · ×4Pix2Story/source/config_deploy/nvidia.yamldetected by trivy finding
What to do
Resolve the 3 High IaC finding(s) in IaC & Container Security — start with Dockerfile (2), nvidia.yaml. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with nvidia.yaml (5), Dockerfile (2). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with nvidia.yaml (4). — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
162 of 162 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Snip-Insights/SnipInsight/AppManager.cs.
Largest orphaned file · ×3Snip-Insights/SnipInsight/AppManager.cs
Dormant codebase
What to do
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with AppManager.cs, NativeMethods.cs, RegistrySettings.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase 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 the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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] · ×15GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.jsondetected by osv-scanner finding
High vulnerability: [GHSA redacted]GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.jsondetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×6GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.jsondetected by osv-scanner finding
Medium vulnerability: [GHSA redacted]GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.jsondetected by osv-scanner finding
Low CVE: [GHSA redacted] · ×4GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 15 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (11), packages.config (4). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 6 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (3), packages.config (3). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No AppArmor/SELinux confinement finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C1 · Data Protection6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×6) — OCRControl.xaml.cs:60, FormatStringConverter.cs:25, NullToVisibilityConverter.cs:21, …
A placeholder string ("youremail@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — OCRViewModel.cs:526
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
`DeleteAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — AppManager.cs:917
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×29) — AIManager.cs:38, ImageAnalysisViewModel.cs:216, AppManager.cs:371, …
What to do
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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).
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
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 gates0.0 / 10Critical✓ 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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build.
What to do
Run what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
R1 · Type Safety8.5 / 10Strong✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:85 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:84 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — BasicCardMapper.js:85
JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.style.ts:16 · JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-node.style.ts:14 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — hocr-document.style.ts:16
JFKFiles/frontend/src/common/components/logo-jfk/svg.component.tsx:8 · JFKFiles/frontend/src/common/components/logo-microsoft/svg.component.tsx:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — svg.component.tsx:8
JFKFiles/frontend/src/common/components/pagination/pagination.tsx:103 · JFKFiles/frontend/src/common/components/pagination/pagination.tsx:127 — 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. — pagination.tsx:103
JFKFiles/frontend/src/pages/search-page/components/selection-controls/checkbox-list.component.tsx:16 · JFKFiles/frontend/src/pages/search-page/components/selection-controls/year-picker.component.tsx:15 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — checkbox-list.component.tsx:16
JFKFiles/frontend/src/az-api/api.ts:19 · JFKFiles/frontend/src/graph-api/api.ts:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — api.ts:19
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/MessagesManager.js:51 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/MessagesManager.js:69 — 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. — MessagesManager.js:51
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:22 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:70 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — BasicCardMapper.js:22
What to do
Extract the duplicated blocks into shared functions/components.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×5) — RichMessageLimitationsManager.js:20, payload.parser.ts:16, CarouselCardMapper.js:26, …
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
0% of 156 production file(s) reachable from 0 test file(s) via the import graph
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D33 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D33). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✗ · lint ✗ · typecheck ✗
What to do
Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
4 file(s) (~3439 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
Unreachable from the 4 application, 4 tooling and 0 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
no import path from any entry point (4 application, 4 tooling, 0 test roots considered) (×3) — conversationQueue.js, index.js, index.ts
Nothing ultimately consumes this binding: its only referrer is the re-export in JFKFiles/frontend/src/graph-api/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in JFKFiles/frontend/src/graph-api/index.ts in the same commit, or the barrel will import a name that no longer exists. — payload.model.ts:10
Nothing ultimately consumes this binding: its only referrer is the re-export in JFKFiles/frontend/src/util/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in JFKFiles/frontend/src/util/index.ts in the same commit, or the barrel will import a name that no longer exists. — log-debug.helper.ts:1
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — detail-page.container.tsx:2
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports3.6 / 10Weak✓ Tool-verified
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
JFKFiles/frontend/src/az-api/payload/filter.parser.ts → JFKFiles/frontend/src/az-api/payload/index.ts → JFKFiles/frontend/src/az-api/payload/filter.parser.ts (one verified cycle inside a mutually-dependent group of 3 files) — filter.parser.ts
JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx → JFKFiles/frontend/src/pages/detail-page/detail-page.memento.ts → JFKFiles/frontend/src/pages/detail-page/index.ts → JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx (one verified cycle inside a mutually-dependent group of 7 files) — detail-page.container.tsx
JFKFiles/frontend/src/pages/search-page/service/index.ts → JFKFiles/frontend/src/pages/search-page/service/service.model.ts → JFKFiles/frontend/src/pages/search-page/view-model/index.ts → JFKFiles/frontend/src/pages/search-page/view-model/state.model.ts → JFKFiles/frontend/src/pages/search-page/service/index.ts (one verified cycle inside a mutually-dependent group of 9 files) — index.ts
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
What to do
Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.
Only 0/31 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×25) — NewsHandler.cs:30, NewsHandler.cs:54, LUISInsights.cs:30, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`throw e;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. — HandWrittenTextHandler.cs:60
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×11) — OCRViewModel.cs:337, OCRViewModel.cs:359, OneNoteManager.cs:285, …
What to do
Rethrow loses stack trace (`throw ex;`)
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 48 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 user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C2 Access Controls — Partial workspace load — the web/host project 'CardsBot' present on disk did not load into the C# workspace (it failed to build/restore and was silently dropped), so its authorization signals were never scanned. The surviving documents carry no evidence for this control, but absence of evidence in an INCOMPLETE document set is not evidence the control is missing — the relevant middleware/attributes most plausibly live in the dropped project. This dimension is therefore Not-evidenced (excluded from the score) rather than asserting a confident negative. Restore/build that project (see diagnostics.md) so it loads and the dimension can be scored.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
D11 Test Reliability — Test reliability not included
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D19 Documentation Quality — LLM evaluation failed
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — At only 19379 LoC across a single project the codebase is trivially small despite having no bounded contexts declared, so boundaries are not needed.
D24 Comment Value — LLM evaluation failed
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check looks for
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
P12 CI test-gate honesty — no CI workflow found
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 applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
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 is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 — no NRT-eligible projects
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Issue — 41 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×15
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— axios 0.18.0: [GHSA redacted] — axios is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin axios to 0.18.1 with an `overrides` entry). This is 1 of 25 advisories with a published fix this scan raises against axios 0.18.0, and their fixed versions do not agree — anything below 0.33.0 still leaves at least one of them open. Take this package to 0.33.0 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 25 advisories this scan raises against axios 0.18.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— body-parser 1.18.3: [GHSA redacted] — this repo declares body-parser ^1.18.3, a range that ALREADY admits the fixed 1.20.3, so there is no manifest edit to make here. Re-resolve the lock so body-parser moves onto 1.20.3 or later; if the flagged 1.18.3 comes back, a dependency is pinning it — upgrade that dependent, or pin body-parser with an `overrides` entry so only one copy resolves. This is 1 of 2 advisories with a published fix this scan raises against body-parser 1.18.3, and their fixed versions do not agree — anything below 1.20.6 still leaves at least one of them open. Take this package to 1.20.6 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 2 advisories this scan raises against body-parser 1.18.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— follow-redirects 1.7.0: [GHSA redacted] — follow-redirects is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin follow-redirects to 1.14.7 with an `overrides` entry). This is 1 of 5 advisories with a published fix this scan raises against follow-redirects 1.7.0, and their fixed versions do not agree — anything below 1.16.0 still leaves at least one of them open. Take this package to 1.16.0 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 5 advisories this scan raises against follow-redirects 1.7.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— jws 3.2.2: [GHSA redacted] — jws is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin jws to 3.2.3 with an `overrides` entry). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
High CVE: [GHSA redacted] Sketch2Code/Sketch2Code.AI/packages.config— Microsoft.Data.OData 5.8.2: [GHSA redacted] — upgrade to 5.8.4 (in 3 dependency files: Sketch2Code/Sketch2Code.AI/packages.config, Sketch2Code/Sketch2Code.Core/packages.config, Sketch2Code/Sketch2Code.Web/packages.config)
High CVE: [GHSA redacted] JFKFiles/JfkWebApiSkills/JfkInitializer/packages.config— Newtonsoft.Json 10.0.2: [GHSA redacted] — upgrade to 13.0.1
High CVE: [GHSA redacted] Sketch2Code/Sketch2Code.AI/packages.config— Newtonsoft.Json 9.0.1: [GHSA redacted] — upgrade to 13.0.1 (in 3 dependency files: Sketch2Code/Sketch2Code.AI/packages.config, Sketch2Code/Sketch2Code.Core/packages.config, Sketch2Code/Sketch2Code.Web/packages.config)
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— node-fetch 2.3.0: [GHSA redacted] — this repo declares node-fetch ^2.3.0, a range that ALREADY admits the fixed 2.6.7, so there is no manifest edit to make here. Re-resolve the lock so node-fetch moves onto 2.6.7 or later; if the flagged 2.3.0 comes back, a dependency is pinning it — upgrade that dependent, or pin node-fetch with an `overrides` entry so only one copy resolves. This is 1 of 2 advisories with a published fix this scan raises against node-fetch 2.3.0, and their fixed versions do not agree — anything below 2.6.7 still leaves at least one of them open. Take this package to 2.6.7 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 2 advisories this scan raises against node-fetch 2.3.0: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— node-forge 0.8.2: [GHSA redacted] — node-forge is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 1.4.0 is a MAJOR ahead of the resolved 0.8.2, so an `overrides` pin would force a breaking version under a dependent written against 0.8.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 15 advisories this scan raises against node-forge 0.8.2: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— path-to-regexp 0.1.7: [GHSA redacted] — path-to-regexp is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin path-to-regexp to 0.1.13 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against path-to-regexp 0.1.7, and their fixed versions do not agree — anything below 0.1.13 still leaves at least one of them open. Take this package to 0.1.13 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 2 advisories this scan raises against path-to-regexp 0.1.7: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— qs 6.5.2: [GHSA redacted] — qs is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the ^6.5.1 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (or pin qs to 6.5.3 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against qs 6.5.2, and their fixed versions do not agree — anything below 6.14.1 still leaves at least one of them open. Take this package to 6.14.1 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 2 advisories this scan raises against qs 6.5.2: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— qs 6.7.0: [GHSA redacted] — qs is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the ^6.5.1 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (or pin qs to 6.7.3 with an `overrides` entry). This is 1 of 3 advisories with a published fix this scan raises against qs 6.7.0, and their fixed versions do not agree — anything below 6.14.2 still leaves at least one of them open. Take this package to 6.14.2 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 3 advisories this scan raises against qs 6.7.0: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— semver 5.7.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 5.7.2 with an `overrides` entry). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
High CVE: [GHSA redacted] Sketch2Code/Sketch2Code.AI/packages.config— System.Net.Http 4.3.3: [GHSA redacted] — upgrade to 4.3.4 (in 2 dependency files: Sketch2Code/Sketch2Code.AI/packages.config, Sketch2Code/Sketch2Code.Web/packages.config)
High CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— ws 6.2.1: [GHSA redacted] — this repo declares ws ^6.1.4, a range that ALREADY admits the fixed 6.2.3, so there is no manifest edit to make here. Re-resolve the lock so ws moves onto 6.2.3 or later; if the flagged 6.2.1 comes back, a dependency is pinning it — upgrade that dependent, or pin ws with an `overrides` entry so only one copy resolves. This is 1 of 3 advisories with a published fix this scan raises against ws 6.2.1, and their fixed versions do not agree — anything below 6.2.4 still leaves at least one of them open. Take this package to 6.2.4 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 3 advisories this scan raises against ws 6.2.1: [GHSA redacted], [GHSA redacted], [GHSA redacted].
EmptyCatchBlock Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:337— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:359— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/AppManager.cs:215— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/SendTo/OneNoteManager.cs:285— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:25— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:793— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:817— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:837— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:861— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:881— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:905— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
High: eval-detected Pix2Story/source/generation/skipthoughts.py:98— Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by external sources. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High: eval-detected Pix2Story/source/skipthoughts_vectors/decoding/train.py:132— Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by external sources. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High: eval-detected Pix2Story/source/skipthoughts_vectors/encdec_functs/layers.py:16— Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by external sources. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High: eval-detected Pix2Story/source/skipthoughts_vectors/encdec_functs/layers.py:36— Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by external sources. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High: eval-detected Pix2Story/source/skipthoughts_vectors/training/train.py:128— Detected the use of eval(). eval() can be dangerous if used to evaluate dynamic content. If this content can be input from outside the program, this may be a code injection vulnerability. Ensure evaluated content is not definable by external sources. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High CVE: Microsoft.Data.OData 5.6.2 — Microsoft.Data.OData 5.6.2 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted] — upgrade to 5.8.4
High CVE: Newtonsoft.Json 10.0.3 — Newtonsoft.Json 10.0.3 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted] — upgrade to 13.0.1
High CVE: System.Net.Http 4.3.3 — System.Net.Http 4.3.3 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted] — upgrade to 4.3.4
High IaC: DS-0002 Pix2Story/source/config_deploy/Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN adduser --system --no-create-home app`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0029 Pix2Story/source/config_deploy/Dockerfile— 'apt-get' missing '--no-install-recommends'
High IaC: KSV-0014 Pix2Story/source/config_deploy/nvidia.yaml— Root file system is not read-only
NoWarnInCsproj Snip-Insights/SnipInsight.Forms/SnipInsight.Forms.csproj:4— NU1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Snip-Insights/SnipInsight.Forms.Tests/SnipInsight.Forms.Tests.csproj:4— NU1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
D17 · Explicit Debt· NoWarnInCsproj repeated 10 times in 2 files · ×1
NoWarnInCsproj repeated 10 times in 2 files VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP/Speaker.Recorder.UWP.csproj:26— The identical NoWarnInCsproj (`2008`) appears 10 times in 2 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 10 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— googleapis 27.0.0: [GHSA redacted] — googleapis is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 39.1.0 is a MAJOR ahead of the resolved 27.0.0, so an `overrides` pin would force a breaking version under a dependent written against 27.0.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
TodoComment Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs:70— //TODO: After Refactoring Log results status and api run time — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:655— // TODO: monitor process of exit code (for telemetry) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:678— // TODO: Make a shortcut for this panel — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1145— //TODO: Delete packages — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1304— //TODO: Delete package — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1633— // TODO: Fix the attachment name — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1687— // TODO: Check which OneNote function is used — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/ImageCapture/SmartBoundaryDetection.cs:201— //TODO(qiazhang) should we return the smallest window? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Ink/AcetateLayerInkCanvas.cs:21— // TODO: Fix Ink Cursor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Package/SnipInsightLink.cs:98— //TODO: Need to add to resoure since date format can be different in other countries. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Package/SnipInsightLink.cs:110— // TODO: Need to add to resource. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:39— // TODO: Log generic user events — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:44— // TODO : Log clicks on UI elements by users — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:49— // TODO : Log web request to AI services — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:57— // TODO : Log transition of states in application. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:65— //TODO: Initialize the or set the logging module to be used to gather user telemetry — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/TrayIcon.cs:20— // TODO: Update the tray icon — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/ViewModels/ViewModelLocator.cs:62— // TODO Clear the ViewModels — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Snip-Insights/SnipInsight/Views/ControlTreeEnumerator.cs:55— // TODO: Can't find a way to get to the children of a UserControl... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Medium: react-dangerouslysetinnerhtml BuildAnIntelligentBot/src/ChatBot/wwwroot/built/FormattedText.js:56— Detection of dangerouslySetInnerHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use dangerouslySetInnerHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/generation/decoder.py:22— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/generation/decoder.py:33— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/generation/embedding.py:23— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/generation/embedding.py:34— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/generation/skipthoughts.py:31— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/decoding/tools.py:25— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/decoding/tools.py:38— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/encdec_functs/utils.py:159— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/encdec_functs/utils.py:179— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/encdec_functs/utils.py:219— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/encdec_functs/vocab.py:35— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/encdec_functs/vocab.py:43— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/encdec_functs/vocab.py:44— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/training/tools.py:30— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/skipthoughts_vectors/training/tools.py:43— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/training/train_encoder.py:15— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: avoid-pickle Pix2Story/source/training/train_encoder.py:21— Avoid using `pickle`, which is known to lead to code execution vulnerabilities. When unpickling, the serialized data could be manipulated to run arbitrary code. Instead, consider serializing the relevant data as JSON or a similar text-based serialization format. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium IaC: DS-0013 Pix2Story/source/config_deploy/Dockerfile— 'RUN cd ...' to change directory
Medium IaC: KSV-0012 Pix2Story/source/config_deploy/nvidia.yaml— Runs as root user One securityContext edit clears this facet's near-duplicate rules together: KSV-0012, KSV-0020, KSV-0021.
Medium IaC: KSV-0023 Pix2Story/source/config_deploy/nvidia.yaml— hostPath volumes mounted
Medium IaC: KSV-0104 Pix2Story/source/config_deploy/nvidia.yaml— Seccomp policies disabled One securityContext edit clears this facet's near-duplicate rules together: KSV-0030, KSV-0104.
Medium IaC: KSV-0125 Pix2Story/source/config_deploy/nvidia.yaml— Restrict container images to trusted registries
Medium IaC: CKV_K8S_8 Pix2Story/source/config_deploy/nvidia.yaml:1— Liveness Probe Should be Configured
Medium IaC: CKV_DOCKER_3 Pix2Story/source/config_deploy/Dockerfile:1— Ensure that a user for the container has been created
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×6
Medium CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— @babel/runtime 7.4.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). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
Medium CVE: [GHSA redacted] Sketch2Code/Sketch2Code.Web/packages.config— bootstrap 4.1.1: [GHSA redacted] — upgrade to 4.1.2. This is 1 of 4 advisories with a published fix this scan raises against bootstrap 4.1.1, and their fixed versions do not agree — anything below 4.3.1 still leaves at least one of them open. Take this package to 4.3.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against bootstrap 4.1.1: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— express 4.16.4: [GHSA redacted] — this repo declares express ^4.16.4, a range that ALREADY admits the fixed 4.19.2, so there is no manifest edit to make here. Re-resolve the lock so express moves onto 4.19.2 or later; if the flagged 4.16.4 comes back, a dependency is pinning it — upgrade that dependent, or pin express with an `overrides` entry so only one copy resolves. This is 1 of 2 advisories with a published fix this scan raises against express 4.16.4, and their fixed versions do not agree — anything below 4.20.0 still leaves at least one of them open. Take this package to 4.20.0 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json) This one row stands for the 2 advisories this scan raises against express 4.16.4: [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] Sketch2Code/Sketch2Code.Web/packages.config— jQuery 3.0.0: [GHSA redacted] — upgrade to 3.4.0. This is 1 of 2 advisories with a published fix this scan raises against jQuery 3.0.0, and their fixed versions do not agree — anything below 3.5.0 still leaves at least one of them open. Take this package to 3.5.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 jQuery 3.0.0: [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] JFKFiles/JfkWebApiSkills/JfkInitializer/packages.config— Microsoft.Rest.ClientRuntime 2.3.11: [GHSA redacted] — upgrade to 2.3.24 (in 3 dependency files: JFKFiles/JfkWebApiSkills/JfkInitializer/packages.config, Sketch2Code/Sketch2Code.AI/packages.config, Sketch2Code/Sketch2Code.Core/packages.config)
Medium CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— uuid 3.3.2: [GHSA redacted] — upgrade to 11.1.1 (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
Low cohesion: MainWindow (LCOM4 10) Snip-Insights/SnipInsight/Views/MainWindow.xaml.cs:20— MainWindow's methods form 10 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AIPanelViewModel (LCOM4 6) Snip-Insights/SnipInsight/ViewModels/AIPanelViewModel.cs:12— AIPanelViewModel's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ToolWindow (LCOM4 6) Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:23— ToolWindow's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AppManager (LCOM4 5) Snip-Insights/SnipInsight/AppManager.cs:38— AppManager's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ImageCaptureWindow (LCOM4 4) Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:21— ImageCaptureWindow's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: LibraryPanel (LCOM4 4) Snip-Insights/SnipInsight/Views/LibraryPanel.xaml.cs:19— LibraryPanel's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
No assertions: ShouldGetLayoutBorders Sketch2Code/Sketch2Code.Tests/ApplicationTests.cs:68— Test method exercises code but verifies nothing — add an assertion.
No assertions: ShouldPredictImage Sketch2Code/Sketch2Code.Tests/AITests.cs:46— Test method exercises code but verifies nothing — add an assertion.
No assertions: ShouldExportResults Sketch2Code/Sketch2Code.Tests/AITests.cs:77— Test method exercises code but verifies nothing — add an assertion.
TooManyMethods: AppManager Snip-Insights/SnipInsight/AppManager.cs:0— TooManyMethods — 970 significant lines (blank, comment-only and punctuation-only lines excluded), 101 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: ToolWindow Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:0— TooManyMethods — 298 significant lines (blank, comment-only and punctuation-only lines excluded), 38 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: AnimationUtilities Snip-Insights/SnipInsight/Util/AnimationUtilities.cs:0— TooManyMethods — 118 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
BareSuppressMessage Snip-Insights/SnipInsight/StateMachine/SnipInsightTrigger.cs:7— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage Snip-Insights/SnipInsight/Util/LogUploader.cs:189— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
FileTooLong: SnipInsight/AppManager.cs Snip-Insights/SnipInsight/AppManager.cs:0— FileTooLong — 1005 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: Util/NativeMethods.cs Snip-Insights/SnipInsight/Util/NativeMethods.cs:0— FileTooLong — 646 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 (9 lines × 2) Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:247— Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:247-255 | Snip-Insights/SnipInsight/Util/WinMessage.cs:38-46 — 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 `Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:247` 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) Snip-Insights/SnipInsight/Util/DpiUtilities.cs:287— Snip-Insights/SnipInsight/Util/DpiUtilities.cs:287-297 | Snip-Insights/SnipInsight/ImageCapture/DpiScalor.cs:32-40 — 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 `Snip-Insights/SnipInsight/Util/DpiUtilities.cs:287` 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. 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.
AppManager.DeleteAsync (cyclomatic 22) Snip-Insights/SnipInsight/AppManager.cs:917— AppManager.DeleteAsync has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OCRViewModel.GetLUISInsights (cyclomatic 20) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:435— OCRViewModel.GetLUISInsights has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 20) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:20— (anonymous) has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
dormant codebase — no living knowledge left to concentrate — All 2 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
Monorepo: only 1 of 9 solutions was scored — This repository contains 9 .NET solutions, but a scan analyzes ONE. Every score, lens, and finding here reflects only `Snip-Insights/SnipInsights.WPF.sln` — the other 8 (`BuildAnIntelligentBot/src/TalkToMyBot.sln`, `GoogleAssistantConnector/DemoBot/DemoBot.sln`, `GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy.sln`, `JFKFiles/JfkWebApiSkills/JfkWebApiSkills.sln`, `Sketch2Code/Sketch2Code.sln`, `Snip-Insights/SnipInsights.GTK.MacOS.sln`, +2 more) were not analyzed and are not represented in the headline. To cover them, scan each solution as its own target and group them in a Solution or Product for a portfolio roll-up. If a secondary solution is an archived or vendored tree, declare it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — to exclude it from discovery the same way generated code is.
D18 · Solution Shape· Analyzed solution does not cover the bulk of the repository · ×1
Analyzed solution does not cover the bulk of the repository — The scored solution `Snip-Insights/SnipInsights.WPF.sln` is not representative of this repository — it references only 161 of 505 discovered C# files (32 %). Lenses that need the product's source (domain modelling, event-driven, event sourcing) abstain because the aggregates, EF configs, and domain events under the product tree were not loaded. Point the scan at the product solution (or scan its directory directly) so the whole codebase is analyzed, not a build-tooling sub-solution.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[0].suggestion | LineNumber: 0 | BytePositionInLine: 1058.
AppManager.DeleteAsync (cognitive 35) Snip-Insights/SnipInsight/AppManager.cs:917— AppManager.DeleteAsync has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 23) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:20— (anonymous) has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OCRViewModel.GetLUISInsights (cognitive 22) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:435— OCRViewModel.GetLUISInsights has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
compact (cognitive 22) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:11— compact has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LogUploader.Send (cognitive 21) Snip-Insights/SnipInsight/Util/LogUploader.cs:113— LogUploader.Send has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AriModernWindow.OnApplyTemplate (cognitive 18) Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:32— AriModernWindow.OnApplyTemplate has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImageAnalysisViewModel.GetCelebrities (cognitive 17) Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:170— ImageAnalysisViewModel.GetCelebrities has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OCRViewModel.CompareResult (cognitive 16) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:326— OCRViewModel.CompareResult has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ToolWindow.OnIsOpenChanged (cognitive 16) Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:163— ToolWindow.OnIsOpenChanged has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SmartBoundaryDetection.GetTopElement (cognitive 16) Snip-Insights/SnipInsight/ImageCapture/SmartBoundaryDetection.cs:105— SmartBoundaryDetection.GetTopElement has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.notable[4] | LineNumber: 0 | BytePositionInLine: 884.
D38 · OSV Dependency Vulnerabilities· Medium vulnerability · ×1
Medium vulnerability: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— https-proxy-agent 2.2.1: [GHSA redacted] — https-proxy-agent is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin https-proxy-agent to 2.2.3 with an `overrides` entry). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
Duplicated block (10 lines × 2) Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:121— Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:121-130 | Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:98-107 — 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 `Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:133— Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:133-140 | Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:160-167 — 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 `Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:133` 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.
Coverage not measured — analyzer environment — Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). 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, no coverage collector was found in your CI either, so there is no existing report to hand us — add a collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and real coverage will be read.
Low CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— cookie 0.3.1: [GHSA redacted] — cookie is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin cookie to 0.7.0 with an `overrides` entry). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
Low CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— debug 3.2.6: [GHSA redacted] — debug is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin debug to 3.2.7 with an `overrides` entry). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
Low CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— send 0.16.2: [GHSA redacted] — send is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin send to 0.19.0 with an `overrides` entry). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
Low CVE: [GHSA redacted] GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json— serve-static 1.13.2: [GHSA redacted] — serve-static is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin serve-static to 1.16.0 with an `overrides` entry). (in 2 dependency files: GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/package-lock.json, GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy/package-lock.json)
Low: httpsconnection-detected Pix2Story/source/preprocessing/text_moderator.py:19— The HTTPSConnection API has changed frequently with minor releases of Python. Ensure you are using the API for your version of Python securely. For example, Python 3 versions prior to 3.4.3 will not verify SSL certificates by default. See https://docs.python.org/3/library/http.client.html#http.client.HTTPSConnection for more information. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Low: httpsconnection-detected Pix2Story/source/services/authadal.py:28— The HTTPSConnection API has changed frequently with minor releases of Python. Ensure you are using the API for your version of Python securely. For example, Python 3 versions prior to 3.4.3 will not verify SSL certificates by default. See https://docs.python.org/3/library/http.client.html#http.client.HTTPSConnection for more information. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Low: dynamic-urllib-use-detected VirtualStage/BackgroundMatting/segmentation_deeplab.py:154— Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control the URLs, or consider using the 'requests' library instead. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
D34 · Knowledge Freshness· Largest orphaned file · ×3
Largest orphaned file Snip-Insights/SnipInsight/AppManager.cs— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file Snip-Insights/SnipInsight/Util/NativeMethods.cs— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file Snip-Insights/SnipInsight/Util/RegistrySettings.cs— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — No test suite was found, so reliability couldn't be assessed.
Split SnipInsight — A generic catch-all name that is huge (20k LoC) and sprawls over 19 unrelated namespaces. Suggested: by namespace: SnipInsights/Text, SnipInsights/Analysis, SnipInsights/Reporting
Dormant codebase — 162 of 162 significant files have no living knowledge — the codebase as a whole is dormant, not 162 separate risks. Re-engage owners or document before change.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No seccomp profile — Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No AppArmor/SELinux confinement — Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
Info — 3 finding(s)
D18 · Solution Shape· Build did not complete in the analyzer · ×1
Build did not complete in the analyzer — `dotnet build` reported 1 error(s) but no C# compiler diagnostic, so this is a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. Worth checking on your side too: a build that needs undeclared host tooling, or that cannot run off its own platform, is the same wall a new contributor hits.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
D9 · Test Distribution· Tests co-located / outside the solution · ×1
Tests co-located / outside the solution — 23 test method(s) were found on disk (co-located in feature projects, or outside the analyzed solution) rather than in dedicated test projects, so the unit/integration/E2E pyramid can't be classified — they're counted as one undifferentiated suite.
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 — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
0
—
Run 019fd241-5869-7cdb-8597-1aa0074e5f1b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 13 field(s) across 3 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by name with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 41 · Warnings: 102 · Recommendations: 21 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 05-08-2026 @ 14:08 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.