Executive summary
Read through the Preview lens: this repo is pre-1.0 / in development, so the colour bands are relaxed to what a preview needs — *green* means good enough for a preview, not yet production-stable. Code correctness and security stay near-strict even here; the score itself is absolute and comparable across repos.
xai-org/grok-build carries serious gaps (48%). 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 Code Health (97%) — the code is clean and low-risk to change. Security (81%) is solid too.
The area that most needs attention is Readiness (17%) — 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. Architecture (69%) is the next concern — the code resists change, so features cost more over time.
Leadership focus, highest impact first: 1 No tests found finding(s) in Test Distribution (Test Distribution); CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); ILogger (or Serilog) and log at meaningful points across… (Observability).
For scale: Hobby (~0 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Code Health foundation (97%); the priorities above are the highest-leverage way to bring the rest up to that level.
Code Health
97% ★
Exemplary
Architecture
69%
Strong
Maturity
80%
Strong
Readiness
17% ⚠
Critical · gated by D9, P1, P2, P3
Security
81%
Strong
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 17% · 47% weightArchitecture 69% · 26% weightMaturity 80% · 14% weightSecurity 81% · 8% weightCode Health 97% · 4% weight
Raise Readiness 17 → 70 (the Healthy floor) ⇒ headline 48 → ~73.
Code composition — where the lines go
Tests 100%
New since the last scan (34+)
- D8 · Coverage not measured — test suite did not build
- D18 · Dimension evaluation failed
- D20 · The body is a self-describing import guide with no context/problem and no consequences/trade-offs; it reads like an ADR for the Grok CLI rather than one about a design decision crates/codegen/xai-grok-pager/docs/tutorial/01-coming-from-another-tool.md
- D20 · No context/problem and no consequences; it is a usage/demo guide rather than an architecture decision crates/codegen/xai-grok-pager/docs/tutorial/02-first-prompt.md
- D20 · No context/problem and no consequences/trade-offs; only three one-line methods are listed with a link to docs crates/codegen/xai-grok-pager/docs/tutorial/03-attach-and-paste.md
- D20 · No consequences/trade-offs section describing why this decision is needed and what could go wrong crates/codegen/xai-grok-pager/docs/tutorial/08-make-it-yours.md
- D20 · This is a self-help guide with no context/problem and no explicit decision; it is pure usage content crates/codegen/xai-grok-pager/docs/tutorial/09-where-next.md
- D28 · Secret: private-key crates/codegen/xai-grok-secrets/src/sanitizer.rs
- D28 · Secret: jwt crates/codegen/xai-grok-secrets/src/sanitizer.rs
- D28 · Secret: generic-api-key crates/codegen/xai-grok-telemetry/src/otel_layer/redact.rs
- D28 · Secret: generic-api-key crates/codegen/xai-grok-workspace/src/hub_auth.rs
- D28 · Secret: generic-api-key crates/codegen/xai-grok-workspace/src/hub_auth.rs
- D38 · Medium CVE: RUSTSEC-2026-0190 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2025-0052 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2025-0012 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2025-0141 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0204 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0221 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2025-0057 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0008 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0183 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0184 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2024-0384 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0002 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0186 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2024-0436 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0194 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0195 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0097 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0206 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0205 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2026-0192 Cargo.lock
- D38 · Medium CVE: RUSTSEC-2024-0320 Cargo.lock
- P2 · No structured logging
Top priorities
1
Resolve the 1 No tests found finding(s) in Test Distribution.
2
Add a CI workflow that builds and runs the test suite on every push/PR.
3
Adopt ILogger (or Serilog) and log at meaningful points across the projects.
Diagnosis — what's actually going on
Highest-leverage move
Of everything flagged, the best return on effort is: Resolve the 1 No tests found finding(s) in Test Distribution. The rest can wait behind it.
At a glance — Code Health
The Good
At a glance — Architecture
The Good
At a glance — Maturity
The Good
At a glance — Readiness
The Bad
The Ugly
At a glance — Security
The Good
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A06:2021 — Vulnerable & Outdated Components | 26 | Medium |
| A02:2021 — Cryptographic Failures | 6 | High / Critical |
Roadmap
Begin by establishing a CI/CD pipeline to automatically build and run the test suite on every push or pull request. Simultaneously, address the single missing test by resolving the identified gap in test distribution. Next, implement structured logging using ILogger or Serilog across all service-like projects to improve observability. Finally, enforce release hygiene by stamping versions or tagging releases with semver, and update the root README to include clear instructions for running the test suite.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +29.3 pts | Low | Test Distribution |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +29.3 pts | Medium | CI/CD gates |
| Adopt ILogger (or Serilog) and log at meaningful points across the projects. | +29.3 pts | Medium | Observability |
| Stamp a version (csproj <Version>, a VERSION file, or GitVersion) or tag releases with semver so builds and releases are traceable. | +23.7 pts | Medium | Release Hygiene |
| Add a 'Testing' section to the root README — how to run the test suite. | +1.5 pts | Medium | Documentation (README) |
| Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root. | +1.5 pts | Medium | Folder & project structure |
| Resolve the 5 Secret finding(s) in Secrets (history) — start with hub_auth.rs (2), sanitizer.rs (2), redact.rs. | +0.7 pts | Low | Secrets (history) |
| Resolve the 22 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with Cargo.lock (22). | +0.6 pts | Medium | OSV Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Cargo.lock | 4.5 | Mixed | OSV Dependency Vulnerabilities: Medium CVE: RUSTSEC-2026-0190 |
| crates/codegen/xai-grok-secrets/src/sanitizer.rs | 5.8 | Mixed | Secrets (history): Secret: private-key |
| crates/codegen/xai-grok-workspace/src/hub_auth.rs | 5.8 | Mixed | Secrets (history): Secret: generic-api-key |
| crates/codegen/xai-grok-telemetry/src/otel_layer/redact.rs | 7.2 | Near-clean | Secrets (history): Secret: generic-api-key |
| crates/codegen/xai-grok-pager/docs/tutorial/01-coming-from-another-tool.md | 8.5 | Near-clean | ADR Quality: The body is a self-describing import guide with no context/problem and no consequences/trade-offs; it reads like an ADR for the Grok CLI rather than one about a design decision |
| crates/codegen/xai-grok-pager/docs/tutorial/02-first-prompt.md | 8.5 | Near-clean | ADR Quality: No context/problem and no consequences; it is a usage/demo guide rather than an architecture decision |
| crates/codegen/xai-grok-pager/docs/tutorial/03-attach-and-paste.md | 8.5 | Near-clean | ADR Quality: No context/problem and no consequences/trade-offs; only three one-line methods are listed with a link to docs |
| crates/codegen/xai-grok-pager/docs/tutorial/08-make-it-yours.md | 8.5 | Near-clean | ADR Quality: No consequences/trade-offs section describing why this decision is needed and what could go wrong |
| crates/codegen/xai-grok-pager/docs/tutorial/09-where-next.md | 8.5 | Near-clean | ADR Quality: This is a self-help guide with no context/problem and no explicit decision; it is pure usage content |
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. 29 of 32 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 32 dimensions across the health lenses
D1D2D3D4D5D7D9D12D13D15D20D21D25D26D27D28D29D33D37D38AX5M1M2M3M4P1P2P3P6X1X3X4
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, 36 of 46 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.301 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.301 | ✓ 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
- D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
- 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.
- D31 IaC & Container Security — 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.
- D32 Data Compliance (PII/GDPR) — 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.
- D36 Supply-chain Provenance & Signing — 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 (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- 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.
- D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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").
- 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.
- 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was no-recursive-grep-guard.lex at 17.
Do you agree with this assessment?
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was run_tests.test_roundtrip_mixed_sources_searchable at 29.
What to do
- Enforce Cognitive Complexity 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?
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?
D5 · Coupling
0 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Enforce Coupling 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?
D7 · Architectural Integrity
Of 12 mechanizable ADRs, 11 are prevented by analyzers, 1 by tests, 0 exist only in prose. Coverage: 100 %. Cycles found: 0.
Do you agree with this assessment?
D9 · Test Distribution
No test projects found.
No tests found
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D12 · Dependency Hygiene
0 outdated, 0 vulnerable, 0 deprecated packages.
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?
D20 · ADR Quality
Evaluated 33 ADR(s) individually; mean quality 7.7/10 (mixed — many ADRs miss context or consequences). 5 flagged with a specific gap.
The body is a self-describing import guide with no context/problem and no consequences/trade-offs; it reads like an ADR for the Grok CLI rather than one about a design decisioncrates/codegen/xai-grok-pager/docs/tutorial/01-coming-from-another-tool.md
No context/problem and no consequences; it is a usage/demo guide rather than an architecture decisioncrates/codegen/xai-grok-pager/docs/tutorial/02-first-prompt.md
No context/problem and no consequences/trade-offs; only three one-line methods are listed with a link to docscrates/codegen/xai-grok-pager/docs/tutorial/03-attach-and-paste.md
No consequences/trade-offs section describing why this decision is needed and what could go wrongcrates/codegen/xai-grok-pager/docs/tutorial/08-make-it-yours.md
This is a self-help guide with no context/problem and no explicit decision; it is pure usage contentcrates/codegen/xai-grok-pager/docs/tutorial/09-where-next.md
What to do
- Resolve the 1 The body is a self-describing import guide with no context/problem and… finding(s) in ADR Quality — start with 01-coming-from-another-tool.md. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No context/problem and no consequences; it is a usage/demo guide rather… finding(s) in ADR Quality — start with 02-first-prompt.md. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No context/problem and no consequences/trade-offs; only three one-line… finding(s) in ADR Quality — start with 03-attach-and-paste.md. — One of this dimension's main actionable groups (1 warning-level).
Do you agree with this assessment?
D21 · Naming Consistency
0 naming inconsistencies across 0 sampled symbols.
Do you agree with this assessment?
D25 · ADR Conformance
5 conform / 0 violate across 33 ADRs.
Do you agree with this assessment?
D26 · Project Cohesion
No projects to assess.
Do you agree with this assessment?
D27 · Navigability
Too little code to assess navigability.
Do you agree with this assessment?
D28 · Secrets (history)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: private-key crates/codegen/xai-grok-secrets/src/sanitizer.rs:444
Rotate the exposed credentials — git history can't be un-committed
What to do
- Resolve the 5 Secret finding(s) in Secrets (history) — start with hub_auth.rs (2), sanitizer.rs (2), redact.rs. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D29 · Static Analysis (SAST)
semgrep found no security issues.
Do you agree with this assessment?
D33 · JS/npm Dependency Vulnerabilities
No known-vulnerable JS/npm dependencies.
Do you agree with this assessment?
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
Do you agree with this assessment?
D38 · OSV Dependency Vulnerabilities
26 finding(s): 0 critical, 0 high, 22 medium, 4 low.
Medium CVE: RUSTSEC-2026-0190 Cargo.lock
Low CVE: [GHSA redacted] Cargo.lock
What to do
- Resolve the 22 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with Cargo.lock (22). — One of this dimension's main actionable groups (22 warning-level).
- Resolve the 4 Low CVE finding(s) in OSV Dependency Vulnerabilities — start with Cargo.lock (4). — One of this dimension's main actionable groups (4 recommendation-level).
Do you agree with this assessment?
Frontend & cross-cutting dimensions
AX5 · Architecture & structure
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.
Do you agree with this assessment?
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 33) — reach 50 to raise the maturity tier; document significant decisions as they're made.
Do you agree with this assessment?
M3 · Folder & project structure
- Projects aren't grouped under a src/ folder — production and tooling code are mixed at the root.
- Test projects aren't grouped under a tests/ folder — the test surface isn't separable from production code at a glance.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Group test projects under tests/ (or test/, spec/) so the test surface is discoverable and CI can scope it.
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?
P2 · Observability
- No ILogger/Serilog usage found — production issues will be hard to diagnose.
What to do
- Adopt ILogger (or Serilog) and log at meaningful points across the projects.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Do you agree with this assessment?
P3 · Security & performance tooling
- No static application security testing (CodeQL / security analyzers / codehealth) detected.
What to do
- Add a SAST step (e.g. CodeQL) 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?
P6 · Release Hygiene
What to do
- Stamp a version (csproj <Version>, a VERSION file, or GitVersion) or tag releases with semver so builds and releases are traceable.
Do you agree with this assessment?
X1 · Async correctness
Do you agree with this assessment?
X3 · Exception handling
Do you agree with this assessment?
X4 · Structured logging
Do you agree with this assessment?
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 97% | Exemplary | Strongest area. |
| Architecture | 69% | Strong | Solid. |
| Maturity | 80% | Strong | Solid. |
| Readiness | 17% | Critical — gated by D9, P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81% | Strong | Solid. |
Not included — 59 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 — no source files detected — code composition not applicable
- AX2 Stateful singletons — no singleton implementations detected
- AX3 Project dependency cycles — no csproj graph available
- AX4 Dependency direction — no csproj graph available
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~2258 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
- D11 Test Reliability — Test reliability not included
- D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
- D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — Dimension evaluation failed
- D19 Documentation Quality — LLM evaluation failed
- D22 Internal API Consistency — No exposed public API
- D23 Boundary Type-Coupling — Zero projects and zero LoC mean the codebase is trivial and has no structure to justify boundaries.
- D24 Comment Value — No inline comments to assess — comment value is not applicable here.
- D30 Dependency Vulnerabilities — No .NET solution found; no NuGet dependencies to scan for vulnerabilities.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No PII/GDPR 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
- D35 Change Coupling — no production change history to mine for change-coupling
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
- D39 IL Efficiency — The target did not build, so no IL was available to measure.
- 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).
- D8 Code Coverage — Coverage not measured — test suite did not build
- DM1 Domain Modelling — not run — only 1/3 markers (1 value object(s))
- ED1 Event-Driven — not run — 0/3 markers found
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not run — 0/3 markers found
- GD1 Unfinished & placeholder code — no source files
- IC1 Incompleteness & stubs — no C# methods found
- P12 CI test-gate honesty — no CI workflow found
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — no data
- X2 Cancellation propagation — no async methods found
- X5 Nullable reference types — no NRT-eligible projects
Appendix A — Findings (grouped)
Issue — 6 finding(s)
D28 · Secrets (history)
- Secret: private-key crates/codegen/xai-grok-secrets/src/sanitizer.rs:444
- Secret: jwt crates/codegen/xai-grok-secrets/src/sanitizer.rs:457
- Secret: generic-api-key crates/codegen/xai-grok-telemetry/src/otel_layer/redact.rs:512
- Secret: generic-api-key crates/codegen/xai-grok-workspace/src/hub_auth.rs:376
- Secret: generic-api-key crates/codegen/xai-grok-workspace/src/hub_auth.rs:422
D18 · Solution Shape
- Dimension evaluation failed
Warning — 30 finding(s)
D38 · OSV Dependency Vulnerabilities
- Medium CVE: RUSTSEC-2026-0190 Cargo.lock
- Medium CVE: RUSTSEC-2025-0052 Cargo.lock
- Medium CVE: RUSTSEC-2025-0012 Cargo.lock
- Medium CVE: RUSTSEC-2025-0141 Cargo.lock
- Medium CVE: RUSTSEC-2026-0204 Cargo.lock
- Medium CVE: RUSTSEC-2026-0221 Cargo.lock
- Medium CVE: RUSTSEC-2025-0057 Cargo.lock
- Medium CVE: RUSTSEC-2026-0008 Cargo.lock
- Medium CVE: RUSTSEC-2026-0183 Cargo.lock
- Medium CVE: RUSTSEC-2026-0184 Cargo.lock
- Medium CVE: RUSTSEC-2024-0384 Cargo.lock
- Medium CVE: RUSTSEC-2026-0002 Cargo.lock
- Medium CVE: RUSTSEC-2026-0186 Cargo.lock
- Medium CVE: RUSTSEC-2024-0436 Cargo.lock
- Medium CVE: RUSTSEC-2026-0194 Cargo.lock
- Medium CVE: RUSTSEC-2026-0195 Cargo.lock
- Medium CVE: RUSTSEC-2026-0097 Cargo.lock
- Medium CVE: RUSTSEC-2023-0071 Cargo.lock
- Medium CVE: RUSTSEC-2026-0206 Cargo.lock
- Medium CVE: RUSTSEC-2026-0205 Cargo.lock
- Medium CVE: RUSTSEC-2026-0192 Cargo.lock
- Medium CVE: RUSTSEC-2024-0320 Cargo.lock
D16 · Bus Factor
- single-maintainer — knowledge-concentration (bus factor) risk
D19 · Documentation Quality
- LLM evaluation failed
D20 · ADR Quality
- The body is a self-describing import guide with no context/problem and no consequences/trade-offs; it reads like an ADR for the Grok CLI rather than one about a design decision crates/codegen/xai-grok-pager/docs/tutorial/01-coming-from-another-tool.md
D20 · ADR Quality
- No context/problem and no consequences; it is a usage/demo guide rather than an architecture decision crates/codegen/xai-grok-pager/docs/tutorial/02-first-prompt.md
D20 · ADR Quality
- No context/problem and no consequences/trade-offs; only three one-line methods are listed with a link to docs crates/codegen/xai-grok-pager/docs/tutorial/03-attach-and-paste.md
D20 · ADR Quality
- No consequences/trade-offs section describing why this decision is needed and what could go wrong crates/codegen/xai-grok-pager/docs/tutorial/08-make-it-yours.md
D20 · ADR Quality
- This is a self-help guide with no context/problem and no explicit decision; it is pure usage content crates/codegen/xai-grok-pager/docs/tutorial/09-where-next.md
D8 · Code Coverage
- Coverage not measured — test suite did not build
Recommendation — 8 finding(s)
D38 · OSV Dependency Vulnerabilities
- Low CVE: [GHSA redacted] Cargo.lock
- Low CVE: [GHSA redacted] Cargo.lock
- Low CVE: [GHSA redacted] Cargo.lock
- Low CVE: [GHSA redacted] Cargo.lock
D11 · Test Reliability
- Test reliability not included
D28 · Secrets (history)
- Rotate the exposed credentials — git history can't be un-committed
D34 · Knowledge Freshness
- early-stage repository — too little history to judge knowledge freshness
D9 · Test Distribution
- No tests found
Info — 2 finding(s)
D15 · Churn × Complexity Hotspots
- git history depth insufficient
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 . | 5 | 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 | — |
| D30 · Dependency Vulnerabilities | dotnet (no .NET solution) | — | dotnet (no .NET solution): not present in this environment | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan. | 0 | — |
| 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/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for. | 0 | — |
| D38 · OSV Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive . | 26 | artifacts/raw/osv-scanner.json |