Executive summary
err0r500/go-realworld-clean is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because the project keeps no record of its design decisions. It scores 72 out of 100, which the At risk rating leaves unchanged.
Maturity, at 65, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Pinning the dependencies to tagged releases is another step, worth about 2 points. Raising Maturity to 70 would lift the score to about 74.
Six known security holes in the packages the code depends on can be used by attackers. Four settings leave the servers or containers unsafe, and one automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages, correcting the unsafe settings and setting a waiting period for automatic updates would close these risks.
The product code is 2,024 lines, about €6,200 to rebuild.
If Maturity rose from 65 to 70, the lowest score rated Strong, the score would rise from 72 to about 74.
Rebuild cost: about €6,200 · Estimate
| Cost to rebuild | €2,100 to €10,000, for 35 to 110 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 72. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,024 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 com/err0r500/go-realworld-clean | 2 com/err0r500/go-realworld-clean/domain | 3 com/err0r500/go-realworld-clean/infra | 4 com/err0r500/go-realworld-clean/uc | 5 com/err0r500/go-realworld-clean/implem/dummy.articleValidator | 6 com/err0r500/go-realworld-clean/implem/jwt.authHandler | 7 com/err0r500/go-realworld-clean/implem/memory.articleRW | 8 com/err0r500/go-realworld-clean/implem/memory.commentRW | 9 com/err0r500/go-realworld-clean/implem/memory.tagsRW | 10 com/err0r500/go-realworld-clean/implem/memory.userRW |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 com/err0r500/go-realworld-clean | ||||||||||
| 2 com/err0r500/go-realworld-clean/domain | ||||||||||
| 3 com/err0r500/go-realworld-clean/infra | ||||||||||
| 4 com/err0r500/go-realworld-clean/uc | 23 | |||||||||
| 5 com/err0r500/go-realworld-clean/implem/dummy.articleValidator | 1 | 2 | ||||||||
| 6 com/err0r500/go-realworld-clean/implem/jwt.authHandler | 2 | |||||||||
| 7 com/err0r500/go-realworld-clean/implem/memory.articleRW | 2 | 2 | ||||||||
| 8 com/err0r500/go-realworld-clean/implem/memory.commentRW | 1 | 2 | ||||||||
| 9 com/err0r500/go-realworld-clean/implem/memory.tagsRW | 2 | |||||||||
| 10 com/err0r500/go-realworld-clean/implem/memory.userRW | 1 | 2 |
4→2 com/err0r500/go-realworld-clean/uc uses com/err0r500/go-realworld-clean/domain✕
- Connections
- 23 pairs of types, where a type in com/err0r500/go-realworld-clean/uc uses a type in com/err0r500/go-realworld-clean/domain.
- The types involved
github.com/err0r500/go-realworld-clean/uc.ArticleLogic→github.com/err0r500/go-realworld-clean/domain.Articlegithub.com/err0r500/go-realworld-clean/uc.ArticleLogic→github.com/err0r500/go-realworld-clean/domain.ArticleUpdatableFieldgithub.com/err0r500/go-realworld-clean/uc.ArticleLogic→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.ArticleRW→github.com/err0r500/go-realworld-clean/domain.Articlegithub.com/err0r500/go-realworld-clean/uc.ArticleRW→github.com/err0r500/go-realworld-clean/domain.ArticleFiltergithub.com/err0r500/go-realworld-clean/uc.ArticleValidator→github.com/err0r500/go-realworld-clean/domain.Articlegithub.com/err0r500/go-realworld-clean/uc.ArticlesLogic→github.com/err0r500/go-realworld-clean/domain.ArticleFiltergithub.com/err0r500/go-realworld-clean/uc.ArticlesLogic→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.CommentRW→github.com/err0r500/go-realworld-clean/domain.Commentgithub.com/err0r500/go-realworld-clean/uc.CommentsLogic→github.com/err0r500/go-realworld-clean/domain.Commentgithub.com/err0r500/go-realworld-clean/uc.FavoritesLogic→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.ProfileLogic→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.UserLogic→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.UserLogic→github.com/err0r500/go-realworld-clean/domain.UserUpdatablePropertygithub.com/err0r500/go-realworld-clean/uc.UserRW→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.UserValidator→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.interactor→github.com/err0r500/go-realworld-clean/domain.Articlegithub.com/err0r500/go-realworld-clean/uc.interactor→github.com/err0r500/go-realworld-clean/domain.ArticleFiltergithub.com/err0r500/go-realworld-clean/uc.interactor→github.com/err0r500/go-realworld-clean/domain.ArticleUpdatableFieldgithub.com/err0r500/go-realworld-clean/uc.interactor→github.com/err0r500/go-realworld-clean/domain.Commentgithub.com/err0r500/go-realworld-clean/uc.interactor→github.com/err0r500/go-realworld-clean/domain.Usergithub.com/err0r500/go-realworld-clean/uc.interactor→github.com/err0r500/go-realworld-clean/domain.UserUpdatablePropertygithub.com/err0r500/go-realworld-clean/uc.uc→github.com/err0r500/go-realworld-clean/domain.ArticleFilter
- Direction
- com/err0r500/go-realworld-clean/uc uses com/err0r500/go-realworld-clean/domain, so a change to com/err0r500/go-realworld-clean/domain can break com/err0r500/go-realworld-clean/uc, while a change to com/err0r500/go-realworld-clean/uc can't break com/err0r500/go-realworld-clean/domain.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/uc uses a module listed above it, which is the healthy direction.
5→2 com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses com/err0r500/go-realworld-clean/domain✕
- Connections
- 1 pair of types, where a type in com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses a type in com/err0r500/go-realworld-clean/domain.
- The types involved
github.com/err0r500/go-realworld-clean/implem/dummy.articleValidator.validator→github.com/err0r500/go-realworld-clean/domain.Article
- Direction
- com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses com/err0r500/go-realworld-clean/domain, so a change to com/err0r500/go-realworld-clean/domain can break com/err0r500/go-realworld-clean/implem/dummy.articleValidator, while a change to com/err0r500/go-realworld-clean/implem/dummy.articleValidator can't break com/err0r500/go-realworld-clean/domain.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses a module listed above it, which is the healthy direction.
5→4 com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses com/err0r500/go-realworld-clean/uc✕
- Connections
- 2 pairs of types, where a type in com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses a type in com/err0r500/go-realworld-clean/uc.
- The types involved
github.com/err0r500/go-realworld-clean/implem/dummy.articleValidator.articleValidator→github.com/err0r500/go-realworld-clean/uc.ArticleValidatorgithub.com/err0r500/go-realworld-clean/implem/dummy.articleValidator.validator→github.com/err0r500/go-realworld-clean/uc.ArticleValidator
- Direction
- com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses com/err0r500/go-realworld-clean/uc, so a change to com/err0r500/go-realworld-clean/uc can break com/err0r500/go-realworld-clean/implem/dummy.articleValidator, while a change to com/err0r500/go-realworld-clean/implem/dummy.articleValidator can't break com/err0r500/go-realworld-clean/uc.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/dummy.articleValidator uses a module listed above it, which is the healthy direction.
6→4 com/err0r500/go-realworld-clean/implem/jwt.authHandler uses com/err0r500/go-realworld-clean/uc✕
- Connections
- 2 pairs of types, where a type in com/err0r500/go-realworld-clean/implem/jwt.authHandler uses a type in com/err0r500/go-realworld-clean/uc.
- The types involved
github.com/err0r500/go-realworld-clean/implem/jwt.authHandler.jwt→github.com/err0r500/go-realworld-clean/uc.AuthHandlergithub.com/err0r500/go-realworld-clean/implem/jwt.authHandler.tokenHandler→github.com/err0r500/go-realworld-clean/uc.AuthHandler
- Direction
- com/err0r500/go-realworld-clean/implem/jwt.authHandler uses com/err0r500/go-realworld-clean/uc, so a change to com/err0r500/go-realworld-clean/uc can break com/err0r500/go-realworld-clean/implem/jwt.authHandler, while a change to com/err0r500/go-realworld-clean/implem/jwt.authHandler can't break com/err0r500/go-realworld-clean/uc.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/jwt.authHandler uses a module listed above it, which is the healthy direction.
7→2 com/err0r500/go-realworld-clean/implem/memory.articleRW uses com/err0r500/go-realworld-clean/domain✕
- Connections
- 2 pairs of types, where a type in com/err0r500/go-realworld-clean/implem/memory.articleRW uses a type in com/err0r500/go-realworld-clean/domain.
- The types involved
github.com/err0r500/go-realworld-clean/implem/memory.articleRW.rw→github.com/err0r500/go-realworld-clean/domain.Articlegithub.com/err0r500/go-realworld-clean/implem/memory.articleRW.rw→github.com/err0r500/go-realworld-clean/domain.ArticleFilter
- Direction
- com/err0r500/go-realworld-clean/implem/memory.articleRW uses com/err0r500/go-realworld-clean/domain, so a change to com/err0r500/go-realworld-clean/domain can break com/err0r500/go-realworld-clean/implem/memory.articleRW, while a change to com/err0r500/go-realworld-clean/implem/memory.articleRW can't break com/err0r500/go-realworld-clean/domain.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/memory.articleRW uses a module listed above it, which is the healthy direction.
7→4 com/err0r500/go-realworld-clean/implem/memory.articleRW uses com/err0r500/go-realworld-clean/uc✕
- Connections
- 2 pairs of types, where a type in com/err0r500/go-realworld-clean/implem/memory.articleRW uses a type in com/err0r500/go-realworld-clean/uc.
- The types involved
github.com/err0r500/go-realworld-clean/implem/memory.articleRW.articleRW→github.com/err0r500/go-realworld-clean/uc.ArticleRWgithub.com/err0r500/go-realworld-clean/implem/memory.articleRW.rw→github.com/err0r500/go-realworld-clean/uc.ArticleRW
- Direction
- com/err0r500/go-realworld-clean/implem/memory.articleRW uses com/err0r500/go-realworld-clean/uc, so a change to com/err0r500/go-realworld-clean/uc can break com/err0r500/go-realworld-clean/implem/memory.articleRW, while a change to com/err0r500/go-realworld-clean/implem/memory.articleRW can't break com/err0r500/go-realworld-clean/uc.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/memory.articleRW uses a module listed above it, which is the healthy direction.
8→2 com/err0r500/go-realworld-clean/implem/memory.commentRW uses com/err0r500/go-realworld-clean/domain✕
- Connections
- 1 pair of types, where a type in com/err0r500/go-realworld-clean/implem/memory.commentRW uses a type in com/err0r500/go-realworld-clean/domain.
- The types involved
github.com/err0r500/go-realworld-clean/implem/memory.commentRW.rw→github.com/err0r500/go-realworld-clean/domain.Comment
- Direction
- com/err0r500/go-realworld-clean/implem/memory.commentRW uses com/err0r500/go-realworld-clean/domain, so a change to com/err0r500/go-realworld-clean/domain can break com/err0r500/go-realworld-clean/implem/memory.commentRW, while a change to com/err0r500/go-realworld-clean/implem/memory.commentRW can't break com/err0r500/go-realworld-clean/domain.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/memory.commentRW uses a module listed above it, which is the healthy direction.
8→4 com/err0r500/go-realworld-clean/implem/memory.commentRW uses com/err0r500/go-realworld-clean/uc✕
- Connections
- 2 pairs of types, where a type in com/err0r500/go-realworld-clean/implem/memory.commentRW uses a type in com/err0r500/go-realworld-clean/uc.
- The types involved
github.com/err0r500/go-realworld-clean/implem/memory.commentRW.commentRW→github.com/err0r500/go-realworld-clean/uc.CommentRWgithub.com/err0r500/go-realworld-clean/implem/memory.commentRW.rw→github.com/err0r500/go-realworld-clean/uc.CommentRW
- Direction
- com/err0r500/go-realworld-clean/implem/memory.commentRW uses com/err0r500/go-realworld-clean/uc, so a change to com/err0r500/go-realworld-clean/uc can break com/err0r500/go-realworld-clean/implem/memory.commentRW, while a change to com/err0r500/go-realworld-clean/implem/memory.commentRW can't break com/err0r500/go-realworld-clean/uc.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/memory.commentRW uses a module listed above it, which is the healthy direction.
9→4 com/err0r500/go-realworld-clean/implem/memory.tagsRW uses com/err0r500/go-realworld-clean/uc✕
- Connections
- 2 pairs of types, where a type in com/err0r500/go-realworld-clean/implem/memory.tagsRW uses a type in com/err0r500/go-realworld-clean/uc.
- The types involved
github.com/err0r500/go-realworld-clean/implem/memory.tagsRW.rw→github.com/err0r500/go-realworld-clean/uc.TagsRWgithub.com/err0r500/go-realworld-clean/implem/memory.tagsRW.tagsRW→github.com/err0r500/go-realworld-clean/uc.TagsRW
- Direction
- com/err0r500/go-realworld-clean/implem/memory.tagsRW uses com/err0r500/go-realworld-clean/uc, so a change to com/err0r500/go-realworld-clean/uc can break com/err0r500/go-realworld-clean/implem/memory.tagsRW, while a change to com/err0r500/go-realworld-clean/implem/memory.tagsRW can't break com/err0r500/go-realworld-clean/uc.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/memory.tagsRW uses a module listed above it, which is the healthy direction.
10→2 com/err0r500/go-realworld-clean/implem/memory.userRW uses com/err0r500/go-realworld-clean/domain✕
- Connections
- 1 pair of types, where a type in com/err0r500/go-realworld-clean/implem/memory.userRW uses a type in com/err0r500/go-realworld-clean/domain.
- The types involved
github.com/err0r500/go-realworld-clean/implem/memory.userRW.rw→github.com/err0r500/go-realworld-clean/domain.User
- Direction
- com/err0r500/go-realworld-clean/implem/memory.userRW uses com/err0r500/go-realworld-clean/domain, so a change to com/err0r500/go-realworld-clean/domain can break com/err0r500/go-realworld-clean/implem/memory.userRW, while a change to com/err0r500/go-realworld-clean/implem/memory.userRW can't break com/err0r500/go-realworld-clean/domain.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/memory.userRW uses a module listed above it, which is the healthy direction.
10→4 com/err0r500/go-realworld-clean/implem/memory.userRW uses com/err0r500/go-realworld-clean/uc✕
- Connections
- 2 pairs of types, where a type in com/err0r500/go-realworld-clean/implem/memory.userRW uses a type in com/err0r500/go-realworld-clean/uc.
- The types involved
github.com/err0r500/go-realworld-clean/implem/memory.userRW.rw→github.com/err0r500/go-realworld-clean/uc.UserRWgithub.com/err0r500/go-realworld-clean/implem/memory.userRW.userRW→github.com/err0r500/go-realworld-clean/uc.UserRW
- Direction
- com/err0r500/go-realworld-clean/implem/memory.userRW uses com/err0r500/go-realworld-clean/uc, so a change to com/err0r500/go-realworld-clean/uc can break com/err0r500/go-realworld-clean/implem/memory.userRW, while a change to com/err0r500/go-realworld-clean/implem/memory.userRW can't break com/err0r500/go-realworld-clean/uc.
- Position
- Below the diagonal: com/err0r500/go-realworld-clean/implem/memory.userRW uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.3 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.9 pts | Medium | Architecture documentation |
| Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +2.5 pts | Low | Dependency Hygiene |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.2 pts | Medium | Deployment & Rollback |
| Swallowed exception (caught, then discarded) | +1.8 pts | Medium | Exception handling |
| Consider OpenTelemetry tracing/metrics (go.opentelemetry.io/otel) and a health-check endpoint (a /healthz handler) for operability. | +0.8 pts | Medium | Observability |
| Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). | +0.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.3 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| uc/articlePut.go | 8.2 | Near-clean | Explicit Debt: TodoComment |
| implem/memory.userRW/readWriter.go | 8.2 | Near-clean | Explicit Debt: TodoComment |
| implem/logrus.logger/logrus.go | 8.2 | Near-clean | Explicit Debt: FixmeComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey 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. All 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 39 dimensions across the health lenses
- 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, 27 of 43 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 or a scanner, 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 |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ 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 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's REDACTED declares a Go language version older than 1.17 (or none), and before 1.17 a REDACTED lists only the modules version selection needs, not every module the build compiles. The licences are resolved per module version, so grading the modules that file happens to list would be a verdict over part of the dependency graph. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 47 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 1 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D34 Knowledge Freshness — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits to judge knowledge freshness (47 commit(s) sampled).
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — -------------------- 6 | ADD . $GOPATH/src/github.com/err0r500/go-realworld-clean 7 | WORKDIR $GOPATH/src/github.com/err0r500/go-realworld-clean 8 | >>> RUN go get -u github.com/golang/dep/cmd/dep 9 | RUN dep ensure -vendor-only 10 | -------------------- ERROR: failed to solve: process "/bin/sh -c go get -u github.com/golang/dep/cmd/dep" did not complete successfully: exit code: 1; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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".
Dimensions
D1 · Cyclomatic Complexity
0 function(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 function(s) exceeded the cognitive complexity threshold of 15.
D4 · Code Duplication
0 duplicated block group(s) detected.
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D8 · Code Coverage
Statement coverage 59.6% — read from a committed Go coverprofile report (coverage.txt); the in-image collector couldn't run the suite (commonly external-service dependencies). A real measurement, but from a committed artifact rather than a fresh in-image run.
D9 · Test Distribution
64 test methods: 64 unit, 0 integration, 0 BDD, 0 e2e. The Go suite contributes 64 test case(s) across 33 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 33 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/err0r500/go-realworld-clean): measured (0 flaky).
D12 · Dependency Hygiene
8 outdated, 0 author-deprecated direct Go module(s), 3 pinning or checksum defect(s). 11 of 11 direct requirement(s) were graded against proxy.golang.org (0 not served there, 2 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and REDACTED there.
What to do
- Resolve the 3 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 2024 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with articlePut.go, readWriter.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with logrus.go. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were 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).
D26 · Project Cohesion
0 of 1 build units (Go) flagged as possibly oversized/incoherent.
D27 · Navigability
39 % of calls cross a namespace and 46 % go through an interface, but 38 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
9 finding(s): 2 critical, 4 high, 3 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
8 finding(s): 0 critical, 4 high, 2 medium, 2 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (go.opentelemetry.io/otel) and a health-check endpoint (a /healthz handler) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P9 · Domain vs controller coverage
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×6) — implem/gin.server/ROUTER.go:116, implem/gin.server/ROUTER.go:121, implem/gin.server/articles.go:22, …
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 70% | Adequate | Acceptable, with room to improve. |
| Security | 92% | Checked 4 of 10 | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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
Not included — 75 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 — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — -------------------- 6 | ADD . $GOPATH/src/github.com/err0r500/go-realworld-clean 7 | WORKDIR $GOPATH/src/github.com/err0r500/go-realworld-clean 8 | >>> RUN go get -u github.com/golang/dep/cmd/dep 9 | RUN dep ensure -vendor-only 10 | -------------------- ERROR: failed to solve: process "/bin/sh -c go get -u github.com/golang/dep/cmd/dep" did not complete successfully: exit code: 1; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~2474 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D14 License Compliance — Go module licences not graded — a REDACTED predates Go 1.17 and does not list its whole module graph
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D3 God Classes — Most of this repository's production source (.go) was not read by god-class detection, so type and module size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's type and module size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go source (service entry point: infra/gin.go:32 (gin.New())
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 18 finding(s)
- Swallowed exception (caught, then discarded) implem/gin.server/ROUTER.go:116
- Swallowed exception (caught, then discarded) implem/gin.server/ROUTER.go:121
- Swallowed exception (caught, then discarded) implem/gin.server/articles.go:22
- Swallowed exception (caught, then discarded) implem/gin.server/articles.go:27
- Swallowed exception (caught, then discarded) implem/gin.server/articles.go:54
- Swallowed exception (caught, then discarded) implem/gin.server/articles.go:59
- Dependency pinned to a stale untagged commit: github.com/asaskevich/govalidator
- Dependency pinned to a stale untagged commit: github.com/gin-gonic/gin
- Dependency pinned to a stale untagged commit: github.com/itsjamie/gin-cors
- REDACTED
- REDACTED
- REDACTED
- TodoComment uc/articlePut.go:16
- TodoComment implem/memory.userRW/readWriter.go:19
- REDACTED
- REDACTED
- FixmeComment implem/logrus.logger/logrus.go:59
- Coverage collected but not gated
Minor — 5 finding(s)
- REDACTED
- REDACTED
- No ADRs found
- High interface indirection
- No ADRs
Minor — 9 finding(s)
- Outdated: github.com/gin-gonic/gin
- Outdated: github.com/golang/mock
- Outdated: github.com/gosimple/slug
- Outdated: github.com/sirupsen/logrus
- Outdated: github.com/spf13/cobra
- Outdated: github.com/spf13/viper
- Outdated: github.com/stretchr/testify
- Outdated: gopkg.in/h2non/baloo.v3
- Coverage read from a committed report
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aa6f8b95ccac4a53976034b09ac2055b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aa6f8b95ccac4a53976034b09ac2055b/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-7e78d12195b143de94629394c0c7071c | 9 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-7e78d12195b143de94629394c0c7071c | 0 | artifacts/raw/osv-scanner.json |