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.
th3hunt/cloud-native-hexagonal-node carries serious gaps (47%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Domain Modelling (100%) — the domain model is expressive and well-guarded. Security (80%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (32%) — 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. Code Health (47%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); readiness/liveness probes and a rolling-update (or blue/green)… (Deployment & Rollback); `tsc --noEmit` as package.json scripts and run them in CI (Tooling).
For scale: Hobby (~628 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Domain Modelling foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
Code Health
47%
Weak · gated by R1, R7
Architecture
69%
Adequate
Maturity
67%
Adequate · gated by M2
Readiness
32%
Weak · gated by P1, P3
Security
80%
Adequate · gated by D38
Domain Modelling
100% ★
Exemplary
How the score is built — each lens's share of the headline
Width 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.
Readiness 32% · 46% weightCode Health 47% · 25% weightMaturity 67% · 14% weightArchitecture 69% · 8% weightSecurity 80% · 4% weightDomain Modelling 100% · 2% weight
Raise Readiness 32 → 70 (the Healthy floor) ⇒ headline 47 → ~60.
New since the last scan (21+)
- D38 · Critical CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · High CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
- D38 · Medium CVE: [GHSA redacted] yarn.lock
Rebuild cost & value ~ Modeled — €190–€950
| Cost to rebuild | €190–€950 |
| Domain complexity | Standard |
| Quality factor | 0.7× (at 47% quality) |
| Size & shape | Hobby · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk) |
| Dead frontend code | ~232 LoC unreachable (10 file(s)) |
Top priorities
1
Add a CI workflow that builds and runs the test suite on every push/PR.
2
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
3
Add `tsc --noEmit` as package.json scripts and run them in CI.
Diagnosis — what's actually going on
Highest-leverage move
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.
At a glance — Code Health
The Good
At a glance — Architecture
At a glance — Maturity
The Good
At a glance — Readiness
At a glance — Security
The Good
At a glance — Domain Modelling
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A06:2021 — Vulnerable & Outdated Components | 50 | High / Critical |
Roadmap
First, establish a continuous integration workflow to build and test every change. Next, implement health checks and automated rollback strategies to ensure safe deployments. Then, enforce type checking in the CI pipeline by adding and running type-checking scripts. After that, clean up the project by removing unused dependencies and explicitly declaring all imports. Finally, migrate all remaining JavaScript files to TypeScript to improve type safety.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +14.2 pts | Medium | CI/CD gates |
| Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically. | +13.4 pts | Medium | Deployment & Rollback |
| Add `tsc --noEmit` as package.json scripts and run them in CI. | +11.6 pts | Medium | Tooling |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +9.5 pts | Medium | Dependency Hygiene |
| Migrate the remaining .js/.jsx files to TypeScript. | +7.1 pts | Medium | Type Safety |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +7.1 pts | Medium | Dead Code |
| Start an ADR log (docs/adr/) recording significant decisions and their rationale. | +2.0 pts | Medium | Architecture documentation |
| Improve Documentation Quality — currently 4.0/10. | +1.8 pts | Medium | Documentation Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| yarn.lock | 0.2 | Slop | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
Methodology & how to trust this report
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. 28 of 30 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.4 — 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.
What we checked — 30 dimensions across the health lenses
D1D2D3D4D13D15D19D21D28D29D31D33D35D38DM6M1M2M3M4P1P3P4R1R10R2R3R6R7R8R9
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, 50 of 58 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| jscpd | Code duplication | — | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.302 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.302 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | Local LLM | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
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
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
- D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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".
The LLM boundary
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
Do you agree with this assessment?
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
Do you agree with this assessment?
D3 · God Classes
0 god class(es) detected.
Do you agree with this assessment?
D4 · Code Duplication
0 duplicated block group(s) detected.
Do you agree with this assessment?
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
Do you agree with this assessment?
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
git history depth insufficient
Do you agree with this assessment?
D19 · Documentation Quality
The single README is a solid WIP boilerplate doc for a hexagonal Node.js microservice. It names the architecture (hexagonal), explains it in terms of use cases and ports/adapters, lists a TODO list that covers domain logic, MongoDB/Postgres/Kafka/GRPC adapters, tests, tracing, and build commands, and documents JS and API docs via yarn commands. However, there is no separate architecture or design doc for the hexagonal structure itself (ports/adapters per use case), so readers cannot tell which adapter belongs to which use case without reading the boilerplate code.
What to do
- Improve Documentation Quality — currently 4.0/10. — The single README is a solid WIP boilerplate doc for a hexagonal Node.js microservice. It names the architecture (hexagonal), explains it in terms of use cases and ports/adapters, lists a TODO list that covers domain logic, MongoDB/Postgres/Kafka/GRPC adapters, tests, tracing, and build commands, and documents JS and API docs via yarn commands. However, there is no separate architecture or design doc for the hexagonal structure itself (ports/adapters per use case), so readers cannot tell which adapter belongs to which use case without reading the boilerplate code.
Do you agree with this assessment?
D21 · Naming Consistency
0 naming inconsistencies across 0 sampled symbols.
Do you agree with this assessment?
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
Do you agree with this assessment?
D29 · Static Analysis (SAST)
semgrep found no security issues.
Do you agree with this assessment?
D31 · IaC & Container Security
trivy found no infrastructure-as-code or container misconfigurations.
Do you agree with this assessment?
D33 · JS/npm Dependency Vulnerabilities
No known-vulnerable JS/npm dependencies.
Do you agree with this assessment?
D35 · Change Coupling
No strong hidden change-coupling between production files.
git history depth insufficient
Do you agree with this assessment?
D38 · OSV Dependency Vulnerabilities
60 finding(s): 11 critical, 30 high, 16 medium, 3 low.
High CVE: [GHSA redacted] yarn.lock
Critical CVE: [GHSA redacted] yarn.lock
High vulnerability: [GHSA redacted]yarn.lock
Medium CVE: [GHSA redacted] yarn.lock
What to do
- Resolve the 29 High CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (29). — One of this dimension's main actionable groups (29 issue-level).
- Resolve the 11 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 1 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock. — One of this dimension's main actionable groups (1 issue-level).
Do you agree with this assessment?
Frontend & cross-cutting dimensions
DM6 · Domain ↔ infrastructure boundary
Do you agree with this assessment?
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Do you agree with this assessment?
M2 · Architecture documentation
- No Architecture Decision Records found — decisions aren't captured for future maintainers.
What to do
- Start an ADR log (docs/adr/) recording significant decisions and their rationale.
Do you agree with this assessment?
M3 · Folder & project structure
Do you agree with this assessment?
M4 · Documentation accuracy
Do you agree with this assessment?
P1 · CI/CD gates
- 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?
P3 · Security & performance tooling
- No static application security testing detected (CodeQL, or your ecosystem's scanner — CodeQL's csharp pack (which analyses VB.NET too — F# is not a CodeQL language, so an F# project's option is `semgrep --config=auto`) or a security analyzer package for .NET, cargo-audit/cargo-deny (or clippy) for Rust, sobelow for Elixir/Phoenix, brakeman for Ruby/Rails, spotbugs/find-sec-bugs for Java/Kotlin, scalafix/scapegoat for Scala/sbt, bandit or `semgrep --config=p/python` (or CodeQL's python pack) for Python, phpstan/psalm for PHP, gosec/govulncheck (or golangci-lint) for Go, dialyzer/elvis for Erlang/OTP, CodeQL's Swift pack for Swift/Xcode, CodeQL's javascript-typescript pack or eslint-plugin-security for JS/TS, semgrep for any).
What to do
- Add a SAST step running whatever your ecosystem ships: CodeQL, semgrep, CodeQL's csharp pack (C#/VB.NET, with `semgrep --config=auto` for F#), `cargo audit`/`cargo deny` or `cargo clippy -- -D warnings` (Rust), sobelow (Elixir/Phoenix), brakeman (Ruby/Rails), spotbugs/find-sec-bugs (Java/Kotlin), scalafix/scapegoat (Scala/sbt), bandit or `semgrep --config=p/python` (Python), phpstan/psalm (PHP), gosec/govulncheck or golangci-lint (Go), dialyzer/elvis via rebar3_lint (Erlang/OTP), CodeQL's Swift pack (Swift/Xcode), or a security analyzer package.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Do you agree with this assessment?
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
R1 · Type Safety
- 0 typed · 23 plain JS
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
Do you agree with this assessment?
R10 · Code Duplication
Do you agree with this assessment?
R2 · Cyclomatic Complexity
Do you agree with this assessment?
R3 · Large Files
Do you agree with this assessment?
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code
- Unreachable from the 4 application, 2 tooling and 1 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, 2 tooling, 1 test roots considered) (×7) — handler.js, command.js, index.js, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Do you agree with this assessment?
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — index.js:2
- Declared in the root/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing.
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 Imports
Do you agree with this assessment?
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 47% | Weak — gated by R1, R7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69% | Adequate | Acceptable, with room to improve. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Adequate — gated by D38 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
Not included — 82 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX10 Code composition — not assessed — code composition is computed by ROLE over the .NET document set and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — no singleton implementations detected
- AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from the .NET project graph (projects, types, namespaces) and no such graph was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over the .NET type surface and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — not assessed — test isolation is computed from the .NET project graph (which projects are test projects, and what they reference) and no such graph was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — no data
- C1 Data Protection — Not assessed: these personal data controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — Not assessed: these audit controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~0 lines of test source are present (.js) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included
- D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
- D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D22 Internal API Consistency — No exposed public API
- D23 Boundary Type-Coupling — Zero projects and zero LoC make this an empty stub rather than a real codebase needing boundaries.
- D24 Comment Value — No inline comments to assess — comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (package.json — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
- D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
- D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
- D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.js) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Aggregate boundaries — not scored for TypeScript: a class holding another class reads the same whether the inner type is an aggregate or a value object, so this cannot be decided from source without guessing — reported as guidance rather than measured
- DM2 Strongly-typed ids — not scored for TypeScript: branded ids (`type Id = string & { __brand }`) are an uncommon idiom, so a bare-string id is not on its own evidence of a missing typed id — reported as guidance rather than measured
- DM3 Integration-event coupling — not scored for TypeScript: a domain type used across packages is indistinguishable in source from a deliberate shared-kernel package, so this is reported as guidance rather than measured
- DM4 Rich vs anemic model — not scored for TypeScript: telling a rich domain entity from an anemic data holder needs the behaviour a source-only read cannot always attribute (components, DTOs and readonly value objects are all legitimately data-shaped), so this is reported as guidance rather than measured
- DM5 Encapsulated state — not scored for TypeScript: the language already steers state behind #private/private/readonly, so a mutable public field is rare enough that we report this as guidance rather than measuring it
- DM7 Repository granularity — not scored for TypeScript: deciding whether a repository belongs to an aggregate root needs the aggregate structure, which source alone does not state — reported as guidance rather than measured
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
- GD1 Unfinished & placeholder code — no source files
- IC1 Incompleteness & stubs — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference (.NET: C#, VB.NET and F# alike), lcov — `swift test --enable-code-coverage` or `xcodebuild -enableCodeCoverage YES` then `xcrun llvm-cov export -format=lcov` (Swift/Xcode), `cargo llvm-cov --lcov`, `go test -coverprofile`, `rebar3 do eunit --cover, cover` or covertool (Erlang/BEAM), `flutter test --coverage` or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov` (Dart/Flutter), `sbt clean coverage test coverageReport` via sbt-scoverage (Scala/sbt), jest/nyc, JaCoCo/Cobertura XML, coverage.py … most ecosystems' coverage tools can emit one) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 1 test file(s) reach none of 22 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D33 (JS/npm Dependency Vulnerabilities)
- S1 Web-Security Posture — Not assessed: these web-security controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — no data
- X1 Async correctness — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- X3 Exception handling — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- X4 Structured logging — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
Issue — 41 finding(s)
D38 · OSV Dependency Vulnerabilities
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
- High CVE: [GHSA redacted] yarn.lock
D38 · OSV Dependency Vulnerabilities
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
- Critical CVE: [GHSA redacted] yarn.lock
D38 · OSV Dependency Vulnerabilities
- High vulnerability: [GHSA redacted] yarn.lock
Warning — 10 finding(s)
D38 · OSV Dependency Vulnerabilities
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
- Medium CVE: [GHSA redacted] yarn.lock
D16 · Bus Factor
- single-maintainer — knowledge-concentration (bus factor) risk
Recommendation — 3 finding(s)
D11 · Test Reliability
- Test reliability not included
D34 · Knowledge Freshness
- early-stage repository — too little history to judge knowledge freshness
D8 · Code Coverage
- Coverage not included — suite not readable by the collector
Info — 4 finding(s)
D12 · Dependency Hygiene
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D15 · Churn × Complexity Hotspots
- git history depth insufficient
D22 · Internal API Consistency
- No exposed public API
D35 · Change Coupling
- git history depth insufficient
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not present in this environment | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan. | 0 | — |
| D33 · JS/npm Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D38 · OSV Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive . | 60 | artifacts/raw/osv-scanner.json |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |