Executive summary
InSyncWithFoo/ryecharm falls short of our standard for a preview release because we found no recorded design decisions and no architecture document or diagram. It scores 61.4 out of 100 and is rated Adequate, and 46 of its 56 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 54.4, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5.8 points. Fixing the seven pipeline jobs with more access than they need comes next, worth about 2.8 points. Raising Maturity to 62 would lift the score to about 64.1.
Forty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The ten pages or frames without a title need a descriptive title.
The product code is 11,720 lines, about €15,000 to rebuild. Three of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
If Maturity rose from 54.4 to 62, the lowest score rated Strong, the score would rise from 61.4 to about 64.1.
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,100 to €26,000, for 86 to 272 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,720 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 ryecharm | 2 ryecharm.Command | 3 ryecharm.DocumentationURI | 4 ryecharm.DocumentationURIHost | 5 ryecharm.RootDisposable | 6 ryecharm.ShowCommandOutputAction | 7 ryecharm.TOMLPath | 8 ryecharm.common.logging | 9 ryecharm.configurations.ruff | 10 ryecharm.configurations.ty | 11 ryecharm.configurations.uv | 12 ryecharm.ruff | 13 ryecharm.rye.commands | 14 ryecharm.ty | 15 ryecharm.ty.commands | 16 ryecharm.uv.commands | 17 ryecharm.common.logging.ConsoleHolderKind | 18 ryecharm.configurations | 19 ryecharm.configurations.ruff.LogLevel | 20 ryecharm.configurations.ruff.RuffLocalService | 21 ryecharm.others.installers | 22 ryecharm.ruff.commands | 23 ryecharm.ruff.documentation.targets | 24 ryecharm.ruff.formatting | 25 ryecharm.ruff.onsave | 26 ryecharm.rye.actions | 27 ryecharm.ty.actions | 28 ryecharm.ty.lsp | 29 ryecharm.uv.actions | 30 ryecharm.uv.intentions | 31 ryecharm.configurations.main | 32 ryecharm.configurations.rye | 33 ryecharm.others.installers.InstallDependencies | 34 ryecharm.ruff.actions | 35 ryecharm.ruff.documentation | 36 ryecharm.ruff.linting | 37 ryecharm.uv.inlayhints.dependencyversions.settings | 38 ryecharm.configurations.main.MainLocalService | 39 ryecharm.configurations.main.MainOverrideService | 40 ryecharm.uv.inlayhints.dependencyversions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ryecharm | ||||||||||||||||||||||||||||||||||||||||
| 2 ryecharm.Command | 1 | |||||||||||||||||||||||||||||||||||||||
| 3 ryecharm.DocumentationURI | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 ryecharm.DocumentationURIHost | 3 | |||||||||||||||||||||||||||||||||||||||
| 5 ryecharm.RootDisposable | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 ryecharm.ShowCommandOutputAction | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 ryecharm.TOMLPath | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 ryecharm.common.logging | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 ryecharm.configurations.ruff | 4 | 10 | ||||||||||||||||||||||||||||||||||||||
| 10 ryecharm.configurations.ty | 3 | 11 | ||||||||||||||||||||||||||||||||||||||
| 11 ryecharm.configurations.uv | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 12 ryecharm.ruff | 4 | |||||||||||||||||||||||||||||||||||||||
| 13 ryecharm.rye.commands | 6 | |||||||||||||||||||||||||||||||||||||||
| 14 ryecharm.ty | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 ryecharm.ty.commands | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 ryecharm.uv.commands | 19 | |||||||||||||||||||||||||||||||||||||||
| 17 ryecharm.common.logging.ConsoleHolderKind | 4 | |||||||||||||||||||||||||||||||||||||||
| 18 ryecharm.configurations | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 ryecharm.configurations.ruff.LogLevel | 5 | |||||||||||||||||||||||||||||||||||||||
| 20 ryecharm.configurations.ruff.RuffLocalService | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 ryecharm.others.installers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 ryecharm.ruff.commands | 16 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 ryecharm.ruff.documentation.targets | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 ryecharm.ruff.formatting | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 ryecharm.ruff.onsave | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 ryecharm.rye.actions | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 ryecharm.ty.actions | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 ryecharm.ty.lsp | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 ryecharm.uv.actions | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 ryecharm.uv.intentions | 9 | 4 | ||||||||||||||||||||||||||||||||||||||
| 31 ryecharm.configurations.main | 10 | |||||||||||||||||||||||||||||||||||||||
| 32 ryecharm.configurations.rye | 10 | |||||||||||||||||||||||||||||||||||||||
| 33 ryecharm.others.installers.InstallDependencies | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 ryecharm.ruff.actions | 7 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 ryecharm.ruff.documentation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 ryecharm.ruff.linting | 5 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 ryecharm.uv.inlayhints.dependencyversions.settings | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 ryecharm.configurations.main.MainLocalService | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 ryecharm.configurations.main.MainOverrideService | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 ryecharm.uv.inlayhints.dependencyversions | 2 | 1 |
2→1 ryecharm.Command uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.Command uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.Command.Coroutine→insyncwithfoo.ryecharm.CoroutineService
- Direction
- ryecharm.Command uses ryecharm, so a change to ryecharm can break ryecharm.Command, while a change to ryecharm.Command can't break ryecharm.
- Position
- Below the diagonal: ryecharm.Command uses a module listed above it, which is the healthy direction.
3→1 ryecharm.DocumentationURI uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.DocumentationURI uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.DocumentationURI.Companion→insyncwithfoo.ryecharm.DocumentationURI
- Direction
- ryecharm.DocumentationURI uses ryecharm, so a change to ryecharm can break ryecharm.DocumentationURI, while a change to ryecharm.DocumentationURI can't break ryecharm.
- Position
- Below the diagonal: ryecharm.DocumentationURI uses a module listed above it, which is the healthy direction.
4→1 ryecharm.DocumentationURIHost uses ryecharm✕
- Connections
- 3 pairs of types, where a type in ryecharm.DocumentationURIHost uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.DocumentationURIHost.Companion→insyncwithfoo.ryecharm.DocumentationURIHostinsyncwithfoo.ryecharm.DocumentationURIHost.RUFF_OPTION→insyncwithfoo.ryecharm.DocumentationURIHostinsyncwithfoo.ryecharm.DocumentationURIHost.RUFF_RULE→insyncwithfoo.ryecharm.DocumentationURIHost
- Direction
- ryecharm.DocumentationURIHost uses ryecharm, so a change to ryecharm can break ryecharm.DocumentationURIHost, while a change to ryecharm.DocumentationURIHost can't break ryecharm.
- Position
- Below the diagonal: ryecharm.DocumentationURIHost uses a module listed above it, which is the healthy direction.
5→1 ryecharm.RootDisposable uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.RootDisposable uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.RootDisposable.Companion→insyncwithfoo.ryecharm.RootDisposable
- Direction
- ryecharm.RootDisposable uses ryecharm, so a change to ryecharm can break ryecharm.RootDisposable, while a change to ryecharm.RootDisposable can't break ryecharm.
- Position
- Below the diagonal: ryecharm.RootDisposable uses a module listed above it, which is the healthy direction.
6→1 ryecharm.ShowCommandOutputAction uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.ShowCommandOutputAction uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ShowCommandOutputAction.ActionCoroutine→insyncwithfoo.ryecharm.CoroutineService
- Direction
- ryecharm.ShowCommandOutputAction uses ryecharm, so a change to ryecharm can break ryecharm.ShowCommandOutputAction, while a change to ryecharm.ShowCommandOutputAction can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ShowCommandOutputAction uses a module listed above it, which is the healthy direction.
7→1 ryecharm.TOMLPath uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.TOMLPath uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.TOMLPath.Companion→insyncwithfoo.ryecharm.TOMLPath
- Direction
- ryecharm.TOMLPath uses ryecharm, so a change to ryecharm can break ryecharm.TOMLPath, while a change to ryecharm.TOMLPath can't break ryecharm.
- Position
- Below the diagonal: ryecharm.TOMLPath uses a module listed above it, which is the healthy direction.
8→1 ryecharm.common.logging uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.common.logging uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.common.logging.RyeCharmLoggerKt→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.common.logging uses ryecharm, so a change to ryecharm can break ryecharm.common.logging, while a change to ryecharm.common.logging can't break ryecharm.
- Position
- Below the diagonal: ryecharm.common.logging uses a module listed above it, which is the healthy direction.
9→1 ryecharm.configurations.ruff uses ryecharm✕
- Connections
- 4 pairs of types, where a type in ryecharm.configurations.ruff uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.configurations.ruff.LogLevel→insyncwithfoo.ryecharm.Labeledinsyncwithfoo.ryecharm.configurations.ruff.RunningMode→insyncwithfoo.ryecharm.Labeledinsyncwithfoo.ryecharm.configurations.ruff.TooltipFormat→insyncwithfoo.ryecharm.Labeledinsyncwithfoo.ryecharm.configurations.ruff.TooltipRuleFormat→insyncwithfoo.ryecharm.Labeled
- Direction
- ryecharm.configurations.ruff uses ryecharm, so a change to ryecharm can break ryecharm.configurations.ruff, while a change to ryecharm.configurations.ruff can't break ryecharm.
- Position
- Below the diagonal: ryecharm.configurations.ruff uses a module listed above it, which is the healthy direction.
9→18 ryecharm.configurations.ruff uses ryecharm.configurations part of a loop✕
- Connections
- 10 pairs of types, where a type in ryecharm.configurations.ruff uses a type in ryecharm.configurations.
- The types involved
insyncwithfoo.ryecharm.configurations.ruff.RuffConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.ruff.RuffConfigurations→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.ruff.RuffGlobalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.ruff.RuffLocalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.ruff.RuffOverrideService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.ruff.RuffOverrides→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.ruff.RuffOverrides→insyncwithfoo.ryecharm.configurations.ProjectOverrideStateinsyncwithfoo.ryecharm.configurations.ruff.RuffPanel→insyncwithfoo.ryecharm.configurations.AdaptivePanelinsyncwithfoo.ryecharm.configurations.ruff.RuffProjectConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.ruff.RuffProjectConfigurable→insyncwithfoo.ryecharm.configurations.ProjectBasedConfigurable
- Direction
- ryecharm.configurations.ruff uses ryecharm.configurations, so a change to ryecharm.configurations can break ryecharm.configurations.ruff, while a change to ryecharm.configurations.ruff can't break ryecharm.configurations.
- 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→1 ryecharm.configurations.ty uses ryecharm✕
- Connections
- 3 pairs of types, where a type in ryecharm.configurations.ty uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.configurations.ty.DiagnosticMode→insyncwithfoo.ryecharm.Labeledinsyncwithfoo.ryecharm.configurations.ty.LogLevel→insyncwithfoo.ryecharm.Labeledinsyncwithfoo.ryecharm.configurations.ty.RunningMode→insyncwithfoo.ryecharm.Labeled
- Direction
- ryecharm.configurations.ty uses ryecharm, so a change to ryecharm can break ryecharm.configurations.ty, while a change to ryecharm.configurations.ty can't break ryecharm.
- Position
- Below the diagonal: ryecharm.configurations.ty uses a module listed above it, which is the healthy direction.
10→18 ryecharm.configurations.ty uses ryecharm.configurations part of a loop✕
- Connections
- 11 pairs of types, where a type in ryecharm.configurations.ty uses a type in ryecharm.configurations.
- The types involved
insyncwithfoo.ryecharm.configurations.ty.TYConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.ty.TYConfigurations→insyncwithfoo.ryecharm.configurations.Copyableinsyncwithfoo.ryecharm.configurations.ty.TYConfigurations→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.ty.TYGlobalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.ty.TYLocalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.ty.TYOverrideService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.ty.TYOverrides→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.ty.TYOverrides→insyncwithfoo.ryecharm.configurations.ProjectOverrideStateinsyncwithfoo.ryecharm.configurations.ty.TYPanel→insyncwithfoo.ryecharm.configurations.AdaptivePanelinsyncwithfoo.ryecharm.configurations.ty.TYProjectConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.ty.TYProjectConfigurable→insyncwithfoo.ryecharm.configurations.ProjectBasedConfigurable
- Direction
- ryecharm.configurations.ty uses ryecharm.configurations, so a change to ryecharm.configurations can break ryecharm.configurations.ty, while a change to ryecharm.configurations.ty can't break ryecharm.configurations.
- 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→1 ryecharm.configurations.uv uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.configurations.uv uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.configurations.uv.UpdateMethod→insyncwithfoo.ryecharm.Labeled
- Direction
- ryecharm.configurations.uv uses ryecharm, so a change to ryecharm can break ryecharm.configurations.uv, while a change to ryecharm.configurations.uv can't break ryecharm.
- Position
- Below the diagonal: ryecharm.configurations.uv uses a module listed above it, which is the healthy direction.
11→18 ryecharm.configurations.uv uses ryecharm.configurations part of a loop✕
- Connections
- 10 pairs of types, where a type in ryecharm.configurations.uv uses a type in ryecharm.configurations.
- The types involved
insyncwithfoo.ryecharm.configurations.uv.UVConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.uv.UVConfigurations→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.uv.UVGlobalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.uv.UVLocalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.uv.UVOverrideService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.uv.UVOverrides→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.uv.UVOverrides→insyncwithfoo.ryecharm.configurations.ProjectOverrideStateinsyncwithfoo.ryecharm.configurations.uv.UVPanel→insyncwithfoo.ryecharm.configurations.AdaptivePanelinsyncwithfoo.ryecharm.configurations.uv.UVProjectConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.uv.UVProjectConfigurable→insyncwithfoo.ryecharm.configurations.ProjectBasedConfigurable
- Direction
- ryecharm.configurations.uv uses ryecharm.configurations, so a change to ryecharm.configurations can break ryecharm.configurations.uv, while a change to ryecharm.configurations.uv can't break ryecharm.configurations.
- 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→1 ryecharm.ruff uses ryecharm✕
- Connections
- 4 pairs of types, where a type in ryecharm.ruff uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.CodeAction→insyncwithfoo.ryecharm.Builderinsyncwithfoo.ryecharm.ruff.DisableRuleComment→insyncwithfoo.ryecharm.Builderinsyncwithfoo.ryecharm.ruff.FixViolation→insyncwithfoo.ryecharm.Builderinsyncwithfoo.ryecharm.ruff.Lint→insyncwithfoo.ryecharm.Builder
- Direction
- ryecharm.ruff uses ryecharm, so a change to ryecharm can break ryecharm.ruff, while a change to ryecharm.ruff can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff uses a module listed above it, which is the healthy direction.
13→1 ryecharm.rye.commands uses ryecharm✕
- Connections
- 6 pairs of types, where a type in ryecharm.rye.commands uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.rye.commands.ConfigCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.rye.commands.RecipeesKt→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.rye.commands.Rye→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.rye.commands.Rye→insyncwithfoo.ryecharm.CommandArgumentsinsyncwithfoo.ryecharm.rye.commands.Rye→insyncwithfoo.ryecharm.CommandFactoryinsyncwithfoo.ryecharm.rye.commands.ShowCommand→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.rye.commands uses ryecharm, so a change to ryecharm can break ryecharm.rye.commands, while a change to ryecharm.rye.commands can't break ryecharm.
- Position
- Below the diagonal: ryecharm.rye.commands uses a module listed above it, which is the healthy direction.
14→1 ryecharm.ty uses ryecharm✕
- Connections
- 2 pairs of types, where a type in ryecharm.ty uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ty.Completions→insyncwithfoo.ryecharm.Builderinsyncwithfoo.ryecharm.ty.InlayHints→insyncwithfoo.ryecharm.Builder
- Direction
- ryecharm.ty uses ryecharm, so a change to ryecharm can break ryecharm.ty, while a change to ryecharm.ty can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ty uses a module listed above it, which is the healthy direction.
15→1 ryecharm.ty.commands uses ryecharm✕
- Connections
- 4 pairs of types, where a type in ryecharm.ty.commands uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ty.commands.TY→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ty.commands.TY→insyncwithfoo.ryecharm.CommandArgumentsinsyncwithfoo.ryecharm.ty.commands.TY→insyncwithfoo.ryecharm.CommandFactoryinsyncwithfoo.ryecharm.ty.commands.VersionCommand→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.ty.commands uses ryecharm, so a change to ryecharm can break ryecharm.ty.commands, while a change to ryecharm.ty.commands can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ty.commands uses a module listed above it, which is the healthy direction.
16→1 ryecharm.uv.commands uses ryecharm✕
- Connections
- 19 pairs of types, where a type in ryecharm.uv.commands uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.uv.commands.AddCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.InitCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.InstallDependenciesCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.PipCompileCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.PipListCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.PipTreeCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.ProjectKind→insyncwithfoo.ryecharm.Labeledinsyncwithfoo.ryecharm.uv.commands.RecipeesKt→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.RemoveCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.SelfUpdateCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.SelfVersionCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.SyncCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.UV→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.UV→insyncwithfoo.ryecharm.CommandArgumentsinsyncwithfoo.ryecharm.uv.commands.UV→insyncwithfoo.ryecharm.CommandFactoryinsyncwithfoo.ryecharm.uv.commands.UpgradeCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.VenvCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.commands.VersionBumpType→insyncwithfoo.ryecharm.Labeledinsyncwithfoo.ryecharm.uv.commands.VersionCommand→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.uv.commands uses ryecharm, so a change to ryecharm can break ryecharm.uv.commands, while a change to ryecharm.uv.commands can't break ryecharm.
- Position
- Below the diagonal: ryecharm.uv.commands uses a module listed above it, which is the healthy direction.
17→8 ryecharm.common.logging.ConsoleHolderKind uses ryecharm.common.logging✕
- Connections
- 4 pairs of types, where a type in ryecharm.common.logging.ConsoleHolderKind uses a type in ryecharm.common.logging.
- The types involved
insyncwithfoo.ryecharm.common.logging.ConsoleHolderKind.RUFF→insyncwithfoo.ryecharm.common.logging.ConsoleHolderKindinsyncwithfoo.ryecharm.common.logging.ConsoleHolderKind.RYE→insyncwithfoo.ryecharm.common.logging.ConsoleHolderKindinsyncwithfoo.ryecharm.common.logging.ConsoleHolderKind.TY→insyncwithfoo.ryecharm.common.logging.ConsoleHolderKindinsyncwithfoo.ryecharm.common.logging.ConsoleHolderKind.UV→insyncwithfoo.ryecharm.common.logging.ConsoleHolderKind
- Direction
- ryecharm.common.logging.ConsoleHolderKind uses ryecharm.common.logging, so a change to ryecharm.common.logging can break ryecharm.common.logging.ConsoleHolderKind, while a change to ryecharm.common.logging.ConsoleHolderKind can't break ryecharm.common.logging.
- Position
- Below the diagonal: ryecharm.common.logging.ConsoleHolderKind uses a module listed above it, which is the healthy direction.
18→9 ryecharm.configurations uses ryecharm.configurations.ruff✕
- Connections
- 1 pair of types, where a type in ryecharm.configurations uses a type in ryecharm.configurations.ruff.
- The types involved
insyncwithfoo.ryecharm.configurations.InteractionsKt→insyncwithfoo.ryecharm.configurations.ruff.RuffConfigurations
- Direction
- ryecharm.configurations uses ryecharm.configurations.ruff, so a change to ryecharm.configurations.ruff can break ryecharm.configurations, while a change to ryecharm.configurations can't break ryecharm.configurations.ruff.
- Position
- Below the diagonal: ryecharm.configurations uses a module listed above it, which is the healthy direction.
18→10 ryecharm.configurations uses ryecharm.configurations.ty✕
- Connections
- 1 pair of types, where a type in ryecharm.configurations uses a type in ryecharm.configurations.ty.
- The types involved
insyncwithfoo.ryecharm.configurations.InteractionsKt→insyncwithfoo.ryecharm.configurations.ty.TYConfigurations
- Direction
- ryecharm.configurations uses ryecharm.configurations.ty, so a change to ryecharm.configurations.ty can break ryecharm.configurations, while a change to ryecharm.configurations can't break ryecharm.configurations.ty.
- Position
- Below the diagonal: ryecharm.configurations uses a module listed above it, which is the healthy direction.
18→11 ryecharm.configurations uses ryecharm.configurations.uv✕
- Connections
- 1 pair of types, where a type in ryecharm.configurations uses a type in ryecharm.configurations.uv.
- The types involved
insyncwithfoo.ryecharm.configurations.InteractionsKt→insyncwithfoo.ryecharm.configurations.uv.UVConfigurations
- Direction
- ryecharm.configurations uses ryecharm.configurations.uv, so a change to ryecharm.configurations.uv can break ryecharm.configurations, while a change to ryecharm.configurations can't break ryecharm.configurations.uv.
- Position
- Below the diagonal: ryecharm.configurations uses a module listed above it, which is the healthy direction.
19→9 ryecharm.configurations.ruff.LogLevel uses ryecharm.configurations.ruff✕
- Connections
- 5 pairs of types, where a type in ryecharm.configurations.ruff.LogLevel uses a type in ryecharm.configurations.ruff.
- The types involved
insyncwithfoo.ryecharm.configurations.ruff.LogLevel.DEBUG→insyncwithfoo.ryecharm.configurations.ruff.LogLevelinsyncwithfoo.ryecharm.configurations.ruff.LogLevel.ERROR→insyncwithfoo.ryecharm.configurations.ruff.LogLevelinsyncwithfoo.ryecharm.configurations.ruff.LogLevel.INFO→insyncwithfoo.ryecharm.configurations.ruff.LogLevelinsyncwithfoo.ryecharm.configurations.ruff.LogLevel.TRACE→insyncwithfoo.ryecharm.configurations.ruff.LogLevelinsyncwithfoo.ryecharm.configurations.ruff.LogLevel.WARN→insyncwithfoo.ryecharm.configurations.ruff.LogLevel
- Direction
- ryecharm.configurations.ruff.LogLevel uses ryecharm.configurations.ruff, so a change to ryecharm.configurations.ruff can break ryecharm.configurations.ruff.LogLevel, while a change to ryecharm.configurations.ruff.LogLevel can't break ryecharm.configurations.ruff.
- Position
- Below the diagonal: ryecharm.configurations.ruff.LogLevel uses a module listed above it, which is the healthy direction.
20→9 ryecharm.configurations.ruff.RuffLocalService uses ryecharm.configurations.ruff✕
- Connections
- 1 pair of types, where a type in ryecharm.configurations.ruff.RuffLocalService uses a type in ryecharm.configurations.ruff.
- The types involved
insyncwithfoo.ryecharm.configurations.ruff.RuffLocalService.Companion→insyncwithfoo.ryecharm.configurations.ruff.RuffLocalService
- Direction
- ryecharm.configurations.ruff.RuffLocalService uses ryecharm.configurations.ruff, so a change to ryecharm.configurations.ruff can break ryecharm.configurations.ruff.RuffLocalService, while a change to ryecharm.configurations.ruff.RuffLocalService can't break ryecharm.configurations.ruff.
- Position
- Below the diagonal: ryecharm.configurations.ruff.RuffLocalService uses a module listed above it, which is the healthy direction.
21→1 ryecharm.others.installers uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.others.installers uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.others.installers.InstallDependencies→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.others.installers uses ryecharm, so a change to ryecharm can break ryecharm.others.installers, while a change to ryecharm.others.installers can't break ryecharm.
- Position
- Below the diagonal: ryecharm.others.installers uses a module listed above it, which is the healthy direction.
21→16 ryecharm.others.installers uses ryecharm.uv.commands✕
- Connections
- 1 pair of types, where a type in ryecharm.others.installers uses a type in ryecharm.uv.commands.
- The types involved
insyncwithfoo.ryecharm.others.installers.InstallDependencies→insyncwithfoo.ryecharm.uv.commands.UV
- Direction
- ryecharm.others.installers uses ryecharm.uv.commands, so a change to ryecharm.uv.commands can break ryecharm.others.installers, while a change to ryecharm.others.installers can't break ryecharm.uv.commands.
- Position
- Below the diagonal: ryecharm.others.installers uses a module listed above it, which is the healthy direction.
22→1 ryecharm.ruff.commands uses ryecharm✕
- Connections
- 16 pairs of types, where a type in ryecharm.ruff.commands uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.commands.AnalyzeGraphCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.CheckCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.CleanCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.ConfigCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.FixCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.FormatCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.LinterCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.OptimizeImportsCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.OrganizeImportsCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.RecipeesKt→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.Ruff→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.Ruff→insyncwithfoo.ryecharm.CommandArgumentsinsyncwithfoo.ryecharm.ruff.commands.Ruff→insyncwithfoo.ryecharm.CommandFactoryinsyncwithfoo.ryecharm.ruff.commands.RuleCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.ShowSettingsCommand→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.commands.VersionCommand→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.ruff.commands uses ryecharm, so a change to ryecharm can break ryecharm.ruff.commands, while a change to ryecharm.ruff.commands can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff.commands uses a module listed above it, which is the healthy direction.
22→12 ryecharm.ruff.commands uses ryecharm.ruff✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.commands uses a type in ryecharm.ruff.
- The types involved
insyncwithfoo.ryecharm.ruff.commands.RecipeesKt→insyncwithfoo.ryecharm.ruff.OneBasedRange
- Direction
- ryecharm.ruff.commands uses ryecharm.ruff, so a change to ryecharm.ruff can break ryecharm.ruff.commands, while a change to ryecharm.ruff.commands can't break ryecharm.ruff.
- Position
- Below the diagonal: ryecharm.ruff.commands uses a module listed above it, which is the healthy direction.
23→1 ryecharm.ruff.documentation.targets uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.documentation.targets uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.documentation.targets.RuffDocumentationTarget→insyncwithfoo.ryecharm.ElementBasedDocumentationTarget
- Direction
- ryecharm.ruff.documentation.targets uses ryecharm, so a change to ryecharm can break ryecharm.ruff.documentation.targets, while a change to ryecharm.ruff.documentation.targets can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff.documentation.targets uses a module listed above it, which is the healthy direction.
23→12 ryecharm.ruff.documentation.targets uses ryecharm.ruff✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.documentation.targets uses a type in ryecharm.ruff.
- The types involved
insyncwithfoo.ryecharm.ruff.documentation.targets.NoqaCodeDocumentationTarget→insyncwithfoo.ryecharm.ruff.NoqaComment
- Direction
- ryecharm.ruff.documentation.targets uses ryecharm.ruff, so a change to ryecharm.ruff can break ryecharm.ruff.documentation.targets, while a change to ryecharm.ruff.documentation.targets can't break ryecharm.ruff.
- Position
- Below the diagonal: ryecharm.ruff.documentation.targets uses a module listed above it, which is the healthy direction.
24→1 ryecharm.ruff.formatting uses ryecharm✕
- Connections
- 2 pairs of types, where a type in ryecharm.ruff.formatting uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.formatting.RuffFormattingTask→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.formatting.RuffImportOptimizer→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.ruff.formatting uses ryecharm, so a change to ryecharm can break ryecharm.ruff.formatting, while a change to ryecharm.ruff.formatting can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff.formatting uses a module listed above it, which is the healthy direction.
24→12 ryecharm.ruff.formatting uses ryecharm.ruff✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.formatting uses a type in ryecharm.ruff.
- The types involved
insyncwithfoo.ryecharm.ruff.formatting.RuffFormatterKt→insyncwithfoo.ryecharm.ruff.OneBasedRange
- Direction
- ryecharm.ruff.formatting uses ryecharm.ruff, so a change to ryecharm.ruff can break ryecharm.ruff.formatting, while a change to ryecharm.ruff.formatting can't break ryecharm.ruff.
- Position
- Below the diagonal: ryecharm.ruff.formatting uses a module listed above it, which is the healthy direction.
25→1 ryecharm.ruff.onsave uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.onsave uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.onsave.RuffOnSaveTasksRunner→insyncwithfoo.ryecharm.Command
- Direction
- ryecharm.ruff.onsave uses ryecharm, so a change to ryecharm can break ryecharm.ruff.onsave, while a change to ryecharm.ruff.onsave can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff.onsave uses a module listed above it, which is the healthy direction.
25→9 ryecharm.ruff.onsave uses ryecharm.configurations.ruff✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.onsave uses a type in ryecharm.configurations.ruff.
- The types involved
insyncwithfoo.ryecharm.ruff.onsave.RuffOnSaveTasksRunnerKt→insyncwithfoo.ryecharm.configurations.ruff.RuffConfigurations
- Direction
- ryecharm.ruff.onsave uses ryecharm.configurations.ruff, so a change to ryecharm.configurations.ruff can break ryecharm.ruff.onsave, while a change to ryecharm.ruff.onsave can't break ryecharm.configurations.ruff.
- Position
- Below the diagonal: ryecharm.ruff.onsave uses a module listed above it, which is the healthy direction.
26→1 ryecharm.rye.actions uses ryecharm✕
- Connections
- 2 pairs of types, where a type in ryecharm.rye.actions uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.rye.actions.ActionCoroutine→insyncwithfoo.ryecharm.CoroutineServiceinsyncwithfoo.ryecharm.rye.actions.ShowExecutable→insyncwithfoo.ryecharm.ShowExecutableAction
- Direction
- ryecharm.rye.actions uses ryecharm, so a change to ryecharm can break ryecharm.rye.actions, while a change to ryecharm.rye.actions can't break ryecharm.
- Position
- Below the diagonal: ryecharm.rye.actions uses a module listed above it, which is the healthy direction.
26→13 ryecharm.rye.actions uses ryecharm.rye.commands✕
- Connections
- 2 pairs of types, where a type in ryecharm.rye.actions uses a type in ryecharm.rye.commands.
- The types involved
insyncwithfoo.ryecharm.rye.actions.OpenConfigurationFile→insyncwithfoo.ryecharm.rye.commands.Ryeinsyncwithfoo.ryecharm.rye.actions.ShowProjectInformation→insyncwithfoo.ryecharm.rye.commands.Rye
- Direction
- ryecharm.rye.actions uses ryecharm.rye.commands, so a change to ryecharm.rye.commands can break ryecharm.rye.actions, while a change to ryecharm.rye.actions can't break ryecharm.rye.commands.
- Position
- Below the diagonal: ryecharm.rye.actions uses a module listed above it, which is the healthy direction.
27→1 ryecharm.ty.actions uses ryecharm✕
- Connections
- 3 pairs of types, where a type in ryecharm.ty.actions uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ty.actions.ShowExecutable→insyncwithfoo.ryecharm.ShowExecutableActioninsyncwithfoo.ryecharm.ty.actions.ShowVersion→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ty.actions.ShowVersion→insyncwithfoo.ryecharm.ShowCommandOutputAction
- Direction
- ryecharm.ty.actions uses ryecharm, so a change to ryecharm can break ryecharm.ty.actions, while a change to ryecharm.ty.actions can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ty.actions uses a module listed above it, which is the healthy direction.
27→10 ryecharm.ty.actions uses ryecharm.configurations.ty✕
- Connections
- 1 pair of types, where a type in ryecharm.ty.actions uses a type in ryecharm.configurations.ty.
- The types involved
insyncwithfoo.ryecharm.ty.actions.Enable→insyncwithfoo.ryecharm.configurations.ty.RunningMode
- Direction
- ryecharm.ty.actions uses ryecharm.configurations.ty, so a change to ryecharm.configurations.ty can break ryecharm.ty.actions, while a change to ryecharm.ty.actions can't break ryecharm.configurations.ty.
- Position
- Below the diagonal: ryecharm.ty.actions uses a module listed above it, which is the healthy direction.
28→10 ryecharm.ty.lsp uses ryecharm.configurations.ty✕
- Connections
- 1 pair of types, where a type in ryecharm.ty.lsp uses a type in ryecharm.configurations.ty.
- The types involved
insyncwithfoo.ryecharm.ty.lsp.TYDescriptor→insyncwithfoo.ryecharm.configurations.ty.TYConfigurations
- Direction
- ryecharm.ty.lsp uses ryecharm.configurations.ty, so a change to ryecharm.configurations.ty can break ryecharm.ty.lsp, while a change to ryecharm.ty.lsp can't break ryecharm.configurations.ty.
- Position
- Below the diagonal: ryecharm.ty.lsp uses a module listed above it, which is the healthy direction.
28→14 ryecharm.ty.lsp uses ryecharm.ty✕
- Connections
- 1 pair of types, where a type in ryecharm.ty.lsp uses a type in ryecharm.ty.
- The types involved
insyncwithfoo.ryecharm.ty.lsp.TYDescriptor→insyncwithfoo.ryecharm.ty.WorkspaceConfiguration
- Direction
- ryecharm.ty.lsp uses ryecharm.ty, so a change to ryecharm.ty can break ryecharm.ty.lsp, while a change to ryecharm.ty.lsp can't break ryecharm.ty.
- Position
- Below the diagonal: ryecharm.ty.lsp uses a module listed above it, which is the healthy direction.
29→1 ryecharm.uv.actions uses ryecharm✕
- Connections
- 5 pairs of types, where a type in ryecharm.uv.actions uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.uv.actions.ActionCoroutine→insyncwithfoo.ryecharm.CoroutineServiceinsyncwithfoo.ryecharm.uv.actions.Install→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.actions.ShowExecutable→insyncwithfoo.ryecharm.ShowExecutableActioninsyncwithfoo.ryecharm.uv.actions.ShowVersion→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.actions.ShowVersion→insyncwithfoo.ryecharm.ShowCommandOutputAction
- Direction
- ryecharm.uv.actions uses ryecharm, so a change to ryecharm can break ryecharm.uv.actions, while a change to ryecharm.uv.actions can't break ryecharm.
- Position
- Below the diagonal: ryecharm.uv.actions uses a module listed above it, which is the healthy direction.
29→16 ryecharm.uv.actions uses ryecharm.uv.commands✕
- Connections
- 1 pair of types, where a type in ryecharm.uv.actions uses a type in ryecharm.uv.commands.
- The types involved
insyncwithfoo.ryecharm.uv.actions.Update→insyncwithfoo.ryecharm.uv.commands.UV
- Direction
- ryecharm.uv.actions uses ryecharm.uv.commands, so a change to ryecharm.uv.commands can break ryecharm.uv.actions, while a change to ryecharm.uv.actions can't break ryecharm.uv.commands.
- Position
- Below the diagonal: ryecharm.uv.actions uses a module listed above it, which is the healthy direction.
30→1 ryecharm.uv.intentions uses ryecharm✕
- Connections
- 9 pairs of types, where a type in ryecharm.uv.intentions uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.uv.intentions.BumpProjectVersion→insyncwithfoo.ryecharm.ExternalIntentionActioninsyncwithfoo.ryecharm.uv.intentions.BumpProjectVersion→insyncwithfoo.ryecharm.WriteIntentionActioninsyncwithfoo.ryecharm.uv.intentions.BumpProjectVersionKt→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.uv.intentions.Bumper→insyncwithfoo.ryecharm.ExternalIntentionActioninsyncwithfoo.ryecharm.uv.intentions.Bumper→insyncwithfoo.ryecharm.WriteIntentionActioninsyncwithfoo.ryecharm.uv.intentions.BumpingKindChoosingDialog→insyncwithfoo.ryecharm.Dialoginsyncwithfoo.ryecharm.uv.intentions.IntentionCoroutine→insyncwithfoo.ryecharm.CoroutineServiceinsyncwithfoo.ryecharm.uv.intentions.SynchronizeProject→insyncwithfoo.ryecharm.ExternalIntentionActioninsyncwithfoo.ryecharm.uv.intentions.SynchronizeProject→insyncwithfoo.ryecharm.WriteIntentionAction
- Direction
- ryecharm.uv.intentions uses ryecharm, so a change to ryecharm can break ryecharm.uv.intentions, while a change to ryecharm.uv.intentions can't break ryecharm.
- Position
- Below the diagonal: ryecharm.uv.intentions uses a module listed above it, which is the healthy direction.
30→16 ryecharm.uv.intentions uses ryecharm.uv.commands✕
- Connections
- 4 pairs of types, where a type in ryecharm.uv.intentions uses a type in ryecharm.uv.commands.
- The types involved
insyncwithfoo.ryecharm.uv.intentions.BumpProjectVersionKt→insyncwithfoo.ryecharm.uv.commands.VersionBumpTypeinsyncwithfoo.ryecharm.uv.intentions.Bumper→insyncwithfoo.ryecharm.uv.commands.VersionBumpTypeinsyncwithfoo.ryecharm.uv.intentions.BumpingKindChoosingDialog→insyncwithfoo.ryecharm.uv.commands.VersionBumpTypeinsyncwithfoo.ryecharm.uv.intentions.SynchronizeProject→insyncwithfoo.ryecharm.uv.commands.UV
- Direction
- ryecharm.uv.intentions uses ryecharm.uv.commands, so a change to ryecharm.uv.commands can break ryecharm.uv.intentions, while a change to ryecharm.uv.intentions can't break ryecharm.uv.commands.
- Position
- Below the diagonal: ryecharm.uv.intentions uses a module listed above it, which is the healthy direction.
31→18 ryecharm.configurations.main uses ryecharm.configurations✕
- Connections
- 10 pairs of types, where a type in ryecharm.configurations.main uses a type in ryecharm.configurations.
- The types involved
insyncwithfoo.ryecharm.configurations.main.MainConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.main.MainConfigurations→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.main.MainGlobalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.main.MainLocalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.main.MainOverrideService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.main.MainOverrides→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.main.MainOverrides→insyncwithfoo.ryecharm.configurations.ProjectOverrideStateinsyncwithfoo.ryecharm.configurations.main.MainPanel→insyncwithfoo.ryecharm.configurations.AdaptivePanelinsyncwithfoo.ryecharm.configurations.main.MainProjectConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.main.MainProjectConfigurable→insyncwithfoo.ryecharm.configurations.ProjectBasedConfigurable
- Direction
- ryecharm.configurations.main uses ryecharm.configurations, so a change to ryecharm.configurations can break ryecharm.configurations.main, while a change to ryecharm.configurations.main can't break ryecharm.configurations.
- Position
- Below the diagonal: ryecharm.configurations.main uses a module listed above it, which is the healthy direction.
32→18 ryecharm.configurations.rye uses ryecharm.configurations✕
- Connections
- 10 pairs of types, where a type in ryecharm.configurations.rye uses a type in ryecharm.configurations.
- The types involved
insyncwithfoo.ryecharm.configurations.rye.RyeConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.rye.RyeConfigurations→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.rye.RyeGlobalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.rye.RyeLocalService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.rye.RyeOverrideService→insyncwithfoo.ryecharm.configurations.ConfigurationServiceinsyncwithfoo.ryecharm.configurations.rye.RyeOverrides→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.configurations.rye.RyeOverrides→insyncwithfoo.ryecharm.configurations.ProjectOverrideStateinsyncwithfoo.ryecharm.configurations.rye.RyePanel→insyncwithfoo.ryecharm.configurations.AdaptivePanelinsyncwithfoo.ryecharm.configurations.rye.RyeProjectConfigurable→insyncwithfoo.ryecharm.configurations.PanelBasedConfigurableinsyncwithfoo.ryecharm.configurations.rye.RyeProjectConfigurable→insyncwithfoo.ryecharm.configurations.ProjectBasedConfigurable
- Direction
- ryecharm.configurations.rye uses ryecharm.configurations, so a change to ryecharm.configurations can break ryecharm.configurations.rye, while a change to ryecharm.configurations.rye can't break ryecharm.configurations.
- Position
- Below the diagonal: ryecharm.configurations.rye uses a module listed above it, which is the healthy direction.
33→1 ryecharm.others.installers.InstallDependencies uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.others.installers.InstallDependencies uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.others.installers.InstallDependencies.Coroutine→insyncwithfoo.ryecharm.CoroutineService
- Direction
- ryecharm.others.installers.InstallDependencies uses ryecharm, so a change to ryecharm can break ryecharm.others.installers.InstallDependencies, while a change to ryecharm.others.installers.InstallDependencies can't break ryecharm.
- Position
- Below the diagonal: ryecharm.others.installers.InstallDependencies uses a module listed above it, which is the healthy direction.
33→21 ryecharm.others.installers.InstallDependencies uses ryecharm.others.installers✕
- Connections
- 1 pair of types, where a type in ryecharm.others.installers.InstallDependencies uses a type in ryecharm.others.installers.
- The types involved
insyncwithfoo.ryecharm.others.installers.InstallDependencies.Companion→insyncwithfoo.ryecharm.others.installers.InstallDependencies
- Direction
- ryecharm.others.installers.InstallDependencies uses ryecharm.others.installers, so a change to ryecharm.others.installers can break ryecharm.others.installers.InstallDependencies, while a change to ryecharm.others.installers.InstallDependencies can't break ryecharm.others.installers.
- Position
- Below the diagonal: ryecharm.others.installers.InstallDependencies uses a module listed above it, which is the healthy direction.
34→1 ryecharm.ruff.actions uses ryecharm✕
- Connections
- 7 pairs of types, where a type in ryecharm.ruff.actions uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.actions.ActionCoroutine→insyncwithfoo.ryecharm.CoroutineServiceinsyncwithfoo.ryecharm.ruff.actions.FixAll→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.actions.LintersDialog→insyncwithfoo.ryecharm.Dialoginsyncwithfoo.ryecharm.ruff.actions.ShowExecutable→insyncwithfoo.ryecharm.ShowExecutableActioninsyncwithfoo.ryecharm.ruff.actions.ShowLinters→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.actions.ShowVersion→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.actions.ShowVersion→insyncwithfoo.ryecharm.ShowCommandOutputAction
- Direction
- ryecharm.ruff.actions uses ryecharm, so a change to ryecharm can break ryecharm.ruff.actions, while a change to ryecharm.ruff.actions can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff.actions uses a module listed above it, which is the healthy direction.
34→22 ryecharm.ruff.actions uses ryecharm.ruff.commands✕
- Connections
- 2 pairs of types, where a type in ryecharm.ruff.actions uses a type in ryecharm.ruff.commands.
- The types involved
insyncwithfoo.ryecharm.ruff.actions.CleanCache→insyncwithfoo.ryecharm.ruff.commands.Ruffinsyncwithfoo.ryecharm.ruff.actions.ShowLinters→insyncwithfoo.ryecharm.ruff.commands.Ruff
- Direction
- ryecharm.ruff.actions uses ryecharm.ruff.commands, so a change to ryecharm.ruff.commands can break ryecharm.ruff.actions, while a change to ryecharm.ruff.actions can't break ryecharm.ruff.commands.
- Position
- Below the diagonal: ryecharm.ruff.actions uses a module listed above it, which is the healthy direction.
35→1 ryecharm.ruff.documentation uses ryecharm✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.documentation uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.documentation.OptionInfoKt→insyncwithfoo.ryecharm.Popup
- Direction
- ryecharm.ruff.documentation uses ryecharm, so a change to ryecharm can break ryecharm.ruff.documentation, while a change to ryecharm.ruff.documentation can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff.documentation uses a module listed above it, which is the healthy direction.
35→23 ryecharm.ruff.documentation uses ryecharm.ruff.documentation.targets✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.documentation uses a type in ryecharm.ruff.documentation.targets.
- The types involved
insyncwithfoo.ryecharm.ruff.documentation.RuffDocumentationLinkHandler→insyncwithfoo.ryecharm.ruff.documentation.targets.RuffDocumentationTarget
- Direction
- ryecharm.ruff.documentation uses ryecharm.ruff.documentation.targets, so a change to ryecharm.ruff.documentation.targets can break ryecharm.ruff.documentation, while a change to ryecharm.ruff.documentation can't break ryecharm.ruff.documentation.targets.
- Position
- Below the diagonal: ryecharm.ruff.documentation uses a module listed above it, which is the healthy direction.
36→1 ryecharm.ruff.linting uses ryecharm✕
- Connections
- 5 pairs of types, where a type in ryecharm.ruff.linting uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.ruff.linting.CheckKt→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.linting.Coroutine→insyncwithfoo.ryecharm.CoroutineServiceinsyncwithfoo.ryecharm.ruff.linting.RuffFixSimilarViolations→insyncwithfoo.ryecharm.Commandinsyncwithfoo.ryecharm.ruff.linting.RuffFixSimilarViolations→insyncwithfoo.ryecharm.ExternalQuickFixinsyncwithfoo.ryecharm.ruff.linting.RuffFixViolation→insyncwithfoo.ryecharm.TopPriorityAction
- Direction
- ryecharm.ruff.linting uses ryecharm, so a change to ryecharm can break ryecharm.ruff.linting, while a change to ryecharm.ruff.linting can't break ryecharm.
- Position
- Below the diagonal: ryecharm.ruff.linting uses a module listed above it, which is the healthy direction.
36→9 ryecharm.ruff.linting uses ryecharm.configurations.ruff✕
- Connections
- 3 pairs of types, where a type in ryecharm.ruff.linting uses a type in ryecharm.configurations.ruff.
- The types involved
insyncwithfoo.ryecharm.ruff.linting.AnnotationResult→insyncwithfoo.ryecharm.configurations.ruff.RuffConfigurationsinsyncwithfoo.ryecharm.ruff.linting.FixesKt→insyncwithfoo.ryecharm.configurations.ruff.RuffConfigurationsinsyncwithfoo.ryecharm.ruff.linting.InitialInfo→insyncwithfoo.ryecharm.configurations.ruff.RuffConfigurations
- Direction
- ryecharm.ruff.linting uses ryecharm.configurations.ruff, so a change to ryecharm.configurations.ruff can break ryecharm.ruff.linting, while a change to ryecharm.ruff.linting can't break ryecharm.configurations.ruff.
- Position
- Below the diagonal: ryecharm.ruff.linting uses a module listed above it, which is the healthy direction.
36→12 ryecharm.ruff.linting uses ryecharm.ruff✕
- Connections
- 3 pairs of types, where a type in ryecharm.ruff.linting uses a type in ryecharm.ruff.
- The types involved
insyncwithfoo.ryecharm.ruff.linting.ConversionsKt→insyncwithfoo.ryecharm.ruff.OneBasedRangeinsyncwithfoo.ryecharm.ruff.linting.Diagnostic→insyncwithfoo.ryecharm.ruff.DiagnosticIDinsyncwithfoo.ryecharm.ruff.linting.RuffDisableRuleComment→insyncwithfoo.ryecharm.ruff.NoqaComment
- Direction
- ryecharm.ruff.linting uses ryecharm.ruff, so a change to ryecharm.ruff can break ryecharm.ruff.linting, while a change to ryecharm.ruff.linting can't break ryecharm.ruff.
- Position
- Below the diagonal: ryecharm.ruff.linting uses a module listed above it, which is the healthy direction.
36→22 ryecharm.ruff.linting uses ryecharm.ruff.commands✕
- Connections
- 1 pair of types, where a type in ryecharm.ruff.linting uses a type in ryecharm.ruff.commands.
- The types involved
insyncwithfoo.ryecharm.ruff.linting.InitialInfo→insyncwithfoo.ryecharm.ruff.commands.Ruff
- Direction
- ryecharm.ruff.linting uses ryecharm.ruff.commands, so a change to ryecharm.ruff.commands can break ryecharm.ruff.linting, while a change to ryecharm.ruff.linting can't break ryecharm.ruff.commands.
- Position
- Below the diagonal: ryecharm.ruff.linting uses a module listed above it, which is the healthy direction.
37→18 ryecharm.uv.inlayhints.dependencyversions.settings uses ryecharm.configurations✕
- Connections
- 2 pairs of types, where a type in ryecharm.uv.inlayhints.dependencyversions.settings uses a type in ryecharm.configurations.
- The types involved
insyncwithfoo.ryecharm.uv.inlayhints.dependencyversions.settings.Settings→insyncwithfoo.ryecharm.configurations.DisplayableStateinsyncwithfoo.ryecharm.uv.inlayhints.dependencyversions.settings.SettingsService→insyncwithfoo.ryecharm.configurations.ConfigurationService
- Direction
- ryecharm.uv.inlayhints.dependencyversions.settings uses ryecharm.configurations, so a change to ryecharm.configurations can break ryecharm.uv.inlayhints.dependencyversions.settings, while a change to ryecharm.uv.inlayhints.dependencyversions.settings can't break ryecharm.configurations.
- Position
- Below the diagonal: ryecharm.uv.inlayhints.dependencyversions.settings uses a module listed above it, which is the healthy direction.
38→31 ryecharm.configurations.main.MainLocalService uses ryecharm.configurations.main✕
- Connections
- 1 pair of types, where a type in ryecharm.configurations.main.MainLocalService uses a type in ryecharm.configurations.main.
- The types involved
insyncwithfoo.ryecharm.configurations.main.MainLocalService.Companion→insyncwithfoo.ryecharm.configurations.main.MainLocalService
- Direction
- ryecharm.configurations.main.MainLocalService uses ryecharm.configurations.main, so a change to ryecharm.configurations.main can break ryecharm.configurations.main.MainLocalService, while a change to ryecharm.configurations.main.MainLocalService can't break ryecharm.configurations.main.
- Position
- Below the diagonal: ryecharm.configurations.main.MainLocalService uses a module listed above it, which is the healthy direction.
39→31 ryecharm.configurations.main.MainOverrideService uses ryecharm.configurations.main✕
- Connections
- 1 pair of types, where a type in ryecharm.configurations.main.MainOverrideService uses a type in ryecharm.configurations.main.
- The types involved
insyncwithfoo.ryecharm.configurations.main.MainOverrideService.Companion→insyncwithfoo.ryecharm.configurations.main.MainOverrideService
- Direction
- ryecharm.configurations.main.MainOverrideService uses ryecharm.configurations.main, so a change to ryecharm.configurations.main can break ryecharm.configurations.main.MainOverrideService, while a change to ryecharm.configurations.main.MainOverrideService can't break ryecharm.configurations.main.
- Position
- Below the diagonal: ryecharm.configurations.main.MainOverrideService uses a module listed above it, which is the healthy direction.
40→1 ryecharm.uv.inlayhints.dependencyversions uses ryecharm✕
- Connections
- 2 pairs of types, where a type in ryecharm.uv.inlayhints.dependencyversions uses a type in ryecharm.
- The types involved
insyncwithfoo.ryecharm.uv.inlayhints.dependencyversions.Coroutine→insyncwithfoo.ryecharm.CoroutineServiceinsyncwithfoo.ryecharm.uv.inlayhints.dependencyversions.DependencyVersionInlayHintsCollector→insyncwithfoo.ryecharm.TOMLPath
- Direction
- ryecharm.uv.inlayhints.dependencyversions uses ryecharm, so a change to ryecharm can break ryecharm.uv.inlayhints.dependencyversions, while a change to ryecharm.uv.inlayhints.dependencyversions can't break ryecharm.
- Position
- Below the diagonal: ryecharm.uv.inlayhints.dependencyversions uses a module listed above it, which is the healthy direction.
40→37 ryecharm.uv.inlayhints.dependencyversions uses ryecharm.uv.inlayhints.dependencyversions.settings✕
- Connections
- 1 pair of types, where a type in ryecharm.uv.inlayhints.dependencyversions uses a type in ryecharm.uv.inlayhints.dependencyversions.settings.
- The types involved
insyncwithfoo.ryecharm.uv.inlayhints.dependencyversions.DependencyVersionInlayHintsCollector→insyncwithfoo.ryecharm.uv.inlayhints.dependencyversions.settings.Settings
- Direction
- ryecharm.uv.inlayhints.dependencyversions uses ryecharm.uv.inlayhints.dependencyversions.settings, so a change to ryecharm.uv.inlayhints.dependencyversions.settings can break ryecharm.uv.inlayhints.dependencyversions, while a change to ryecharm.uv.inlayhints.dependencyversions can't break ryecharm.uv.inlayhints.dependencyversions.settings.
- Position
- Below the diagonal: ryecharm.uv.inlayhints.dependencyversions 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 48 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 15 | Medium |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; 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; Resolve the 7 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (6), REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.8 pts | Medium | Architecture documentation |
| Resolve the 7 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (6), REDACTED. | +2.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +2.1 pts | Low | Static Analysis (SAST) |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +3.0 pts | Medium | Documentation (README) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.1 pts | Medium | Page structure |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +1.2 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/ruff/linting/RuffGlobalInspection.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/main/kotlin/insyncwithfoo/ryecharm/KnownFiles.kt | 7.3 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/ruff/documentation/OptionInfo.kt | 7.3 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/ruff/intentions/FixAll.kt | 7.8 | Near-clean | Code Duplication: Edited copies of one member (3 members, 19+ corresponding lines) |
| src/main/kotlin/insyncwithfoo/ryecharm/ty/lsp/TYDescriptor.kt | 7.8 | Near-clean | Code Duplication: Edited copy of a member (14 corresponding lines) |
| src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/RuffDescriptor.kt | 7.8 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| src/test/kotlin/insyncwithfoo/ryecharm/ruff/folding/RuffRuleFoldingTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/APIAvailability.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/Documentation.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/ProcessNotifications.kt | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/main/kotlin/insyncwithfoo/ryecharm/uv/documentation/DependencyTreeDocumentationTarget.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/uv/documentation/DependencyTreeDocumentationTargetProvider.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/uv/commands/Recipees.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main/kotlin/insyncwithfoo/ryecharm/uv/actions/Update.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 38 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, 135 of 142 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (JaCoCo's report, finalizing the tests in build.gradle.kts), uploaded by `codecov/codecov-action` and a Codecov configuration (codecov.yml) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.py, .kt), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py, .kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because cache-redirector.jetbrains.com — the registry that answers it — was asked and did not reply (the build stopped because cache-redirector.jetbrains.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add cache-redirector.jetbrains.com to the allowlist and re-run — not to build anything.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 2 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 781 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (11720 LoC, 519 module-visible types across 48 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D30 Dependency Vulnerabilities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/main/kotlin/insyncwithfoo/ryecharm/configurations/States.kt`, `src/main/kotlin/insyncwithfoo/ryecharm/others/scriptmetadata/EditScriptMetadataFragment.kt`, `src/main/kotlin/insyncwithfoo/ryecharm/ruff/NoqaComment.kt`, `src/main/kotlin/insyncwithfoo/ryecharm/ruff/intentions/ReenableRule.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 10 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
9 duplicated block group(s) detected. 2.7 % of the production lines (322 of 11,720) are in a reported copy. A further 8 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with RuffDescriptor.kt (2), TYDescriptor.kt, RuffServerFactory.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with DiagnosticsSupport.kt, FixAll.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with RuffServerConnectionProvider.kt, Panels.kt. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 28 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
26 deducted task-comment markers across 11720 LoC (0.2/KLoC) → score 9.6. 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 23 TodoComment finding(s) in Explicit Debt — start with RuffGlobalInspection.kt (3), KnownFiles.kt (2), Recipees.kt (2). — One of this dimension's main actionable groups (23 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with ProcessNotifications.kt, LSP.kt, NoqaComment.kt. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 30 document(s) read across 1 unit(s).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
48 finding(s): 0 critical, 46 high, 2 medium, 0 low. 40 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. semgrep hit a parse error in 3 file(s) — `gradlew` (line 74, line 178), `scripts/command_specs.py` (line 27), `src/main/kotlin/insyncwithfoo/ryecharm/others/scriptmetadata/EditScriptMetadataFragment.kt` (line 128) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 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 40 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 (40 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 71 of the 204 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 7 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×10) — src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.others.dependencygroups.DependencyGroupInspection.html:1, src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.ruff.linting.RuffGlobalInspection.html:1, src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.uv.inspections.DevDependenciesInspection.html:1, …
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×10) — src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.others.dependencygroups.DependencyGroupInspection.html:1, src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.ruff.linting.RuffGlobalInspection.html:1, src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.uv.inspections.DevDependenciesInspection.html:1, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:5
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X3 · Exception handling
- `catch (_: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/kotlin/insyncwithfoo/ryecharm/uv/inlayhints/dependencyversions/DependencyVersionInlayHintsProvider.kt:54
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84.4 | Strong | Solid. |
| Architecture | 100.0 | Exemplary | Strongest area. |
| Maturity | 54.4 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 71.9 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58.0 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 68.3 | Adequate — gated by AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 11 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 — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2315 lines of test source are present (.py, .kt) 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.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — cache-redirector.jetbrains.com did not answer
- D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 4 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Scanner failed to run — not a clean result
- D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 46 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 30 current-state document(s) make no claim of a kind M4 checks. 12 claim(s) of kinds M4 does not check were not checked (path 12); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P2 Observability — This repository's JVM source (1 module(s), 213 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 56 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
- Document without a <title> src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.others.dependencygroups.DependencyGroupInspection.html:1
- Document without a <title> src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.ruff.linting.RuffGlobalInspection.html:1
- Document without a <title> src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.uv.inspections.DevDependenciesInspection.html:1
- Document without a <title> src/main/resources/intentionDescriptions/BumpProjectVersion/description.html:1
- Document without a <title> src/main/resources/intentionDescriptions/EditScriptMetadataFragment/description.html:1
- Document without a <title> src/main/resources/intentionDescriptions/FixAllSafe/description.html:1
- Document without a <title> src/main/resources/intentionDescriptions/FixAllUnsafe/description.html:1
- Document without a <title> src/main/resources/intentionDescriptions/OrganizeImports/description.html:1
- Document without a <title> src/main/resources/intentionDescriptions/ReenableRule/description.html:1
- Document without a <title> src/main/resources/intentionDescriptions/SynchronizeProject/description.html:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 67 finding(s)
- TodoComment src/test/kotlin/insyncwithfoo/ryecharm/ruff/folding/RuffRuleFoldingTest.kt:31
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/APIAvailability.kt:52
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/Documentation.kt:16
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/KnownFiles.kt:105
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/KnownFiles.kt:141
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/uv/documentation/DependencyTreeDocumentationTarget.kt:44
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/uv/documentation/DependencyTreeDocumentationTargetProvider.kt:54
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/uv/commands/Recipees.kt:146
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/uv/actions/Update.kt:125
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/onsave/RuffOnSaveTasksRunner.kt:41
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt:70
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/linting/RuffAnnotator.kt:63
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/linting/RuffFixViolation.kt:55
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/linting/RuffGlobalInspection.kt:47
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/linting/RuffGlobalInspection.kt:67
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/linting/RuffGlobalInspection.kt:68
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/hierarchy/ImportGraphTreeStructure.kt:126
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/documentation/OptionInfo.kt:134
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/documentation/OptionInfo.kt:155
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/documentation/RuleInfo.kt:93
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/commands/Recipees.kt:20
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/others/scriptmetadata/ScriptMetadataPSI.kt:10
- TodoComment src/main/kotlin/insyncwithfoo/ryecharm/common/icons/RyeCharmFilesIconProvider.kt:41
- Page without a main landmark src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.others.dependencygroups.DependencyGroupInspection.html:1
- Page without a main landmark src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.ruff.linting.RuffGlobalInspection.html:1
- Page without a main landmark src/main/resources/inspectionDescriptions/insyncwithfoo.ryecharm.uv.inspections.DevDependenciesInspection.html:1
- Page without a main landmark src/main/resources/intentionDescriptions/BumpProjectVersion/description.html:1
- Page without a main landmark src/main/resources/intentionDescriptions/EditScriptMetadataFragment/description.html:1
- Page without a main landmark src/main/resources/intentionDescriptions/FixAllSafe/description.html:1
- Page without a main landmark src/main/resources/intentionDescriptions/FixAllUnsafe/description.html:1
- Page without a main landmark src/main/resources/intentionDescriptions/OrganizeImports/description.html:1
- Page without a main landmark src/main/resources/intentionDescriptions/ReenableRule/description.html:1
- Page without a main landmark src/main/resources/intentionDescriptions/SynchronizeProject/description.html:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/RuffDescriptor.kt:86
- Duplicated block (7 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/RuffDescriptor.kt:94
- Duplicated block (7 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ty/lsp/TYDescriptor.kt:85
- Duplicated block (7 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp4ij/RuffServerFactory.kt:27
- FixmeComment src/main/kotlin/insyncwithfoo/ryecharm/ProcessNotifications.kt:210
- FixmeComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/LSP.kt:39
- FixmeComment src/main/kotlin/insyncwithfoo/ryecharm/ruff/NoqaComment.kt:28
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt:50
- Duplicated block (10 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ruff/actions/FixAll.kt:56
- Duplicated block (8 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp4ij/RuffServerConnectionProvider.kt:14
- Duplicated block (8 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/configurations/ty/Panels.kt:102
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt:49
- Edited copy of a member (19 corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/ruff/documentation/providers/RuffOptionDocumentationTargetProvider.kt:49
- Edited copies of one member (3 members, 19+ corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/ruff/intentions/FixAll.kt:41
- Edited copy of a member (14 corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/ty/lsp/TYDescriptor.kt:93
- Edited copy of a member (9 corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/ruff/intentions/FixAll.kt:31
- Edited copy of a member (15 corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/rye/actions/OpenConfigurationFile.kt:32
- Edited copies of one member (3 members, 10+ corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/ruff/formatting/RuffImportOptimizer.kt:79
- Edited copy of a member (8 corresponding lines) src/main/kotlin/insyncwithfoo/ryecharm/others/installers/InstallDependencies.kt:57
- Duplicated block (11 lines × 2) src/main/kotlin/insyncwithfoo/ryecharm/ruff/formatting/RuffFormatter.kt:175
- Swallowed exception (caught, then discarded) src/main/kotlin/insyncwithfoo/ryecharm/uv/inlayhints/dependencyversions/DependencyVersionInlayHintsProvider.kt:54
Minor — 19 finding(s)
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/CodeActionsSupport.kt:31
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/CodeActionsSupport.kt:25
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/CodeActionsSupport.kt:32
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/CodeActionsSupport.kt:26
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt:39
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/uv/intentions/BumpProjectVersion.kt:143
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/documentation/RuleDocumentation.kt:180
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp4ij/RuffServerFactory.kt:32
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt:56
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt:79
- Duplicated predicate src/main/kotlin/insyncwithfoo/ryecharm/ruff/lsp/DiagnosticsSupport.kt:80
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:7
- Dependabot does not watch pip REDACTED:5
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-fb6021cb15ad4f399d54c57964e397f1/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=581" --report-format json --report-path /tmp/watchdog-gitleaks-fb6021cb15ad4f399d54c57964e397f1/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fb6021cb15ad4f399d54c57964e397f1/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 48 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 4 file(s) — `src/main/kotlin/insyncwithfoo/ryecharm/configurations/States.kt`, `src/main/kotlin/insyncwithfoo/ryecharm/others/scriptmetadata/EditScriptMetadataFragment.kt`, `src/main/kotlin/insyncwithfoo/ryecharm/ruff/NoqaComment.kt`, `src/main/kotlin/insyncwithfoo/ryecharm/ruff/intentions/ReenableRule.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |