Executive summary
huggingface/swift-transformers falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 68 out of 100 and is rated Adequate, and two of its three critical findings are security problems in its automatic dependency updates and in the build pipeline.
Maturity, at 62, is the weakest lens and counts most in the score. The best first steps are making the naming consistent and recording design decisions, each worth about 6 points. Raising Maturity to 70 would lift the score to about 72.
One automatic update takes new releases before a bad one can be spotted. One pipeline tool is referenced by a changeable name, so the build pipeline can be tampered with. Setting a waiting period for automatic updates and pinning the tool to an exact version would close both risks. The test the project itself marks as unreliable needs fixing or deleting.
The product code is 8,510 lines, about €19,000 to rebuild.
If Maturity rose from 62 to 70, the lowest score rated Strong, the score would rise from 68 to about 72.
New since the last survey: 16 findings
- Cognitive Complexity · BinaryDistinctString.decodeUTF16 (cognitive 16) Sources/Hub/BinaryDistinct.swift
- Code Duplication · Edited copy of a member (16 corresponding lines) Sources/Tokenizers/Decoder.swift
- Code Duplication · Edited copy of a member (13 corresponding lines) Sources/Tokenizers/Normalizer.swift
- Code Duplication · Edited copy of a member (11 corresponding lines) Sources/Tokenizers/Tokenizer.swift
- Code Duplication · Edited copy of a member (10 corresponding lines) Sources/Tokenizers/PreTokenizer.swift
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) Sources/Generation/LogitsWarper/MinPLogitsWarper.swift
- Code Duplication · Edited copy of a member (13 corresponding lines) Sources/Tokenizers/Tokenizer.swift
- Code Duplication · Edited copy of a member (4 corresponding lines) Sources/Hub/BinaryDistinct.swift
- Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) Sources/Hub/HubApi.swift
- Code Duplication · Edited copy of a member (4 corresponding lines) Sources/Hub/HubApi.swift
- Code Duplication · Edited copy of a member (10 corresponding lines) Sources/Tokenizers/BertTokenizer.swift
- Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) Sources/Hub/HubApi.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) Sources/Hub/HubApi.swift
- Code Duplication · Edited copy of a member (6 corresponding lines) Sources/Generation/LogitsWarper/RepetitionPenaltyLogitsProcessor.swift
- Code Duplication · Edited copy of a member (14 corresponding lines) Sources/Tokenizers/BertTokenizer.swift
- Test Quality · No assertions: missingVocabThrowsFirst Tests/TokenizersTests/BPEMergesTests.swift
Fixed since the last survey: 4 findings
- Code Duplication · Duplicated block (10–11 lines × 2) Sources/Generation/LogitsWarper/MinPLogitsWarper.swift
- Code Duplication · Duplicated block (8 lines × 2) Sources/Models/LanguageModel.swift
- Code Duplication · Duplicated block (6 lines × 2) Sources/Generation/LogitsWarper/RepetitionPenaltyLogitsProcessor.swift
- Churn × Complexity Hotspots · Hotspot: Sources/Tokenizers/Normalizer.swift Sources/Tokenizers/Normalizer.swift
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,200 to €31,000, for 103 to 327 hours of work, about 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.0 at a score of 68. 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: 8,510 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Tokenizers | 2 Hub | 3 Generation | 4 Models |
|---|---|---|---|---|
| 1 Tokenizers | 118 | |||
| 2 Hub | 4 | |||
| 3 Generation | 1 | 1 | ||
| 4 Models | 3 | 10 | 5 |
1→2 Tokenizers uses Hub part of a loop✕
- Connections
- 118 pairs of types, where a type in Tokenizers uses a type in Hub. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tokenizers.AutoTokenizer→Hub.ConfigTokenizers.AutoTokenizer→Hub.HubApiTokenizers.AutoTokenizer→Hub.StringTokenizers.BPETokenizer→Hub.ConfigTokenizers.BPETokenizer→Hub.StringTokenizers.BasicTokenizer→Hub.StringTokenizers.BertNormalizer→Hub.ConfigTokenizers.BertNormalizer→Hub.StringTokenizers.BertPreTokenizer→Hub.ConfigTokenizers.BertPreTokenizer→Hub.StringTokenizers.BertProcessing→Hub.ConfigTokenizers.BertProcessing→Hub.StringTokenizers.BertTokenizer→Hub.ConfigTokenizers.BertTokenizer→Hub.StringTokenizers.ByteFallbackDecoder→Hub.ConfigTokenizers.ByteFallbackDecoder→Hub.StringTokenizers.ByteLevelDecoder→Hub.ConfigTokenizers.ByteLevelDecoder→Hub.StringTokenizers.ByteLevelPostProcessor→Hub.ConfigTokenizers.ByteLevelPostProcessor→Hub.StringTokenizers.ByteLevelPreTokenizer→Hub.ConfigTokenizers.ByteLevelPreTokenizer→Hub.StringTokenizers.BytePair→Hub.StringTokenizers.Decoder→Hub.ConfigTokenizers.Decoder→Hub.String
- Direction
- Tokenizers uses Hub, so a change to Hub can break Tokenizers, while a change to Tokenizers can't break Hub.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→1 Hub uses Tokenizers✕
- Connections
- 4 pairs of types, where a type in Hub uses a type in Tokenizers.
- The types involved
Hub.BinaryDistinctCharacter→Tokenizers.CharacterHub.Config→Tokenizers.DecoderHub.String→Tokenizers.CharacterHub.String→Tokenizers.SplitDelimiterBehavior
- Direction
- Hub uses Tokenizers, so a change to Tokenizers can break Hub, while a change to Hub can't break Tokenizers.
- Position
- Below the diagonal: Hub uses a module listed above it, which is the healthy direction.
3→1 Generation uses Tokenizers✕
- Connections
- 1 pair of types, where a type in Generation uses a type in Tokenizers.
- The types involved
Generation.Generation→Tokenizers.Tokenizer
- Direction
- Generation uses Tokenizers, so a change to Tokenizers can break Generation, while a change to Generation can't break Tokenizers.
- Position
- Below the diagonal: Generation uses a module listed above it, which is the healthy direction.
3→2 Generation uses Hub✕
- Connections
- 1 pair of types, where a type in Generation uses a type in Hub.
- The types involved
Generation.Generation→Hub.String
- Direction
- Generation uses Hub, so a change to Hub can break Generation, while a change to Generation can't break Hub.
- Position
- Below the diagonal: Generation uses a module listed above it, which is the healthy direction.
4→1 Models uses Tokenizers✕
- Connections
- 3 pairs of types, where a type in Models uses a type in Tokenizers.
- The types involved
Models.LanguageModel→Tokenizers.TokenizerModels.LanguageModelProtocol→Tokenizers.TokenizerModels.LanguageModelWithStatefulKVCache→Tokenizers.Tokenizer
- Direction
- Models uses Tokenizers, so a change to Tokenizers can break Models, while a change to Models can't break Tokenizers.
- Position
- Below the diagonal: Models uses a module listed above it, which is the healthy direction.
4→2 Models uses Hub✕
- Connections
- 10 pairs of types, where a type in Models uses a type in Hub.
- The types involved
Models.Header→Hub.DataModels.LanguageModel→Hub.ConfigModels.LanguageModel→Hub.LanguageModelConfigurationFromHubModels.LanguageModel→Hub.StringModels.LanguageModelProtocol→Hub.StringModels.Offset→Hub.StringModels.Safetensor→Hub.DataModels.TextGenerationModel→Hub.StringModels.TokenizerError→Hub.StringModels.WeightsError→Hub.String
- Direction
- Models uses Hub, so a change to Hub can break Models, while a change to Models can't break Hub.
- Position
- Below the diagonal: Models uses a module listed above it, which is the healthy direction.
4→3 Models uses Generation✕
- Connections
- 5 pairs of types, where a type in Models uses a type in Generation.
- The types involved
Models.LanguageModel→Generation.GenerationConfigModels.LanguageModelProtocol→Generation.GenerationConfigModels.LanguageModelWithStatefulKVCache→Generation.GenerationConfigModels.TextGenerationModel→Generation.GenerationModels.TextGenerationModel→Generation.GenerationConfig
- Direction
- Models uses Generation, so a change to Generation can break Models, while a change to Models can't break Generation.
- Position
- Below the diagonal: Models 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
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
Top priorities: 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 1 `HubRepoIDCacheActor` spells `ID` where 46 names in the project spell it… finding(s) in Naming Consistency — start with HubApi.swift; Resolve the 1 `resolveHubClientRepoID` spells `ID` where 46 names in the project spell… finding(s) in Naming Consistency — start with HubApi.swift.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 `HubRepoIDCacheActor` spells `ID` where 46 names in the project spell it… finding(s) in Naming Consistency — start with HubApi.swift. | +5.9 pts | Low | Naming Consistency |
| Resolve the 1 `resolveHubClientRepoID` spells `ID` where 46 names in the project spell… finding(s) in Naming Consistency — start with HubApi.swift. | +5.9 pts | Low | Naming Consistency |
| 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. | +5.9 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.9 pts | Medium | Security & performance tooling |
| Swallowed exception (empty catch) | +2.6 pts | Medium | Exception handling |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with YYJSONParser.swift, MinPLogitsWarper.swift, RepetitionPenaltyLogitsProcessor.swift. | +1.2 pts | Low | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.1 pts | Medium | Release Hygiene |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.5 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Sources/Tokenizers/Tokenizer.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/Hub/HubApi.swift | 6.3 | Mixed | Cyclomatic Complexity: DownloadProgressBridge.emitIfNeeded (cyclomatic 22) |
| Sources/Tokenizers/TokenLattice.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Sources/Tokenizers/Decoder.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tests/HubTests/HubApiTests.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Tests/TokenizersTests/NormalizerTests.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Sources/Hub/Config.swift | 7.1 | Mixed | Cyclomatic Complexity: Data.== (cyclomatic 21) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| Sources/Models/LanguageModel.swift | 7.3 | Mixed | Explicit Debt: TodoComment |
| Sources/Tokenizers/BPETokenizer.swift | 7.8 | Mixed | Cyclomatic Complexity: BPETokenizer.bpe (cyclomatic 19) |
| Sources/Tokenizers/Normalizer.swift | 7.8 | Mixed | Cyclomatic Complexity: UnicodeScalar.isCJKUnifiedIdeograph (cyclomatic 16) |
| Sources/Hub/BinaryDistinct.swift | 7.8 | Mixed | Cognitive Complexity: BinaryDistinctString.decodeUTF16 (cognitive 16) |
| Sources/Tokenizers/BertTokenizer.swift | 7.8 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| Tests/GenerationTests/LogitsProcessorTests.swift | 7.8 | Mixed | Test Quality: No assertions: testTemperatureWarper |
| Tests/TokenizersIntegrationTests/ChatTemplateTests.swift | 8.0 | Near-clean | Test Reliability: Test declared unreliable: deepSeekQwenChatTemplate |
| Tests/TokenizersTests/PreTokenizerTests.swift | 8.2 | Near-clean | Explicit Debt: TodoComment |
| Sources/Tokenizers/Trie.swift | 8.2 | Near-clean | Explicit Debt: TodoComment |
| Sources/Hub/Hub.swift | 8.5 | Near-clean | Cognitive Complexity: LanguageModelConfigurationFromHub.loadConfig (cognitive 25) |
| Sources/Generation/Generation.swift | 8.5 | Near-clean | Cognitive Complexity: Generation.createLogitsProcessorList (cognitive 17) |
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 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 36 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, 87 of 97 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — 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 repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- 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 — 9 SwiftPM declaration(s) across 3 `Package.swift` and 0 committed pin(s) were read for PINNING discipline (2 defect(s) reported), but the outdated signal comes from listing each declared repository's release tags rather than from a registry, and none of them resolved to a version to compare, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — 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. 2 of this repository's SwiftPM dependencies could not be fetched at a pinned revision and are repositories api.deps.dev has not indexed, so their licences were not read and the verdict does not cover them: benchmark, swift-jinja.
- D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `Sources/Generation/Generation.swift`, `Sources/Hub/Hub.swift`, `Sources/Hub/HubApi.swift`, `Sources/Hub/YYJSONParser.swift`, `Sources/Models/LanguageModel.swift`, … (+2 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- 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.
- 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.
- 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 Swift 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 Swift 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.
- 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.
- X15 Unvalidated length from an untrusted reader — 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, Ruby, Python, Go, Rust and Dart source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust or Dart 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 JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python 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.
- 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 Swift 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.
- 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.
- X30 Support guard that admits what it rejects — 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 Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart and Ruby source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, 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.
- 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.
- 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, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Swift 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.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- 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.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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.
- 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
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PreTrainedTokenizer.applyChatTemplate at 28.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PreTrainedTokenizer.applyChatTemplate (cyclomatic 28), DownloadProgressBridge.emitIfNeeded (cyclomatic 22), Data.== (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
13 method(s) exceeded the cognitive complexity threshold of 15; the worst was PreTrainedTokenizer.applyChatTemplate at 45.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with PreTrainedTokenizer.applyChatTemplate (cognitive 45). — Refactoring it lifts Cognitive Complexity from 7.6 to about 8.1/10.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with Config.swift, HubApi.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with HubApi.swift, Config.swift. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 3.4 % of the production lines (289 of 8,510) are in a reported copy. A further 14 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with Normalizer.swift, Tokenizer.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with PreTokenizer.swift, BertTokenizer.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with BinaryDistinct.swift, HubApi.swift. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
4 production modules (SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 15 classes have LCOM4 above 3.
D10 · Test Quality
2 skipped (1 with a documented reason), 19 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 287 tests (1 harness-style project(s) excluded from the assertion penalty).
What to do
- Resolve the 15 No direct assertions finding(s) in Test Quality — start with PreTokenizeBenchmarkTests.swift (4), UnigramTokenizerBenchmarkTests.swift (4), BPEPreTokenizeBenchmarkTests.swift (3). — One of this dimension's main actionable groups (15 recommendation-level).
- Resolve the 4 No assertions finding(s) in Test Quality — start with LogitsProcessorTests.swift (2), BPEMergesTests.swift, NormalizerTests.swift. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Skipped test finding(s) in Test Quality — start with HubApiTests.swift. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 0 of them read from the licence file the repository carries at the revision Package.resolved pins, and 5 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 7 of them are declared by a manifest that commits no Package.resolved (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict. ★ 2 package(s) could not be read at a pinned revision and are not known to the index, and were NOT graded — this verdict does not cover them: `benchmark`, `swift-jinja`.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Sources/Hub/BinaryDistinct.swift. Counted over 30 of the 32 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
10 deducted task-comment markers across 8510 LoC (0.1/KLoC) → score 9.8. 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 9 TodoComment finding(s) in Explicit Debt — start with LanguageModel.swift (2), NormalizerTests.swift, PreTokenizerTests.swift. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with Tokenizer.swift. — One of this dimension's main actionable groups (1 warning-level).
D21 · Naming Consistency
2 naming inconsistencies among 33 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `resolveHubClientRepoID` spells `ID` where 46 names in the project spell… finding(s) in Naming Consistency — start with HubApi.swift. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `HubRepoIDCacheActor` spells `ID` where 46 names in the project spell it… finding(s) in Naming Consistency — start with HubApi.swift. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
6 % of calls cross a namespace and 17 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Separately, one or more rules could not re-parse an embedded snippet in 1 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 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.
D34 · Knowledge Freshness
3 of 30 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Sources/Hub/YYJSONParser.swift. Counted over 30 of the 32 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with YYJSONParser.swift, MinPLogitsWarper.swift, RepetitionPenaltyLogitsProcessor.swift. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — Sources/Hub/Config.swift:681, Sources/Hub/Config.swift:686, Sources/Hub/Config.swift:691, …
- `catch` 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. — Sources/Hub/Config.swift:754
What to do
- Swallowed exception (empty catch)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Strong | Solid. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Checked 2 of 7 | Solid. |
| Performance | 94% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
Not evidenced — 3 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.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 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; this repository's Swift 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. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) 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 property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D12 Dependency Hygiene — Not scored — 9 SwiftPM declaration(s) across 3 `Package.swift` and 0 committed pin(s) were read for PINNING discipline (2 defect(s) reported), but the outdated signal comes from listing each declared repository's release tags rather than from a registry, and none of them resolved to a version to compare, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- 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.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
- 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 .py, .swift, 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (7932 LoC, 118 module-visible types across 5 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 7 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
- 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.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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
- D8 Code Coverage — Coverage not measured — Swift suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- 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
- 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'.
- P2 Observability — This repository's Swift source (1 module(s), 31 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Swift 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
- 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.
- 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 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
- 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 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. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. 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
- 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: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. Swift's `Array`, `Dictionary` and `Set` are values: `for x in items` walks the copy taken when the loop starts, so a body that adds to or removes from `items` changes a different value, nothing is invalidated, and every original element is still visited. This repository's Swift names no Foundation mutable collection (`NSMutableArray` and kin), the one kind a Swift loop can walk by reference. Not a gap in the analyzer and not a finding about your code.
- 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 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
- X30 Support guard that admits what it rejects — 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 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 — 3 finding(s)
- Test declared unreliable: deepSeekQwenChatTemplate Tests/TokenizersIntegrationTests/ChatTemplateTests.swift:51
- REDACTED
- REDACTED
Serious — 64 finding(s)
- TodoComment Tests/TokenizersTests/NormalizerTests.swift:135
- TodoComment Tests/TokenizersTests/PreTokenizerTests.swift:268
- TodoComment Tests/HubTests/HubApiTests.swift:12
- TodoComment Sources/Tokenizers/Decoder.swift:56
- TodoComment Sources/Tokenizers/TokenLattice.swift:97
- TodoComment Sources/Tokenizers/Tokenizer.swift:130
- TodoComment Sources/Tokenizers/Trie.swift:78
- TodoComment Sources/Models/LanguageModel.swift:536
- TodoComment Sources/Models/LanguageModel.swift:545
- Swallowed exception (empty catch) Sources/Hub/Config.swift:681
- Swallowed exception (empty catch) Sources/Hub/Config.swift:686
- Swallowed exception (empty catch) Sources/Hub/Config.swift:691
- Swallowed exception (empty catch) Sources/Hub/Config.swift:696
- Swallowed exception (empty catch) Sources/Hub/Config.swift:724
- Swallowed exception (empty catch) Sources/Hub/Config.swift:740
- No assertions: testTemperatureWarper Tests/GenerationTests/LogitsProcessorTests.swift:13
- No assertions: testTemperatureWarperWithDifferentValues Tests/GenerationTests/LogitsProcessorTests.swift:27
- No assertions: missingVocabThrowsFirst Tests/TokenizersTests/BPEMergesTests.swift:33
- No assertions: malformedPrecompiledCharsmap Tests/TokenizersTests/NormalizerTests.swift:219
- TooManyMethods: Config Sources/Hub/Config.swift:18
- TooManyMethods: HubApi Sources/Hub/HubApi.swift:96
- FileTooLong: Hub/HubApi.swift Sources/Hub/HubApi.swift
- FileTooLong: Hub/Config.swift Sources/Hub/Config.swift
- Edited copy of a member (13 corresponding lines) Sources/Tokenizers/Normalizer.swift:471
- Edited copy of a member (13 corresponding lines) Sources/Tokenizers/Tokenizer.swift:409
- Edited copy of a member (10 corresponding lines) Sources/Tokenizers/PreTokenizer.swift:50
- Edited copy of a member (10 corresponding lines) Sources/Tokenizers/BertTokenizer.swift:184
- Edited copy of a member (4 corresponding lines) Sources/Hub/BinaryDistinct.swift:255
- Edited copy of a member (4 corresponding lines) Sources/Hub/HubApi.swift:978
- PreTrainedTokenizer.applyChatTemplate (cyclomatic 28) Sources/Tokenizers/Tokenizer.swift:753
- DownloadProgressBridge.emitIfNeeded (cyclomatic 22) Sources/Hub/HubApi.swift:363
- Data.== (cyclomatic 21) Sources/Hub/Config.swift:58
- BPETokenizer.bpe (cyclomatic 19) Sources/Tokenizers/BPETokenizer.swift:275
- Config.convertToBinaryDistinctKeys (cyclomatic 18) Sources/Hub/Config.swift:235
- UnicodeScalar.isCJKUnifiedIdeograph (cyclomatic 16) Sources/Tokenizers/Normalizer.swift:257
- Skipped test: testCustomEndpointDownload Tests/HubTests/HubApiTests.swift:430
- No Package.resolved committed (Benchmarks/Package.swift)
- No Package.resolved committed (Examples/transformers-cli/Package.swift)
- HackComment Sources/Tokenizers/Tokenizer.swift:969
- PreTrainedTokenizer.applyChatTemplate (cognitive 45) Sources/Tokenizers/Tokenizer.swift:753
- RedirectDelegate.urlSession (cognitive 30) Sources/Hub/HubApi.swift:1360
- LanguageModelConfigurationFromHub.loadConfig (cognitive 25) Sources/Hub/Hub.swift:247
- BPETokenizer.bpe (cognitive 25) Sources/Tokenizers/BPETokenizer.swift:275
- HubApi.snapshot (cognitive 23) Sources/Hub/HubApi.swift:891
- DownloadProgressBridge.emitIfNeeded (cognitive 23) Sources/Hub/HubApi.swift:363
- Data.== (cognitive 20) Sources/Hub/Config.swift:58
- Config.convertToBinaryDistinctKeys (cognitive 19) Sources/Hub/Config.swift:235
- TokenLattice.viterbi (cognitive 18) Sources/Tokenizers/TokenLattice.swift:70
- Generation.createLogitsProcessorList (cognitive 17) Sources/Generation/Generation.swift:115
- HubApi.readDownloadMetadata (cognitive 17) Sources/Hub/HubApi.swift:629
- BinaryDistinctString.decodeUTF16 (cognitive 16) Sources/Hub/BinaryDistinct.swift:46
- YYJSONParser.convertToConfig (cognitive 16) Sources/Hub/YYJSONParser.swift:84
- Edited copy of a member (16 corresponding lines) Sources/Tokenizers/Decoder.swift:55
- Edited copy of a member (11 corresponding lines) Sources/Tokenizers/Tokenizer.swift:927
- Edited copies of one member (3 members, 11+ corresponding lines) Sources/Generation/LogitsWarper/MinPLogitsWarper.swift:32
- Edited copies of one member (4 members, 4+ corresponding lines) Sources/Hub/HubApi.swift:985
- Edited copies of one member (3 members, 3+ corresponding lines) Sources/Hub/HubApi.swift:1260
- Edited copy of a member (3 corresponding lines) Sources/Hub/HubApi.swift:990
- Edited copy of a member (6 corresponding lines) Sources/Generation/LogitsWarper/RepetitionPenaltyLogitsProcessor.swift:33
- Edited copy of a member (14 corresponding lines) Sources/Tokenizers/BertTokenizer.swift:241
- Duplicated block (7–8 lines × 2) Sources/Hub/HubApi.swift:651
- Duplicated block (7 lines × 2) Sources/Tokenizers/Tokenizer.swift:990
- Off the main sequence: Hub
- Swallowed exception (caught, then discarded) Sources/Hub/Config.swift:754
Minor — 28 finding(s)
- No direct assertions: byteLevelPreTokenizerMicro Tests/Benchmarks/BPEPreTokenizeBenchmarkTests.swift:69
- No direct assertions: bpeTokenizerHelperMicro Tests/Benchmarks/BPEPreTokenizeBenchmarkTests.swift:99
- No direct assertions: encodeThroughput Tests/Benchmarks/BPEPreTokenizeBenchmarkTests.swift:136
- No direct assertions: encodeThroughput Tests/Benchmarks/BPETokenizerBenchmarkTests.swift:68
- No direct assertions: bpeMergeInnerLoop Tests/Benchmarks/BPETokenizerBenchmarkTests.swift:90
- No direct assertions: compareParsingSpeed Tests/Benchmarks/JSONParserBenchmarkTests.swift:143
- No direct assertions: compareTokenizerLoadingSpeed Tests/Benchmarks/JSONParserBenchmarkTests.swift:220
- No direct assertions: bertPreTokenizer Tests/Benchmarks/PreTokenizeBenchmarkTests.swift:63
- No direct assertions: whitespacePreTokenizer Tests/Benchmarks/PreTokenizeBenchmarkTests.swift:80
- No direct assertions: punctuationPreTokenizer Tests/Benchmarks/PreTokenizeBenchmarkTests.swift:97
- No direct assertions: digitsPreTokenizer Tests/Benchmarks/PreTokenizeBenchmarkTests.swift:114
- No direct assertions: unigramTokenizeMicro Tests/Benchmarks/UnigramTokenizerBenchmarkTests.swift:79
- No direct assertions: unigramTokenizeScaling Tests/Benchmarks/UnigramTokenizerBenchmarkTests.swift:101
- No direct assertions: trieCommonPrefixSearchMicro Tests/Benchmarks/UnigramTokenizerBenchmarkTests.swift:125
- No direct assertions: encodeThroughput Tests/Benchmarks/UnigramTokenizerBenchmarkTests.swift:147
- Orphaned file Sources/Hub/YYJSONParser.swift:1
- Orphaned file Sources/Generation/LogitsWarper/MinPLogitsWarper.swift:1
- Orphaned file Sources/Generation/LogitsWarper/RepetitionPenaltyLogitsProcessor.swift:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- `resolveHubClientRepoID` spells `ID` where 46 names in the project spell it `Id` Sources/Hub/HubApi.swift:246
- `HubRepoIDCacheActor` spells `ID` where 46 names in the project spell it `Id` Sources/Hub/HubApi.swift:1425
- Orphaned files with no living knowledge
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- Dependabot does not watch pip REDACTED:2
- No changelog
Minor — 2 finding(s)
- Skipped (documented): deepSeekQwenChatTemplate Tests/TokenizersIntegrationTests/ChatTemplateTests.swift:51
- Dependency hygiene PARTLY measured — SwiftPM pinning read, dependency currency NOT established
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-faa2fe992acc41b5b9835a434a4ca5cb/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-faa2fe992acc41b5b9835a434a4ca5cb/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 . | 2 | 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: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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. semgrep could not parse 7 file(s) — `Sources/Generation/Generation.swift`, `Sources/Hub/Hub.swift`, `Sources/Hub/HubApi.swift`, `Sources/Hub/YYJSONParser.swift`, `Sources/Models/LanguageModel.swift`, … (+2 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). | 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 . | 0 | artifacts/raw/osv-scanner.json |