LivrariaOnline — Watchdog Audit

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.

tmoreirafreitas/LivrariaOnline carries serious risk (43%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.

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 (35%) — operating, monitoring and recovering the system safely is harder. Maturity (40%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.

Leadership focus, highest impact first: 9 Deprecated finding(s) in Dependency Hygiene (Dependency Hygiene); Extend structured logging to the remaining service-like… (Observability); readiness/liveness probes and a rolling-update (or blue/green)… (Deployment & Rollback).

For scale: Hobby (~869 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.

Code Health 76% Strong Architecture 83% Strong Maturity 40% Weak · gated by M1, M2 Readiness 35% Weak · gated by D12, P3 Security 45% Weak · gated by D30, D36, C2

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 35% · 47% weightMaturity 40% · 26% weightSecurity 45% · 14% weightCode Health 76% · 8% weightArchitecture 83% · 4% weight

Raise Readiness 35 → 70 (the Healthy floor) ⇒ headline 43 → ~50.

Code composition — where the lines go

Business logic 11%Plumbing 58%Tests 30%

Rebuild cost & value ~ Modeled — €300–€1,500

Cost to rebuild	€300–€1,500 (0.1 person-years (5–15 h), ~1 engineer)
Domain complexity	Low — harder problems cost more per line
Quality factor	0.7× (at 43% quality) — the last 20% of quality is most of the work
Size & shape	Hobby · 46% boilerplate · 38% straight-line · 16% branching logic

How we model this: boilerplate at a scaffolding rate + logic × domain Low (×0.9) — service/app, transaction-script/CRUD × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Resolve the 9 Deprecated finding(s) in Dependency Hygiene.

+9.2 pts · Low effort · Dependency Hygiene

Resolve the 4 Vulnerable finding(s) in Dependency Hygiene.

+6.2 pts · Low effort · Dependency Hygiene

Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.

+8.8 pts · Medium effort · Observability

Diagnosis — what's actually going on

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Resolve the 9 Deprecated finding(s) in Dependency Hygiene. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Resolve the 9 Deprecated finding(s) in Dependency Hygiene.

Improving trajectory · Info · Trajectory

The headline is improving steadily (+6.2 pts/run over 6 runs) — whatever you're doing is working; keep the gate.

Evidence: trajectory: +6.2 pts/run over 6 runs

Trajectory

The Ugly

D30 · .NET / C# Dependency Vulnerabilities 0.0 D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C2 · Repo Access Controls 3.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A06:2021 — Vulnerable & Outdated Components	44	High / Critical

Roadmap

First, resolve the nine deprecated dependencies to improve security and stability. Next, extend structured logging across all services to ensure full production diagnosability. Then, implement readiness and liveness probes with an automated rollback strategy to safely manage deployments. After that, adopt explicit Entity Framework migrations to manage database schema changes. Finally, expand the README with getting-started instructions, an architecture overview, and a project map.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Resolve the 9 Deprecated finding(s) in Dependency Hygiene.	+9.2 pts	Low	Dependency Hygiene
Resolve the 4 Vulnerable finding(s) in Dependency Hygiene.	+6.2 pts	Low	Dependency Hygiene
Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.	+8.8 pts	Medium	Observability
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.	+8.7 pts	Medium	Deployment & Rollback
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+4.1 pts	Low	ADR Quality
Adopt EF migrations (dotnet ef migrations add + Migrate() on startup) as the explicit, versioned schema strategy — no migration mechanism was detected.	+8.0 pts	Medium	Schema migrations
Expand the README with getting-started, architecture overview and a project map.	+6.9 pts	Medium	Documentation (README)
Start an ADR log (docs/adr/) recording significant decisions and their rationale.	+6.9 pts	Medium	Architecture documentation

File quality

Per-file score 0–10 — a quality signature. Of 1 files carrying findings, judged against the Production bar: 0% slop · 0% mixed · 100% near-clean.

File	Score	Band	Worst signal
LivrariaOnline.Application.Api/Startup.cs	9.5	Near-clean	Comment Value: redundant comment

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. 46 of 49 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.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 49 dimensions across the health lenses

D1D2D3D4D5D6D9D10D12D13D14D15D17D18D19D20D21D24D26D28D29D30D35D36D39AX1AX10AX2AX3AX5AX6AX8C2GD1IC1M1M2M3M4P1P2P3P4P8S1X1X2X3X4

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 5 of 91 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	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

Every finding is locatable in findings.md. Run 019f1315-ed45-78c1-ac1a-197d4236eb42.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

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.
D33 JS/npm 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.
D37 Vulnerability-disclosure Policy — 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.
D38 OSV 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (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.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (EF migrations, designer files, snapshots) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
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.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".

The LLM boundary

LLM-set scores this run (5): D19, D20, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity10.0 / 10Exemplary✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cognitive complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

Do you agree with this assessment?

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

Do you agree with this assessment?

D4 · Code Duplication10.0 / 10Exemplary✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 duplicated block group(s) detected.

✓ On the Gold path — maintain.

Detailed fixes: d4_recommendation.md.

Do you agree with this assessment?

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 5 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

21 test methods: 21 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 21 tests.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene1.0 / 10Critical✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 1.0 / 10 · rule-coverage 100% · ceiling Verified

13 outdated, 4 vulnerable, 9 deprecated packages.

Vulnerable: Microsoft.NETCore.App · ×4

Deprecated: Microsoft.NETCore.App · ×9

Outdated: FluentValidation · ×13

What to do

Resolve the 9 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 4 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 issue-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 13 packages use a banned license.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

git history depth insufficient

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted debt markers + 0 dead symbols across 869 LoC (0.0/KLoC) → score 10.0.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

Do you agree with this assessment?

D18 · Solution Shape9.0 / 10Strong✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

5 projects, 25 .cs files, 1245 hand-written lines of code (869 production / 376 test), 6 inter-project edges.

Thin analysable surface across projects

What to do

Resolve the 1 Thin analysable surface across projects finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation Quality / 10Weak◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Documented

The single README is a one-line description of the project (LivrariaOnline) as an ASP.NET Core web API built with DDD, EF, AutoMapper, and IoC. It gives no architecture overview, no usage guidance, no endpoints, no configuration, and no prerequisites; it has no documentation at all.

XML-doc coverage: LivrariaOnline.Domain · ×4LivrariaOnline.Domain/LivrariaOnline.Domain.csproj

What to do

Improve Documentation Quality — currently 3.0/10. — The single README is a one-line description of the project (LivrariaOnline) as an ASP.NET Core web API built with DDD, EF, AutoMapper, and IoC. It gives no architecture overview, no usage guidance, no endpoints, no configuration, and no prerequisites; it has no documentation at all.

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D20 · ADR Quality / 10Critical◐ Sampled · advisory

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective Critical / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D21 · Naming Consistency / 10Strong◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Verified

4 naming inconsistencies across 200 sampled symbols.

Inconsistent spelling of 'Author' and 'Between' in method names. 'Autor' (Portuguese) is used in some places, while 'Author' (English) is used in others. Similarly, 'Beetwen' (typo) is used instead of 'Between'.

Inconsistent naming for the author field. The entity uses 'Autor' (Portuguese) while the DTO also uses 'Autor'. However, the interface and service methods use 'Author' (English) or 'Name' for books. This creates a mismatch between the domain model and the service/DTO layer.

Inconsistent naming for price. The entity and DTO use 'Preco' (Portuguese), while the service/DTO might expect 'Price' (English) or 'Cost'.

Inconsistent naming for publication date. The entity and DTO use 'DataPublicacao' (Portuguese), while the service/DTO might expect 'PublicationDate' (English).

What to do

Resolve the 1 Inconsistent spelling of 'Author' and 'Between' in method names. 'Autor'… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Inconsistent naming for the author field. The entity uses 'Autor'… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Inconsistent naming for price. The entity and DTO use 'Preco'… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D24 · Comment Value / 10Weak◐ Sampled · advisory

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Documented

10 valuable / 1 redundant across 29 sampled comments; 1 shown with locations.

redundant commentLivrariaOnline.Application.Api/Startup.cs:49

What to do

Resolve the 1 redundant comment finding(s) in Comment Value — start with Startup.cs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 5 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep --config auto across the repo; severity rules (ERROR/WARNING/INFO) map to a 0-10 wide normalizer. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.

Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

44 vulnerable package(s): 2 critical, 17 high, 25 medium, 0 low.

High CVE: Microsoft.NETCore.App 2.2.0 · ×17detected by dotnet list package --vulnerable

Critical CVE: System.Text.Encodings.Web 4.5.0 · ×2detected by dotnet list package --vulnerable

Medium CVE: Microsoft.NETCore.App 2.2.0 · ×25detected by dotnet list package --vulnerable

What to do

Resolve the 25 Medium CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 17 High CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (17 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

git history depth insufficient

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/3 supply-chain integrity signals present (provenance, signing, SBOM).

No build provenance

No artifact signing

No SBOM

What to do

Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No SBOM finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified

Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 72 first-party methods have an oversized IL body.

✓ On the Gold path — maintain.

Detailed fixes: d39_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

Do you agree with this assessment?

AX10 · Code composition4.0 / 10Weak✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

Do you agree with this assessment?

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

C2 · Access Controls3.0 / 10Weak✓ Tool-verified

Other · Security — Whether access is authorized by default — [Authorize]/policies or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.

What to do

Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

Do you agree with this assessment?

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

Do you agree with this assessment?

M1 · Documentation (README)2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

The root README is 19 words — likely missing build/run/architecture context.

What to do

Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — decisions aren't captured for future maintainers.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.

What to do

Start an ADR log (docs/adr/) recording significant decisions and their rationale.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.

Do you agree with this assessment?

M3 · Folder & project structure6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

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 accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (dotnet test / npm test / pytest / a test job) was matched — the gate may be running tests, or "test" may be incidental (a path, "latest", a reporter). Make the test step explicit so the gate is unambiguous.

What to do

Run the test suite in CI via an explicit runner step (e.g. `dotnet test`) and gate merges on it.

Do you agree with this assessment?

P2 · Observability4.8 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

Only 1/4 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log).

What to do

Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.

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?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.

What to do

Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.

Do you agree with this assessment?

P8 · Schema migrations6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage. Exhaustive per project, deterministic.

EF Core is used but neither migrations nor EnsureCreated were detected — confirm how the production schema is created and evolved.

What to do

Adopt EF migrations (dotnet ef migrations add + Migrate() on startup) as the explicit, versioned schema strategy — no migration mechanism was detected.

Do you agree with this assessment?

S1 · Web-Security Posture6.5 / 10Adequate✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. Deterministic.

No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.)

What to do

Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.

Do you agree with this assessment?

X1 · Async correctness6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Make the caller `async` and `await` instead. — BooksController.cs:146

What to do

Sync-over-async (deadlock risk)

Do you agree with this assessment?

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.

Only 0/36 async methods accept a CancellationToken, so requests can't be cancelled cleanly under load or on client disconnect. In Blazor Server circuits and other short-write hosts, omitting it can be an accepted convention — judge against your hosting model.
No CancellationToken parameter — work can't be cancelled cleanly on disconnect/shutdown. (×25) — BookService.cs:22, BookService.cs:32, BookService.cs:38, …

What to do

Thread a CancellationToken through async methods so work stops promptly on cancellation.

Do you agree with this assessment?

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

Do you agree with this assessment?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	76%	Strong	Solid.
Architecture	83%	Strong	Strongest area.
Maturity	40%	Weak — gated by M1, M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	35%	Weak — gated by D12, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	45%	Weak — gated by D30, D36, C2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.

Not included — 45 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AC1 Text alternatives — No 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.
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — no data
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.
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.
D11 Test Reliability — No tests discovered
D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — At only 869 LoC the codebase is tiny and single-purpose despite five projects, so explicit boundaries are unnecessary.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
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-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not run — only 1/3 markers (a Domain/Aggregates/ValueObjects layer)
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
P12 CI test-gate honesty — no data
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 — no outbound HTTP 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.
SC1 Supply-chain hygiene — no data
X5 Nullable reference types — no NRT-eligible projects
X6 Hand-rolled structured-format parsing — no data
X7 Silent fallback defaults — no data

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Issue — 23 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×17

High CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a High advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Newtonsoft.Json 11.0.2 — Newtonsoft.Json 11.0.2 (transitive) has a High advisory; affects 4 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: AutoMapper 8.0.0 — AutoMapper 8.0.0 (direct) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.App 2.2.0 — Microsoft.AspNetCore.App 2.2.0 (direct) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.WebSockets 2.2.0 — Microsoft.AspNetCore.WebSockets 2.2.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Data.SqlClient 4.6.0 — System.Data.SqlClient 4.6.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Http 4.3.0 — System.Net.Http 4.3.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.WebSockets.WebSocketProtocol 4.5.1 — System.Net.WebSockets.WebSocketProtocol 4.5.1 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.RegularExpressions 4.3.0 — System.Text.RegularExpressions 4.3.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.All 2.2.1 — Microsoft.AspNetCore.All 2.2.1 (direct) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.DataProtection.AzureStorage 2.2.0 — Microsoft.AspNetCore.DataProtection.AzureStorage 2.2.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.Data.OData 5.8.2 — Microsoft.Data.OData 5.8.2 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]

D12 · Dependency Hygiene · Vulnerable · ×4

Vulnerable: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) severity. 2.2.0
Vulnerable: AutoMapper — AutoMapper 8.0.0 — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Microsoft.AspNetCore.App — Microsoft.AspNetCore.App [2.2.0, — ) severity. 2.2.0
Vulnerable: Microsoft.AspNetCore.All — Microsoft.AspNetCore.All 2.2.1 — High severity. https://github.com/advisories/[GHSA redacted]

D30 · Dependency Vulnerabilities · Critical CVE · ×2

Critical CVE: System.Text.Encodings.Web 4.5.0 — System.Text.Encodings.Web 4.5.0 (transitive) has a Critical advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Critical CVE: Microsoft.AspNetCore.Server.Kestrel.Core 2.2.0 — Microsoft.AspNetCore.Server.Kestrel.Core 2.2.0 (transitive) has a Critical advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]

Warning — 36 finding(s)

D30 · Dependency Vulnerabilities · Medium CVE · ×25

Medium CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a Medium advisory; affects 5 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.AspNetCore.App 2.2.0 — Microsoft.AspNetCore.App 2.2.0 (direct) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.AspNetCore.Server.HttpSys 2.2.0 — Microsoft.AspNetCore.Server.HttpSys 2.2.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.AspNetCore.Server.IIS 2.2.0 — Microsoft.AspNetCore.Server.IIS 2.2.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.AspNetCore.SpaServices 2.2.0 — Microsoft.AspNetCore.SpaServices 2.2.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.IdentityModel.JsonWebTokens 5.3.0 — Microsoft.IdentityModel.JsonWebTokens 5.3.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Data.SqlClient 4.6.0 — System.Data.SqlClient 4.6.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.IdentityModel.Tokens.Jwt 5.3.0 — System.IdentityModel.Tokens.Jwt 5.3.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Security.Cryptography.Xml 4.5.0 — System.Security.Cryptography.Xml 4.5.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.AspNetCore.All 2.2.1 — Microsoft.AspNetCore.All 2.2.1 (direct) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: MessagePack 1.7.3.4 — MessagePack 1.7.3.4 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.AspNetCore.Server.IIS 2.2.1 — Microsoft.AspNetCore.Server.IIS 2.2.1 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.Rest.ClientRuntime 2.3.8 — Microsoft.Rest.ClientRuntime 2.3.8 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]
Medium CVE: System.Net.Security 4.3.0 — System.Net.Security 4.3.0 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]

D12 · Dependency Hygiene · Deprecated · ×9

Deprecated: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) 2.2.0 Other,Legacy
Deprecated: Microsoft.EntityFrameworkCore.InMemory — Microsoft.EntityFrameworkCore.InMemory 2.2.2 — Other,Legacy
Deprecated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 2.2.0 — Other,Legacy
Deprecated: Microsoft.AspNetCore.Http — Microsoft.AspNetCore.Http 2.2.2 — Other,Legacy
Deprecated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 2.2.0 — Other,Legacy
Deprecated: Microsoft.AspNetCore.App — Microsoft.AspNetCore.App [2.2.0, — ) 2.2.0 Other,Legacy
Deprecated: Microsoft.AspNetCore.Razor.Design — Microsoft.AspNetCore.Razor.Design 2.2.0 — Other,Legacy
Deprecated: Microsoft.AspNetCore.All — Microsoft.AspNetCore.All 2.2.1 — Other,Legacy
Deprecated: Microsoft.AspNetCore.TestHost — Microsoft.AspNetCore.TestHost 2.2.0 — Other,Legacy

D16 · Bus Factor · single-maintainer · ×1

single-maintainer — knowledge-concentration (bus factor) risk — single-maintainer — knowledge-concentration (bus factor) risk (1 author(s) across 25 commit(s) sampled).

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — analyzer environment — Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, commit the Cobertura/OpenCover/lcov report your CI already produces and real coverage will be read.

Recommendation — 12 finding(s)

D11 · Test Reliability · No tests discovered · ×1

No tests discovered — Test reliability not scored — the test tier(s) built and ran but no tests were discovered, so reliability couldn't be exercised.

D18 · Solution Shape · Thin analysable surface across projects · ×1

Thin analysable surface across projects — 1 project(s) carry only a thin slice of real code (e.g. `LivrariaOnline.CrossCutting.IoC` with 24 significant line(s)). The mean analysable-surface weight is 87 %, lowering Solution Shape by about 1.0 point(s). Consolidate thin projects or grow them into substantial, well-scoped assemblies.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found at common paths; consider documenting architectural decisions in Docs/ADL/ or similar.

D21 · Naming Consistency · Inconsistent spelling of 'Author' and 'Between' in method names. 'Autor' (Portuguese) is used in some places, while 'Author' (English) is used in others. Similarly, 'Beetwen' (typo) is used instead of 'Between'. · ×1

Inconsistent spelling of 'Author' and 'Between' in method names. 'Autor' (Portuguese) is used in some places, while 'Author' (English) is used in others. Similarly, 'Beetwen' (typo) is used instead of 'Between'. — Standardize to 'Author' and 'Between' (English) or 'Autor' and 'Entre' (Portuguese) consistently across all interfaces, services, and controllers. (symbols: LivraOnline.Domain.Interfaces.Services.IBookService.GetByAutor, LivraOnline.Application.Api.Controllers.BooksController.FindByAutor, LivraOnline.UnitTest.Api.Test.BooksControllerTest.FindByAutorOkResultTest, LivraOnline.Domain.Services.BookService.GetByAuthor, LivraOnline.Domain.Interfaces.Services.IBookService.GetByAuthor, LivraOnline.Domain.Services.BookService.GetByName, LivraOnline.Domain.Interfaces.Services.IBookService.GetByName, LivraOnline.Domain.Services.BookService.GetBeetwenDatePublish, LivraOnline.Domain.Interfaces.Services.IBookService.GetBeetwenDatePublish, LivraOnline.Application.Api.Controllers.BooksController.FindBeetwenDatePublish, LivraOnline.UnitTest.Api.Test.BooksControllerTest.FindBeetwenDatePublishOkResultTest)

