Executive summary
arxanas/git-branchless falls short of our standard for a preview release, in part because the project keeps no record of its design decisions. It scores 64 out of 100 and is rated Adequate, and all 29 of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 10 points. Having someone learn and document the 35 files no active contributor knows comes next, worth about 9 points. Raising Maturity to 62 would lift the score to about 68.
Twenty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one pipeline step runs a download nobody checks. Pinning each tool to an exact version, setting a waiting period for automatic updates and checking the download against a checksum would close these risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration.
The product code is 36,450 lines, about €69,000 to rebuild.
If Maturity rose from 53 to 62, the lowest score rated Strong, the score would rise from 64 to about 68.
New since the last survey: 11 findings
- Cognitive Complexity · EventReplayer::process_event (cognitive 18) git-branchless-lib/src/core/eventlog.rs
- Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) git-branchless-move/src/lib.rs
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 6 findings
- Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) git-branchless-move/src/lib.rs
- Churn × Complexity Hotspots · Hotspot: git-branchless-move/src/lib.rs git-branchless-move/src/lib.rs
- Churn × Complexity Hotspots · Hotspot: git-branchless-test/src/lib.rs git-branchless-test/src/lib.rs
- Churn × Complexity Hotspots · Repeated repair: git-branchless-lib/src/testing.rs git-branchless-lib/src/testing.rs
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €69,000 · Estimate
| Cost to rebuild | €23,000 to €120,000, for 384 to 1,219 hours of work, about 0.5 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.9 at a score of 64. 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 | Medium: 36,450 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 git_branchless_lib.core.formatting | 2 git_branchless_lib.git.oid | 3 git_branchless_lib.core.effects | 4 git_branchless_lib.core.repo_ext | 5 git_branchless_lib.git.tree | 6 git_branchless_lib.git.object | 7 git_branchless_lib.git.run | 8 git_branchless_invoke | 9 git_branchless_lib.core.rewrite.plan | 10 git_branchless_lib.git.index | 11 git_branchless_lib.git.snapshot | 12 git_branchless_lib.core.check_out | 13 git_branchless_lib.core.rewrite.execute | 14 git_branchless_lib.core.rewrite.execute.on_disk | 15 git_branchless_lib.git.repo | 16 git_branchless_lib.git.reference | 17 git_branchless_lib.git.test | 18 git_branchless_lib.core.eventlog | 19 git_branchless_lib.core.worktree | 20 git_branchless_lib.core.dag | 21 git_branchless_lib.core.node_descriptors | 22 git_branchless_lib.core.rewrite.execute.in_memory | 23 git_branchless_lib.core.rewrite.rewrite_hooks | 24 git_branchless_lib.core.untracked_file_cache | 25 git_branchless.commands.bug_report | 26 git_branchless_navigation | 27 git_branchless_revset.eval | 28 git_branchless_smartlog.graph | 29 git_branchless_undo | 30 git_branchless_opts | 31 git_branchless.commands.restack | 32 git_branchless.commands.sync | 33 git_branchless_init | 34 git_branchless_record | 35 git_branchless_smartlog.render | 36 git_branchless_submit | 37 git_branchless_submit.branch_forge | 38 git_branchless_submit.github | 39 git_branchless_submit.github.client | 40 git_branchless_submit.phabricator |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 git_branchless_lib.core.formatting | ||||||||||||||||||||||||||||||||||||||||
| 2 git_branchless_lib.git.oid | ||||||||||||||||||||||||||||||||||||||||
| 3 git_branchless_lib.core.effects | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 git_branchless_lib.core.repo_ext | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 git_branchless_lib.git.tree | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 git_branchless_lib.git.object | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 7 git_branchless_lib.git.run | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 git_branchless_invoke | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 git_branchless_lib.core.rewrite.plan | 3 | 3 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 10 git_branchless_lib.git.index | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 11 git_branchless_lib.git.snapshot | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 git_branchless_lib.core.check_out | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 13 git_branchless_lib.core.rewrite.execute | 1 | 2 | 1 | 1 | 2 | 3 | 3 | |||||||||||||||||||||||||||||||||
| 14 git_branchless_lib.core.rewrite.execute.on_disk | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 15 git_branchless_lib.git.repo | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||
| 16 git_branchless_lib.git.reference | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 git_branchless_lib.git.test | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 git_branchless_lib.core.eventlog | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 19 git_branchless_lib.core.worktree | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 20 git_branchless_lib.core.dag | 1 | 1 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 21 git_branchless_lib.core.node_descriptors | 9 | 1 | 1 | 4 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 22 git_branchless_lib.core.rewrite.execute.in_memory | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 23 git_branchless_lib.core.rewrite.rewrite_hooks | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 24 git_branchless_lib.core.untracked_file_cache | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 git_branchless.commands.bug_report | 2 | 1 | 3 | 2 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 26 git_branchless_navigation | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 27 git_branchless_revset.eval | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 git_branchless_smartlog.graph | 3 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 git_branchless_undo | 1 | 1 | 1 | 2 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||
| 30 git_branchless_opts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 git_branchless.commands.restack | 1 | 1 | 1 | 2 | 1 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 32 git_branchless.commands.sync | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 33 git_branchless_init | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 34 git_branchless_record | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 35 git_branchless_smartlog.render | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 36 git_branchless_submit | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 6 | |||||||||||||||||||||||||||||||
| 37 git_branchless_submit.branch_forge | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 38 git_branchless_submit.github | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 39 git_branchless_submit.github.client | 2 | 3 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 40 git_branchless_submit.phabricator | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 |
3→1 git_branchless_lib.core.effects uses git_branchless_lib.core.formatting✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.effects uses a type in git_branchless_lib.core.formatting.
- The types involved
git_branchless_lib.core.effects.Effects→git_branchless_lib.core.formatting.Glyphs
- Direction
- git_branchless_lib.core.effects uses git_branchless_lib.core.formatting, so a change to git_branchless_lib.core.formatting can break git_branchless_lib.core.effects, while a change to git_branchless_lib.core.effects can't break git_branchless_lib.core.formatting.
- Position
- Below the diagonal: git_branchless_lib.core.effects uses a module listed above it, which is the healthy direction.
4→2 git_branchless_lib.core.repo_ext uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.repo_ext uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.repo_ext.RepoReferencesSnapshot→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.repo_ext uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.repo_ext, while a change to git_branchless_lib.core.repo_ext can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.repo_ext uses a module listed above it, which is the healthy direction.
5→2 git_branchless_lib.git.tree uses git_branchless_lib.git.oid✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.tree uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.git.tree.Tree→git_branchless_lib.git.oid.NonZeroOidgit_branchless_lib.git.tree.TreeEntry→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.git.tree uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.git.tree, while a change to git_branchless_lib.git.tree can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.git.tree uses a module listed above it, which is the healthy direction.
5→15 git_branchless_lib.git.tree uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.tree uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.git.tree.Tree→git_branchless_lib.git.repo.Repogit_branchless_lib.git.tree.tree$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.git.tree uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.git.tree, while a change to git_branchless_lib.git.tree can't break git_branchless_lib.git.repo.
- 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 git_branchless_lib.git.object uses git_branchless_lib.core.formatting✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.object uses a type in git_branchless_lib.core.formatting.
- The types involved
git_branchless_lib.git.object.Commit→git_branchless_lib.core.formatting.Glyphs
- Direction
- git_branchless_lib.git.object uses git_branchless_lib.core.formatting, so a change to git_branchless_lib.core.formatting can break git_branchless_lib.git.object, while a change to git_branchless_lib.git.object can't break git_branchless_lib.core.formatting.
- Position
- Below the diagonal: git_branchless_lib.git.object uses a module listed above it, which is the healthy direction.
6→2 git_branchless_lib.git.object uses git_branchless_lib.git.oid✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.object uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.git.object.Commit→git_branchless_lib.git.oid.MaybeZeroOidgit_branchless_lib.git.object.Commit→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.git.object uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.git.object, while a change to git_branchless_lib.git.object can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.git.object uses a module listed above it, which is the healthy direction.
6→5 git_branchless_lib.git.object uses git_branchless_lib.git.tree✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.object uses a type in git_branchless_lib.git.tree.
- The types involved
git_branchless_lib.git.object.Commit→git_branchless_lib.git.tree.Tree
- Direction
- git_branchless_lib.git.object uses git_branchless_lib.git.tree, so a change to git_branchless_lib.git.tree can break git_branchless_lib.git.object, while a change to git_branchless_lib.git.object can't break git_branchless_lib.git.tree.
- Position
- Below the diagonal: git_branchless_lib.git.object uses a module listed above it, which is the healthy direction.
6→15 git_branchless_lib.git.object uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.object uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.git.object.Commit→git_branchless_lib.git.repo.Signaturegit_branchless_lib.git.object.Commit→git_branchless_lib.git.repo.Time
- Direction
- git_branchless_lib.git.object uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.git.object, while a change to git_branchless_lib.git.object can't break git_branchless_lib.git.repo.
- 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→3 git_branchless_lib.git.run uses git_branchless_lib.core.effects✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.run uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.git.run.GitRunInfo→git_branchless_lib.core.effects.Effectsgit_branchless_lib.git.run.GitRunInfo→git_branchless_lib.core.effects.OutputStream
- Direction
- git_branchless_lib.git.run uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.git.run, while a change to git_branchless_lib.git.run can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.git.run uses a module listed above it, which is the healthy direction.
7→15 git_branchless_lib.git.run uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.run uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.git.run.GitRunInfo→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.git.run uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.git.run, while a change to git_branchless_lib.git.run can't break git_branchless_lib.git.repo.
- 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→18 git_branchless_lib.git.run uses git_branchless_lib.core.eventlog part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.run uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.git.run.GitRunInfo→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_lib.git.run uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.git.run, while a change to git_branchless_lib.git.run can't break git_branchless_lib.core.eventlog.
- 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.
8→3 git_branchless_invoke uses git_branchless_lib.core.effects✕
- Connections
- 2 pairs of types, where a type in git_branchless_invoke uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_invoke.CommandContext→git_branchless_lib.core.effects.Effectsgit_branchless_invoke.git_branchless_invoke$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_invoke uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_invoke, while a change to git_branchless_invoke can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_invoke uses a module listed above it, which is the healthy direction.
8→7 git_branchless_invoke uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_invoke uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_invoke.CommandContext→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_invoke uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_invoke, while a change to git_branchless_invoke can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_invoke uses a module listed above it, which is the healthy direction.
9→2 git_branchless_lib.core.rewrite.plan uses git_branchless_lib.git.oid✕
- Connections
- 3 pairs of types, where a type in git_branchless_lib.core.rewrite.plan uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.rewrite.plan.ConstraintGraph→git_branchless_lib.git.oid.NonZeroOidgit_branchless_lib.core.rewrite.plan.RebasePlan→git_branchless_lib.git.oid.NonZeroOidgit_branchless_lib.core.rewrite.plan.RebasePlanBuilder→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.rewrite.plan uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.rewrite.plan, while a change to git_branchless_lib.core.rewrite.plan can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.plan uses a module listed above it, which is the healthy direction.
9→3 git_branchless_lib.core.rewrite.plan uses git_branchless_lib.core.effects✕
- Connections
- 3 pairs of types, where a type in git_branchless_lib.core.rewrite.plan uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.rewrite.plan.BuildRebasePlanError→git_branchless_lib.core.effects.Effectsgit_branchless_lib.core.rewrite.plan.ConstraintGraph→git_branchless_lib.core.effects.Effectsgit_branchless_lib.core.rewrite.plan.RebasePlanBuilder→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.rewrite.plan uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.rewrite.plan, while a change to git_branchless_lib.core.rewrite.plan can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.plan uses a module listed above it, which is the healthy direction.
9→6 git_branchless_lib.core.rewrite.plan uses git_branchless_lib.git.object✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.plan uses a type in git_branchless_lib.git.object.
- The types involved
git_branchless_lib.core.rewrite.plan.RebasePlanBuilder→git_branchless_lib.git.object.Commit
- Direction
- git_branchless_lib.core.rewrite.plan uses git_branchless_lib.git.object, so a change to git_branchless_lib.git.object can break git_branchless_lib.core.rewrite.plan, while a change to git_branchless_lib.core.rewrite.plan can't break git_branchless_lib.git.object.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.plan uses a module listed above it, which is the healthy direction.
9→15 git_branchless_lib.core.rewrite.plan uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.rewrite.plan uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.rewrite.plan.BuildRebasePlanError→git_branchless_lib.git.repo.Repogit_branchless_lib.core.rewrite.plan.RebasePlanBuilder→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.rewrite.plan uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.rewrite.plan, while a change to git_branchless_lib.core.rewrite.plan can't break git_branchless_lib.git.repo.
- 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.
9→20 git_branchless_lib.core.rewrite.plan uses git_branchless_lib.core.dag part of a loop✕
- Connections
- 4 pairs of types, where a type in git_branchless_lib.core.rewrite.plan uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_lib.core.rewrite.plan.BuildRebasePlanError→git_branchless_lib.core.dag.Daggit_branchless_lib.core.rewrite.plan.ConstraintGraph→git_branchless_lib.core.dag.Daggit_branchless_lib.core.rewrite.plan.RebasePlanBuilder→git_branchless_lib.core.dag.Daggit_branchless_lib.core.rewrite.plan.RebasePlanPermissions→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_lib.core.rewrite.plan uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_lib.core.rewrite.plan, while a change to git_branchless_lib.core.rewrite.plan can't break git_branchless_lib.core.dag.
- 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.
10→2 git_branchless_lib.git.index uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.index uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.git.index.IndexEntry→git_branchless_lib.git.oid.MaybeZeroOid
- Direction
- git_branchless_lib.git.index uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.git.index, while a change to git_branchless_lib.git.index can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.git.index uses a module listed above it, which is the healthy direction.
10→5 git_branchless_lib.git.index uses git_branchless_lib.git.tree✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.index uses a type in git_branchless_lib.git.tree.
- The types involved
git_branchless_lib.git.index.Index→git_branchless_lib.git.tree.Tree
- Direction
- git_branchless_lib.git.index uses git_branchless_lib.git.tree, so a change to git_branchless_lib.git.tree can break git_branchless_lib.git.index, while a change to git_branchless_lib.git.index can't break git_branchless_lib.git.tree.
- Position
- Below the diagonal: git_branchless_lib.git.index uses a module listed above it, which is the healthy direction.
10→7 git_branchless_lib.git.index uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.index uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.git.index.index$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.git.index uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.git.index, while a change to git_branchless_lib.git.index can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.git.index uses a module listed above it, which is the healthy direction.
10→15 git_branchless_lib.git.index uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.index uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.git.index.index$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.git.index uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.git.index, while a change to git_branchless_lib.git.index can't break git_branchless_lib.git.repo.
- 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.
10→18 git_branchless_lib.git.index uses git_branchless_lib.core.eventlog part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.index uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.git.index.index$module→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_lib.git.index uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.git.index, while a change to git_branchless_lib.git.index can't break git_branchless_lib.core.eventlog.
- 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.
11→6 git_branchless_lib.git.snapshot uses git_branchless_lib.git.object✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.snapshot uses a type in git_branchless_lib.git.object.
- The types involved
git_branchless_lib.git.snapshot.WorkingCopySnapshot→git_branchless_lib.git.object.Commit
- Direction
- git_branchless_lib.git.snapshot uses git_branchless_lib.git.object, so a change to git_branchless_lib.git.object can break git_branchless_lib.git.snapshot, while a change to git_branchless_lib.git.snapshot can't break git_branchless_lib.git.object.
- Position
- Below the diagonal: git_branchless_lib.git.snapshot uses a module listed above it, which is the healthy direction.
11→10 git_branchless_lib.git.snapshot uses git_branchless_lib.git.index✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.snapshot uses a type in git_branchless_lib.git.index.
- The types involved
git_branchless_lib.git.snapshot.WorkingCopySnapshot→git_branchless_lib.git.index.Indexgit_branchless_lib.git.snapshot.WorkingCopySnapshot→git_branchless_lib.git.index.Stage
- Direction
- git_branchless_lib.git.snapshot uses git_branchless_lib.git.index, so a change to git_branchless_lib.git.index can break git_branchless_lib.git.snapshot, while a change to git_branchless_lib.git.snapshot can't break git_branchless_lib.git.index.
- Position
- Below the diagonal: git_branchless_lib.git.snapshot uses a module listed above it, which is the healthy direction.
11→15 git_branchless_lib.git.snapshot uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.snapshot uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.git.snapshot.WorkingCopySnapshot→git_branchless_lib.git.repo.Repogit_branchless_lib.git.snapshot.WorkingCopySnapshot→git_branchless_lib.git.repo.ResolvedReferenceInfo
- Direction
- git_branchless_lib.git.snapshot uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.git.snapshot, while a change to git_branchless_lib.git.snapshot can't break git_branchless_lib.git.repo.
- 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.
11→16 git_branchless_lib.git.snapshot uses git_branchless_lib.git.reference part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.snapshot uses a type in git_branchless_lib.git.reference.
- The types involved
git_branchless_lib.git.snapshot.WorkingCopySnapshot→git_branchless_lib.git.reference.ReferenceName
- Direction
- git_branchless_lib.git.snapshot uses git_branchless_lib.git.reference, so a change to git_branchless_lib.git.reference can break git_branchless_lib.git.snapshot, while a change to git_branchless_lib.git.snapshot can't break git_branchless_lib.git.reference.
- 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.
12→2 git_branchless_lib.core.check_out uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.check_out uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.check_out.check_out$module→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.check_out uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.check_out, while a change to git_branchless_lib.core.check_out can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.check_out uses a module listed above it, which is the healthy direction.
12→3 git_branchless_lib.core.check_out uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.check_out uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.check_out.check_out$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.check_out uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.check_out, while a change to git_branchless_lib.core.check_out can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.check_out uses a module listed above it, which is the healthy direction.
12→7 git_branchless_lib.core.check_out uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.check_out uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.core.check_out.check_out$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.core.check_out uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.core.check_out, while a change to git_branchless_lib.core.check_out can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.core.check_out uses a module listed above it, which is the healthy direction.
12→11 git_branchless_lib.core.check_out uses git_branchless_lib.git.snapshot✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.check_out uses a type in git_branchless_lib.git.snapshot.
- The types involved
git_branchless_lib.core.check_out.check_out$module→git_branchless_lib.git.snapshot.WorkingCopySnapshot
- Direction
- git_branchless_lib.core.check_out uses git_branchless_lib.git.snapshot, so a change to git_branchless_lib.git.snapshot can break git_branchless_lib.core.check_out, while a change to git_branchless_lib.core.check_out can't break git_branchless_lib.git.snapshot.
- Position
- Below the diagonal: git_branchless_lib.core.check_out uses a module listed above it, which is the healthy direction.
12→15 git_branchless_lib.core.check_out uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.check_out uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.check_out.check_out$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.check_out uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.check_out, while a change to git_branchless_lib.core.check_out can't break git_branchless_lib.git.repo.
- 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.
12→18 git_branchless_lib.core.check_out uses git_branchless_lib.core.eventlog part of a loop✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.check_out uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.core.check_out.check_out$module→git_branchless_lib.core.eventlog.EventLogDbgit_branchless_lib.core.check_out.check_out$module→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_lib.core.check_out uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.core.check_out, while a change to git_branchless_lib.core.check_out can't break git_branchless_lib.core.eventlog.
- 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.
13→2 git_branchless_lib.core.rewrite.execute uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.rewrite.execute uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.rewrite.execute, while a change to git_branchless_lib.core.rewrite.execute can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute uses a module listed above it, which is the healthy direction.
13→3 git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.effects✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.rewrite.execute uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.rewrite.execute.FailedMergeInfo→git_branchless_lib.core.effects.Effectsgit_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.rewrite.execute, while a change to git_branchless_lib.core.rewrite.execute can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute uses a module listed above it, which is the healthy direction.
13→7 git_branchless_lib.core.rewrite.execute uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.core.rewrite.execute uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.core.rewrite.execute, while a change to git_branchless_lib.core.rewrite.execute can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute uses a module listed above it, which is the healthy direction.
13→9 git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.rewrite.plan✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute uses a type in git_branchless_lib.core.rewrite.plan.
- The types involved
git_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.core.rewrite.plan.RebasePlan
- Direction
- git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.rewrite.plan, so a change to git_branchless_lib.core.rewrite.plan can break git_branchless_lib.core.rewrite.execute, while a change to git_branchless_lib.core.rewrite.execute can't break git_branchless_lib.core.rewrite.plan.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute uses a module listed above it, which is the healthy direction.
13→12 git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.check_out✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.rewrite.execute uses a type in git_branchless_lib.core.check_out.
- The types involved
git_branchless_lib.core.rewrite.execute.ExecuteRebasePlanOptions→git_branchless_lib.core.check_out.CheckOutCommitOptionsgit_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.core.check_out.CheckOutCommitOptions
- Direction
- git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.check_out, so a change to git_branchless_lib.core.check_out can break git_branchless_lib.core.rewrite.execute, while a change to git_branchless_lib.core.rewrite.execute can't break git_branchless_lib.core.check_out.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute uses a module listed above it, which is the healthy direction.
13→15 git_branchless_lib.core.rewrite.execute uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 3 pairs of types, where a type in git_branchless_lib.core.rewrite.execute uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.rewrite.execute.FailedMergeInfo→git_branchless_lib.git.repo.Repogit_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.git.repo.Repogit_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.git.repo.ResolvedReferenceInfo
- Direction
- git_branchless_lib.core.rewrite.execute uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.rewrite.execute, while a change to git_branchless_lib.core.rewrite.execute can't break git_branchless_lib.git.repo.
- 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.
13→18 git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.eventlog part of a loop✕
- Connections
- 3 pairs of types, where a type in git_branchless_lib.core.rewrite.execute uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.core.rewrite.execute.ExecuteRebasePlanOptions→git_branchless_lib.core.eventlog.EventTransactionIdgit_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.core.eventlog.EventLogDbgit_branchless_lib.core.rewrite.execute.execute$module→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_lib.core.rewrite.execute uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.core.rewrite.execute, while a change to git_branchless_lib.core.rewrite.execute can't break git_branchless_lib.core.eventlog.
- 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.
14→3 git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.on_disk uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.rewrite.execute.on_disk.on_disk$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.rewrite.execute.on_disk, while a change to git_branchless_lib.core.rewrite.execute.on_disk can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.on_disk uses a module listed above it, which is the healthy direction.
14→7 git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.on_disk uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.core.rewrite.execute.on_disk.on_disk$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.core.rewrite.execute.on_disk, while a change to git_branchless_lib.core.rewrite.execute.on_disk can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.on_disk uses a module listed above it, which is the healthy direction.
14→9 git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.core.rewrite.plan✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.on_disk uses a type in git_branchless_lib.core.rewrite.plan.
- The types involved
git_branchless_lib.core.rewrite.execute.on_disk.on_disk$module→git_branchless_lib.core.rewrite.plan.RebasePlan
- Direction
- git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.core.rewrite.plan, so a change to git_branchless_lib.core.rewrite.plan can break git_branchless_lib.core.rewrite.execute.on_disk, while a change to git_branchless_lib.core.rewrite.execute.on_disk can't break git_branchless_lib.core.rewrite.plan.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.on_disk uses a module listed above it, which is the healthy direction.
14→13 git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.core.rewrite.execute✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.on_disk uses a type in git_branchless_lib.core.rewrite.execute.
- The types involved
git_branchless_lib.core.rewrite.execute.on_disk.on_disk$module→git_branchless_lib.core.rewrite.execute.ExecuteRebasePlanOptions
- Direction
- git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.core.rewrite.execute, so a change to git_branchless_lib.core.rewrite.execute can break git_branchless_lib.core.rewrite.execute.on_disk, while a change to git_branchless_lib.core.rewrite.execute.on_disk can't break git_branchless_lib.core.rewrite.execute.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.on_disk uses a module listed above it, which is the healthy direction.
14→15 git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.git.repo part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.on_disk uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.rewrite.execute.on_disk.on_disk$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.rewrite.execute.on_disk uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.rewrite.execute.on_disk, while a change to git_branchless_lib.core.rewrite.execute.on_disk can't break git_branchless_lib.git.repo.
- 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.
15→1 git_branchless_lib.git.repo uses git_branchless_lib.core.formatting✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.core.formatting.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.core.formatting.Glyphs
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.core.formatting, so a change to git_branchless_lib.core.formatting can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.core.formatting.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→2 git_branchless_lib.git.repo uses git_branchless_lib.git.oid✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.git.oid.NonZeroOidgit_branchless_lib.git.repo.ResolvedReferenceInfo→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→3 git_branchless_lib.git.repo uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→4 git_branchless_lib.git.repo uses git_branchless_lib.core.repo_ext✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.core.repo_ext.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.core.repo_ext.RepoExt
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.core.repo_ext, so a change to git_branchless_lib.core.repo_ext can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.core.repo_ext.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→5 git_branchless_lib.git.repo uses git_branchless_lib.git.tree✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.git.tree.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.git.tree.Tree
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.git.tree, so a change to git_branchless_lib.git.tree can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.git.tree.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→6 git_branchless_lib.git.repo uses git_branchless_lib.git.object✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.git.object.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.git.object.Commit
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.git.object, so a change to git_branchless_lib.git.object can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.git.object.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→7 git_branchless_lib.git.repo uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→10 git_branchless_lib.git.repo uses git_branchless_lib.git.index✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.git.index.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.git.index.Index
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.git.index, so a change to git_branchless_lib.git.index can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.git.index.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→14 git_branchless_lib.git.repo uses git_branchless_lib.core.rewrite.execute.on_disk✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.core.rewrite.execute.on_disk.
- The types involved
git_branchless_lib.git.repo.repo$module→git_branchless_lib.core.rewrite.execute.on_disk.Error
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.core.rewrite.execute.on_disk, so a change to git_branchless_lib.core.rewrite.execute.on_disk can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.core.rewrite.execute.on_disk.
- Position
- Below the diagonal: git_branchless_lib.git.repo uses a module listed above it, which is the healthy direction.
15→16 git_branchless_lib.git.repo uses git_branchless_lib.git.reference part of a loop✕
- Connections
- 3 pairs of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.git.reference.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.git.reference.Referencegit_branchless_lib.git.repo.Repo→git_branchless_lib.git.reference.ReferenceNamegit_branchless_lib.git.repo.ResolvedReferenceInfo→git_branchless_lib.git.reference.ReferenceName
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.git.reference, so a change to git_branchless_lib.git.reference can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.git.reference.
- 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.
15→18 git_branchless_lib.git.repo uses git_branchless_lib.core.eventlog part of a loop✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.repo uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.git.repo.Repo→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_lib.git.repo uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.git.repo, while a change to git_branchless_lib.git.repo can't break git_branchless_lib.core.eventlog.
- 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.
16→2 git_branchless_lib.git.reference uses git_branchless_lib.git.oid✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.git.reference uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.git.reference.ReferenceName→git_branchless_lib.git.oid.MaybeZeroOidgit_branchless_lib.git.reference.ReferenceName→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.git.reference uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.git.reference, while a change to git_branchless_lib.git.reference can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.git.reference uses a module listed above it, which is the healthy direction.
16→15 git_branchless_lib.git.reference uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.reference uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.git.reference.Branch→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.git.reference uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.git.reference, while a change to git_branchless_lib.git.reference can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.git.reference uses a module listed above it, which is the healthy direction.
17→2 git_branchless_lib.git.test uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.test uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.git.test.SerializedNonZeroOid→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.git.test uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.git.test, while a change to git_branchless_lib.git.test can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.git.test uses a module listed above it, which is the healthy direction.
17→6 git_branchless_lib.git.test uses git_branchless_lib.git.object✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.test uses a type in git_branchless_lib.git.object.
- The types involved
git_branchless_lib.git.test.test$module→git_branchless_lib.git.object.Commit
- Direction
- git_branchless_lib.git.test uses git_branchless_lib.git.object, so a change to git_branchless_lib.git.object can break git_branchless_lib.git.test, while a change to git_branchless_lib.git.test can't break git_branchless_lib.git.object.
- Position
- Below the diagonal: git_branchless_lib.git.test uses a module listed above it, which is the healthy direction.
17→15 git_branchless_lib.git.test uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.git.test uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.git.test.test$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.git.test uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.git.test, while a change to git_branchless_lib.git.test can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.git.test uses a module listed above it, which is the healthy direction.
18→2 git_branchless_lib.core.eventlog uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.eventlog uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.eventlog.EventReplayer→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.eventlog uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.eventlog, while a change to git_branchless_lib.core.eventlog can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.eventlog uses a module listed above it, which is the healthy direction.
18→3 git_branchless_lib.core.eventlog uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.eventlog uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.eventlog.EventReplayer→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.eventlog uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.eventlog, while a change to git_branchless_lib.core.eventlog can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.eventlog uses a module listed above it, which is the healthy direction.
18→15 git_branchless_lib.core.eventlog uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.eventlog uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.eventlog.EventReplayer→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.eventlog uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.eventlog, while a change to git_branchless_lib.core.eventlog can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.core.eventlog uses a module listed above it, which is the healthy direction.
18→16 git_branchless_lib.core.eventlog uses git_branchless_lib.git.reference✕
- Connections
- 3 pairs of types, where a type in git_branchless_lib.core.eventlog uses a type in git_branchless_lib.git.reference.
- The types involved
git_branchless_lib.core.eventlog.EventReplayer→git_branchless_lib.git.reference.ReferenceNamegit_branchless_lib.core.eventlog.Row→git_branchless_lib.git.reference.ReferenceNamegit_branchless_lib.core.eventlog.eventlog$module→git_branchless_lib.git.reference.ReferenceName
- Direction
- git_branchless_lib.core.eventlog uses git_branchless_lib.git.reference, so a change to git_branchless_lib.git.reference can break git_branchless_lib.core.eventlog, while a change to git_branchless_lib.core.eventlog can't break git_branchless_lib.git.reference.
- Position
- Below the diagonal: git_branchless_lib.core.eventlog uses a module listed above it, which is the healthy direction.
19→2 git_branchless_lib.core.worktree uses git_branchless_lib.git.oid✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.worktree uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.worktree.WorktreeEntry→git_branchless_lib.git.oid.NonZeroOidgit_branchless_lib.core.worktree.WorktreeSnapshot→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.worktree uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.worktree, while a change to git_branchless_lib.core.worktree can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.worktree uses a module listed above it, which is the healthy direction.
19→7 git_branchless_lib.core.worktree uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.worktree uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.core.worktree.worktree$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.core.worktree uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.core.worktree, while a change to git_branchless_lib.core.worktree can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.core.worktree uses a module listed above it, which is the healthy direction.
19→15 git_branchless_lib.core.worktree uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.worktree uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.worktree.worktree$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.worktree uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.worktree, while a change to git_branchless_lib.core.worktree can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.core.worktree uses a module listed above it, which is the healthy direction.
19→16 git_branchless_lib.core.worktree uses git_branchless_lib.git.reference✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.worktree uses a type in git_branchless_lib.git.reference.
- The types involved
git_branchless_lib.core.worktree.WorktreeEntry→git_branchless_lib.git.reference.ReferenceNamegit_branchless_lib.core.worktree.WorktreeSnapshot→git_branchless_lib.git.reference.ReferenceName
- Direction
- git_branchless_lib.core.worktree uses git_branchless_lib.git.reference, so a change to git_branchless_lib.git.reference can break git_branchless_lib.core.worktree, while a change to git_branchless_lib.core.worktree can't break git_branchless_lib.git.reference.
- Position
- Below the diagonal: git_branchless_lib.core.worktree uses a module listed above it, which is the healthy direction.
20→2 git_branchless_lib.core.dag uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.dag uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.dag.Dag→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.dag uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.dag, while a change to git_branchless_lib.core.dag can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.dag uses a module listed above it, which is the healthy direction.
20→3 git_branchless_lib.core.dag uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.dag uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.dag.Dag→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.dag uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.dag, while a change to git_branchless_lib.core.dag can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.dag uses a module listed above it, which is the healthy direction.
20→4 git_branchless_lib.core.dag uses git_branchless_lib.core.repo_ext✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.dag uses a type in git_branchless_lib.core.repo_ext.
- The types involved
git_branchless_lib.core.dag.Dag→git_branchless_lib.core.repo_ext.RepoReferencesSnapshot
- Direction
- git_branchless_lib.core.dag uses git_branchless_lib.core.repo_ext, so a change to git_branchless_lib.core.repo_ext can break git_branchless_lib.core.dag, while a change to git_branchless_lib.core.dag can't break git_branchless_lib.core.repo_ext.
- Position
- Below the diagonal: git_branchless_lib.core.dag uses a module listed above it, which is the healthy direction.
20→15 git_branchless_lib.core.dag uses git_branchless_lib.git.repo✕
- Connections
- 3 pairs of types, where a type in git_branchless_lib.core.dag uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.dag.Dag→git_branchless_lib.git.repo.Repogit_branchless_lib.core.dag.GitParentsBlocking→git_branchless_lib.git.repo.Repogit_branchless_lib.core.dag.dag$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.dag uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.dag, while a change to git_branchless_lib.core.dag can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.core.dag uses a module listed above it, which is the healthy direction.
20→18 git_branchless_lib.core.dag uses git_branchless_lib.core.eventlog✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.dag uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.core.dag.Dag→git_branchless_lib.core.eventlog.EventCursorgit_branchless_lib.core.dag.Dag→git_branchless_lib.core.eventlog.EventReplayer
- Direction
- git_branchless_lib.core.dag uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.core.dag, while a change to git_branchless_lib.core.dag can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_lib.core.dag uses a module listed above it, which is the healthy direction.
21→1 git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.formatting✕
- Connections
- 9 pairs of types, where a type in git_branchless_lib.core.node_descriptors uses a type in git_branchless_lib.core.formatting.
- The types involved
git_branchless_lib.core.node_descriptors.BranchesDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.CommitMessageDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.CommitOidDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.DifferentialRevisionDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.NodeDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.ObsolescenceExplanationDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.RelativeTimeDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.WorktreeDescriptor→git_branchless_lib.core.formatting.Glyphsgit_branchless_lib.core.node_descriptors.node_descriptors$module→git_branchless_lib.core.formatting.Glyphs
- Direction
- git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.formatting, so a change to git_branchless_lib.core.formatting can break git_branchless_lib.core.node_descriptors, while a change to git_branchless_lib.core.node_descriptors can't break git_branchless_lib.core.formatting.
- Position
- Below the diagonal: git_branchless_lib.core.node_descriptors uses a module listed above it, which is the healthy direction.
21→2 git_branchless_lib.core.node_descriptors uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.node_descriptors uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.node_descriptors.NodeObject→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.node_descriptors uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.node_descriptors, while a change to git_branchless_lib.core.node_descriptors can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.node_descriptors uses a module listed above it, which is the healthy direction.
21→4 git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.repo_ext✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.node_descriptors uses a type in git_branchless_lib.core.repo_ext.
- The types involved
git_branchless_lib.core.node_descriptors.BranchesDescriptor→git_branchless_lib.core.repo_ext.RepoReferencesSnapshot
- Direction
- git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.repo_ext, so a change to git_branchless_lib.core.repo_ext can break git_branchless_lib.core.node_descriptors, while a change to git_branchless_lib.core.node_descriptors can't break git_branchless_lib.core.repo_ext.
- Position
- Below the diagonal: git_branchless_lib.core.node_descriptors uses a module listed above it, which is the healthy direction.
21→15 git_branchless_lib.core.node_descriptors uses git_branchless_lib.git.repo✕
- Connections
- 4 pairs of types, where a type in git_branchless_lib.core.node_descriptors uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.node_descriptors.BranchesDescriptor→git_branchless_lib.git.repo.Repogit_branchless_lib.core.node_descriptors.BranchesDescriptor→git_branchless_lib.git.repo.ResolvedReferenceInfogit_branchless_lib.core.node_descriptors.DifferentialRevisionDescriptor→git_branchless_lib.git.repo.Repogit_branchless_lib.core.node_descriptors.RelativeTimeDescriptor→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.node_descriptors uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.node_descriptors, while a change to git_branchless_lib.core.node_descriptors can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.core.node_descriptors uses a module listed above it, which is the healthy direction.
21→16 git_branchless_lib.core.node_descriptors uses git_branchless_lib.git.reference✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.node_descriptors uses a type in git_branchless_lib.git.reference.
- The types involved
git_branchless_lib.core.node_descriptors.Redactor→git_branchless_lib.git.reference.ReferenceName
- Direction
- git_branchless_lib.core.node_descriptors uses git_branchless_lib.git.reference, so a change to git_branchless_lib.git.reference can break git_branchless_lib.core.node_descriptors, while a change to git_branchless_lib.core.node_descriptors can't break git_branchless_lib.git.reference.
- Position
- Below the diagonal: git_branchless_lib.core.node_descriptors uses a module listed above it, which is the healthy direction.
21→18 git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.eventlog✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.node_descriptors uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.core.node_descriptors.ObsolescenceExplanationDescriptor→git_branchless_lib.core.eventlog.EventCursorgit_branchless_lib.core.node_descriptors.ObsolescenceExplanationDescriptor→git_branchless_lib.core.eventlog.EventReplayer
- Direction
- git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.core.node_descriptors, while a change to git_branchless_lib.core.node_descriptors can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_lib.core.node_descriptors uses a module listed above it, which is the healthy direction.
21→19 git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.worktree✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.node_descriptors uses a type in git_branchless_lib.core.worktree.
- The types involved
git_branchless_lib.core.node_descriptors.WorktreeDescriptor→git_branchless_lib.core.worktree.WorktreeSnapshot
- Direction
- git_branchless_lib.core.node_descriptors uses git_branchless_lib.core.worktree, so a change to git_branchless_lib.core.worktree can break git_branchless_lib.core.node_descriptors, while a change to git_branchless_lib.core.node_descriptors can't break git_branchless_lib.core.worktree.
- Position
- Below the diagonal: git_branchless_lib.core.node_descriptors uses a module listed above it, which is the healthy direction.
22→2 git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.in_memory uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.rewrite.execute.in_memory.in_memory$module→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.rewrite.execute.in_memory, while a change to git_branchless_lib.core.rewrite.execute.in_memory can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.in_memory uses a module listed above it, which is the healthy direction.
22→3 git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.in_memory uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.rewrite.execute.in_memory.in_memory$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.rewrite.execute.in_memory, while a change to git_branchless_lib.core.rewrite.execute.in_memory can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.in_memory uses a module listed above it, which is the healthy direction.
22→7 git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.in_memory uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.core.rewrite.execute.in_memory.in_memory$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.core.rewrite.execute.in_memory, while a change to git_branchless_lib.core.rewrite.execute.in_memory can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.in_memory uses a module listed above it, which is the healthy direction.
22→9 git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.rewrite.plan✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.in_memory uses a type in git_branchless_lib.core.rewrite.plan.
- The types involved
git_branchless_lib.core.rewrite.execute.in_memory.in_memory$module→git_branchless_lib.core.rewrite.plan.RebasePlan
- Direction
- git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.rewrite.plan, so a change to git_branchless_lib.core.rewrite.plan can break git_branchless_lib.core.rewrite.execute.in_memory, while a change to git_branchless_lib.core.rewrite.execute.in_memory can't break git_branchless_lib.core.rewrite.plan.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.in_memory uses a module listed above it, which is the healthy direction.
22→13 git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.rewrite.execute✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.in_memory uses a type in git_branchless_lib.core.rewrite.execute.
- The types involved
git_branchless_lib.core.rewrite.execute.in_memory.in_memory$module→git_branchless_lib.core.rewrite.execute.ExecuteRebasePlanOptions
- Direction
- git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.rewrite.execute, so a change to git_branchless_lib.core.rewrite.execute can break git_branchless_lib.core.rewrite.execute.in_memory, while a change to git_branchless_lib.core.rewrite.execute.in_memory can't break git_branchless_lib.core.rewrite.execute.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.in_memory uses a module listed above it, which is the healthy direction.
22→15 git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.in_memory uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.rewrite.execute.in_memory.in_memory$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.rewrite.execute.in_memory, while a change to git_branchless_lib.core.rewrite.execute.in_memory can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.in_memory uses a module listed above it, which is the healthy direction.
22→18 git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.execute.in_memory uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.core.rewrite.execute.in_memory.in_memory$module→git_branchless_lib.core.eventlog.EventLogDb
- Direction
- git_branchless_lib.core.rewrite.execute.in_memory uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.core.rewrite.execute.in_memory, while a change to git_branchless_lib.core.rewrite.execute.in_memory can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.execute.in_memory uses a module listed above it, which is the healthy direction.
23→2 git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.rewrite_hooks uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_lib.core.rewrite.rewrite_hooks.rewrite_hooks$module→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_lib.core.rewrite.rewrite_hooks, while a change to git_branchless_lib.core.rewrite.rewrite_hooks can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.rewrite_hooks uses a module listed above it, which is the healthy direction.
23→3 git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.rewrite_hooks uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.rewrite.rewrite_hooks.rewrite_hooks$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.rewrite.rewrite_hooks, while a change to git_branchless_lib.core.rewrite.rewrite_hooks can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.rewrite_hooks uses a module listed above it, which is the healthy direction.
23→7 git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.rewrite_hooks uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.core.rewrite.rewrite_hooks.rewrite_hooks$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.core.rewrite.rewrite_hooks, while a change to git_branchless_lib.core.rewrite.rewrite_hooks can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.rewrite_hooks uses a module listed above it, which is the healthy direction.
23→15 git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.git.repo✕
- Connections
- 2 pairs of types, where a type in git_branchless_lib.core.rewrite.rewrite_hooks uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.rewrite.rewrite_hooks.rewrite_hooks$module→git_branchless_lib.git.repo.Repogit_branchless_lib.core.rewrite.rewrite_hooks.rewrite_hooks$module→git_branchless_lib.git.repo.ResolvedReferenceInfo
- Direction
- git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.rewrite.rewrite_hooks, while a change to git_branchless_lib.core.rewrite.rewrite_hooks can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.rewrite_hooks uses a module listed above it, which is the healthy direction.
23→18 git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.rewrite.rewrite_hooks uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.core.rewrite.rewrite_hooks.rewrite_hooks$module→git_branchless_lib.core.eventlog.EventLogDb
- Direction
- git_branchless_lib.core.rewrite.rewrite_hooks uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.core.rewrite.rewrite_hooks, while a change to git_branchless_lib.core.rewrite.rewrite_hooks can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_lib.core.rewrite.rewrite_hooks uses a module listed above it, which is the healthy direction.
24→3 git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.untracked_file_cache uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_lib.core.untracked_file_cache.untracked_file_cache$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_lib.core.untracked_file_cache, while a change to git_branchless_lib.core.untracked_file_cache can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_lib.core.untracked_file_cache uses a module listed above it, which is the healthy direction.
24→7 git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.untracked_file_cache uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_lib.core.untracked_file_cache.untracked_file_cache$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_lib.core.untracked_file_cache, while a change to git_branchless_lib.core.untracked_file_cache can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_lib.core.untracked_file_cache uses a module listed above it, which is the healthy direction.
24→15 git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.untracked_file_cache uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_lib.core.untracked_file_cache.untracked_file_cache$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_lib.core.untracked_file_cache, while a change to git_branchless_lib.core.untracked_file_cache can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_lib.core.untracked_file_cache uses a module listed above it, which is the healthy direction.
24→18 git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless_lib.core.untracked_file_cache uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_lib.core.untracked_file_cache.untracked_file_cache$module→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_lib.core.untracked_file_cache uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_lib.core.untracked_file_cache, while a change to git_branchless_lib.core.untracked_file_cache can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_lib.core.untracked_file_cache uses a module listed above it, which is the healthy direction.
25→3 git_branchless.commands.bug_report uses git_branchless_lib.core.effects✕
- Connections
- 2 pairs of types, where a type in git_branchless.commands.bug_report uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless.commands.bug_report.EventCollector→git_branchless_lib.core.effects.Effectsgit_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless.commands.bug_report uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless.commands.bug_report, while a change to git_branchless.commands.bug_report can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless.commands.bug_report uses a module listed above it, which is the healthy direction.
25→4 git_branchless.commands.bug_report uses git_branchless_lib.core.repo_ext✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.bug_report uses a type in git_branchless_lib.core.repo_ext.
- The types involved
git_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.repo_ext.RepoReferencesSnapshot
- Direction
- git_branchless.commands.bug_report uses git_branchless_lib.core.repo_ext, so a change to git_branchless_lib.core.repo_ext can break git_branchless.commands.bug_report, while a change to git_branchless.commands.bug_report can't break git_branchless_lib.core.repo_ext.
- Position
- Below the diagonal: git_branchless.commands.bug_report uses a module listed above it, which is the healthy direction.
25→7 git_branchless.commands.bug_report uses git_branchless_lib.git.run✕
- Connections
- 3 pairs of types, where a type in git_branchless.commands.bug_report uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless.commands.bug_report.EventCollector→git_branchless_lib.git.run.GitRunInfogit_branchless.commands.bug_report.HookCollector→git_branchless_lib.git.run.GitRunInfogit_branchless.commands.bug_report.bug_report$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless.commands.bug_report uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless.commands.bug_report, while a change to git_branchless.commands.bug_report can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless.commands.bug_report uses a module listed above it, which is the healthy direction.
25→15 git_branchless.commands.bug_report uses git_branchless_lib.git.repo✕
- Connections
- 2 pairs of types, where a type in git_branchless.commands.bug_report uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless.commands.bug_report.bug_report$module→git_branchless_lib.git.repo.Repogit_branchless.commands.bug_report.bug_report$module→git_branchless_lib.git.repo.ResolvedReferenceInfo
- Direction
- git_branchless.commands.bug_report uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless.commands.bug_report, while a change to git_branchless.commands.bug_report can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless.commands.bug_report uses a module listed above it, which is the healthy direction.
25→18 git_branchless.commands.bug_report uses git_branchless_lib.core.eventlog✕
- Connections
- 4 pairs of types, where a type in git_branchless.commands.bug_report uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.eventlog.Eventgit_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.eventlog.EventCursorgit_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.eventlog.EventLogDbgit_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.eventlog.EventReplayer
- Direction
- git_branchless.commands.bug_report uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless.commands.bug_report, while a change to git_branchless.commands.bug_report can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless.commands.bug_report uses a module listed above it, which is the healthy direction.
25→20 git_branchless.commands.bug_report uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.bug_report uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless.commands.bug_report uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless.commands.bug_report, while a change to git_branchless.commands.bug_report can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless.commands.bug_report uses a module listed above it, which is the healthy direction.
25→21 git_branchless.commands.bug_report uses git_branchless_lib.core.node_descriptors✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.bug_report uses a type in git_branchless_lib.core.node_descriptors.
- The types involved
git_branchless.commands.bug_report.bug_report$module→git_branchless_lib.core.node_descriptors.Redactor
- Direction
- git_branchless.commands.bug_report uses git_branchless_lib.core.node_descriptors, so a change to git_branchless_lib.core.node_descriptors can break git_branchless.commands.bug_report, while a change to git_branchless.commands.bug_report can't break git_branchless_lib.core.node_descriptors.
- Position
- Below the diagonal: git_branchless.commands.bug_report uses a module listed above it, which is the healthy direction.
26→2 git_branchless_navigation uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_navigation uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_navigation.git_branchless_navigation$module→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_navigation uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_navigation, while a change to git_branchless_navigation can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_navigation uses a module listed above it, which is the healthy direction.
26→3 git_branchless_navigation uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_navigation uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_navigation.git_branchless_navigation$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_navigation uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_navigation, while a change to git_branchless_navigation can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_navigation uses a module listed above it, which is the healthy direction.
26→7 git_branchless_navigation uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_navigation uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_navigation.git_branchless_navigation$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_navigation uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_navigation, while a change to git_branchless_navigation can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_navigation uses a module listed above it, which is the healthy direction.
26→15 git_branchless_navigation uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_navigation uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_navigation.git_branchless_navigation$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_navigation uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_navigation, while a change to git_branchless_navigation can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_navigation uses a module listed above it, which is the healthy direction.
26→20 git_branchless_navigation uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_navigation uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_navigation.git_branchless_navigation$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_navigation uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_navigation, while a change to git_branchless_navigation can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_navigation uses a module listed above it, which is the healthy direction.
26→30 git_branchless_navigation uses git_branchless_opts part of a loop✕
- Connections
- 2 pairs of types, where a type in git_branchless_navigation uses a type in git_branchless_opts.
- The types involved
git_branchless_navigation.git_branchless_navigation$module→git_branchless_opts.SwitchOptionsgit_branchless_navigation.git_branchless_navigation$module→git_branchless_opts.TraverseCommitsOptions
- Direction
- git_branchless_navigation uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless_navigation, while a change to git_branchless_navigation can't break git_branchless_opts.
- 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.
27→3 git_branchless_revset.eval uses git_branchless_lib.core.effects✕
- Connections
- 2 pairs of types, where a type in git_branchless_revset.eval uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_revset.eval.Context→git_branchless_lib.core.effects.Effectsgit_branchless_revset.eval.eval$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_revset.eval uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_revset.eval, while a change to git_branchless_revset.eval can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_revset.eval uses a module listed above it, which is the healthy direction.
27→14 git_branchless_revset.eval uses git_branchless_lib.core.rewrite.execute.on_disk✕
- Connections
- 1 pair of types, where a type in git_branchless_revset.eval uses a type in git_branchless_lib.core.rewrite.execute.on_disk.
- The types involved
git_branchless_revset.eval.eval$module→git_branchless_lib.core.rewrite.execute.on_disk.Error
- Direction
- git_branchless_revset.eval uses git_branchless_lib.core.rewrite.execute.on_disk, so a change to git_branchless_lib.core.rewrite.execute.on_disk can break git_branchless_revset.eval, while a change to git_branchless_revset.eval can't break git_branchless_lib.core.rewrite.execute.on_disk.
- Position
- Below the diagonal: git_branchless_revset.eval uses a module listed above it, which is the healthy direction.
27→15 git_branchless_revset.eval uses git_branchless_lib.git.repo✕
- Connections
- 2 pairs of types, where a type in git_branchless_revset.eval uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_revset.eval.Context→git_branchless_lib.git.repo.Repogit_branchless_revset.eval.eval$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_revset.eval uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_revset.eval, while a change to git_branchless_revset.eval can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_revset.eval uses a module listed above it, which is the healthy direction.
27→20 git_branchless_revset.eval uses git_branchless_lib.core.dag✕
- Connections
- 2 pairs of types, where a type in git_branchless_revset.eval uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_revset.eval.Context→git_branchless_lib.core.dag.Daggit_branchless_revset.eval.eval$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_revset.eval uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_revset.eval, while a change to git_branchless_revset.eval can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_revset.eval uses a module listed above it, which is the healthy direction.
28→2 git_branchless_smartlog.graph uses git_branchless_lib.git.oid✕
- Connections
- 3 pairs of types, where a type in git_branchless_smartlog.graph uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_smartlog.graph.AncestorInfo→git_branchless_lib.git.oid.NonZeroOidgit_branchless_smartlog.graph.ChildInfo→git_branchless_lib.git.oid.NonZeroOidgit_branchless_smartlog.graph.Node→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_smartlog.graph uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_smartlog.graph, while a change to git_branchless_smartlog.graph can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_smartlog.graph uses a module listed above it, which is the healthy direction.
28→3 git_branchless_smartlog.graph uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.graph uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_smartlog.graph.graph$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_smartlog.graph uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_smartlog.graph, while a change to git_branchless_smartlog.graph can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_smartlog.graph uses a module listed above it, which is the healthy direction.
28→6 git_branchless_smartlog.graph uses git_branchless_lib.git.object✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.graph uses a type in git_branchless_lib.git.object.
- The types involved
git_branchless_smartlog.graph.SmartlogGraph→git_branchless_lib.git.object.Commit
- Direction
- git_branchless_smartlog.graph uses git_branchless_lib.git.object, so a change to git_branchless_lib.git.object can break git_branchless_smartlog.graph, while a change to git_branchless_smartlog.graph can't break git_branchless_lib.git.object.
- Position
- Below the diagonal: git_branchless_smartlog.graph uses a module listed above it, which is the healthy direction.
28→15 git_branchless_smartlog.graph uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.graph uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_smartlog.graph.graph$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_smartlog.graph uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_smartlog.graph, while a change to git_branchless_smartlog.graph can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_smartlog.graph uses a module listed above it, which is the healthy direction.
28→18 git_branchless_smartlog.graph uses git_branchless_lib.core.eventlog✕
- Connections
- 2 pairs of types, where a type in git_branchless_smartlog.graph uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_smartlog.graph.graph$module→git_branchless_lib.core.eventlog.EventCursorgit_branchless_smartlog.graph.graph$module→git_branchless_lib.core.eventlog.EventReplayer
- Direction
- git_branchless_smartlog.graph uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_smartlog.graph, while a change to git_branchless_smartlog.graph can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_smartlog.graph uses a module listed above it, which is the healthy direction.
28→20 git_branchless_smartlog.graph uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.graph uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_smartlog.graph.graph$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_smartlog.graph uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_smartlog.graph, while a change to git_branchless_smartlog.graph can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_smartlog.graph uses a module listed above it, which is the healthy direction.
28→21 git_branchless_smartlog.graph uses git_branchless_lib.core.node_descriptors✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.graph uses a type in git_branchless_lib.core.node_descriptors.
- The types involved
git_branchless_smartlog.graph.Node→git_branchless_lib.core.node_descriptors.NodeObject
- Direction
- git_branchless_smartlog.graph uses git_branchless_lib.core.node_descriptors, so a change to git_branchless_lib.core.node_descriptors can break git_branchless_smartlog.graph, while a change to git_branchless_smartlog.graph can't break git_branchless_lib.core.node_descriptors.
- Position
- Below the diagonal: git_branchless_smartlog.graph uses a module listed above it, which is the healthy direction.
29→1 git_branchless_undo uses git_branchless_lib.core.formatting✕
- Connections
- 1 pair of types, where a type in git_branchless_undo uses a type in git_branchless_lib.core.formatting.
- The types involved
git_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.formatting.Glyphs
- Direction
- git_branchless_undo uses git_branchless_lib.core.formatting, so a change to git_branchless_lib.core.formatting can break git_branchless_undo, while a change to git_branchless_undo can't break git_branchless_lib.core.formatting.
- Position
- Below the diagonal: git_branchless_undo uses a module listed above it, which is the healthy direction.
29→3 git_branchless_undo uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_undo uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_undo uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_undo, while a change to git_branchless_undo can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_undo uses a module listed above it, which is the healthy direction.
29→7 git_branchless_undo uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_undo uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_undo.git_branchless_undo$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_undo uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_undo, while a change to git_branchless_undo can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_undo uses a module listed above it, which is the healthy direction.
29→12 git_branchless_undo uses git_branchless_lib.core.check_out✕
- Connections
- 2 pairs of types, where a type in git_branchless_undo uses a type in git_branchless_lib.core.check_out.
- The types involved
git_branchless_undo.UndoCheckoutTarget→git_branchless_lib.core.check_out.CheckOutCommitOptionsgit_branchless_undo.UndoCheckoutTarget→git_branchless_lib.core.check_out.CheckoutTarget
- Direction
- git_branchless_undo uses git_branchless_lib.core.check_out, so a change to git_branchless_lib.core.check_out can break git_branchless_undo, while a change to git_branchless_undo can't break git_branchless_lib.core.check_out.
- Position
- Below the diagonal: git_branchless_undo uses a module listed above it, which is the healthy direction.
29→15 git_branchless_undo uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_undo uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_undo.git_branchless_undo$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_undo uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_undo, while a change to git_branchless_undo can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_undo uses a module listed above it, which is the healthy direction.
29→18 git_branchless_undo uses git_branchless_lib.core.eventlog✕
- Connections
- 5 pairs of types, where a type in git_branchless_undo uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.eventlog.Eventgit_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.eventlog.EventCursorgit_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.eventlog.EventLogDbgit_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.eventlog.EventReplayergit_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_undo uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_undo, while a change to git_branchless_undo can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_undo uses a module listed above it, which is the healthy direction.
29→20 git_branchless_undo uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_undo uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_undo.git_branchless_undo$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_undo uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_undo, while a change to git_branchless_undo can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_undo uses a module listed above it, which is the healthy direction.
30→24 git_branchless_opts uses git_branchless_lib.core.untracked_file_cache✕
- Connections
- 1 pair of types, where a type in git_branchless_opts uses a type in git_branchless_lib.core.untracked_file_cache.
- The types involved
git_branchless_opts.RecordArgs→git_branchless_lib.core.untracked_file_cache.UntrackedFileStrategy
- Direction
- git_branchless_opts uses git_branchless_lib.core.untracked_file_cache, so a change to git_branchless_lib.core.untracked_file_cache can break git_branchless_opts, while a change to git_branchless_opts can't break git_branchless_lib.core.untracked_file_cache.
- Position
- Below the diagonal: git_branchless_opts uses a module listed above it, which is the healthy direction.
30→26 git_branchless_opts uses git_branchless_navigation✕
- Connections
- 1 pair of types, where a type in git_branchless_opts uses a type in git_branchless_navigation.
- The types involved
git_branchless_opts.Opts→git_branchless_navigation.Command
- Direction
- git_branchless_opts uses git_branchless_navigation, so a change to git_branchless_navigation can break git_branchless_opts, while a change to git_branchless_opts can't break git_branchless_navigation.
- Position
- Below the diagonal: git_branchless_opts uses a module listed above it, which is the healthy direction.
31→3 git_branchless.commands.restack uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.restack uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless.commands.restack uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
31→7 git_branchless.commands.restack uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.restack uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless.commands.restack uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
31→9 git_branchless.commands.restack uses git_branchless_lib.core.rewrite.plan✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.restack uses a type in git_branchless_lib.core.rewrite.plan.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_lib.core.rewrite.plan.BuildRebasePlanOptions
- Direction
- git_branchless.commands.restack uses git_branchless_lib.core.rewrite.plan, so a change to git_branchless_lib.core.rewrite.plan can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_lib.core.rewrite.plan.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
31→13 git_branchless.commands.restack uses git_branchless_lib.core.rewrite.execute✕
- Connections
- 2 pairs of types, where a type in git_branchless.commands.restack uses a type in git_branchless_lib.core.rewrite.execute.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_lib.core.rewrite.execute.ExecuteRebasePlanOptionsgit_branchless.commands.restack.restack$module→git_branchless_lib.core.rewrite.execute.MergeConflictRemediation
- Direction
- git_branchless.commands.restack uses git_branchless_lib.core.rewrite.execute, so a change to git_branchless_lib.core.rewrite.execute can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_lib.core.rewrite.execute.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
31→15 git_branchless.commands.restack uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.restack uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless.commands.restack uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
31→18 git_branchless.commands.restack uses git_branchless_lib.core.eventlog✕
- Connections
- 3 pairs of types, where a type in git_branchless.commands.restack uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_lib.core.eventlog.EventCursorgit_branchless.commands.restack.restack$module→git_branchless_lib.core.eventlog.EventLogDbgit_branchless.commands.restack.restack$module→git_branchless_lib.core.eventlog.EventReplayer
- Direction
- git_branchless.commands.restack uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
31→20 git_branchless.commands.restack uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.restack uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless.commands.restack uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
31→30 git_branchless.commands.restack uses git_branchless_opts✕
- Connections
- 3 pairs of types, where a type in git_branchless.commands.restack uses a type in git_branchless_opts.
- The types involved
git_branchless.commands.restack.restack$module→git_branchless_opts.MoveOptionsgit_branchless.commands.restack.restack$module→git_branchless_opts.ResolveRevsetOptionsgit_branchless.commands.restack.restack$module→git_branchless_opts.Revset
- Direction
- git_branchless.commands.restack uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless.commands.restack, while a change to git_branchless.commands.restack can't break git_branchless_opts.
- Position
- Below the diagonal: git_branchless.commands.restack uses a module listed above it, which is the healthy direction.
32→3 git_branchless.commands.sync uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.sync uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless.commands.sync uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
32→7 git_branchless.commands.sync uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.sync uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless.commands.sync uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
32→9 git_branchless.commands.sync uses git_branchless_lib.core.rewrite.plan✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.sync uses a type in git_branchless_lib.core.rewrite.plan.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_lib.core.rewrite.plan.BuildRebasePlanOptions
- Direction
- git_branchless.commands.sync uses git_branchless_lib.core.rewrite.plan, so a change to git_branchless_lib.core.rewrite.plan can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_lib.core.rewrite.plan.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
32→13 git_branchless.commands.sync uses git_branchless_lib.core.rewrite.execute✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.sync uses a type in git_branchless_lib.core.rewrite.execute.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_lib.core.rewrite.execute.ExecuteRebasePlanOptions
- Direction
- git_branchless.commands.sync uses git_branchless_lib.core.rewrite.execute, so a change to git_branchless_lib.core.rewrite.execute can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_lib.core.rewrite.execute.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
32→15 git_branchless.commands.sync uses git_branchless_lib.git.repo✕
- Connections
- 2 pairs of types, where a type in git_branchless.commands.sync uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_lib.git.repo.Repogit_branchless.commands.sync.sync$module→git_branchless_lib.git.repo.ResolvedReferenceInfo
- Direction
- git_branchless.commands.sync uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
32→18 git_branchless.commands.sync uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.sync uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_lib.core.eventlog.EventLogDb
- Direction
- git_branchless.commands.sync uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
32→20 git_branchless.commands.sync uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless.commands.sync uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless.commands.sync uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
32→30 git_branchless.commands.sync uses git_branchless_opts✕
- Connections
- 3 pairs of types, where a type in git_branchless.commands.sync uses a type in git_branchless_opts.
- The types involved
git_branchless.commands.sync.sync$module→git_branchless_opts.MoveOptionsgit_branchless.commands.sync.sync$module→git_branchless_opts.ResolveRevsetOptionsgit_branchless.commands.sync.sync$module→git_branchless_opts.Revset
- Direction
- git_branchless.commands.sync uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless.commands.sync, while a change to git_branchless.commands.sync can't break git_branchless_opts.
- Position
- Below the diagonal: git_branchless.commands.sync uses a module listed above it, which is the healthy direction.
33→3 git_branchless_init uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_init uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_init.git_branchless_init$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_init uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_init, while a change to git_branchless_init can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_init uses a module listed above it, which is the healthy direction.
33→7 git_branchless_init uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_init uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_init.git_branchless_init$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_init uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_init, while a change to git_branchless_init can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_init uses a module listed above it, which is the healthy direction.
33→8 git_branchless_init uses git_branchless_invoke✕
- Connections
- 1 pair of types, where a type in git_branchless_init uses a type in git_branchless_invoke.
- The types involved
git_branchless_init.git_branchless_init$module→git_branchless_invoke.CommandContext
- Direction
- git_branchless_init uses git_branchless_invoke, so a change to git_branchless_invoke can break git_branchless_init, while a change to git_branchless_init can't break git_branchless_invoke.
- Position
- Below the diagonal: git_branchless_init uses a module listed above it, which is the healthy direction.
33→15 git_branchless_init uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_init uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_init.git_branchless_init$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_init uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_init, while a change to git_branchless_init can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_init uses a module listed above it, which is the healthy direction.
33→30 git_branchless_init uses git_branchless_opts✕
- Connections
- 2 pairs of types, where a type in git_branchless_init uses a type in git_branchless_opts.
- The types involved
git_branchless_init.git_branchless_init$module→git_branchless_opts.InitArgsgit_branchless_init.git_branchless_init$module→git_branchless_opts.InstallManPagesArgs
- Direction
- git_branchless_init uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless_init, while a change to git_branchless_init can't break git_branchless_opts.
- Position
- Below the diagonal: git_branchless_init uses a module listed above it, which is the healthy direction.
34→3 git_branchless_record uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_record uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_record uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
34→7 git_branchless_record uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_record uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_record uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
34→8 git_branchless_record uses git_branchless_invoke✕
- Connections
- 1 pair of types, where a type in git_branchless_record uses a type in git_branchless_invoke.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_invoke.CommandContext
- Direction
- git_branchless_record uses git_branchless_invoke, so a change to git_branchless_invoke can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_invoke.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
34→11 git_branchless_record uses git_branchless_lib.git.snapshot✕
- Connections
- 2 pairs of types, where a type in git_branchless_record uses a type in git_branchless_lib.git.snapshot.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_lib.git.snapshot.WorkingCopyChangesTypegit_branchless_record.git_branchless_record$module→git_branchless_lib.git.snapshot.WorkingCopySnapshot
- Direction
- git_branchless_record uses git_branchless_lib.git.snapshot, so a change to git_branchless_lib.git.snapshot can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_lib.git.snapshot.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
34→15 git_branchless_record uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_record uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_record uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
34→18 git_branchless_record uses git_branchless_lib.core.eventlog✕
- Connections
- 2 pairs of types, where a type in git_branchless_record uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_lib.core.eventlog.EventLogDbgit_branchless_record.git_branchless_record$module→git_branchless_lib.core.eventlog.EventTransactionId
- Direction
- git_branchless_record uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
34→24 git_branchless_record uses git_branchless_lib.core.untracked_file_cache✕
- Connections
- 1 pair of types, where a type in git_branchless_record uses a type in git_branchless_lib.core.untracked_file_cache.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_lib.core.untracked_file_cache.UntrackedFileStrategy
- Direction
- git_branchless_record uses git_branchless_lib.core.untracked_file_cache, so a change to git_branchless_lib.core.untracked_file_cache can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_lib.core.untracked_file_cache.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
34→30 git_branchless_record uses git_branchless_opts✕
- Connections
- 2 pairs of types, where a type in git_branchless_record uses a type in git_branchless_opts.
- The types involved
git_branchless_record.git_branchless_record$module→git_branchless_opts.RecordArgsgit_branchless_record.git_branchless_record$module→git_branchless_opts.Revset
- Direction
- git_branchless_record uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless_record, while a change to git_branchless_record can't break git_branchless_opts.
- Position
- Below the diagonal: git_branchless_record uses a module listed above it, which is the healthy direction.
35→1 git_branchless_smartlog.render uses git_branchless_lib.core.formatting✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.render uses a type in git_branchless_lib.core.formatting.
- The types involved
git_branchless_smartlog.render.render$module→git_branchless_lib.core.formatting.Glyphs
- Direction
- git_branchless_smartlog.render uses git_branchless_lib.core.formatting, so a change to git_branchless_lib.core.formatting can break git_branchless_smartlog.render, while a change to git_branchless_smartlog.render can't break git_branchless_lib.core.formatting.
- Position
- Below the diagonal: git_branchless_smartlog.render uses a module listed above it, which is the healthy direction.
35→2 git_branchless_smartlog.render uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.render uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_smartlog.render.render$module→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_smartlog.render uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_smartlog.render, while a change to git_branchless_smartlog.render can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_smartlog.render uses a module listed above it, which is the healthy direction.
35→3 git_branchless_smartlog.render uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.render uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_smartlog.render.render$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_smartlog.render uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_smartlog.render, while a change to git_branchless_smartlog.render can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_smartlog.render uses a module listed above it, which is the healthy direction.
35→15 git_branchless_smartlog.render uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.render uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_smartlog.render.render$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_smartlog.render uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_smartlog.render, while a change to git_branchless_smartlog.render can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_smartlog.render uses a module listed above it, which is the healthy direction.
35→20 git_branchless_smartlog.render uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.render uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_smartlog.render.render$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_smartlog.render uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_smartlog.render, while a change to git_branchless_smartlog.render can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_smartlog.render uses a module listed above it, which is the healthy direction.
35→28 git_branchless_smartlog.render uses git_branchless_smartlog.graph✕
- Connections
- 1 pair of types, where a type in git_branchless_smartlog.render uses a type in git_branchless_smartlog.graph.
- The types involved
git_branchless_smartlog.render.render$module→git_branchless_smartlog.graph.SmartlogGraph
- Direction
- git_branchless_smartlog.render uses git_branchless_smartlog.graph, so a change to git_branchless_smartlog.graph can break git_branchless_smartlog.render, while a change to git_branchless_smartlog.render can't break git_branchless_smartlog.graph.
- Position
- Below the diagonal: git_branchless_smartlog.render uses a module listed above it, which is the healthy direction.
35→30 git_branchless_smartlog.render uses git_branchless_opts✕
- Connections
- 2 pairs of types, where a type in git_branchless_smartlog.render uses a type in git_branchless_opts.
- The types involved
git_branchless_smartlog.render.SmartlogOptions→git_branchless_opts.ResolveRevsetOptionsgit_branchless_smartlog.render.SmartlogOptions→git_branchless_opts.Revset
- Direction
- git_branchless_smartlog.render uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless_smartlog.render, while a change to git_branchless_smartlog.render can't break git_branchless_opts.
- Position
- Below the diagonal: git_branchless_smartlog.render uses a module listed above it, which is the healthy direction.
36→2 git_branchless_submit uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_submit.CreateStatus→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_submit uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→3 git_branchless_submit uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_submit.git_branchless_submit$module→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_submit uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→4 git_branchless_submit uses git_branchless_lib.core.repo_ext✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_lib.core.repo_ext.
- The types involved
git_branchless_submit.git_branchless_submit$module→git_branchless_lib.core.repo_ext.RepoReferencesSnapshot
- Direction
- git_branchless_submit uses git_branchless_lib.core.repo_ext, so a change to git_branchless_lib.core.repo_ext can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_lib.core.repo_ext.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→7 git_branchless_submit uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_submit.git_branchless_submit$module→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_submit uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→8 git_branchless_submit uses git_branchless_invoke✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_invoke.
- The types involved
git_branchless_submit.git_branchless_submit$module→git_branchless_invoke.CommandContext
- Direction
- git_branchless_submit uses git_branchless_invoke, so a change to git_branchless_invoke can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_invoke.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→15 git_branchless_submit uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_submit.git_branchless_submit$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_submit uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→18 git_branchless_submit uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_submit.git_branchless_submit$module→git_branchless_lib.core.eventlog.EventLogDb
- Direction
- git_branchless_submit uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→20 git_branchless_submit uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_submit uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_submit.git_branchless_submit$module→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_submit uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
36→30 git_branchless_submit uses git_branchless_opts✕
- Connections
- 6 pairs of types, where a type in git_branchless_submit uses a type in git_branchless_opts.
- The types involved
git_branchless_submit.SubmitOptions→git_branchless_opts.TestExecutionStrategygit_branchless_submit.git_branchless_submit$module→git_branchless_opts.ForgeKindgit_branchless_submit.git_branchless_submit$module→git_branchless_opts.ResolveRevsetOptionsgit_branchless_submit.git_branchless_submit$module→git_branchless_opts.Revsetgit_branchless_submit.git_branchless_submit$module→git_branchless_opts.SubmitArgsgit_branchless_submit.git_branchless_submit$module→git_branchless_opts.TestExecutionStrategy
- Direction
- git_branchless_submit uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless_submit, while a change to git_branchless_submit can't break git_branchless_opts.
- Position
- Below the diagonal: git_branchless_submit uses a module listed above it, which is the healthy direction.
37→3 git_branchless_submit.branch_forge uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.branch_forge uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_submit.branch_forge.BranchForge→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_submit.branch_forge uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_submit.branch_forge, while a change to git_branchless_submit.branch_forge can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_submit.branch_forge uses a module listed above it, which is the healthy direction.
37→4 git_branchless_submit.branch_forge uses git_branchless_lib.core.repo_ext✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.branch_forge uses a type in git_branchless_lib.core.repo_ext.
- The types involved
git_branchless_submit.branch_forge.BranchForge→git_branchless_lib.core.repo_ext.RepoReferencesSnapshot
- Direction
- git_branchless_submit.branch_forge uses git_branchless_lib.core.repo_ext, so a change to git_branchless_lib.core.repo_ext can break git_branchless_submit.branch_forge, while a change to git_branchless_submit.branch_forge can't break git_branchless_lib.core.repo_ext.
- Position
- Below the diagonal: git_branchless_submit.branch_forge uses a module listed above it, which is the healthy direction.
37→7 git_branchless_submit.branch_forge uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.branch_forge uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_submit.branch_forge.BranchForge→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_submit.branch_forge uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_submit.branch_forge, while a change to git_branchless_submit.branch_forge can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_submit.branch_forge uses a module listed above it, which is the healthy direction.
37→15 git_branchless_submit.branch_forge uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.branch_forge uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_submit.branch_forge.BranchForge→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_submit.branch_forge uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_submit.branch_forge, while a change to git_branchless_submit.branch_forge can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_submit.branch_forge uses a module listed above it, which is the healthy direction.
37→18 git_branchless_submit.branch_forge uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.branch_forge uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_submit.branch_forge.BranchForge→git_branchless_lib.core.eventlog.EventLogDb
- Direction
- git_branchless_submit.branch_forge uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_submit.branch_forge, while a change to git_branchless_submit.branch_forge can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_submit.branch_forge uses a module listed above it, which is the healthy direction.
37→20 git_branchless_submit.branch_forge uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.branch_forge uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_submit.branch_forge.BranchForge→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_submit.branch_forge uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_submit.branch_forge, while a change to git_branchless_submit.branch_forge can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_submit.branch_forge uses a module listed above it, which is the healthy direction.
37→36 git_branchless_submit.branch_forge uses git_branchless_submit✕
- Connections
- 2 pairs of types, where a type in git_branchless_submit.branch_forge uses a type in git_branchless_submit.
- The types involved
git_branchless_submit.branch_forge.BranchForge→git_branchless_submit.Forgegit_branchless_submit.branch_forge.BranchForge→git_branchless_submit.SubmitOptions
- Direction
- git_branchless_submit.branch_forge uses git_branchless_submit, so a change to git_branchless_submit can break git_branchless_submit.branch_forge, while a change to git_branchless_submit.branch_forge can't break git_branchless_submit.
- Position
- Below the diagonal: git_branchless_submit.branch_forge uses a module listed above it, which is the healthy direction.
38→2 git_branchless_submit.github uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_submit.github uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
38→3 git_branchless_submit.github uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_submit.github uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
38→4 git_branchless_submit.github uses git_branchless_lib.core.repo_ext✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github uses a type in git_branchless_lib.core.repo_ext.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_lib.core.repo_ext.RepoReferencesSnapshot
- Direction
- git_branchless_submit.github uses git_branchless_lib.core.repo_ext, so a change to git_branchless_lib.core.repo_ext can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_lib.core.repo_ext.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
38→7 git_branchless_submit.github uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_submit.github uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
38→15 git_branchless_submit.github uses git_branchless_lib.git.repo✕
- Connections
- 2 pairs of types, where a type in git_branchless_submit.github uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_lib.git.repo.Repogit_branchless_submit.github.github$module→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_submit.github uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
38→18 git_branchless_submit.github uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_lib.core.eventlog.EventLogDb
- Direction
- git_branchless_submit.github uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
38→20 git_branchless_submit.github uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_submit.github uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
38→36 git_branchless_submit.github uses git_branchless_submit✕
- Connections
- 2 pairs of types, where a type in git_branchless_submit.github uses a type in git_branchless_submit.
- The types involved
git_branchless_submit.github.GithubForge→git_branchless_submit.Forgegit_branchless_submit.github.GithubForge→git_branchless_submit.SubmitOptions
- Direction
- git_branchless_submit.github uses git_branchless_submit, so a change to git_branchless_submit can break git_branchless_submit.github, while a change to git_branchless_submit.github can't break git_branchless_submit.
- Position
- Below the diagonal: git_branchless_submit.github uses a module listed above it, which is the healthy direction.
39→2 git_branchless_submit.github.client uses git_branchless_lib.git.oid✕
- Connections
- 2 pairs of types, where a type in git_branchless_submit.github.client uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_submit.github.client.CreatePullRequestArgs→git_branchless_lib.git.oid.NonZeroOidgit_branchless_submit.github.client.UpdatePullRequestArgs→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_submit.github.client uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_submit.github.client, while a change to git_branchless_submit.github.client can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_submit.github.client uses a module listed above it, which is the healthy direction.
39→3 git_branchless_submit.github.client uses git_branchless_lib.core.effects✕
- Connections
- 3 pairs of types, where a type in git_branchless_submit.github.client uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_submit.github.client.GithubClient→git_branchless_lib.core.effects.Effectsgit_branchless_submit.github.client.MockGithubClient→git_branchless_lib.core.effects.Effectsgit_branchless_submit.github.client.RealGithubClient→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_submit.github.client uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_submit.github.client, while a change to git_branchless_submit.github.client can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_submit.github.client uses a module listed above it, which is the healthy direction.
39→7 git_branchless_submit.github.client uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github.client uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_submit.github.client.RealGithubClient→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_submit.github.client uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_submit.github.client, while a change to git_branchless_submit.github.client can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_submit.github.client uses a module listed above it, which is the healthy direction.
39→15 git_branchless_submit.github.client uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github.client uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_submit.github.client.MockState→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_submit.github.client uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_submit.github.client, while a change to git_branchless_submit.github.client can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_submit.github.client uses a module listed above it, which is the healthy direction.
39→17 git_branchless_submit.github.client uses git_branchless_lib.git.test✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.github.client uses a type in git_branchless_lib.git.test.
- The types involved
git_branchless_submit.github.client.PullRequestInfo→git_branchless_lib.git.test.SerializedNonZeroOid
- Direction
- git_branchless_submit.github.client uses git_branchless_lib.git.test, so a change to git_branchless_lib.git.test can break git_branchless_submit.github.client, while a change to git_branchless_submit.github.client can't break git_branchless_lib.git.test.
- Position
- Below the diagonal: git_branchless_submit.github.client uses a module listed above it, which is the healthy direction.
39→36 git_branchless_submit.github.client uses git_branchless_submit✕
- Connections
- 3 pairs of types, where a type in git_branchless_submit.github.client uses a type in git_branchless_submit.
- The types involved
git_branchless_submit.github.client.GithubClient→git_branchless_submit.SubmitOptionsgit_branchless_submit.github.client.MockGithubClient→git_branchless_submit.SubmitOptionsgit_branchless_submit.github.client.RealGithubClient→git_branchless_submit.SubmitOptions
- Direction
- git_branchless_submit.github.client uses git_branchless_submit, so a change to git_branchless_submit can break git_branchless_submit.github.client, while a change to git_branchless_submit.github.client can't break git_branchless_submit.
- Position
- Below the diagonal: git_branchless_submit.github.client uses a module listed above it, which is the healthy direction.
40→2 git_branchless_submit.phabricator uses git_branchless_lib.git.oid✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_lib.git.oid.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_lib.git.oid.NonZeroOid
- Direction
- git_branchless_submit.phabricator uses git_branchless_lib.git.oid, so a change to git_branchless_lib.git.oid can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_lib.git.oid.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
40→3 git_branchless_submit.phabricator uses git_branchless_lib.core.effects✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_lib.core.effects.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_lib.core.effects.Effects
- Direction
- git_branchless_submit.phabricator uses git_branchless_lib.core.effects, so a change to git_branchless_lib.core.effects can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_lib.core.effects.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
40→7 git_branchless_submit.phabricator uses git_branchless_lib.git.run✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_lib.git.run.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_lib.git.run.GitRunInfo
- Direction
- git_branchless_submit.phabricator uses git_branchless_lib.git.run, so a change to git_branchless_lib.git.run can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_lib.git.run.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
40→15 git_branchless_submit.phabricator uses git_branchless_lib.git.repo✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_lib.git.repo.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_lib.git.repo.Repo
- Direction
- git_branchless_submit.phabricator uses git_branchless_lib.git.repo, so a change to git_branchless_lib.git.repo can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_lib.git.repo.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
40→18 git_branchless_submit.phabricator uses git_branchless_lib.core.eventlog✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_lib.core.eventlog.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_lib.core.eventlog.EventLogDb
- Direction
- git_branchless_submit.phabricator uses git_branchless_lib.core.eventlog, so a change to git_branchless_lib.core.eventlog can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_lib.core.eventlog.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
40→20 git_branchless_submit.phabricator uses git_branchless_lib.core.dag✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_lib.core.dag.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_lib.core.dag.Dag
- Direction
- git_branchless_submit.phabricator uses git_branchless_lib.core.dag, so a change to git_branchless_lib.core.dag can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_lib.core.dag.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
40→30 git_branchless_submit.phabricator uses git_branchless_opts✕
- Connections
- 1 pair of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_opts.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_opts.Revset
- Direction
- git_branchless_submit.phabricator uses git_branchless_opts, so a change to git_branchless_opts can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_opts.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
40→36 git_branchless_submit.phabricator uses git_branchless_submit✕
- Connections
- 2 pairs of types, where a type in git_branchless_submit.phabricator uses a type in git_branchless_submit.
- The types involved
git_branchless_submit.phabricator.PhabricatorForge→git_branchless_submit.Forgegit_branchless_submit.phabricator.PhabricatorForge→git_branchless_submit.SubmitOptions
- Direction
- git_branchless_submit.phabricator uses git_branchless_submit, so a change to git_branchless_submit can break git_branchless_submit.phabricator, while a change to git_branchless_submit.phabricator can't break git_branchless_submit.
- Position
- Below the diagonal: git_branchless_submit.phabricator uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 39 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 31 | Medium |
| A02:2025 — Security Misconfiguration | 4 | Medium |
Roadmap
Begin by addressing the lack of Architectural Decision Records to ensure significant design choices are properly documented and traceable. Next, improve knowledge freshness by removing orphaned files, starting with lib.rs, testing.rs, and dag.rs, while also updating the README to clearly explain how to run the test suite. Finally, strengthen supply-chain security by resolving permission issues in the lint, linux, and macos workflow files.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +10.1 pts | Low | ADR Quality |
| Resolve the 35 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (2), testing.rs (2), dag.rs. | +8.6 pts | Medium | Knowledge Freshness |
| 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. | +8.4 pts | Medium | Architecture documentation |
| 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. | +4.9 pts | Medium | Documentation (README) |
| Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. | +1.4 pts | Low | Platform End-of-Life |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with execute.rs, github.rs, phabricator.rs. | +1.0 pts | Low | Knowledge Freshness |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| git-branchless/src/commands/split.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| git-branchless-lib/src/core/rewrite/execute.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| git-branchless-lib/src/git/diff.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| git-branchless-test/src/lib.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| git-branchless-lib/src/core/rewrite/plan.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| git-branchless/src/commands/amend.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| git-branchless-submit/src/phabricator.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| git-branchless-record/src/lib.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| git-branchless-undo/src/lib.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| git-branchless-submit/src/github.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 51 of 51 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 51 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, 331 of 369 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog 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: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (44 contributor(s) across 2052 commit(s) sampled, automation and bot accounts excluded). One of them holds 85% of the history; the other 43 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gitpod/workspace-full 2 | 3 | # The following environment variables are necessary for `cargo test` to pass. -------------------- ERROR: failed to solve: failed to register layer: write /home/gitpod/.sdkman/candidates/java/11.0.28.fx-zulu/lib/libjfxwebkit.so: no space left on device; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust 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.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog 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 Rust 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
24 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was git_branchless_move::r#move at 57. A further 2 function(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 OperationType::fmt at 30 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: git-branchless-lib/src/core/effects.rs (OperationType::fmt at 30), git-branchless-lib/src/core/formatting.rs (git_branchless_lib::core::formatting::render_style_as_ansi at 27). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with git_branchless_move::r#move (cyclomatic 57), git_branchless::commands::split::split (cyclomatic 48), git_branchless::commands::command_main (cyclomatic 35). — 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 4 together lifts Cyclomatic Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
37 function(s) exceeded the cognitive complexity threshold of 15; the worst was git_branchless_move::r#move at 106.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with git_branchless_move::r#move (cognitive 106). — Refactoring it lifts Cognitive Complexity from 4.5 to about 5.5/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
63 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 34 FunctionTooLong finding(s) in God Classes — start with lib.rs (24), execute.rs (2), split.rs. — One of this dimension's main actionable groups (34 warning-level).
- Resolve the 15 FileTooLong finding(s) in God Classes — start with lib.rs (6), repo.rs, plan.rs. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 7 MethodTooLong finding(s) in God Classes — start with phabricator.rs (2), github.rs (2), lib.rs. — One of this dimension's main actionable groups (7 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
47 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 8 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with lib.rs (3), effects.rs, untracked_file_cache.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 4 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with lib.rs (2), worktree.rs, restack.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with lib.rs (2), effects.rs, diff.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
17 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 13 of the 17 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Unstable project git-branchless-submit finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 49 classes have LCOM4 above 3.
D9 · Test Distribution
438 test methods: 40 unit, 398 integration, 0 BDD, 0 e2e. The Rust suite contributes 438 `#[test]` function(s) across 51 file(s) declaring at least one; its unit/integration split is Cargo's own — 36 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
What to do
- Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 51 test files): measured (0 flaky).
D12 · Dependency Hygiene
22 outdated, 0 yanked direct Cargo dependencies. 50 of 51 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 470 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
45 deducted task-comment markers across 36450 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 37 FixmeComment finding(s) in Explicit Debt — start with lib.rs (8), plan.rs (5), execute.rs (4). — One of this dimension's main actionable groups (37 warning-level).
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with basic.rs, phabricator.rs, formatting.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 HackComment finding(s) in Explicit Debt — start with parser.rs, execute.rs, plan.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 16 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
39 finding(s): 0 critical, 29 high, 10 medium, 0 low. 26 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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 26 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 (26 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
18 finding(s): 0 critical, 0 high, 18 medium, 0 low.
What to do
- Resolve the 8 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 4 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 0 high, 1 medium, 3 low.
What to do
- Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
38 of 70 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is git-branchless-lib/src/core/rewrite/execute.rs. Counted over 70 of the 86 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 35 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (2), testing.rs (2), dag.rs. — One of this dimension's main actionable groups (35 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with execute.rs, github.rs, phabricator.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: restack.rs↔sync.rs 55%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with restack.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
DM5 · Encapsulated state
M1 · Documentation (README)
- 28 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 15 of 17 project(s) that lack one — worth up to 1.8 pts.
- Review the README against recent changes; refresh the parts that drifted.
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
- 170/234 types (73%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 690 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-branchless-reword/src/lib.rs:690
- `info!` at line 125 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-branchless-invoke/src/lib.rs:125
- `warn!` at line 129 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-branchless-invoke/src/lib.rs:129
- `warn!` at line 95 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — git-branchless-hook/src/lib.rs:95
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 79% | Strong | Solid. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 53% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 75% | Strong | Solid. |
| Security | 66% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gitpod/workspace-full 2 | 3 | # The following environment variables are necessary for `cargo test` to pass. -------------------- ERROR: failed to solve: failed to register layer: write /home/gitpod/.sdkman/candidates/java/11.0.28.fx-zulu/lib/libjfxwebkit.so: no space left on device; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~23530 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 included — suite not readable by the collector
- DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner 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 4 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 82 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- 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.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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.
- 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 — 29 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
- REDACTED
- REDACTED
- REDACTED
Serious — 262 finding(s)
- FixmeComment scm-bisect/src/search.rs:232
- FixmeComment scm-bisect/src/search.rs:249
- FixmeComment git-branchless-undo/src/lib.rs:71
- FixmeComment git-branchless-test/src/lib.rs:1064
- FixmeComment git-branchless-test/src/lib.rs:2130
- FixmeComment git-branchless-test/src/lib.rs:2776
- FixmeComment git-branchless-submit/src/branch_forge.rs:211
- FixmeComment git-branchless-submit/src/github.rs:321
- FixmeComment git-branchless-submit/src/github.rs:829
- FixmeComment git-branchless-submit/src/phabricator.rs:863
- FixmeComment git-branchless-submit/src/phabricator.rs:912
- FixmeComment git-branchless-record/src/lib.rs:141
- FixmeComment git-branchless-opts/src/lib.rs:470
- FixmeComment git-branchless-lib/tests/test_rewrite_plan.rs:448
- FixmeComment git-branchless-lib/src/git/diff.rs:248
- FixmeComment git-branchless-lib/src/git/reference.rs:139
- FixmeComment git-branchless-lib/src/core/check_out.rs:280
- FixmeComment git-branchless-lib/src/core/dag.rs:684
- FixmeComment git-branchless-lib/src/core/dag.rs:736
- FixmeComment git-branchless-lib/src/core/rewrite/execute.rs:296
- FixmeComment git-branchless-lib/src/core/rewrite/execute.rs:632
- FixmeComment git-branchless-lib/src/core/rewrite/execute.rs:666
- FixmeComment git-branchless-lib/src/core/rewrite/execute.rs:1315
- FixmeComment git-branchless-lib/src/core/rewrite/plan.rs:169
- FixmeComment git-branchless-lib/src/core/rewrite/plan.rs:427
- FunctionTooLong: git_branchless::commands::split::split git-branchless/src/commands/split.rs:48
- FunctionTooLong: git_branchless_move::r#move git-branchless-move/src/lib.rs:67
- FunctionTooLong: git_branchless_lib::core::rewrite::execute::in_memory::rebase_in_memory git-branchless-lib/src/core/rewrite/execute.rs:461
- FunctionTooLong: git_branchless::commands::amend::amend git-branchless/src/commands/amend.rs:38
- FunctionTooLong: git_branchless_lib::git::diff::process_diff_for_record git-branchless-lib/src/git/diff.rs:80
- FunctionTooLong: git_branchless_submit::submit git-branchless-submit/src/lib.rs:214
- FunctionTooLong: git_branchless_undo::describe_event git-branchless-undo/src/lib.rs:112
- FunctionTooLong: git_branchless_test::apply_fixes git-branchless-test/src/lib.rs:1935
- FunctionTooLong: git_branchless_reword::reword git-branchless-reword/src/lib.rs:86
- FunctionTooLong: git_branchless::commands::command_main git-branchless/src/commands/mod.rs:25
- FunctionTooLong: git_branchless_test::run_tests_inner git-branchless-test/src/lib.rs:1275
- FunctionTooLong: git_branchless_test::print_summary git-branchless-test/src/lib.rs:1733
- FunctionTooLong: git_branchless_record::create_commit_with_changes git-branchless-record/src/lib.rs:243
- FunctionTooLong: git_branchless_lib::core::untracked_file_cache::process_untracked_files git-branchless-lib/src/core/untracked_file_cache.rs:40
- FunctionTooLong: git_branchless_test::test_commit git-branchless-test/src/lib.rs:2644
- FunctionTooLong: git_branchless_undo::select_past_event git-branchless-undo/src/lib.rs:431
- FunctionTooLong: git_branchless_navigation::advance git-branchless-navigation/src/lib.rs:90
- FunctionTooLong: git_branchless_smartlog::render::get_child_output git-branchless-smartlog/src/lib.rs:452
- FunctionTooLong: git_branchless_smartlog::smartlog git-branchless-smartlog/src/lib.rs:765
- FunctionTooLong: git_branchless_test::event_loop git-branchless-test/src/lib.rs:1529
- FunctionTooLong: git_branchless::commands::sync::execute_main_branch_sync_plan git-branchless/src/commands/sync.rs:140
- FunctionTooLong: git_branchless_reword::prepare_messages git-branchless-reword/src/lib.rs:431
- FunctionTooLong: git_branchless_record::record_interactive git-branchless-record/src/lib.rs:563
- FunctionTooLong: git_branchless_lib::git::tree::get_changed_paths_between_trees_internal git-branchless-lib/src/git/tree.rs:164
- FunctionTooLong: git_branchless_undo::undo_events git-branchless-undo/src/lib.rs:788
- FileTooLong: src/lib.rs git-branchless-test/src/lib.rs
- FileTooLong: git/repo.rs git-branchless-lib/src/git/repo.rs
- FileTooLong: rewrite/plan.rs git-branchless-lib/src/core/rewrite/plan.rs
- FileTooLong: src/github.rs git-branchless-submit/src/github.rs
- FileTooLong: rewrite/execute.rs git-branchless-lib/src/core/rewrite/execute.rs
- FileTooLong: core/eventlog.rs git-branchless-lib/src/core/eventlog.rs
- FileTooLong: src/phabricator.rs git-branchless-submit/src/phabricator.rs
- FileTooLong: src/lib.rs git-branchless-undo/src/lib.rs
- FileTooLong: src/lib.rs git-branchless-record/src/lib.rs
- FileTooLong: src/lib.rs git-branchless-smartlog/src/lib.rs
- FileTooLong: src/testing.rs git-branchless-lib/src/testing.rs
- FileTooLong: core/effects.rs git-branchless-lib/src/core/effects.rs
- FileTooLong: src/builtins.rs git-branchless-revset/src/builtins.rs
- FileTooLong: src/lib.rs git-branchless-reword/src/lib.rs
- FileTooLong: src/lib.rs git-branchless-init/src/lib.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) git-branchless-lib/src/core/effects.rs:642
- Duplicated block (11 lines × 2) git-branchless-lib/src/core/untracked_file_cache.rs:68
- Duplicated block (11 lines × 2) git-branchless-lib/src/git/run.rs:164
- Duplicated block (11 lines × 2) git-branchless-move/src/lib.rs:312
- Duplicated block (11 lines × 2) git-branchless-submit/src/phabricator.rs:735
- Duplicated block (11 lines × 2) git-branchless/src/commands/hide.rs:49
- Duplicated block (11 lines × 2) git-branchless-undo/src/lib.rs:328
- Duplicated block (11 lines × 2) git-branchless-submit/src/lib.rs:421
- git_branchless_lib::core::rewrite::execute::move_branches (cognitive 59) git-branchless-lib/src/core/rewrite/execute.rs:27
- git_branchless_lib::core::rewrite::execute::in_memory::rebase_in_memory (cognitive 58) git-branchless-lib/src/core/rewrite/execute.rs:461
- git_branchless_lib::git::diff::process_diff_for_record (cognitive 58) git-branchless-lib/src/git/diff.rs:80
- git_branchless_lib::core::untracked_file_cache::process_untracked_files (cognitive 29) git-branchless-lib/src/core/untracked_file_cache.rs:40
- git_branchless_lib::core::check_out::check_out_commit (cognitive 17) git-branchless-lib/src/core/check_out.rs:112
- git_branchless_lib::core::rewrite::execute::execute_rebase_plan (cognitive 17) git-branchless-lib/src/core/rewrite/execute.rs:1259
- git_branchless_lib::testing::pty::run_in_pty (cognitive 17) git-branchless-lib/src/testing.rs:983
- MethodTooLong: PhabricatorForge.create git-branchless-submit/src/phabricator.rs:321
- MethodTooLong: ResolvedTestOptions.resolve git-branchless-test/src/lib.rs:221
- MethodTooLong: RebasePlanBuilder.make_rebase_plan_for_current_commit git-branchless-lib/src/core/rewrite/plan.rs:755
- MethodTooLong: GithubForge.create git-branchless-submit/src/github.rs:196
- MethodTooLong: PhabricatorForge.update git-branchless-submit/src/phabricator.rs:571
- MethodTooLong: GithubForge.make_updated_pull_request_info git-branchless-submit/src/github.rs:519
- MethodTooLong: BranchForge.query_status git-branchless-submit/src/branch_forge.rs:32
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment scm-bisect/src/basic.rs:157
- TodoComment git-branchless-submit/src/phabricator.rs:123
- TodoComment git-branchless-lib/src/core/formatting.rs:250
- TodoComment git-branchless/src/commands/amend.rs:356
- TodoComment git-branchless/src/commands/split.rs:389
- git_branchless_test::event_loop (cognitive 40) git-branchless-test/src/lib.rs:1529
- git_branchless_test::print_summary (cognitive 29) git-branchless-test/src/lib.rs:1733
- git_branchless_test::run_tests_inner (cognitive 23) git-branchless-test/src/lib.rs:1275
- git_branchless_test::prepare_working_directory (cognitive 17) git-branchless-test/src/lib.rs:2524
- git_branchless_test::apply_fixes (cognitive 16) git-branchless-test/src/lib.rs:1935
- git_branchless_lib::core::rewrite::execute::in_memory::rebase_in_memory (cyclomatic 31) git-branchless-lib/src/core/rewrite/execute.rs:461
- git_branchless_lib::git::diff::process_diff_for_record (cyclomatic 30) git-branchless-lib/src/git/diff.rs:80
- git_branchless_lib::core::untracked_file_cache::process_untracked_files (cyclomatic 19) git-branchless-lib/src/core/untracked_file_cache.rs:40
- git_branchless_lib::core::rewrite::execute::move_branches (cyclomatic 17) git-branchless-lib/src/core/rewrite/execute.rs:27
- git_branchless_test::event_loop (cyclomatic 24) git-branchless-test/src/lib.rs:1529
- git_branchless_test::run_tests_inner (cyclomatic 21) git-branchless-test/src/lib.rs:1275
- git_branchless_test::print_summary (cyclomatic 18) git-branchless-test/src/lib.rs:1733
- git_branchless_test::apply_fixes (cyclomatic 16) git-branchless-test/src/lib.rs:1935
- ClassTooLong: Repo git-branchless-lib/src/git/repo.rs:466
- ClassTooLong: PhabricatorForge git-branchless-submit/src/phabricator.rs:233
- ClassTooLong: RebasePlanBuilder git-branchless-lib/src/core/rewrite/plan.rs:562
- ClassTooLong: GithubForge git-branchless-submit/src/github.rs:110
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (17 lines × 2) git-branchless-lib/src/core/worktree.rs:232
- Duplicated block (17 lines × 2) git-branchless-test/src/lib.rs:1839
- Duplicated block (17 lines × 2) git-branchless-test/src/lib.rs:2858
- Duplicated block (17 lines × 2) git-branchless/src/commands/restack.rs:329
- Duplicated block (12 lines × 2) git-branchless-lib/src/core/effects.rs:179
- Duplicated block (12 lines × 2) git-branchless-lib/src/git/diff.rs:357
- Duplicated block (12 lines × 2) git-branchless-undo/src/lib.rs:339
- Duplicated block (12 lines × 2) git-branchless-reword/src/lib.rs:208
- git_branchless::commands::split::split (cyclomatic 48) git-branchless/src/commands/split.rs:48
- git_branchless::commands::command_main (cyclomatic 35) git-branchless/src/commands/mod.rs:25
- git_branchless::commands::amend::amend (cyclomatic 20) git-branchless/src/commands/amend.rs:38
- git_branchless_smartlog::render::get_child_output (cyclomatic 23) git-branchless-smartlog/src/lib.rs:452
- git_branchless_smartlog::graph::build_graph (cyclomatic 22) git-branchless-smartlog/src/lib.rs:160
- git_branchless_smartlog::smartlog (cyclomatic 20) git-branchless-smartlog/src/lib.rs:765
- HackComment git-branchless-revset/src/parser.rs:23
- HackComment git-branchless-lib/src/core/rewrite/execute.rs:84
- HackComment git-branchless-lib/src/core/rewrite/plan.rs:476
- git_branchless::commands::split::split (cognitive 57) git-branchless/src/commands/split.rs:48
- git_branchless::commands::amend::amend (cognitive 23) git-branchless/src/commands/amend.rs:38
- git_branchless::commands::hide::hide (cognitive 16) git-branchless/src/commands/hide.rs:24
- git_branchless_smartlog::graph::build_graph (cognitive 43) git-branchless-smartlog/src/lib.rs:160
- git_branchless_smartlog::render::get_child_output (cognitive 31) git-branchless-smartlog/src/lib.rs:452
- git_branchless_smartlog::smartlog (cognitive 29) git-branchless-smartlog/src/lib.rs:765
- PhabricatorForge::create (cognitive 17) git-branchless-submit/src/phabricator.rs:321
- PhabricatorForge::query_status (cognitive 16) git-branchless-submit/src/phabricator.rs:244
- PhabricatorForge::update_dependencies (cognitive 16) git-branchless-submit/src/phabricator.rs:884
- TooManyMethods: Repo git-branchless-lib/src/git/repo.rs:466
- TooManyMethods: Dag git-branchless-lib/src/core/dag.rs:132
- TooManyMethods: Git git-branchless-lib/src/testing.rs:69
- Duplicated block (13 lines × 2) git-branchless-undo/src/lib.rs:182
- Duplicated block (13 lines × 2) git-branchless-undo/src/lib.rs:238
- Duplicated block (13 lines × 2) git-branchless-undo/src/lib.rs:161
- Duplicated block (10 lines × 2) git-branchless-lib/src/git/object.rs:174
- Duplicated block (10 lines × 2) git-branchless-submit/src/phabricator.rs:747
- Duplicated block (10 lines × 2) git-branchless/src/commands/hide.rs:61
- Off the main sequence: git-branchless-opts
- Off the main sequence: git-branchless-lib
- Off the main sequence: git-branchless-invoke
- git_branchless_navigation::advance (cyclomatic 23) git-branchless-navigation/src/lib.rs:90
- git_branchless_navigation::traverse_commits (cyclomatic 16) git-branchless-navigation/src/lib.rs:313
- GithubForge::create (cognitive 25) git-branchless-submit/src/github.rs:196
- GithubForge::make_updated_pull_request_info (cognitive 20) git-branchless-submit/src/github.rs:519
- git_branchless_undo::select_past_event (cognitive 16) git-branchless-undo/src/lib.rs:431
- git_branchless_undo::undo_events (cognitive 16) git-branchless-undo/src/lib.rs:788
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2) git-branchless/src/commands/hide.rs:199
- Duplicated block (18 lines × 2) scm-bisect/src/basic.rs:52
- Duplicated block (14 lines × 2) git-branchless-record/src/lib.rs:427
- Duplicated block (14 lines × 2) scm-bisect/src/search.rs:427
- Duplicated block (8 lines × 3) git-branchless-lib/src/git/run.rs:137
- Duplicated block (8 lines × 3) git-branchless/src/commands/hide.rs:49
- Duplicated block (8 lines × 2) git-branchless-move/src/lib.rs:116
- Duplicated block (8 lines × 2) git-branchless-lib/src/git/repo.rs:1428
- git_branchless_move::r#move (cyclomatic 57) git-branchless-move/src/lib.rs:67
- ResolvedTestOptions::resolve (cyclomatic 28) git-branchless-test/src/lib.rs:221
- RebasePlanBuilder::make_rebase_plan_for_current_commit (cyclomatic 21) git-branchless-lib/src/core/rewrite/plan.rs:755
- git_branchless_reword::reword (cyclomatic 18) git-branchless-reword/src/lib.rs:86
- PhabricatorForge::create (cyclomatic 18) git-branchless-submit/src/phabricator.rs:321
- TestStatus::describe (cyclomatic 17) git-branchless-test/src/lib.rs:911
- git_branchless_record::create_commit_with_changes (cyclomatic 17) git-branchless-record/src/lib.rs:243
- git_branchless_undo::select_past_event (cyclomatic 16) git-branchless-undo/src/lib.rs:431
- git_branchless_move::r#move (cognitive 106) git-branchless-move/src/lib.rs:67
- RebasePlanBuilder::make_rebase_plan_for_current_commit (cognitive 42) git-branchless-lib/src/core/rewrite/plan.rs:755
- git_branchless_navigation::advance (cognitive 41) git-branchless-navigation/src/lib.rs:90
- ResolvedTestOptions::resolve (cognitive 39) git-branchless-test/src/lib.rs:221
- git_branchless_record::create_commit_with_changes (cognitive 26) git-branchless-record/src/lib.rs:243
- git_branchless_reword::prepare_messages (cognitive 22) git-branchless-reword/src/lib.rs:431
- BranchForge::query_status (cognitive 22) git-branchless-submit/src/branch_forge.rs:32
- TestStatus::describe (cognitive 22) git-branchless-test/src/lib.rs:911
- ConstraintGraph::add_constraints (cognitive 19) git-branchless-lib/src/core/rewrite/plan.rs:261
- Search::search (cognitive 19) scm-bisect/src/search.rs:268
- EventReplayer::process_event (cognitive 18) git-branchless-lib/src/core/eventlog.rs:846
- Repo::cherry_pick_fast (cognitive 17) git-branchless-lib/src/git/repo.rs:1374
- REDACTED
- Change coupling: restack.rs ↔ sync.rs git-branchless/src/commands/restack.rs:1
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) git-branchless-move/src/lib.rs:79
- Duplicated block (35 lines × 2) git-branchless-lib/src/core/worktree.rs:195
- Duplicated block (28 lines × 2) git-branchless-lib/src/core/effects.rs:147
- Duplicated block (23 lines × 2) git-branchless-submit/src/phabricator.rs:346
- Duplicated block (14–15 lines × 2) git-branchless-test/src/lib.rs:611
- Duplicated block (11–14 lines × 5) git-branchless-query/src/lib.rs:52
- Duplicated block (12–14 lines × 5) git-branchless-reword/src/lib.rs:95
- Duplicated block (13 lines × 3) git-branchless-revset/src/builtins.rs:677
- Duplicated block (12 lines × 6) git-branchless-move/src/lib.rs:103
- Duplicated block (10–12 lines × 6) git-branchless-query/src/lib.rs:51
- Duplicated block (10 lines × 3) git-branchless-record/src/lib.rs:402
- Duplicated block (9 lines × 2) git-branchless-lib/src/git/repo.rs:1234
- Duplicated block (7 lines × 3) git-branchless-move/src/lib.rs:117
- Duplicated block (7 lines × 2) git-branchless-lib/src/git/tree.rs:171
- Duplicated block (6–7 lines × 2) git-branchless-navigation/src/lib.rs:358
- Duplicated block (6 lines × 2) git-branchless-test/src/lib.rs:2377
- Duplicated block (5 lines × 5) git-branchless-query/src/lib.rs:48
- Duplicated block (5 lines × 2) git-branchless-test/src/lib.rs:589
- End-of-life runtime: Rust 1.86 rust-toolchain.toml:1
- Unstable project git-branchless-submit
- README may be stale
Minor — 56 finding(s)
- Orphaned file git-branchless-lib/src/core/dag.rs:1
- Orphaned file git-branchless-init/src/lib.rs:1
- Orphaned file scm-bisect/src/basic.rs:1
- Orphaned file git-branchless-lib/src/git/tree.rs:1
- Orphaned file git-branchless-lib/src/core/rewrite/rewrite_hooks.rs:1
- Orphaned file scm-bisect/src/search.rs:1
- Orphaned file git-branchless-lib/src/git/run.rs:1
- Orphaned file git-branchless-lib/src/git/reference.rs:1
- Orphaned file git-branchless-lib/src/core/check_out.rs:1
- Orphaned file git-branchless-submit/src/branch_forge.rs:1
- Orphaned file git-branchless-lib/src/core/worktree.rs:1
- Orphaned file git-branchless-lib/src/git/config.rs:1
- Orphaned file git-branchless-lib/src/git/object.rs:1
- Orphaned file git-branchless/src/commands/bug_report.rs:1
- Orphaned file git-branchless-revset/src/pattern.rs:1
- Orphaned file git-branchless/src/commands/hide.rs:1
- Orphaned file git-branchless-lib/src/git/oid.rs:1
- Orphaned file git-branchless-lib/src/core/repo_ext.rs:1
- Orphaned file git-branchless-navigation/src/prompt.rs:1
- Orphaned file git-branchless-reword/src/dialoguer_edit.rs:1
- Orphaned file git-branchless-lib/src/git/index.rs:1
- Orphaned file git-branchless-test/src/worker.rs:1
- Orphaned file git-branchless-lib/src/core/gc.rs:1
- Orphaned file git-branchless/src/commands/repair.rs:1
- Orphaned file git-branchless-lib/src/core/task.rs:1
- Interpolated log message defeats structured logging git-branchless-reword/src/lib.rs:690
- Interpolated log message defeats structured logging git-branchless-invoke/src/lib.rs:125
- Interpolated log message defeats structured logging git-branchless-invoke/src/lib.rs:129
- Interpolated log message defeats structured logging git-branchless-hook/src/lib.rs:95
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file git-branchless-lib/src/core/rewrite/execute.rs:1
- Most significant orphaned file git-branchless-submit/src/github.rs:1
- Most significant orphaned file git-branchless-submit/src/phabricator.rs:1
- No ADRs found
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- Large public API surface
- Silent fallback default on Err git-branchless/src/commands/sync.rs:278
Minor — 22 finding(s)
- Outdated: anyhow
- Outdated: async-trait
- Outdated: bstr
- Outdated: chrono
- Outdated: clap
- Outdated: clap_mangen
- Outdated: console
- Outdated: crossbeam
- Outdated: cursive_core
- Outdated: eyre
- Outdated: futures
- Outdated: glob
- Outdated: indexmap
- Outdated: indicatif
- Outdated: lalrpop
- Outdated: lalrpop-util
- Outdated: lazy_static
- Outdated: regex
- Outdated: serde
- Outdated: serde_json
- Outdated: textwrap
- Outdated: thiserror
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-841f58ceca1b411bab487a7637374e3f/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-841f58ceca1b411bab487a7637374e3f/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/watchdog-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 . | 39 | 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 . | 18 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 |