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.
gruz0/checkmvp is sound in substance but carries real gaps (64%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Domain Modelling (100%) — the domain model is expressive and well-guarded. Code Health (88%) 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 (59%) — 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. Accessibility (60%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: SAST step to CI running what this repository's stack ships (Security & performance tooling); tests that import the unreached modules (directly or through… (Test Coverage); Give every control a programmatic label (a <label for> /… (Forms & labels).
For scale: Small (~19,716 production lines); rebuilding it from scratch would take roughly ~0.2 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
88%
Strong
Architecture
87%
Strong
Maturity
70%
Adequate · gated by D34
Readiness
59%
Adequate · gated by R4, P3
Security
68%
Adequate · gated by D38
Domain Modelling
100% ★
Exemplary
Accessibility
60%
Adequate · gated by AC4
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 59% · 46% weightAccessibility 60% · 25% weightSecurity 68% · 14% weightMaturity 70% · 8% weightArchitecture 87% · 4% weightCode Health 88% · 2% weightDomain Modelling 100% · 1% weight
Raise Readiness 59 → 70 (the Healthy floor) ⇒ headline 64 → ~67.
Code composition — where the lines go
Tests 100%
New since the last scan (10+)
- D29 · High: github-actions-mutable-action-tag .github/workflows/docker-image.yml
- D29 · High: github-actions-mutable-action-tag .github/workflows/docker-image.yml
- D29 · High: github-actions-mutable-action-tag .github/workflows/spell.yml
- D29 · High: github-actions-mutable-action-tag .github/workflows/spell.yml
- D35 · Change coupling clique: page.tsx, ConceptRepositorySQLite.ts, ConceptEvaluationSubscriber.ts src/app/concepts/[id]/page.tsx
- D38 · High CVE: [GHSA redacted] package-lock.json
- D38 · High CVE: [GHSA redacted] package-lock.json
- D38 · High CVE: [GHSA redacted] package-lock.json
- D38 · High CVE: [GHSA redacted] package-lock.json
- D38 · High vulnerability: [GHSA redacted] package-lock.json
Rebuild cost & value ~ Modeled — €11,000–€55,000
| Cost to rebuild | €11,000–€55,000 |
| Domain complexity | Standard |
| Quality factor | 0.9× (at 64% quality) |
| Size & shape | Small · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk) |
This codebase represents roughly ~0.2 person-years of build effort (about ~€33,000 to rebuild). Its weakest lens is Readiness at 59% — the part of that asset most exposed by the findings below.
Top priorities
1
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
2
Add tests that import the unreached modules (directly or through their public entry).
3
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Diagnosis — what's actually going on
Value concentrated against a weak lens
This is a Small asset (~0.2 person-years to rebuild), and its weakest lens is Readiness at 59%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Highest-leverage move
Of everything flagged, the best return on effort is: Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. 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
The Good
At a glance — Security
The Good
The Ugly
At a glance — Domain Modelling
At a glance — Accessibility
The Ugly
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A06:2021 — Vulnerable & Outdated Components | 23 | High / Critical |
| A03:2021 — Injection | 5 | High / Critical |
| A05:2021 — Security Misconfiguration | 1 | Medium |
Roadmap
First, integrate static security scanning into the CI pipeline to automatically block security regressions. Next, expand test coverage to include all currently unreachable production modules. Then, ensure every form control and button has a proper programmatic label to improve usability. Finally, make custom controls fully keyboard-operable and enforce accessibility standards through linting and automated testing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +4.4 pts | Medium | Security & performance tooling |
| Add tests that import the unreached modules (directly or through their public entry). | +4.4 pts | Medium | Test Coverage |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +4.0 pts | Medium | Forms & labels |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +4.0 pts | Medium | Keyboard semantics |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +4.0 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.8 pts | Medium | Page structure |
| Add an approval/environment gate (required reviewers / protection rules) before production promotion. | +3.5 pts | Medium | Deployment & Rollback |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +1.5 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| package-lock.json | 0.0 | Slop | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| .github/workflows/docker-image.yml | 5.8 | Mixed | Static Analysis (SAST): High: github-actions-mutable-action-tag |
| .github/workflows/spell.yml | 5.8 | Mixed | Static Analysis (SAST): High: github-actions-mutable-action-tag |
| src/app/ideas/[id]/IdeaAnalysisReport.tsx | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: IdeaAnalysisReport.tsx ↔ Service.ts |
| src/app/concepts/[id]/ProblemRequiresChanges.tsx | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: ProblemRequiresChanges.tsx ↔ page.tsx |
| .github/dependabot.yml | 7.2 | Mixed | Static Analysis (SAST): High: dependabot-missing-cooldown |
| src/app/start/page.tsx | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: page.tsx ↔ ConceptForm.tsx |
| src/app/concepts/[id]/page.tsx | 8.5 | Near-clean | Change Coupling: Change coupling clique: page.tsx, ConceptRepositorySQLite.ts, ConceptEvaluationSubscriber.ts |
| src/idea/domain/Aggregate.ts | 8.5 | Near-clean | Change Coupling: Change coupling: Aggregate.ts ↔ Service.ts |
| src/idea/adapters/IdeaRepositorySQLite.ts | 8.5 | Near-clean | Change Coupling: Change coupling: IdeaRepositorySQLite.ts ↔ GetIdea.ts |
| Dockerfile | 9.3 | Near-clean | IaC & Container Security: Low IaC: DS-0026 |
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. 36 of 38 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 38 dimensions across the health lenses
D4D7D13D15D16D20D21D28D29D31D33D34D35D38AC2AC3AC4AC5AC6AC7DM6M1M2M3M4P1P3P4R1R10R2R3R4R5R6R7R8R9
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, 38 of 45 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
- 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.
- 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
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- 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.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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
D4 · Code Duplication
0 duplicated block group(s) detected.
Do you agree with this assessment?
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured (scan coverage 100 %). Cycles found: 0.
What to do
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
Do you agree with this assessment?
D16 · Bus Factor
20 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/components/IdeaPDFReport.tsx.
Small-team knowledge concentration
Do you agree with this assessment?
D20 · ADR Quality
Evaluated 1 ADR(s) individually; mean quality 7.0/10 (mixed — many ADRs miss context or consequences). 0 flagged with a specific gap.
What to do
- Improve ADR Quality — currently 7.0/10. — Evaluated 1 ADR(s) individually; mean quality 7.0/10 (mixed — many ADRs miss context or consequences). 0 flagged with a specific gap.
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)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low.
High: dependabot-missing-cooldown .github/dependabot.yml:3
What to do
- Resolve the 5 High finding(s) in Static Analysis (SAST) — start with docker-image.yml (2), spell.yml (2), dependabot.yml. — One of this dimension's main actionable groups (5 issue-level).
Do you agree with this assessment?
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 0 medium, 1 low.
Low IaC: DS-0026Dockerfile
Do you agree with this assessment?
D33 · JS/npm Dependency Vulnerabilities
No known-vulnerable JS/npm dependencies.
Do you agree with this assessment?
D34 · Knowledge Freshness
71 of 91 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/app/concepts/[id]/audiences/TargetAudiences.tsx.
Dormant codebase
What to do
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D35 · Change Coupling
Strongest change-coupling: Aggregate.ts↔Service.ts 77%; IdeaAnalysisReport.tsx↔Service.ts 69%; ProblemRequiresChanges.tsx↔WellDefinedProblem.tsx 69%
Boundary-crossing change coupling: IdeaAnalysisReport.tsx ↔ Service.ts src/app/ideas/[id]/IdeaAnalysisReport.tsx
Change coupling: Aggregate.ts ↔ Service.ts src/idea/domain/Aggregate.ts
Change coupling clique: page.tsx, ConceptRepositorySQLite.ts, ConceptEvaluationSubscriber.tssrc/app/concepts/[id]/page.tsx
Do you agree with this assessment?
D38 · OSV Dependency Vulnerabilities
23 finding(s): 2 critical, 11 high, 7 medium, 3 low.
High CVE: [GHSA redacted] package-lock.json
Critical CVE: [GHSA redacted] package-lock.json
High vulnerability: [GHSA redacted] package-lock.json
Medium CVE: [GHSA redacted] package-lock.json
Medium vulnerability: [GHSA redacted] package-lock.json
What to do
- Resolve the 9 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (9). — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 2 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (2). — One of this dimension's main actionable groups (2 issue-level).
Do you agree with this assessment?
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×6) — TargetAudiences.tsx:199, TargetAudiences.tsx:224, page.tsx:75, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — global-error.tsx:17
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — global-error.tsx:17, layout.tsx:24
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×5) — page.tsx:26, page.tsx:20, page.tsx:53, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Do you agree with this assessment?
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — ConfirmationPopup.tsx:29
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Do you agree with this assessment?
AC5 · ARIA correctness
Do you agree with this assessment?
AC6 · Visual & motion safety
Do you agree with this assessment?
AC7 · A11y enforcement
- An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI.
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Do you agree with this assessment?
DM6 · Domain ↔ infrastructure boundary
Do you agree with this assessment?
M1 · Documentation (README)
What to do
- Add a 'Testing' section to the root README — how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Do you agree with this assessment?
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 3) — reach 8 to raise the maturity tier; document significant decisions as they're made.
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
Do you agree with this assessment?
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step.
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Do you agree with this assessment?
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
R1 · Type Safety
Do you agree with this assessment?
R10 · Code Duplication
- src/app/agencies/page.tsx:114 · src/app/developers/page.tsx:113 · src/app/freelancers/page.tsx:116 · src/app/indie-hackers/page.tsx:119 — page.tsx:114
- src/app/hypotheses/[hypothesisId]/experiments/[experimentId]/setup/page.tsx:20 · src/app/hypotheses/[hypothesisId]/experiments/[experimentId]/setup/page.tsx:82 — page.tsx:20
- src/app/concepts/[id]/page.tsx:18 · src/app/concepts/[id]/types.ts:10 — page.tsx:18
- src/idea/adapters/OpenAIService/TestingPlanEvaluator.ts:18 · src/idea/domain/TestingPlan.ts:14 · src/idea/events/subscribers/TestingPlanEvaluationSubscriber.ts:22 — TestingPlanEvaluator.ts:18
- src/idea/events/subscribers/CompetitorAnalysisEvaluationSubscriber.ts:101 · src/idea/events/subscribers/MarketAnalysisEvaluationSubscriber.ts:73 · src/idea/events/subscribers/SWOTAnalysisEvaluationSubscriber.ts:85 — CompetitorAnalysisEvaluationSubscriber.ts:101
- src/app/hypotheses/[hypothesisId]/experiments/[experimentId]/setup/page.tsx:115 · src/app/hypotheses/new/page.tsx:84 — page.tsx:115
- src/app/template.tsx:45 · src/app/template.tsx:69 · src/app/template.tsx:109 · src/app/template.tsx:135 — template.tsx:45
- src/app/template.tsx:127 · src/app/template.tsx:191 — template.tsx:127
What to do
- Extract the duplicated blocks into shared functions/components.
Do you agree with this assessment?
R2 · Cyclomatic Complexity
- Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — TestingPlan.ts:81, ContextAnalysis.ts:32, IdeaRepositorySQLite.ts:318, …
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files
What to do
- Split the oversized components into smaller, focused ones.
Do you agree with this assessment?
R4 · Test Coverage
- No test imports this module directly or transitively. If it is a CLI, check whether a suite runs it as a child process; otherwise it has no test reaching it. (×8) — IdeaPDFReport.tsx, IdeaRepositorySQLite.ts, ConceptForm.tsx, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling
Do you agree with this assessment?
R7 · Dead Code
- 328 file(s) (~32610 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.
Do you agree with this assessment?
R8 · Dependency Hygiene
Do you agree with this assessment?
R9 · Circular Imports
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 88% | Strong | Solid. |
| Architecture | 87% | Strong | Solid. |
| Maturity | 70% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by R4, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68% | Adequate — gated by D38 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 60% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- 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.
- D1 Cyclomatic Complexity — Most of this repository's production source (.ts, .tsx) had no cyclomatic complexity computed for it, so cyclomatic complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
- D10 Test Quality — ~8749 lines of test source are present (.ts) 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.
- 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.
- D19 Documentation Quality — LLM evaluation failed
- D2 Cognitive Complexity — Most of this repository's production source (.ts, .tsx) had no cognitive complexity computed for it, so cognitive complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
- D22 Internal API Consistency — No exposed public API
- D23 Boundary Type-Coupling — Production source is present (.ts, .tsx) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["Acme.Billing"]`, `Catalog: ["Acme.Catalog"]`.
- D24 Comment Value — No inline comments to assess — comment value is not applicable here.
- D25 ADR Conformance — none of 1 ADRs are conformance-checkable — unverifiable.
- D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D3 God Classes — Most of this repository's production source (.tsx) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a NuGet package, a container image, a GitHub release).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — 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) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .ts, .tsx, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.ts) 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 data
- 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 (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) 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.
- 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 — 23 finding(s)
D38 · OSV Dependency Vulnerabilities
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
D29 · Static Analysis (SAST)
- High: dependabot-missing-cooldown .github/dependabot.yml:3
- High: github-actions-mutable-action-tag .github/workflows/docker-image.yml:13
- High: github-actions-mutable-action-tag .github/workflows/docker-image.yml:15
- High: github-actions-mutable-action-tag .github/workflows/spell.yml:19
- High: github-actions-mutable-action-tag .github/workflows/spell.yml:22
D35 · Change Coupling
- Boundary-crossing change coupling: IdeaAnalysisReport.tsx ↔ Service.ts src/app/ideas/[id]/IdeaAnalysisReport.tsx
- Boundary-crossing change coupling: IdeaAnalysisReport.tsx ↔ IdeaRepositorySQLite.ts src/app/ideas/[id]/IdeaAnalysisReport.tsx
- Boundary-crossing change coupling: IdeaAnalysisReport.tsx ↔ Aggregate.ts src/app/ideas/[id]/IdeaAnalysisReport.tsx
- Boundary-crossing change coupling: page.tsx ↔ ConceptForm.tsx src/app/start/page.tsx
- Boundary-crossing change coupling: ProblemRequiresChanges.tsx ↔ page.tsx src/app/concepts/[id]/ProblemRequiresChanges.tsx
D38 · OSV Dependency Vulnerabilities
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
D38 · OSV Dependency Vulnerabilities
- High vulnerability: [GHSA redacted] package-lock.json
- High vulnerability: [GHSA redacted] package-lock.json
Warning — 12 finding(s)
D38 · OSV Dependency Vulnerabilities
- Medium CVE: [GHSA redacted] package-lock.json
- Medium CVE: [GHSA redacted] package-lock.json
- Medium CVE: [GHSA redacted] package-lock.json
- Medium CVE: [GHSA redacted] package-lock.json
- Medium CVE: [GHSA redacted] package-lock.json
D35 · Change Coupling
- Change coupling: Aggregate.ts ↔ Service.ts src/idea/domain/Aggregate.ts
- Change coupling: ProblemRequiresChanges.tsx ↔ WellDefinedProblem.tsx src/app/concepts/[id]/ProblemRequiresChanges.tsx
- Change coupling: IdeaRepositorySQLite.ts ↔ GetIdea.ts src/idea/adapters/IdeaRepositorySQLite.ts
D38 · OSV Dependency Vulnerabilities
- Medium vulnerability: [GHSA redacted] package-lock.json
- Medium vulnerability: [GHSA redacted] package-lock.json
D19 · Documentation Quality
- LLM evaluation failed
D35 · Change Coupling
- Change coupling clique: page.tsx, ConceptRepositorySQLite.ts, ConceptEvaluationSubscriber.ts src/app/concepts/[id]/page.tsx
Recommendation — 8 finding(s)
D38 · OSV Dependency Vulnerabilities
- Low CVE: [GHSA redacted] package-lock.json
- Low CVE: [GHSA redacted] package-lock.json
- Low CVE: [GHSA redacted] package-lock.json
D11 · Test Reliability
- Test reliability not included
D16 · Bus Factor
- Small-team knowledge concentration
D31 · IaC & Container Security
- Low IaC: DS-0026 Dockerfile
D34 · Knowledge Freshness
- Dormant codebase
D8 · Code Coverage
- Coverage not included — suite not readable by the collector
Info — 2 finding(s)
D12 · Dependency Hygiene
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D22 · Internal API Consistency
- No exposed public API
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 . | 5 | 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 . | 1 | 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 — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a NuGet package, a container image, a GitHub release). | 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 . | 23 | 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 | — |