D21 · Naming Consistency · Inconsistent naming for the author field. The entity uses 'Autor' (Portuguese) while the DTO also uses 'Autor'. However, the interface and service methods use 'Author' (English) or 'Name' for books. This creates a mismatch between the domain model and the service/DTO layer. · ×1

Inconsistent naming for the author field. The entity uses 'Autor' (Portuguese) while the DTO also uses 'Autor'. However, the interface and service methods use 'Author' (English) or 'Name' for books. This creates a mismatch between the domain model and the service/DTO layer. — Align the property name in the Entity and DTO to match the service/interface naming convention (e.g., 'Author' in English or 'Autor' in Portuguese, but be consistent). (symbols: LivraOnline.Domain.Entities.Book.Autor, LivraOnline.Application.Api.Dto.BookDto.Autor)

D21 · Naming Consistency · Inconsistent naming for price. The entity and DTO use 'Preco' (Portuguese), while the service/DTO might expect 'Price' (English) or 'Cost'. · ×1

Inconsistent naming for price. The entity and DTO use 'Preco' (Portuguese), while the service/DTO might expect 'Price' (English) or 'Cost'. — Standardize to 'Price' (English) or 'Preco' (Portuguese) consistently across all layers. (symbols: LivraOnline.Domain.Entities.Book.Preco, LivraOnline.Application.Api.Dto.BookDto.Preco)

D21 · Naming Consistency · Inconsistent naming for publication date. The entity and DTO use 'DataPublicacao' (Portuguese), while the service/DTO might expect 'PublicationDate' (English). · ×1

Inconsistent naming for publication date. The entity and DTO use 'DataPublicacao' (Portuguese), while the service/DTO might expect 'PublicationDate' (English). — Standardize to 'PublicationDate' (English) or 'DataPublicacao' (Portuguese) consistently across all layers. (symbols: LivraOnline.Domain.Entities.Book.DataPublicacao, LivraOnline.Application.Api.Dto.BookDto.DataPublicacao)

D24 · Comment Value · redundant comment · ×1

redundant comment LivrariaOnline.Application.Api/Startup.cs:49 — ".NET Native DI Abstraction" — delete - .NET Native is self-describing; the DI abstraction is clear from context

D34 · Knowledge Freshness · early-stage repository · ×1

early-stage repository — too little history to judge knowledge freshness — early-stage repository — too little history to judge knowledge freshness (25 commit(s) sampled).

