Executive summary
astral-sh/ty falls short of our standard for a preview release because its Testing dimensions are rated Critical, and the project has no automated tests. It scores 56.9 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 43.2, is the weakest lens and counts most in the score. The best first step for the work it takes is adding a diagnostic log, worth about 8.5 points. Adding automated tests comes next, worth about 13.7 points. Raising Production Readiness to 62 would lift the score to about 65.5.
Eight secrets can leak from the build pipeline. Two settings leave the servers or containers unsafe, and one pipeline tool is referenced by a changeable name, so the build pipeline can be tampered with. Limiting each secret to its own step, correcting the unsafe settings and pinning the tool to an exact version would close these risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration.
The product code is 1,398 lines, about β¬1,400 to rebuild.
If Production Readiness rose from 43.2 to 62, the lowest score rated Strong, the score would rise from 56.9 to about 65.5.
Fixed since the last survey: 4 findings
- Cyclomatic Complexity Β· build_ty_pgo.profile_language_server (cyclomatic 17) scripts/build_ty_pgo.py
- Cognitive Complexity Β· build_ty_pgo.profile_language_server (cognitive 19) scripts/build_ty_pgo.py
- Cognitive Complexity Β· build_ty_pgo.ecosystem_python_files (cognitive 18) scripts/build_ty_pgo.py
- God Classes Β· FileTooLong: scripts/build_ty_pgo.py scripts/build_ty_pgo.py
Rebuild cost: about β¬1,400 Β· Estimate
| Cost to rebuild | β¬480 to β¬2,400, for 8 to 25 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 | ×0.8 at a score of 57. 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 | Very small: 1,398 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 docs.js | 2 python.ty | 3 python.ty._find_ty | 4 scripts.build_ty_pgo | 5 scripts.update_schemastore | 6 scripts |
|---|---|---|---|---|---|---|
| 1 docs.js | ||||||
| 2 python.ty | ||||||
| 3 python.ty._find_ty | ||||||
| 4 scripts.build_ty_pgo | ||||||
| 5 scripts.update_schemastore | ||||||
| 6 scripts | 1 | 2 |
6β4 scripts uses scripts.build_ty_pgo✕
- Connections
- 1 pair of types, where a type in scripts uses a type in scripts.build_ty_pgo.
- The types involved
scripts.build_ty_pgoβscripts.build_ty_pgo.EcosystemProject
- Direction
- scripts uses scripts.build_ty_pgo, so a change to scripts.build_ty_pgo can break scripts, while a change to scripts can't break scripts.build_ty_pgo.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
6β5 scripts uses scripts.update_schemastore✕
- Connections
- 2 pairs of types, where a type in scripts uses a type in scripts.update_schemastore.
- The types involved
scripts.update_schemastoreβscripts.update_schemastore.GitProtocolscripts.update_schemastoreβscripts.update_schemastore.SchemastoreRepos
- Direction
- scripts uses scripts.update_schemastore, so a change to scripts.update_schemastore can break scripts, while a change to scripts can't break scripts.update_schemastore.
- Position
- Below the diagonal: scripts 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 |
|---|---|---|
| A05:2025 β Injection | 10 | High / Critical |
| A02:2025 β Security Misconfiguration | 4 | High / Critical |
| A03:2025 β Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing β a discarded error is the failure the user cannot describe and you cannot reproduce; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing β a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.5 pts | Medium | Observability |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +13.7 pts | High | Code Coverage |
| 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. | +4.0 pts | Medium | Architecture documentation |
| Resolve the 1 Scattered collaborators finding(s) in Navigability. | +1.7 pts | Low | Navigability |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (8). | +0.6 pts | Low | Static Analysis (SAST) |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.2 pts | Medium | Documentation (README) |
| Reconcile the README with reality: docs/python-version.md names Python 3.7, but pyproject.toml:4 requires `requires-python = ">=3.8"`: the package does not install on Python 3.7. | +0.7 pts | Medium | Documentation accuracy |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED. | +0.2 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Near-clean | Supply-chain Provenance & Signing: REDACTED |
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 37 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 β 37 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, 16 of 22 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
- D12 Dependency Hygiene β 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 β 0 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and the index lookup answered not published for every exact pin asked about (0 lookup(s)), so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (a Python pyproject.toml/requirements.txt (pip/uv/Poetry)), which this pass does not parse yet β so this dimension asserts nothing about this repository's licensing in either direction.
- 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.
- 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 an ADMISSION gap, not an environment fault: it declares a published package (pyproject.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises β so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker β not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AXB2 Runtime readiness β 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. A file the REDACTED copies (`ruff/Cargo.lock`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it. (rule: missing-build-input). The renderer reported: docker build failed (exit 1) β 44 | >>> COPY ruff/Cargo.lock Cargo.lock 45 | COPY dist-workspace.toml ../dist-workspace.toml 46 | RUN cargo zigbuild --bin ty --target $(cat rust_target.txt) --release -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref e7ae7cc1-cbd9-4ed8-98dd-bf3e0216b471::es5u3y40pc2eloxqt37nmsqv4: "/ruff/Cargo.lock": not found; likely cause (not identified): a file the REDACTED copies (`ruff/Cargo.lock`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it; runtime evidence skipped.
- 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) β 44 | >>> COPY ruff/Cargo.lock Cargo.lock 45 | COPY dist-workspace.toml ../dist-workspace.toml 46 | RUN cargo zigbuild --bin ty --target $(cat rust_target.txt) --release -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref e7ae7cc1-cbd9-4ed8-98dd-bf3e0216b471::es5u3y40pc2eloxqt37nmsqv4: "/ruff/Cargo.lock": not found; likely cause (not identified): a file the REDACTED copies (`ruff/Cargo.lock`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it; 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.
- 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, Scala, Rust and Java source only, and this repository's Python is most of its product and 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, Scala and Rust source only, and this repository's Python is most of its product and 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.
- M4 Documentation accuracy β 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P3 Security & performance tooling β 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. `.github/renovate.json5` is not valid JSON ('r' is invalid after a value. Expected either ',', '}', or ']'. LineNumber: 13 | BytePositionInLine: 65.). Each was counted as dependency-update automation without being read, so whether it actually schedules updates is unverified: if it does not, the dep-scan credit on this card is not earned.
- 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.
- 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, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
- X5 Nullable reference types β 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Python 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.
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.
- 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 β 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.
- D5 Coupling: Coupling is measured between projects/assemblies β runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree β a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history β a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension β pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension β code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS β files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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 (go.mod, 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) β controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 Β· Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 Β· Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 Β· God Classes
0 god class(es) detected.
D4 Β· Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 1,398) are in a reported copy.
D5 Β· Coupling
3 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D8 Β· Code Coverage
No automated tests β no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. β One of this dimension's main actionable groups (1 issue-level).
D13 Β· Secret Scanning
Secret scan ran and found no leaked secrets.
D15 Β· Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 Β· Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 5 of the 8 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 Β· Explicit Debt
0 deducted task-comment markers across 1398 LoC (0.0/KLoC) β score 10.0. 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.
D19 Β· Documentation Quality
1 of 1 documentation facets pass in full. 21 document(s) read across 1 unit(s).
D27 Β· Navigability
100 % of calls cross a namespace and 0 % go through an interface, but 25 % of collaborators are co-located β so following a call takes several hops. Baseline: small β navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators 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)
10 finding(s): 0 critical, 10 high, 0 medium, 0 low. semgrep hit a parse error in 1 file(s) β `docs/.overrides/main.html` (lines 1β4, line 6, line 8, β¦) β so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (8). β One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED. β One of this dimension's main actionable groups (1 issue-level).
- 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
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 Β· IaC & Container Security
4 finding(s): 0 critical, 2 high, 2 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security β start with REDACTED (2). β One of this dimension's main actionable groups (2 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).
D34 Β· Knowledge Freshness
Every significant source file has living knowledge β recently and meaningfully worked. Counted over 5 of the 8 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 Β· Change Coupling
No strong hidden change-coupling between production files.
D36 Β· Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing β start with REDACTED. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 recommendation-level).
D37 Β· Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 3 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)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
M4 Β· Documentation accuracy
- docs/python-version.md names Python 3.7, but pyproject.toml:4 requires `requires-python = ">=3.8"`: the package does not install on Python 3.7. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. β docs/python-version.md:49
What to do
- Reconcile the README with reality: docs/python-version.md names Python 3.7, but pyproject.toml:4 requires `requires-python = ">=3.8"`: the package does not install on Python 3.7.
P1 Β· CI/CD gates
P10 Β· Library API & versioning
P2 Β· Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page β but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing β a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 Β· Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 Β· Deployment & Rollback
P6 Β· Release Hygiene
X12 Β· Unreachable branch
X3 Β· Exception handling
Reference β by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100.0 | Exemplary | Strongest area. |
| Architecture | 69.0 | Strong | Solid. |
| Maturity | 60.7 | Adequate β gated by M2 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Readiness | 43.2 | Adequate β gated by D8, P2 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Security | 80.7 | Adequate β gated by D29 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
Not evidenced β 1 control(s) we could not find positive evidence for
- P5 DR & Backup β not evidenced β repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included β 79 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.
- AX1 Captive dependencies β Not applicable: this repository's Python 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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 β no interface, protocol or abstract type declares an operation an implementer must write
- 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) β 44 | >>> COPY ruff/Cargo.lock Cargo.lock 45 | COPY dist-workspace.toml ../dist-workspace.toml 46 | RUN cargo zigbuild --bin ty --target $(cat rust_target.txt) --release -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref e7ae7cc1-cbd9-4ed8-98dd-bf3e0216b471::es5u3y40pc2eloxqt37nmsqv4: "/ruff/Cargo.lock": not found; likely cause (not identified): a file the REDACTED copies (`ruff/Cargo.lock`) is not in the build context; the repository declares git submodules, and a submodule our checkout did not fetch would explain it; 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 β No access-control surface detected in the analyzed source β this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here β a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail β No personal data detected in a persisted data model β no PII-named field (email, first_name, date_of_birth, phone, β¦) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema β and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, β¦) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention β No personal data detected in a persisted data model β no PII-named field (email, first_name, date_of_birth, phone, β¦) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema β and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, β¦) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights β No personal data detected in a persisted data model β no PII-named field (email, first_name, date_of_birth, phone, β¦) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema β and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, β¦) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality β No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability β No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk β which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite β found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene β Not scored β 0 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and the index lookup answered not published for every exact pin asked about (0 lookup(s)), so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance β Package manifest not parsed for licence data β analyzer language-coverage gap
- D18 Solution Shape β D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality β N/A β ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency β N/A β too few peers to establish a naming convention (96 declarations, no unit with a dominant convention).
- 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; comments in this repository's .py source were not judged.
- D25 ADR Conformance β no ADRs to check
- D26 Project Cohesion β This repository is one build unit, `(repository root)` (1475 LoC, 12 module-visible types across 3 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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.
- 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.
- D6 Cohesion (LCOM4) β Cohesion (LCOM4) was not measured: of the 8 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (3 with fewer than two methods, 5 stateless), so LCOM4 is undefined for every type in this repository. Not scored β the metric does not apply here, and this is not a finding about this repository.
- 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 β not scored β this repository shows only 1 of the 3 signals this lens looks for (2 value object(s))
- 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, Scala, Rust and Java, 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
- P12 CI test-gate honesty β Reported, not scored β and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience β not applicable β no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- 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
- P9 Domain vs controller coverage β coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here β Test coverage (D8) says why
- PF1 Benchmark discipline β Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, 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: this repository declares no async functions, 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.
- X1 Async correctness β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation β no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller β a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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 β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 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
- 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 β 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No automated tests
Serious β 5 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No structured logging
Minor β 4 finding(s)
- Scattered collaborators
- REDACTED
- No ADRs
- README/code drift docs/python-version.md:49
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-80dadf7acf8f468b8f2d51870fb818b0/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 Β· Secrets (history) | gitleaks | β | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=578" --report-format json --report-path /tmp/watchdog-gitleaks-80dadf7acf8f468b8f2d51870fb818b0/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-80dadf7acf8f468b8f2d51870fb818b0/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 . | 10 | 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 . | 0 | artifacts/raw/osv-scanner.json |
| D31 Β· IaC & Container Security | trivy | β | trivy config --format json --quiet . | 4 | 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 | β |
| 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 . | 0 | artifacts/raw/osv-scanner.json |