Executive summary
HeroTransitions/Hero is rated At risk because critical security findings are open. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 58 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 50, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Adding a diagnostic log would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 63.
Thirteen known security holes in the packages the code depends on can be used by attackers. Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. The pipeline step that runs a download without checking it needs each download checked against a known checksum first. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 7,586 lines, about €7,900 to rebuild.
If Production Readiness rose from 50 to 70, the lowest score rated Strong, the score would rise from 58 to about 63.
New since the last survey: 12 findings
- Code Duplication · Edited copy of a member (13 corresponding lines) Sources/Transition/HeroTransition+Interactive.swift
- Code Duplication · Edited copy of a member (12 corresponding lines) Sources/Transition/HeroTransition+Interactive.swift
- Code Duplication · Edited copy of a member (8 corresponding lines) Sources/Transition/HeroTransition+UINavigationControllerDelegate.swift
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) Sources/Preprocessors/CascadePreprocessor.swift
- Code Duplication · Edited copy of a member (25 corresponding lines) Examples/AppStoreCardExample.swift
- Code Duplication · Edited copy of a member (18 corresponding lines) LegacyExamples/Examples/ImageGallery/ImageViewController.swift
- Code Duplication · Edited copy of a member (13 corresponding lines) LegacyExamples/Examples/ListToGrid/GridCollectionViewController.swift
- Code Duplication · Edited copy of a member (7 corresponding lines) LegacyExamples/Examples/ListToGrid/GridCollectionViewController.swift
- Code Duplication · Edited copy of a member (5 corresponding lines) LegacyExamples/Examples/CityGuide/CityGuideViewController.swift
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) LegacyExamples/Examples/ImageGallery/ImageGalleryCollectionViewController.swift
- Code Duplication · Duplicated block (11 lines × 2) Examples/AppStoreCardExample.swift
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Code Duplication · Duplicated block (7 lines × 2) Sources/Animator/HeroCoreAnimationViewContext.swift
- Code Duplication · Duplicated block (11 lines × 2) Examples/AppStoreCardExample.swift
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €7,900 · Estimate
| Cost to rebuild | €2,600 to €13,000, for 44 to 139 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. 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: 7,586 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Parser | 2 docs.docsets.Hero_docset.Contents.Resources.Documents.js | 3 docs.js | 4 repository | 5 Transition | 6 Preprocessors | 7 Extensions | 8 Animator | 9 Debug Plugin |
|---|---|---|---|---|---|---|---|---|---|
| 1 Parser | |||||||||
| 2 docs.docsets.Hero_docset.Contents.Resources.Documents.js | |||||||||
| 3 docs.js | |||||||||
| 4 repository | 8 | 3 | 4 | 20 | |||||
| 5 Transition | 9 | 2 | 6 | ||||||
| 6 Preprocessors | 5 | 3 | 2 | 2 | |||||
| 7 Extensions | 3 | 2 | |||||||
| 8 Animator | 2 | 7 | 1 | 7 | |||||
| 9 Debug Plugin | 1 | 7 | 1 |
4→1 repository uses Parser✕
- Connections
- 8 pairs of types, where a type in repository uses a type in Parser.
- The types involved
repository.HeroContext→Parser.Stringrepository.HeroExtension→Parser.Stringrepository.HeroModifier→Parser.ExprNoderepository.HeroModifier→Parser.Stringrepository.HeroTargetState→Parser.Stringrepository.LegacyExampleViewController→Parser.Stringrepository.UINavigationController→Parser.Stringrepository.UIViewController→Parser.String
- Direction
- repository uses Parser, so a change to Parser can break repository, while a change to repository can't break Parser.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
4→5 repository uses Transition part of a loop✕
- Connections
- 3 pairs of types, where a type in repository uses a type in Transition.
- The types involved
repository.HeroAnimator→Transition.HeroTransitionrepository.HeroPlugin→Transition.HeroTransitionrepository.HeroPreprocessor→Transition.HeroTransition
- Direction
- repository uses Transition, so a change to Transition can break repository, while a change to repository can't break Transition.
- 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.
4→6 repository uses Preprocessors part of a loop✕
- Connections
- 4 pairs of types, where a type in repository uses a type in Preprocessors.
- The types involved
repository.HeroExtension→Preprocessors.HeroDefaultAnimationTyperepository.HeroModifier→Preprocessors.CascadeDirectionrepository.UINavigationController→Preprocessors.HeroDefaultAnimationTyperepository.UIViewController→Preprocessors.HeroDefaultAnimationType
- Direction
- repository uses Preprocessors, so a change to Preprocessors can break repository, while a change to repository can't break Preprocessors.
- 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.
4→7 repository uses Extensions part of a loop✕
- Connections
- 20 pairs of types, where a type in repository uses a type in Extensions.
- The types involved
repository.HeroAnimator→Extensions.TimeIntervalrepository.HeroExtension→Extensions.CGFloatrepository.HeroExtension→Extensions.HeroViewControllerConfigrepository.HeroModifier→Extensions.CAMediaTimingFunctionrepository.HeroModifier→Extensions.CATransform3Drepository.HeroModifier→Extensions.CGFloatrepository.HeroModifier→Extensions.CGPointrepository.HeroModifier→Extensions.CGRectrepository.HeroModifier→Extensions.CGSizerepository.HeroModifier→Extensions.TimeIntervalrepository.HeroModifier→Extensions.UIColorrepository.HeroPlugin→Extensions.TimeIntervalrepository.HeroTargetState→Extensions.CAMediaTimingFunctionrepository.HeroTargetState→Extensions.CATransform3Drepository.HeroTargetState→Extensions.CGFloatrepository.HeroTargetState→Extensions.CGPointrepository.HeroTargetState→Extensions.CGRectrepository.HeroTargetState→Extensions.CGSizerepository.HeroTargetState→Extensions.TimeIntervalrepository.UIViewController→Extensions.HeroViewControllerConfig
- Direction
- repository uses Extensions, so a change to Extensions can break repository, while a change to repository can't break Extensions.
- 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.
5→4 Transition uses repository✕
- Connections
- 9 pairs of types, where a type in Transition uses a type in repository.
- The types involved
Transition.HeroTransition→repository.HeroAnimatorTransition.HeroTransition→repository.HeroContextTransition.HeroTransition→repository.HeroModifierTransition.HeroTransition→repository.HeroPluginTransition.HeroTransition→repository.HeroPreprocessorTransition.HeroTransition→repository.HeroProgressUpdateObserverTransition.HeroTransition→repository.HeroViewOrderingStrategyTransition.HeroTransition→repository.UINavigationControllerTransition.HeroTransition→repository.UIViewController
- Direction
- Transition uses repository, so a change to repository can break Transition, while a change to Transition can't break repository.
- Position
- Below the diagonal: Transition uses a module listed above it, which is the healthy direction.
5→6 Transition uses Preprocessors part of a loop✕
- Connections
- 2 pairs of types, where a type in Transition uses a type in Preprocessors.
- The types involved
Transition.HeroTransition→Preprocessors.HeroDefaultAnimationTypeTransition.HeroTransition→Preprocessors.Strategy
- Direction
- Transition uses Preprocessors, so a change to Preprocessors can break Transition, while a change to Transition can't break Preprocessors.
- 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.
5→7 Transition uses Extensions part of a loop✕
- Connections
- 6 pairs of types, where a type in Transition uses a type in Extensions.
- The types involved
Transition.HeroProgressRunner→Extensions.TimeIntervalTransition.HeroTransition→Extensions.CGFloatTransition.HeroTransition→Extensions.CGRectTransition.HeroTransition→Extensions.TimeIntervalTransition.HeroTransition→Extensions.UIColorTransition.HeroTransition→Extensions.UITabBarController
- Direction
- Transition uses Extensions, so a change to Extensions can break Transition, while a change to Transition can't break Extensions.
- 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.
6→1 Preprocessors uses Parser✕
- Connections
- 5 pairs of types, where a type in Preprocessors uses a type in Parser.
- The types involved
Preprocessors.CascadeDirection→Parser.StringPreprocessors.Direction→Parser.ExprNodePreprocessors.Direction→Parser.HeroStringConvertiblePreprocessors.HeroDefaultAnimationType→Parser.ExprNodePreprocessors.HeroDefaultAnimationType→Parser.String
- Direction
- Preprocessors uses Parser, so a change to Parser can break Preprocessors, while a change to Preprocessors can't break Parser.
- Position
- Below the diagonal: Preprocessors uses a module listed above it, which is the healthy direction.
6→4 Preprocessors uses repository✕
- Connections
- 3 pairs of types, where a type in Preprocessors uses a type in repository.
- The types involved
Preprocessors.BasePreprocessor→repository.HeroContextPreprocessors.BasePreprocessor→repository.HeroPreprocessorPreprocessors.HeroConditionalContext→repository.UIViewController
- Direction
- Preprocessors uses repository, so a change to repository can break Preprocessors, while a change to Preprocessors can't break repository.
- Position
- Below the diagonal: Preprocessors uses a module listed above it, which is the healthy direction.
6→5 Preprocessors uses Transition✕
- Connections
- 2 pairs of types, where a type in Preprocessors uses a type in Transition.
- The types involved
Preprocessors.BasePreprocessor→Transition.HeroTransitionPreprocessors.HeroConditionalContext→Transition.HeroTransition
- Direction
- Preprocessors uses Transition, so a change to Transition can break Preprocessors, while a change to Preprocessors can't break Transition.
- Position
- Below the diagonal: Preprocessors uses a module listed above it, which is the healthy direction.
6→7 Preprocessors uses Extensions part of a loop✕
- Connections
- 2 pairs of types, where a type in Preprocessors uses a type in Extensions.
- The types involved
Preprocessors.DefaultAnimationPreprocessor→Extensions.CGPointPreprocessors.DefaultAnimationPreprocessor→Extensions.CGSize
- Direction
- Preprocessors uses Extensions, so a change to Extensions can break Preprocessors, while a change to Preprocessors can't break Extensions.
- 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.
7→1 Extensions uses Parser✕
- Connections
- 3 pairs of types, where a type in Extensions uses a type in Parser.
- The types involved
Extensions.CAMediaTimingFunction→Parser.StringExtensions.UIColor→Parser.StringExtensions.UITabBarController→Parser.String
- Direction
- Extensions uses Parser, so a change to Parser can break Extensions, while a change to Extensions can't break Parser.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
7→6 Extensions uses Preprocessors✕
- Connections
- 2 pairs of types, where a type in Extensions uses a type in Preprocessors.
- The types involved
Extensions.HeroViewControllerConfig→Preprocessors.HeroDefaultAnimationTypeExtensions.UITabBarController→Preprocessors.HeroDefaultAnimationType
- Direction
- Extensions uses Preprocessors, so a change to Preprocessors can break Extensions, while a change to Extensions can't break Preprocessors.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
8→1 Animator uses Parser✕
- Connections
- 2 pairs of types, where a type in Animator uses a type in Parser.
- The types involved
Animator.CALayer→Parser.StringAnimator.HeroCoreAnimationViewContext→Parser.String
- Direction
- Animator uses Parser, so a change to Parser can break Animator, while a change to Animator can't break Parser.
- Position
- Below the diagonal: Animator uses a module listed above it, which is the healthy direction.
8→4 Animator uses repository✕
- Connections
- 7 pairs of types, where a type in Animator uses a type in repository.
- The types involved
Animator.HeroAnimatorViewContext→repository.HeroAnimatorAnimator.HeroAnimatorViewContext→repository.HeroTargetStateAnimator.HeroCoreAnimationViewContext→repository.HeroTargetStateAnimator.HeroDefaultAnimator→repository.HeroAnimatorAnimator.HeroDefaultAnimator→repository.HeroContextAnimator.HeroDefaultAnimator→repository.HeroTargetStateAnimator.HeroViewPropertyViewContext→repository.HeroTargetState
- Direction
- Animator uses repository, so a change to repository can break Animator, while a change to Animator can't break repository.
- Position
- Below the diagonal: Animator uses a module listed above it, which is the healthy direction.
8→5 Animator uses Transition✕
- Connections
- 1 pair of types, where a type in Animator uses a type in Transition.
- The types involved
Animator.HeroDefaultAnimator→Transition.HeroTransition
- Direction
- Animator uses Transition, so a change to Transition can break Animator, while a change to Animator can't break Transition.
- Position
- Below the diagonal: Animator uses a module listed above it, which is the healthy direction.
8→7 Animator uses Extensions✕
- Connections
- 7 pairs of types, where a type in Animator uses a type in Extensions.
- The types involved
Animator.CALayer→Extensions.CATransform3DAnimator.HeroAnimatorViewContext→Extensions.TimeIntervalAnimator.HeroCoreAnimationViewContext→Extensions.CAMediaTimingFunctionAnimator.HeroCoreAnimationViewContext→Extensions.CGSizeAnimator.HeroCoreAnimationViewContext→Extensions.TimeIntervalAnimator.HeroDefaultAnimator→Extensions.TimeIntervalAnimator.HeroViewPropertyViewContext→Extensions.TimeInterval
- Direction
- Animator uses Extensions, so a change to Extensions can break Animator, while a change to Animator can't break Extensions.
- Position
- Below the diagonal: Animator uses a module listed above it, which is the healthy direction.
9→4 Debug Plugin uses repository✕
- Connections
- 1 pair of types, where a type in Debug Plugin uses a type in repository.
- The types involved
Debug Plugin.HeroDebugPlugin→repository.HeroPlugin
- Direction
- Debug Plugin uses repository, so a change to repository can break Debug Plugin, while a change to Debug Plugin can't break repository.
- Position
- Below the diagonal: Debug Plugin uses a module listed above it, which is the healthy direction.
9→7 Debug Plugin uses Extensions✕
- Connections
- 7 pairs of types, where a type in Debug Plugin uses a type in Extensions.
- The types involved
Debug Plugin.HeroDebugPlugin→Extensions.CGFloatDebug Plugin.HeroDebugPlugin→Extensions.CGPointDebug Plugin.HeroDebugPlugin→Extensions.TimeIntervalDebug Plugin.HeroDebugView→Extensions.CGFloatDebug Plugin.HeroDebugView→Extensions.CGPointDebug Plugin.HeroDebugViewDelegate→Extensions.CGFloatDebug Plugin.HeroDebugViewDelegate→Extensions.CGPoint
- Direction
- Debug Plugin uses Extensions, so a change to Extensions can break Debug Plugin, while a change to Debug Plugin can't break Extensions.
- Position
- Below the diagonal: Debug Plugin uses a module listed above it, which is the healthy direction.
9→8 Debug Plugin uses Animator✕
- Connections
- 1 pair of types, where a type in Debug Plugin uses a type in Animator.
- The types involved
Debug Plugin.HeroDebugPlugin→Animator.CALayer
- Direction
- Debug Plugin uses Animator, so a change to Animator can break Debug Plugin, while a change to Debug Plugin can't break Animator.
- Position
- Below the diagonal: Debug Plugin uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 15 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj; Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with HeroCoreAnimationViewContext.swift, DefaultAnimationPreprocessor.swift, HeroModifier.swift; Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. | +6.6 pts | Low | ADR Quality |
| Resolve the 1 Banned license finding(s) in License Compliance. | +3.5 pts | Low | License Compliance |
| Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with HeroCoreAnimationViewContext.swift, DefaultAnimationPreprocessor.swift, HeroModifier.swift. | +6.6 pts | Medium | Knowledge Freshness |
| Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +5.5 pts | Medium | Observability |
| 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. | +5.5 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.0 pts | Medium | Architecture documentation |
| Swallowed exception (caught, then discarded) | +3.2 pts | Medium | Exception handling |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.8 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| Sources/Preprocessors/DefaultAnimationPreprocessor.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/Extensions/UIViewController+Hero.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/Extensions/UIView+Hero.swift | 6.6 | Mixed | Explicit Debt: TodoComment |
| Sources/Transition/HeroTransition.swift | 7.0 | Mixed | God Classes: TooManyMethods: HeroTransition |
| LegacyExamples/Examples/ImageGallery/ImageViewController.swift | 7.0 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| LegacyExamples/Examples/ImageGallery/ImageGalleryCollectionViewController.swift | 7.0 | Mixed | Code Duplication: Edited copies of one member (3 members, 5+ corresponding lines) |
| Sources/Animator/HeroCoreAnimationViewContext.swift | 7.2 | Mixed | Cyclomatic Complexity: HeroCoreAnimationViewContext.viewState (cyclomatic 23) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| Sources/HeroContext.swift | 7.4 | Mixed | Cyclomatic Complexity: HeroContext.snapshotView (cyclomatic 42) |
| Sources/HeroModifier+HeroStringConvertible.swift | 7.8 | Mixed | Cyclomatic Complexity: HeroModifier.from (cyclomatic 39) |
| Sources/Transition/HeroTransition+Complete.swift | 7.8 | Mixed | Cyclomatic Complexity: HeroTransition.complete (cyclomatic 36) |
| Sources/Transition/HeroTransition+Start.swift | 7.8 | Mixed | Cyclomatic Complexity: HeroTransition.start (cyclomatic 32) |
| Sources/Preprocessors/MatchPreprocessor.swift | 7.8 | Mixed | Cyclomatic Complexity: MatchPreprocessor.process (cyclomatic 17) |
| Sources/Preprocessors/CascadePreprocessor.swift | 7.8 | Mixed | Cognitive Complexity: CascadePreprocessor.process (cognitive 16) |
| Sources/Transition/HeroTransition+Interactive.swift | 7.8 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
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 34 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 — 34 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, 126 of 131 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 — a Codecov configuration (.codecov.yml) and a coverage step in CI (`-enableCodeCoverage YES`) shows coverage is measured in your own CI.
- 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. Test source is present (.swift) and this repository declares a SwiftPM test suite (Hero), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 31 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 17 of the 50 production source files in this repository: 19 are under the ~2,400-byte size floor this dimension measures over, and the remaining 14 have no attributable history left to measure.
- D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — 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. `(repository root)` (7586 LoC, 133 module-visible types across 21 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (TvOSExamples/Basic.storyboard). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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 this repository's Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- P8 Schema migrations — 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 EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
- 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.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- 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 this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, 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.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HeroContext.snapshotView at 42. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HeroDefaultAnimationType.reversed at 35 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with HeroContext.snapshotView (cyclomatic 42), HeroModifier.from (cyclomatic 39), DefaultAnimationPreprocessor.process (cyclomatic 36). — 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 9 together lifts Cyclomatic Complexity from 8.2 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 HeroTransition.complete at 58.
What to do
- Bring the 13 bodies over 15 down to 15 or less in Cognitive Complexity — start with HeroTransition.complete (cognitive 58), HeroContext.snapshotView (cognitive 55), HeroTransition.start (cognitive 39). — 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 13 together lifts Cognitive Complexity from 7.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with HeroModifier.swift, HeroTransition.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with HeroContext.swift, DefaultAnimationPreprocessor.swift. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 3.1 % of the production lines (238 of 7,586) are in a reported copy. A further 10 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 7 of the 12 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with HeroTransition+Interactive.swift, GridCollectionViewController.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with HeroTransition+Interactive.swift. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with HeroTransition+UINavigationControllerDelegate.swift. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
9 of 37 classes have LCOM4 above 3.
What to do
- Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with AppDelegate.swift (2), SwiftSupport.swift, HeroAnimatorViewContext.swift. — One of this dimension's main actionable groups (9 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5 tests.
D12 · Dependency Hygiene
0 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question. 1 third-party CocoaPods resolved by a committed Podfile.lock were graded against the CocoaPods trunk (cdn.cocoapods.org): a pod is behind only when the trunk lists a newer release on the same major, which `pod update` reaches under a `~>` requirement. A pod sourced from a path, git URL or local podspec has no trunk release to compare and is not asked about. Carthage dependencies are not graded.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 112 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 112 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 4 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
12 deducted task-comment markers across 7586 LoC (0.1/KLoC) → score 9.7. 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 12 TodoComment finding(s) in Explicit Debt — start with UIViewController+Hero.swift (6), UIView+Hero.swift (4), DefaultAnimationPreprocessor.swift. — One of this dimension's main actionable groups (12 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
11 % of calls cross a namespace and 4 % 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)
14 finding(s): 0 critical, 13 high, 1 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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).
- No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
15 finding(s): 2 critical, 11 high, 2 medium, 0 low.
What to do
- Resolve the 11 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
31 of 31 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Sources/Animator/HeroCoreAnimationViewContext.swift. Counted over 31 of the 50 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 31 Orphaned file finding(s) in Knowledge Freshness — start with HeroCoreAnimationViewContext.swift, DefaultAnimationPreprocessor.swift, HeroModifier.swift. — One of this dimension's main actionable groups (31 recommendation-level).
- Resolve the 1 Dormant codebase 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.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- 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 5 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
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X3 · Exception handling
- `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/Parser/Regex.swift:21
What to do
- Swallowed exception (caught, then discarded)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 54% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 82% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 4 observation(s) recorded · 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). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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 — 78 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 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 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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 — D19 withholds "Documentation: empty section": 1 candidate(s) were measured and not published.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
- 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; comments in this repository's .swift source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 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.
- 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.
- D5 Coupling — Not applicable — this SwiftPM build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- 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
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — 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
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 0% of this repository's production lines — swift (7,586 lines), c (13 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not 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 — X16 reached only 0% of this repository's production lines — swift (7,586 lines), c (13 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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 — X21 reached only 0% of this repository's production lines — swift (7,586 lines), c (13 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — Not applicable: 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. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: cocoapods-repo-update
- REDACTED
Serious — 68 finding(s)
- TodoComment Sources/Preprocessors/DefaultAnimationPreprocessor.swift:363
- TodoComment Sources/Extensions/UIView+Hero.swift:120
- TodoComment Sources/Extensions/UIView+Hero.swift:127
- TodoComment Sources/Extensions/UIView+Hero.swift:134
- TodoComment Sources/Extensions/UIView+Hero.swift:147
- TodoComment Sources/Extensions/UIViewController+Hero.swift:64
- TodoComment Sources/Extensions/UIViewController+Hero.swift:70
- TodoComment Sources/Extensions/UIViewController+Hero.swift:167
- TodoComment Sources/Extensions/UIViewController+Hero.swift:206
- TodoComment Sources/Extensions/UIViewController+Hero.swift:355
- TodoComment Sources/Extensions/UIViewController+Hero.swift:361
- TodoComment Examples/MainViewController.swift:64
- Low cohesion: UIViewController (LCOM4 9) Sources/SwiftSupport.swift:40
- Low cohesion: HeroAnimatorViewContext (LCOM4 6) Sources/Animator/HeroAnimatorViewContext.swift:27
- Low cohesion: AppDelegate (LCOM4 6) TvOSExamples/AppDelegate.swift:25
- Low cohesion: AppDelegate (LCOM4 6) Examples/Resources/AppDelegate.swift:26
- Low cohesion: ImageGalleryViewController (LCOM4 6) LegacyExamples/Examples/ImageGallery/ImageGalleryCollectionViewController.swift:26
- Low cohesion: HeroDebugPlugin (LCOM4 5) Sources/Debug Plugin/HeroDebugPlugin.swift:27
- Low cohesion: HeroTransition (LCOM4 5) Sources/Transition/HeroTransition.swift:53
- Low cohesion: AnimationSelectTableViewController (LCOM4 5) LegacyExamples/Examples/BuiltInTransition/AnimationSelectTableViewController.swift:33
- Low cohesion: ImageViewController (LCOM4 5) LegacyExamples/Examples/ImageGallery/ImageViewController.swift:26
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: HeroModifier Sources/HeroModifier.swift:28
- TooManyMethods: HeroTransition Sources/Transition/HeroTransition.swift:53
- MethodTooLong: HeroContext.snapshotView Sources/HeroContext.swift:117
- MethodTooLong: DefaultAnimationPreprocessor.process Sources/Preprocessors/DefaultAnimationPreprocessor.swift:257
- REDACTED
- REDACTED
- Edited copy of a member (13 corresponding lines) Sources/Transition/HeroTransition+Interactive.swift:47
- Edited copy of a member (13 corresponding lines) LegacyExamples/Examples/ListToGrid/GridCollectionViewController.swift:48
- HeroContext.snapshotView (cyclomatic 42) Sources/HeroContext.swift:117
- HeroModifier.from (cyclomatic 39) Sources/HeroModifier+HeroStringConvertible.swift:29
- DefaultAnimationPreprocessor.process (cyclomatic 36) Sources/Preprocessors/DefaultAnimationPreprocessor.swift:257
- HeroTransition.complete (cyclomatic 36) Sources/Transition/HeroTransition+Complete.swift:28
- HeroDefaultAnimationType.from (cyclomatic 35) Sources/Preprocessors/DefaultAnimationPreprocessor.swift:185
- HeroTransition.start (cyclomatic 32) Sources/Transition/HeroTransition+Start.swift:28
- HeroCoreAnimationViewContext.viewState (cyclomatic 23) Sources/Animator/HeroCoreAnimationViewContext.swift:266
- HeroCoreAnimationViewContext.canAnimate (cyclomatic 17) Sources/Animator/HeroCoreAnimationViewContext.swift:68
- MatchPreprocessor.process (cyclomatic 17) Sources/Preprocessors/MatchPreprocessor.swift:28
- HeroTransition.complete (cognitive 58) Sources/Transition/HeroTransition+Complete.swift:28
- HeroContext.snapshotView (cognitive 55) Sources/HeroContext.swift:117
- HeroTransition.start (cognitive 39) Sources/Transition/HeroTransition+Start.swift:28
- DefaultAnimationPreprocessor.process (cognitive 33) Sources/Preprocessors/DefaultAnimationPreprocessor.swift:257
- HeroDefaultAnimationType.from (cognitive 31) Sources/Preprocessors/DefaultAnimationPreprocessor.swift:185
- MatchPreprocessor.process (cognitive 31) Sources/Preprocessors/MatchPreprocessor.swift:28
- HeroExtension.unwindToViewController (cognitive 31) Sources/Extensions/UIViewController+Hero.swift:256
- HeroCoreAnimationViewContext.viewState (cognitive 29) Sources/Animator/HeroCoreAnimationViewContext.swift:266
- HeroModifier.from (cognitive 28) Sources/HeroModifier+HeroStringConvertible.swift:29
- HeroTransition.animate (cognitive 22) Sources/Transition/HeroTransition+Animate.swift:27
- HeroCoreAnimationViewContext.canAnimate (cognitive 16) Sources/Animator/HeroCoreAnimationViewContext.swift:68
- CascadePreprocessor.process (cognitive 16) Sources/Preprocessors/CascadePreprocessor.swift:107
- HeroExtension.replaceViewController (cognitive 16) Sources/Extensions/UIViewController+Hero.swift:310
- REDACTED
- Edited copy of a member (12 corresponding lines) Sources/Transition/HeroTransition+Interactive.swift:96
- Edited copy of a member (8 corresponding lines) Sources/Transition/HeroTransition+UINavigationControllerDelegate.swift:40
- Edited copies of one member (3 members, 4+ corresponding lines) Sources/Preprocessors/CascadePreprocessor.swift:102
- Duplicated block (5 lines × 3) Sources/Preprocessors/DefaultAnimationPreprocessor.swift:311
- Edited copy of a member (25 corresponding lines) Examples/AppStoreCardExample.swift:144
- Edited copy of a member (18 corresponding lines) LegacyExamples/Examples/ImageGallery/ImageViewController.swift:53
- Edited copy of a member (7 corresponding lines) LegacyExamples/Examples/ListToGrid/GridCollectionViewController.swift:64
- Edited copy of a member (5 corresponding lines) LegacyExamples/Examples/CityGuide/CityGuideViewController.swift:42
- Edited copies of one member (3 members, 5+ corresponding lines) LegacyExamples/Examples/ImageGallery/ImageGalleryCollectionViewController.swift:38
- Duplicated block (11 lines × 2) Examples/AppStoreCardExample.swift:158
- No structured logging
- Swallowed exception (caught, then discarded) Sources/Parser/Regex.swift:21
Minor — 36 finding(s)
- Orphaned file Sources/Animator/HeroCoreAnimationViewContext.swift:1
- Orphaned file Sources/Preprocessors/DefaultAnimationPreprocessor.swift:1
- Orphaned file Sources/HeroModifier.swift:1
- Orphaned file Sources/Extensions/UIViewController+Hero.swift:1
- Orphaned file Sources/HeroContext.swift:1
- Orphaned file Sources/Transition/HeroTransition.swift:1
- Orphaned file Sources/Extensions/UIView+Hero.swift:1
- Orphaned file Sources/Transition/HeroTransition+Start.swift:1
- Orphaned file Sources/Debug Plugin/HeroDebugView.swift:1
- Orphaned file Sources/Transition/HeroTransition+Complete.swift:1
- Orphaned file Sources/Debug Plugin/HeroDebugPlugin.swift:1
- Orphaned file Sources/HeroPlugin.swift:1
- Orphaned file Sources/Animator/HeroDefaultAnimator.swift:1
- Orphaned file Sources/HeroModifier+Advanced.swift:1
- Orphaned file Sources/HeroModifier+HeroStringConvertible.swift:1
- Orphaned file Sources/Extensions/CG+Hero.swift:1
- Orphaned file Sources/Transition/HeroTransition+Interactive.swift:1
- Orphaned file Sources/Preprocessors/CascadePreprocessor.swift:1
- Orphaned file Sources/HeroTargetState.swift:1
- Orphaned file Sources/Preprocessors/SourcePreprocessor.swift:1
- Orphaned file Sources/Transition/HeroTransition+UIViewControllerTransitioningDelegate.swift:1
- Orphaned file Sources/Animator/HeroViewPropertyViewContext.swift:1
- Orphaned file TvOSExamples/AppDelegate.swift:1
- Orphaned file Sources/Preprocessors/ConditionalPreprocessor.swift:1
- Orphaned file Sources/Transition/HeroTransition+Animate.swift:1
- No ADRs found Hero.xcodeproj/project.pbxproj:1
- Dormant codebase
- REDACTED
- No ADRs
- No SAST REDACTED:4
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-a639df5a0b264bc08a1fa348b97918cd/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-a639df5a0b264bc08a1fa348b97918cd/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 . | 14 | 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 . | 15 | 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. | 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 |