D36 · Supply-chain Provenance & Signing · No build provenance · ×1

No build provenance — No SLSA provenance generation or build attestation found in CI (e.g. slsa-github-generator, actions/attest-build-provenance).

D36 · Supply-chain Provenance & Signing · No artifact signing · ×1

No artifact signing — No artifact signing found in CI (e.g. cosign / sigstore / gitsign).

D36 · Supply-chain Provenance & Signing · No SBOM · ×1

No SBOM — No SBOM generation or committed SBOM found (e.g. syft / anchore/sbom-action / *.spdx.json / *.cdx.json).

Info — 20 finding(s)

D12 · Dependency Hygiene · Outdated · ×13

Outdated: FluentValidation — FluentValidation 8.1.3 → 12.1.1 available.
Outdated: Microsoft.EntityFrameworkCore.InMemory — Microsoft.EntityFrameworkCore.InMemory 2.2.2 → 10.0.9 available.
Outdated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 2.2.0 → 10.0.9 available.
Outdated: Microsoft.AspNetCore.Http — Microsoft.AspNetCore.Http 2.2.2 → 2.3.11 available.
Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 2.2.0 → 10.0.9 available.
Outdated: AutoMapper — AutoMapper 8.0.0 → 16.1.1 available.
Outdated: AutoMapper.Extensions.Microsoft.DependencyInjection — AutoMapper.Extensions.Microsoft.DependencyInjection 6.0.0 → 12.0.1 available.
Outdated: Microsoft.AspNetCore.Razor.Design — Microsoft.AspNetCore.Razor.Design 2.2.0 → 2.3.0 available.
Outdated: Microsoft.AspNetCore.All — Microsoft.AspNetCore.All 2.2.1 → 2.2.8 available.
Outdated: Microsoft.AspNetCore.TestHost — Microsoft.AspNetCore.TestHost 2.2.0 → 10.0.9 available.
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 15.9.0 → 18.7.0 available.
Outdated: MSTest.TestAdapter — MSTest.TestAdapter 1.3.2 → 4.2.3 available.
Outdated: MSTest.TestFramework — MSTest.TestFramework 1.3.2 → 4.2.3 available.

D19 · Documentation Quality · XML-doc coverage · ×4

XML-doc coverage: LivrariaOnline.Domain LivrariaOnline.Domain/LivrariaOnline.Domain.csproj — LivrariaOnline.Domain: 0 % XML-doc coverage (0/38).
XML-doc coverage: LivrariaOnline.Infra.Data LivrariaOnline.Infra.Data/LivrariaOnline.Infra.Data.csproj — LivrariaOnline.Infra.Data: 0 % XML-doc coverage (0/27).
XML-doc coverage: LivrariaOnline.CrossCutting.IoC LivrariaOnline.CrossCutting.IoC/LivrariaOnline.CrossCutting.IoC.csproj — LivrariaOnline.CrossCutting.IoC: 0 % XML-doc coverage (0/2).
XML-doc coverage: LivrariaOnline.Application.Api LivrariaOnline.Application.Api/LivrariaOnline.Application.Api.csproj — LivrariaOnline.Application.Api: 0 % XML-doc coverage (0/35).

D15 · Churn × Complexity Hotspots · git history depth insufficient · ×1

git history depth insufficient — git history depth insufficient — install a full clone for reliable trend signal.

D22 · Internal API Consistency · No exposed public API · ×1

No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.

D35 · Change Coupling · git history depth insufficient · ×1

git history depth insufficient — git history depth insufficient — a full clone gives reliable change-coupling.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

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 auto --json --quiet --timeout 0 --metrics off .	0	—
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list LivrariaOnline.sln package --vulnerable --include-transitive --format json	44	artifacts/raw/dotnet-vulnerable.json
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-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.	0	—
D33 · JS/npm Dependency Vulnerabilities	trivy	—	trivy: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .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: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.	0	—

Run 019f1315-ed45-78c1-ac1a-197d4236eb42 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Tmoreirafreitas/LivrariaOnline

Executive summary

Top priorities

Diagnosis — what's actually going on

Trajectory

Architecture — module dependency graph

At a glance — Code Health · 76% · Strong

At a glance — Architecture · 83% · Strong

At a glance — Maturity · 40% · Weak · gated by M1, M2

At a glance — Readiness · 35% · Weak · gated by D12, P3

At a glance — Security · 45% · Weak · gated by D30, D36, C2

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts