Executive summary
j178/prek meets our standard for a preview release. It scores 73 out of 100 and is rated Strong, and all 14 of its critical findings are security problems.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first steps are automating dependency updates and documenting the recovery plan, each worth about 4 points.
Eight secrets can leak from the build pipeline. Two pipeline steps run downloads nobody checks, and two settings leave the servers or containers unsafe. Limiting each secret to its own step, checking each download against a checksum and correcting the unsafe settings would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and fixing the weaknesses the scanner points to would deal with the security weakness in the code.
The product code is 51,575 lines, about €110,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
New since the last survey: 7 findings
- Cyclomatic Complexity · prek::cli::run::run::set_env_vars (cyclomatic 16) crates/prek/src/cli/run/run.rs
- Cognitive Complexity · prek::hooks::builtin_hooks::check_commit_trailers::check_message (cognitive 27) crates/prek/src/hooks/builtin_hooks/check_commit_trailers.rs
- Cognitive Complexity · Project::find_configs (cognitive 24) crates/prek/src/workspace.rs
- Cognitive Complexity · prek::cli::run::run::set_env_vars (cognitive 16) crates/prek/src/cli/run/run.rs
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change coupling: run.rs ↔ system.rs crates/prek/src/cli/run/run.rs
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 6 findings
- Cognitive Complexity · prek::cli::self_update::self_update (cognitive 19) crates/prek/src/cli/self_update.rs
- Code Duplication · Duplicated block (20 lines × 2) crates/prek/src/languages/rust/rustup.rs
- Code Duplication · Duplicated block (8 lines × 2) crates/prek/src/hooks/builtin_hooks/mod.rs
- Code Duplication · Duplicated block (5 lines × 2) crates/prek-pty/src/pty.rs
- Churn × Complexity Hotspots · Hotspot: crates/prek/src/hooks/pre_commit_hooks/mod.rs crates/prek/src/hooks/pre_commit_hooks/mod.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €37,000 to €190,000, for 618 to 1,962 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 73. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 51,575 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 config.pattern | 2 printer | 3 cli | 4 cli.run.selector | 5 config.repo | 6 git | 7 process | 8 store | 9 workspace | 10 cli.run.reporter | 11 languages | 12 config.hook | 13 cli.install | 14 cli.list | 15 cli.try_repo | 16 config | 17 languages.version | 18 hook | 19 settings | 20 cli.cache_gc | 21 cli.reporter | 22 cli.run.filter | 23 cli.update | 24 hooks | 25 hooks.builtin_hooks | 26 cli.run.install | 27 cli.run.run | 28 hooks.meta_hooks | 29 languages.docker | 30 languages.docker_image | 31 languages.fail | 32 languages.julia | 33 languages.node.node | 34 languages.php | 35 languages.pygrep.pygrep | 36 languages.r | 37 languages.rust.rust | 38 archive | 39 languages.python.uv | 40 languages.python.python |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 config.pattern | ||||||||||||||||||||||||||||||||||||||||
| 2 printer | ||||||||||||||||||||||||||||||||||||||||
| 3 cli | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 4 cli.run.selector | 3 | |||||||||||||||||||||||||||||||||||||||
| 5 config.repo | 9 | |||||||||||||||||||||||||||||||||||||||
| 6 git | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 process | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 store | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 workspace | 4 | 3 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 cli.run.reporter | 1 | 1 | 1 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 11 languages | 1 | 1 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||
| 12 config.hook | 2 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 13 cli.install | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 14 cli.list | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 15 cli.try_repo | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 config | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 languages.version | 5 | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 hook | 1 | 2 | 1 | 1 | 14 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 19 settings | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 cli.cache_gc | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 21 cli.reporter | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 cli.run.filter | 1 | 1 | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 23 cli.update | 1 | 1 | 1 | 1 | 7 | 3 | ||||||||||||||||||||||||||||||||||
| 24 hooks | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 hooks.builtin_hooks | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 cli.run.install | 2 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 cli.run.run | 3 | 2 | 1 | 2 | 6 | 2 | 1 | 1 | 3 | 1 | 9 | 1 | ||||||||||||||||||||||||||||
| 28 hooks.meta_hooks | 1 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 29 languages.docker | 1 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 30 languages.docker_image | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 31 languages.fail | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 32 languages.julia | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 33 languages.node.node | 1 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 34 languages.php | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 35 languages.pygrep.pygrep | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 36 languages.r | 1 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 languages.rust.rust | 1 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 38 archive | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 languages.python.uv | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 languages.python.python | 1 | 1 | 1 | 2 | 3 | 1 | 1 | 1 |
3→12 cli uses config.hook part of a loop✕
- Connections
- 8 pairs of types, where a type in cli uses a type in config.hook.
- The types involved
prek.cli.HookImplArgs→prek.config.hook.HookTypeprek.cli.InitTemplateDirArgs→prek.config.hook.HookTypeprek.cli.InstallArgs→prek.config.hook.HookTypeprek.cli.ListArgs→prek.config.hook.Languageprek.cli.ListArgs→prek.config.hook.Stageprek.cli.RunArgs→prek.config.hook.Stageprek.cli.TryRepoArgs→prek.config.hook.Stageprek.cli.UninstallArgs→prek.config.hook.HookType
- Direction
- cli uses config.hook, so a change to config.hook can break cli, while a change to cli can't break config.hook.
- 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.
3→16 cli uses config part of a loop✕
- Connections
- 1 pair of types, where a type in cli uses a type in config.
- The types involved
prek.cli.RunOptions→prek.config.HideStatus
- Direction
- cli uses config, so a change to config can break cli, while a change to cli can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→18 cli.run.selector uses hook part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.run.selector uses a type in hook.
- The types involved
prek.cli.run.selector.GroupFilters→prek.hook.Hookprek.cli.run.selector.Selector→prek.hook.Hookprek.cli.run.selector.Selectors→prek.hook.Hook
- Direction
- cli.run.selector uses hook, so a change to hook can break cli.run.selector, while a change to cli.run.selector can't break hook.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→12 config.repo uses config.hook part of a loop✕
- Connections
- 9 pairs of types, where a type in config.repo uses a type in config.hook.
- The types involved
prek.config.repo.BuiltinRepo→prek.config.hook.BuiltinHookprek.config.repo.HookConfigRef→prek.config.hook.BuiltinHookprek.config.repo.HookConfigRef→prek.config.hook.HookOptionsprek.config.repo.HookConfigRef→prek.config.hook.LocalHookprek.config.repo.HookConfigRef→prek.config.hook.MetaHookprek.config.repo.HookConfigRef→prek.config.hook.RemoteHookprek.config.repo.LocalRepo→prek.config.hook.LocalHookprek.config.repo.MetaRepo→prek.config.hook.MetaHookprek.config.repo.RemoteRepo→prek.config.hook.RemoteHook
- Direction
- config.repo uses config.hook, so a change to config.hook can break config.repo, while a change to config.repo can't break config.hook.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→3 git uses cli✕
- Connections
- 1 pair of types, where a type in git uses a type in cli.
- The types involved
prek.git.git$module→prek.cli.Command
- Direction
- git uses cli, so a change to cli can break git, while a change to git can't break cli.
- Position
- Below the diagonal: git uses a module listed above it, which is the healthy direction.
6→38 git uses archive part of a loop✕
- Connections
- 1 pair of types, where a type in git uses a type in archive.
- The types involved
prek.git.git$module→prek.archive.Error
- Direction
- git uses archive, so a change to archive can break git, while a change to git can't break archive.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 process uses cli✕
- Connections
- 4 pairs of types, where a type in process uses a type in cli.
- The types involved
prek.process.Cmd→prek.cli.Commandprek.process.Cmd→prek.cli.ExitStatusprek.process.MergedOutput→prek.cli.ExitStatusprek.process.StatusError→prek.cli.ExitStatus
- Direction
- process uses cli, so a change to cli can break process, while a change to process can't break cli.
- Position
- Below the diagonal: process uses a module listed above it, which is the healthy direction.
7→6 process uses git✕
- Connections
- 1 pair of types, where a type in process uses a type in git.
- The types involved
prek.process.Cmd→prek.git.GitCommandExt
- Direction
- process uses git, so a change to git can break process, while a change to process can't break git.
- Position
- Below the diagonal: process uses a module listed above it, which is the healthy direction.
7→38 process uses archive part of a loop✕
- Connections
- 1 pair of types, where a type in process uses a type in archive.
- The types involved
prek.process.Cmd→prek.archive.Error
- Direction
- process uses archive, so a change to archive can break process, while a change to process can't break archive.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→5 store uses config.repo✕
- Connections
- 2 pairs of types, where a type in store uses a type in config.repo.
- The types involved
prek.store.PendingClone→prek.config.repo.RemoteRepoprek.store.Store→prek.config.repo.RemoteRepo
- Direction
- store uses config.repo, so a change to config.repo can break store, while a change to store can't break config.repo.
- Position
- Below the diagonal: store uses a module listed above it, which is the healthy direction.
8→6 store uses git✕
- Connections
- 1 pair of types, where a type in store uses a type in git.
- The types involved
prek.store.Store→prek.git.TerminalPrompt
- Direction
- store uses git, so a change to git can break store, while a change to store can't break git.
- Position
- Below the diagonal: store uses a module listed above it, which is the healthy direction.
9→4 workspace uses cli.run.selector✕
- Connections
- 4 pairs of types, where a type in workspace uses a type in cli.run.selector.
- The types involved
prek.workspace.HookInitFilters→prek.cli.run.selector.ConfiguredHookprek.workspace.HookInitFilters→prek.cli.run.selector.GroupFiltersprek.workspace.HookInitFilters→prek.cli.run.selector.Selectorsprek.workspace.Workspace→prek.cli.run.selector.Selectors
- Direction
- workspace uses cli.run.selector, so a change to cli.run.selector can break workspace, while a change to workspace can't break cli.run.selector.
- Position
- Below the diagonal: workspace uses a module listed above it, which is the healthy direction.
9→5 workspace uses config.repo✕
- Connections
- 3 pairs of types, where a type in workspace uses a type in config.repo.
- The types involved
prek.workspace.HookInitFilters→prek.config.repo.RemoteRepoprek.workspace.ProjectInitPlan→prek.config.repo.Repoprek.workspace.workspace$module→prek.config.repo.RemoteRepo
- Direction
- workspace uses config.repo, so a change to config.repo can break workspace, while a change to workspace can't break config.repo.
- Position
- Below the diagonal: workspace uses a module listed above it, which is the healthy direction.
9→8 workspace uses store✕
- Connections
- 4 pairs of types, where a type in workspace uses a type in store.
- The types involved
prek.workspace.Project→prek.store.Storeprek.workspace.Workspace→prek.store.Storeprek.workspace.WorkspaceCache→prek.store.Storeprek.workspace.workspace$module→prek.store.Store
- Direction
- workspace uses store, so a change to store can break workspace, while a change to workspace can't break store.
- Position
- Below the diagonal: workspace uses a module listed above it, which is the healthy direction.
9→16 workspace uses config part of a loop✕
- Connections
- 1 pair of types, where a type in workspace uses a type in config.
- The types involved
prek.workspace.Project→prek.config.Config
- Direction
- workspace uses config, so a change to config can break workspace, while a change to workspace can't break config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 cli.run.reporter uses printer✕
- Connections
- 1 pair of types, where a type in cli.run.reporter uses a type in printer.
- The types involved
prek.cli.run.reporter.HookRunReporter→prek.printer.Printer
- Direction
- cli.run.reporter uses printer, so a change to printer can break cli.run.reporter, while a change to cli.run.reporter can't break printer.
- Position
- Below the diagonal: cli.run.reporter uses a module listed above it, which is the healthy direction.
10→7 cli.run.reporter uses process✕
- Connections
- 1 pair of types, where a type in cli.run.reporter uses a type in process.
- The types involved
prek.cli.run.reporter.HookOutputSink→prek.process.OutputSink
- Direction
- cli.run.reporter uses process, so a change to process can break cli.run.reporter, while a change to cli.run.reporter can't break process.
- Position
- Below the diagonal: cli.run.reporter uses a module listed above it, which is the healthy direction.
10→9 cli.run.reporter uses workspace✕
- Connections
- 1 pair of types, where a type in cli.run.reporter uses a type in workspace.
- The types involved
prek.cli.run.reporter.HookRunReporter→prek.workspace.Project
- Direction
- cli.run.reporter uses workspace, so a change to workspace can break cli.run.reporter, while a change to cli.run.reporter can't break workspace.
- Position
- Below the diagonal: cli.run.reporter uses a module listed above it, which is the healthy direction.
10→18 cli.run.reporter uses hook part of a loop✕
- Connections
- 4 pairs of types, where a type in cli.run.reporter uses a type in hook.
- The types involved
prek.cli.run.reporter.CompletedBars→prek.hook.HookKeyprek.cli.run.reporter.HookBar→prek.hook.Hookprek.cli.run.reporter.HookBar→prek.hook.HookKeyprek.cli.run.reporter.HookRunReporter→prek.hook.Hook
- Direction
- cli.run.reporter uses hook, so a change to hook can break cli.run.reporter, while a change to cli.run.reporter can't break hook.
- 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→21 cli.run.reporter uses cli.reporter part of a loop✕
- Connections
- 2 pairs of types, where a type in cli.run.reporter uses a type in cli.reporter.
- The types involved
prek.cli.run.reporter.HookBar→prek.cli.reporter.ProgressReporterprek.cli.run.reporter.HookRunReporter→prek.cli.reporter.ProgressReporter
- Direction
- cli.run.reporter uses cli.reporter, so a change to cli.reporter can break cli.run.reporter, while a change to cli.run.reporter can't break cli.reporter.
- 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→36 cli.run.reporter uses languages.r part of a loop✕
- Connections
- 1 pair of types, where a type in cli.run.reporter uses a type in languages.r.
- The types involved
prek.cli.run.reporter.HookRunReporter→prek.languages.r.R
- Direction
- cli.run.reporter uses languages.r, so a change to languages.r can break cli.run.reporter, while a change to cli.run.reporter can't break languages.r.
- 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→7 languages uses process✕
- Connections
- 1 pair of types, where a type in languages uses a type in process.
- The types involved
prek.languages.EnvironmentPatch→prek.process.Cmd
- Direction
- languages uses process, so a change to process can break languages, while a change to languages can't break process.
- Position
- Below the diagonal: languages uses a module listed above it, which is the healthy direction.
11→8 languages uses store✕
- Connections
- 1 pair of types, where a type in languages uses a type in store.
- The types involved
prek.languages.LanguageBackend→prek.store.Store
- Direction
- languages uses store, so a change to store can break languages, while a change to languages can't break store.
- Position
- Below the diagonal: languages uses a module listed above it, which is the healthy direction.
11→10 languages uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in languages uses a type in cli.run.reporter.
- The types involved
prek.languages.LanguageBackend→prek.cli.run.reporter.HookRunReporter
- Direction
- languages uses cli.run.reporter, so a change to cli.run.reporter can break languages, while a change to languages can't break cli.run.reporter.
- Position
- Below the diagonal: languages uses a module listed above it, which is the healthy direction.
11→18 languages uses hook part of a loop✕
- Connections
- 5 pairs of types, where a type in languages uses a type in hook.
- The types involved
prek.languages.ExecutionEnvironment→prek.hook.InstalledHookprek.languages.LanguageBackend→prek.hook.Hookprek.languages.LanguageBackend→prek.hook.InstallInfoprek.languages.LanguageBackend→prek.hook.InstalledHookprek.languages.languages$module→prek.hook.Hook
- Direction
- languages uses hook, so a change to hook can break languages, while a change to languages can't break hook.
- 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→21 languages uses cli.reporter part of a loop✕
- Connections
- 1 pair of types, where a type in languages uses a type in cli.reporter.
- The types involved
prek.languages.LanguageBackend→prek.cli.reporter.HookInstallReporter
- Direction
- languages uses cli.reporter, so a change to cli.reporter can break languages, while a change to languages can't break cli.reporter.
- 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 config.hook uses config.pattern✕
- Connections
- 2 pairs of types, where a type in config.hook uses a type in config.pattern.
- The types involved
prek.config.hook.HookOptions→prek.config.pattern.FilePatternprek.config.hook.HookWire→prek.config.pattern.FilePattern
- Direction
- config.hook uses config.pattern, so a change to config.pattern can break config.hook, while a change to config.hook can't break config.pattern.
- Position
- Below the diagonal: config.hook uses a module listed above it, which is the healthy direction.
12→8 config.hook uses store✕
- Connections
- 1 pair of types, where a type in config.hook uses a type in store.
- The types involved
prek.config.hook.Language→prek.store.Store
- Direction
- config.hook uses store, so a change to store can break config.hook, while a change to config.hook can't break store.
- Position
- Below the diagonal: config.hook uses a module listed above it, which is the healthy direction.
12→10 config.hook uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in config.hook uses a type in cli.run.reporter.
- The types involved
prek.config.hook.Language→prek.cli.run.reporter.HookRunReporter
- Direction
- config.hook uses cli.run.reporter, so a change to cli.run.reporter can break config.hook, while a change to config.hook can't break cli.run.reporter.
- Position
- Below the diagonal: config.hook uses a module listed above it, which is the healthy direction.
12→11 config.hook uses languages✕
- Connections
- 1 pair of types, where a type in config.hook uses a type in languages.
- The types involved
prek.config.hook.Language→prek.languages.ShellSupport
- Direction
- config.hook uses languages, so a change to languages can break config.hook, while a change to config.hook can't break languages.
- Position
- Below the diagonal: config.hook uses a module listed above it, which is the healthy direction.
12→18 config.hook uses hook part of a loop✕
- Connections
- 3 pairs of types, where a type in config.hook uses a type in hook.
- The types involved
prek.config.hook.Language→prek.hook.Hookprek.config.hook.Language→prek.hook.InstallInfoprek.config.hook.Language→prek.hook.InstalledHook
- Direction
- config.hook uses hook, so a change to hook can break config.hook, while a change to config.hook can't break hook.
- 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→21 config.hook uses cli.reporter part of a loop✕
- Connections
- 1 pair of types, where a type in config.hook uses a type in cli.reporter.
- The types involved
prek.config.hook.Language→prek.cli.reporter.HookInstallReporter
- Direction
- config.hook uses cli.reporter, so a change to cli.reporter can break config.hook, while a change to config.hook can't break cli.reporter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 cli.install uses printer✕
- Connections
- 1 pair of types, where a type in cli.install uses a type in printer.
- The types involved
prek.cli.install.install$module→prek.printer.Printer
- Direction
- cli.install uses printer, so a change to printer can break cli.install, while a change to cli.install can't break printer.
- Position
- Below the diagonal: cli.install uses a module listed above it, which is the healthy direction.
13→4 cli.install uses cli.run.selector✕
- Connections
- 1 pair of types, where a type in cli.install uses a type in cli.run.selector.
- The types involved
prek.cli.install.install$module→prek.cli.run.selector.Selectors
- Direction
- cli.install uses cli.run.selector, so a change to cli.run.selector can break cli.install, while a change to cli.install can't break cli.run.selector.
- Position
- Below the diagonal: cli.install uses a module listed above it, which is the healthy direction.
13→8 cli.install uses store✕
- Connections
- 1 pair of types, where a type in cli.install uses a type in store.
- The types involved
prek.cli.install.install$module→prek.store.Store
- Direction
- cli.install uses store, so a change to store can break cli.install, while a change to cli.install can't break store.
- Position
- Below the diagonal: cli.install uses a module listed above it, which is the healthy direction.
13→9 cli.install uses workspace✕
- Connections
- 1 pair of types, where a type in cli.install uses a type in workspace.
- The types involved
prek.cli.install.install$module→prek.workspace.Project
- Direction
- cli.install uses workspace, so a change to workspace can break cli.install, while a change to cli.install can't break workspace.
- Position
- Below the diagonal: cli.install uses a module listed above it, which is the healthy direction.
13→12 cli.install uses config.hook✕
- Connections
- 1 pair of types, where a type in cli.install uses a type in config.hook.
- The types involved
prek.cli.install.install$module→prek.config.hook.HookType
- Direction
- cli.install uses config.hook, so a change to config.hook can break cli.install, while a change to cli.install can't break config.hook.
- Position
- Below the diagonal: cli.install uses a module listed above it, which is the healthy direction.
14→2 cli.list uses printer✕
- Connections
- 1 pair of types, where a type in cli.list uses a type in printer.
- The types involved
prek.cli.list.list$module→prek.printer.Printer
- Direction
- cli.list uses printer, so a change to printer can break cli.list, while a change to cli.list can't break printer.
- Position
- Below the diagonal: cli.list uses a module listed above it, which is the healthy direction.
14→3 cli.list uses cli✕
- Connections
- 1 pair of types, where a type in cli.list uses a type in cli.
- The types involved
prek.cli.list.list$module→prek.cli.ListOutputFormat
- Direction
- cli.list uses cli, so a change to cli can break cli.list, while a change to cli.list can't break cli.
- Position
- Below the diagonal: cli.list uses a module listed above it, which is the healthy direction.
14→8 cli.list uses store✕
- Connections
- 1 pair of types, where a type in cli.list uses a type in store.
- The types involved
prek.cli.list.list$module→prek.store.Store
- Direction
- cli.list uses store, so a change to store can break cli.list, while a change to cli.list can't break store.
- Position
- Below the diagonal: cli.list uses a module listed above it, which is the healthy direction.
14→12 cli.list uses config.hook✕
- Connections
- 4 pairs of types, where a type in cli.list uses a type in config.hook.
- The types involved
prek.cli.list.SerializableHook→prek.config.hook.Languageprek.cli.list.SerializableHook→prek.config.hook.Stageprek.cli.list.list$module→prek.config.hook.Languageprek.cli.list.list$module→prek.config.hook.Stage
- Direction
- cli.list uses config.hook, so a change to config.hook can break cli.list, while a change to cli.list can't break config.hook.
- Position
- Below the diagonal: cli.list uses a module listed above it, which is the healthy direction.
15→2 cli.try_repo uses printer✕
- Connections
- 1 pair of types, where a type in cli.try_repo uses a type in printer.
- The types involved
prek.cli.try_repo.try_repo$module→prek.printer.Printer
- Direction
- cli.try_repo uses printer, so a change to printer can break cli.try_repo, while a change to cli.try_repo can't break printer.
- Position
- Below the diagonal: cli.try_repo uses a module listed above it, which is the healthy direction.
15→3 cli.try_repo uses cli✕
- Connections
- 1 pair of types, where a type in cli.try_repo uses a type in cli.
- The types involved
prek.cli.try_repo.try_repo$module→prek.cli.RunOptions
- Direction
- cli.try_repo uses cli, so a change to cli can break cli.try_repo, while a change to cli.try_repo can't break cli.
- Position
- Below the diagonal: cli.try_repo uses a module listed above it, which is the healthy direction.
15→4 cli.try_repo uses cli.run.selector✕
- Connections
- 1 pair of types, where a type in cli.try_repo uses a type in cli.run.selector.
- The types involved
prek.cli.try_repo.try_repo$module→prek.cli.run.selector.Selectors
- Direction
- cli.try_repo uses cli.run.selector, so a change to cli.run.selector can break cli.try_repo, while a change to cli.try_repo can't break cli.run.selector.
- Position
- Below the diagonal: cli.try_repo uses a module listed above it, which is the healthy direction.
15→12 cli.try_repo uses config.hook✕
- Connections
- 1 pair of types, where a type in cli.try_repo uses a type in config.hook.
- The types involved
prek.cli.try_repo.try_repo$module→prek.config.hook.Stage
- Direction
- cli.try_repo uses config.hook, so a change to config.hook can break cli.try_repo, while a change to cli.try_repo can't break config.hook.
- Position
- Below the diagonal: cli.try_repo uses a module listed above it, which is the healthy direction.
16→1 config uses config.pattern✕
- Connections
- 1 pair of types, where a type in config uses a type in config.pattern.
- The types involved
prek.config.Config→prek.config.pattern.FilePattern
- Direction
- config uses config.pattern, so a change to config.pattern can break config, while a change to config can't break config.pattern.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
16→5 config uses config.repo✕
- Connections
- 1 pair of types, where a type in config uses a type in config.repo.
- The types involved
prek.config.Config→prek.config.repo.Repo
- Direction
- config uses config.repo, so a change to config.repo can break config, while a change to config can't break config.repo.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
16→12 config uses config.hook✕
- Connections
- 2 pairs of types, where a type in config uses a type in config.hook.
- The types involved
prek.config.Config→prek.config.hook.HookTypeprek.config.Config→prek.config.hook.Stages
- Direction
- config uses config.hook, so a change to config.hook can break config, while a change to config can't break config.hook.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
17→12 languages.version uses config.hook✕
- Connections
- 5 pairs of types, where a type in languages.version uses a type in config.hook.
- The types involved
prek.languages.version.LanguageRequest→prek.config.hook.Languageprek.languages.version.LanguageRequest→prek.config.hook.LanguageVersionprek.languages.version.LanguageRequest→prek.config.hook.ToolchainPreferenceprek.languages.version.ToolchainPolicy→prek.config.hook.ToolchainPreferenceprek.languages.version.VersionRequest→prek.config.hook.Language
- Direction
- languages.version uses config.hook, so a change to config.hook can break languages.version, while a change to languages.version can't break config.hook.
- Position
- Below the diagonal: languages.version uses a module listed above it, which is the healthy direction.
17→18 languages.version uses hook part of a loop✕
- Connections
- 3 pairs of types, where a type in languages.version uses a type in hook.
- The types involved
prek.languages.version.LanguageRequest→prek.hook.InstallInfoprek.languages.version.SemverRequest→prek.hook.InstallInfoprek.languages.version.VersionRequest→prek.hook.InstallInfo
- Direction
- languages.version uses hook, so a change to hook can break languages.version, while a change to languages.version can't break hook.
- 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.
18→1 hook uses config.pattern✕
- Connections
- 1 pair of types, where a type in hook uses a type in config.pattern.
- The types involved
prek.hook.Hook→prek.config.pattern.FilePattern
- Direction
- hook uses config.pattern, so a change to config.pattern can break hook, while a change to hook can't break config.pattern.
- Position
- Below the diagonal: hook uses a module listed above it, which is the healthy direction.
18→5 hook uses config.repo✕
- Connections
- 2 pairs of types, where a type in hook uses a type in config.repo.
- The types involved
prek.hook.Hook→prek.config.repo.Repoprek.hook.HookSpec→prek.config.repo.Repo
- Direction
- hook uses config.repo, so a change to config.repo can break hook, while a change to hook can't break config.repo.
- Position
- Below the diagonal: hook uses a module listed above it, which is the healthy direction.
18→8 hook uses store✕
- Connections
- 1 pair of types, where a type in hook uses a type in store.
- The types involved
prek.hook.InstalledHook→prek.store.Store
- Direction
- hook uses store, so a change to store can break hook, while a change to hook can't break store.
- Position
- Below the diagonal: hook uses a module listed above it, which is the healthy direction.
18→9 hook uses workspace✕
- Connections
- 1 pair of types, where a type in hook uses a type in workspace.
- The types involved
prek.hook.Hook→prek.workspace.Project
- Direction
- hook uses workspace, so a change to workspace can break hook, while a change to hook can't break workspace.
- Position
- Below the diagonal: hook uses a module listed above it, which is the healthy direction.
18→12 hook uses config.hook✕
- Connections
- 14 pairs of types, where a type in hook uses a type in config.hook.
- The types involved
prek.hook.Hook→prek.config.hook.Languageprek.hook.Hook→prek.config.hook.PassFilenamesprek.hook.Hook→prek.config.hook.Stagesprek.hook.HookEnvRequirement→prek.config.hook.Languageprek.hook.HookEnvRequirementRef→prek.config.hook.Languageprek.hook.HookSpec→prek.config.hook.BuiltinHookprek.hook.HookSpec→prek.config.hook.HookOptionsprek.hook.HookSpec→prek.config.hook.Languageprek.hook.HookSpec→prek.config.hook.LocalHookprek.hook.HookSpec→prek.config.hook.ManifestHookprek.hook.HookSpec→prek.config.hook.MetaHookprek.hook.HookSpec→prek.config.hook.RemoteHookprek.hook.InstallInfo→prek.config.hook.Languageprek.hook.Repo→prek.config.hook.ManifestHook
- Direction
- hook uses config.hook, so a change to config.hook can break hook, while a change to hook can't break config.hook.
- Position
- Below the diagonal: hook uses a module listed above it, which is the healthy direction.
18→16 hook uses config✕
- Connections
- 2 pairs of types, where a type in hook uses a type in config.
- The types involved
prek.hook.HookEnvRequirement→prek.config.Configprek.hook.HookSpec→prek.config.Config
- Direction
- hook uses config, so a change to config can break hook, while a change to hook can't break config.
- Position
- Below the diagonal: hook uses a module listed above it, which is the healthy direction.
18→17 hook uses languages.version✕
- Connections
- 3 pairs of types, where a type in hook uses a type in languages.version.
- The types involved
prek.hook.Hook→prek.languages.version.LanguageRequestprek.hook.HookEnvRequirement→prek.languages.version.LanguageRequestprek.hook.HookEnvRequirementRef→prek.languages.version.LanguageRequest
- Direction
- hook uses languages.version, so a change to languages.version can break hook, while a change to hook can't break languages.version.
- Position
- Below the diagonal: hook uses a module listed above it, which is the healthy direction.
18→38 hook uses archive part of a loop✕
- Connections
- 1 pair of types, where a type in hook uses a type in archive.
- The types involved
prek.hook.hook$module→prek.archive.Error
- Direction
- hook uses archive, so a change to archive can break hook, while a change to hook can't break archive.
- 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.
19→16 settings uses config✕
- Connections
- 1 pair of types, where a type in settings uses a type in config.
- The types involved
prek.settings.Options→prek.config.HideStatus
- Direction
- settings uses config, so a change to config can break settings, while a change to settings can't break config.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
20→2 cli.cache_gc uses printer✕
- Connections
- 1 pair of types, where a type in cli.cache_gc uses a type in printer.
- The types involved
prek.cli.cache_gc.cache_gc$module→prek.printer.Printer
- Direction
- cli.cache_gc uses printer, so a change to printer can break cli.cache_gc, while a change to cli.cache_gc can't break printer.
- Position
- Below the diagonal: cli.cache_gc uses a module listed above it, which is the healthy direction.
20→8 cli.cache_gc uses store✕
- Connections
- 2 pairs of types, where a type in cli.cache_gc uses a type in store.
- The types involved
prek.cli.cache_gc.cache_gc$module→prek.store.Storeprek.cli.cache_gc.cache_gc$module→prek.store.ToolBucket
- Direction
- cli.cache_gc uses store, so a change to store can break cli.cache_gc, while a change to cli.cache_gc can't break store.
- Position
- Below the diagonal: cli.cache_gc uses a module listed above it, which is the healthy direction.
20→16 cli.cache_gc uses config✕
- Connections
- 1 pair of types, where a type in cli.cache_gc uses a type in config.
- The types involved
prek.cli.cache_gc.cache_gc$module→prek.config.Config
- Direction
- cli.cache_gc uses config, so a change to config can break cli.cache_gc, while a change to cli.cache_gc can't break config.
- Position
- Below the diagonal: cli.cache_gc uses a module listed above it, which is the healthy direction.
20→18 cli.cache_gc uses hook✕
- Connections
- 2 pairs of types, where a type in cli.cache_gc uses a type in hook.
- The types involved
prek.cli.cache_gc.cache_gc$module→prek.hook.HookEnvRequirementprek.cli.cache_gc.cache_gc$module→prek.hook.InstallInfo
- Direction
- cli.cache_gc uses hook, so a change to hook can break cli.cache_gc, while a change to cli.cache_gc can't break hook.
- Position
- Below the diagonal: cli.cache_gc uses a module listed above it, which is the healthy direction.
21→2 cli.reporter uses printer✕
- Connections
- 5 pairs of types, where a type in cli.reporter uses a type in printer.
- The types involved
prek.cli.reporter.CleaningReporter→prek.printer.Printerprek.cli.reporter.HookInitReporter→prek.printer.Printerprek.cli.reporter.HookInstallReporter→prek.printer.Printerprek.cli.reporter.ProgressReporter→prek.printer.Printerprek.cli.reporter.UpdateReporter→prek.printer.Printer
- Direction
- cli.reporter uses printer, so a change to printer can break cli.reporter, while a change to cli.reporter can't break printer.
- Position
- Below the diagonal: cli.reporter uses a module listed above it, which is the healthy direction.
21→18 cli.reporter uses hook✕
- Connections
- 1 pair of types, where a type in cli.reporter uses a type in hook.
- The types involved
prek.cli.reporter.HookInstallReporter→prek.hook.Hook
- Direction
- cli.reporter uses hook, so a change to hook can break cli.reporter, while a change to cli.reporter can't break hook.
- Position
- Below the diagonal: cli.reporter uses a module listed above it, which is the healthy direction.
22→1 cli.run.filter uses config.pattern✕
- Connections
- 1 pair of types, where a type in cli.run.filter uses a type in config.pattern.
- The types involved
prek.cli.run.filter.FilenameFilter→prek.config.pattern.FilePattern
- Direction
- cli.run.filter uses config.pattern, so a change to config.pattern can break cli.run.filter, while a change to cli.run.filter can't break config.pattern.
- Position
- Below the diagonal: cli.run.filter uses a module listed above it, which is the healthy direction.
22→3 cli.run.filter uses cli✕
- Connections
- 1 pair of types, where a type in cli.run.filter uses a type in cli.
- The types involved
prek.cli.run.filter.FileSelection→prek.cli.FileSelectionArgs
- Direction
- cli.run.filter uses cli, so a change to cli can break cli.run.filter, while a change to cli.run.filter can't break cli.
- Position
- Below the diagonal: cli.run.filter uses a module listed above it, which is the healthy direction.
22→6 cli.run.filter uses git✕
- Connections
- 1 pair of types, where a type in cli.run.filter uses a type in git.
- The types involved
prek.cli.run.filter.filter$module→prek.git.FileMode
- Direction
- cli.run.filter uses git, so a change to git can break cli.run.filter, while a change to cli.run.filter can't break git.
- Position
- Below the diagonal: cli.run.filter uses a module listed above it, which is the healthy direction.
22→9 cli.run.filter uses workspace✕
- Connections
- 2 pairs of types, where a type in cli.run.filter uses a type in workspace.
- The types involved
prek.cli.run.filter.ProjectFiles→prek.workspace.Projectprek.cli.run.filter.RunFileIndex→prek.workspace.Project
- Direction
- cli.run.filter uses workspace, so a change to workspace can break cli.run.filter, while a change to cli.run.filter can't break workspace.
- Position
- Below the diagonal: cli.run.filter uses a module listed above it, which is the healthy direction.
22→12 cli.run.filter uses config.hook✕
- Connections
- 2 pairs of types, where a type in cli.run.filter uses a type in config.hook.
- The types involved
prek.cli.run.filter.RunInputMode→prek.config.hook.Stageprek.cli.run.filter.filter$module→prek.config.hook.Stage
- Direction
- cli.run.filter uses config.hook, so a change to config.hook can break cli.run.filter, while a change to cli.run.filter can't break config.hook.
- Position
- Below the diagonal: cli.run.filter uses a module listed above it, which is the healthy direction.
22→18 cli.run.filter uses hook✕
- Connections
- 2 pairs of types, where a type in cli.run.filter uses a type in hook.
- The types involved
prek.cli.run.filter.HookFileFilter→prek.hook.Hookprek.cli.run.filter.ProjectFiles→prek.hook.Hook
- Direction
- cli.run.filter uses hook, so a change to hook can break cli.run.filter, while a change to cli.run.filter can't break hook.
- Position
- Below the diagonal: cli.run.filter uses a module listed above it, which is the healthy direction.
23→1 cli.update uses config.pattern✕
- Connections
- 1 pair of types, where a type in cli.update uses a type in config.pattern.
- The types involved
prek.cli.update.TagFilters→prek.config.pattern.GlobPatterns
- Direction
- cli.update uses config.pattern, so a change to config.pattern can break cli.update, while a change to cli.update can't break config.pattern.
- Position
- Below the diagonal: cli.update uses a module listed above it, which is the healthy direction.
23→2 cli.update uses printer✕
- Connections
- 1 pair of types, where a type in cli.update uses a type in printer.
- The types involved
prek.cli.update.update$module→prek.printer.Printer
- Direction
- cli.update uses printer, so a change to printer can break cli.update, while a change to cli.update can't break printer.
- Position
- Below the diagonal: cli.update uses a module listed above it, which is the healthy direction.
23→3 cli.update uses cli✕
- Connections
- 1 pair of types, where a type in cli.update uses a type in cli.
- The types involved
prek.cli.update.update$module→prek.cli.RepoTagPattern
- Direction
- cli.update uses cli, so a change to cli can break cli.update, while a change to cli.update can't break cli.
- Position
- Below the diagonal: cli.update uses a module listed above it, which is the healthy direction.
23→8 cli.update uses store✕
- Connections
- 1 pair of types, where a type in cli.update uses a type in store.
- The types involved
prek.cli.update.update$module→prek.store.Store
- Direction
- cli.update uses store, so a change to store can break cli.update, while a change to cli.update can't break store.
- Position
- Below the diagonal: cli.update uses a module listed above it, which is the healthy direction.
23→9 cli.update uses workspace✕
- Connections
- 7 pairs of types, where a type in cli.update uses a type in workspace.
- The types involved
prek.cli.update.DisplayEvent→prek.workspace.Projectprek.cli.update.FrozenMismatch→prek.workspace.Projectprek.cli.update.FrozenWarningEvent→prek.workspace.Projectprek.cli.update.ProjectUpdateKey→prek.workspace.Projectprek.cli.update.RepoUsage→prek.workspace.Projectprek.cli.update.update$module→prek.workspace.Projectprek.cli.update.update$module→prek.workspace.Workspace
- Direction
- cli.update uses workspace, so a change to workspace can break cli.update, while a change to cli.update can't break workspace.
- Position
- Below the diagonal: cli.update uses a module listed above it, which is the healthy direction.
23→19 cli.update uses settings✕
- Connections
- 3 pairs of types, where a type in cli.update uses a type in settings.
- The types involved
prek.cli.update.TagFilters→prek.settings.TagFilterOptionsprek.cli.update.update$module→prek.settings.CliTagFilterOptionsprek.cli.update.update$module→prek.settings.FilesystemOptions
- Direction
- cli.update uses settings, so a change to settings can break cli.update, while a change to cli.update can't break settings.
- Position
- Below the diagonal: cli.update uses a module listed above it, which is the healthy direction.
24→8 hooks uses store✕
- Connections
- 1 pair of types, where a type in hooks uses a type in store.
- The types involved
prek.hooks.hooks$module→prek.store.Store
- Direction
- hooks uses store, so a change to store can break hooks, while a change to hooks can't break store.
- Position
- Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
24→10 hooks uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in hooks uses a type in cli.run.reporter.
- The types involved
prek.hooks.hooks$module→prek.cli.run.reporter.HookRunReporter
- Direction
- hooks uses cli.run.reporter, so a change to cli.run.reporter can break hooks, while a change to hooks can't break cli.run.reporter.
- Position
- Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
24→18 hooks uses hook✕
- Connections
- 1 pair of types, where a type in hooks uses a type in hook.
- The types involved
prek.hooks.hooks$module→prek.hook.Hook
- Direction
- hooks uses hook, so a change to hook can break hooks, while a change to hooks can't break hook.
- Position
- Below the diagonal: hooks uses a module listed above it, which is the healthy direction.
25→3 hooks.builtin_hooks uses cli✕
- Connections
- 1 pair of types, where a type in hooks.builtin_hooks uses a type in cli.
- The types involved
prek.hooks.builtin_hooks.BuiltinHooks→prek.cli.Command
- Direction
- hooks.builtin_hooks uses cli, so a change to cli can break hooks.builtin_hooks, while a change to hooks.builtin_hooks can't break cli.
- Position
- Below the diagonal: hooks.builtin_hooks uses a module listed above it, which is the healthy direction.
25→8 hooks.builtin_hooks uses store✕
- Connections
- 1 pair of types, where a type in hooks.builtin_hooks uses a type in store.
- The types involved
prek.hooks.builtin_hooks.BuiltinHooks→prek.store.Store
- Direction
- hooks.builtin_hooks uses store, so a change to store can break hooks.builtin_hooks, while a change to hooks.builtin_hooks can't break store.
- Position
- Below the diagonal: hooks.builtin_hooks uses a module listed above it, which is the healthy direction.
25→10 hooks.builtin_hooks uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in hooks.builtin_hooks uses a type in cli.run.reporter.
- The types involved
prek.hooks.builtin_hooks.BuiltinHooks→prek.cli.run.reporter.HookRunReporter
- Direction
- hooks.builtin_hooks uses cli.run.reporter, so a change to cli.run.reporter can break hooks.builtin_hooks, while a change to hooks.builtin_hooks can't break cli.run.reporter.
- Position
- Below the diagonal: hooks.builtin_hooks uses a module listed above it, which is the healthy direction.
25→18 hooks.builtin_hooks uses hook✕
- Connections
- 1 pair of types, where a type in hooks.builtin_hooks uses a type in hook.
- The types involved
prek.hooks.builtin_hooks.BuiltinHooks→prek.hook.Hook
- Direction
- hooks.builtin_hooks uses hook, so a change to hook can break hooks.builtin_hooks, while a change to hooks.builtin_hooks can't break hook.
- Position
- Below the diagonal: hooks.builtin_hooks uses a module listed above it, which is the healthy direction.
26→8 cli.run.install uses store✕
- Connections
- 2 pairs of types, where a type in cli.run.install uses a type in store.
- The types involved
prek.cli.run.install.InstallCache→prek.store.Storeprek.cli.run.install.install$module→prek.store.Store
- Direction
- cli.run.install uses store, so a change to store can break cli.run.install, while a change to cli.run.install can't break store.
- Position
- Below the diagonal: cli.run.install uses a module listed above it, which is the healthy direction.
26→12 cli.run.install uses config.hook✕
- Connections
- 1 pair of types, where a type in cli.run.install uses a type in config.hook.
- The types involved
prek.cli.run.install.install$module→prek.config.hook.Language
- Direction
- cli.run.install uses config.hook, so a change to config.hook can break cli.run.install, while a change to cli.run.install can't break config.hook.
- Position
- Below the diagonal: cli.run.install uses a module listed above it, which is the healthy direction.
26→18 cli.run.install uses hook✕
- Connections
- 4 pairs of types, where a type in cli.run.install uses a type in hook.
- The types involved
prek.cli.run.install.CachedInstallInfo→prek.hook.InstallInfoprek.cli.run.install.InstallCache→prek.hook.Hookprek.cli.run.install.InstallCache→prek.hook.InstalledHookprek.cli.run.install.install$module→prek.hook.Hook
- Direction
- cli.run.install uses hook, so a change to hook can break cli.run.install, while a change to cli.run.install can't break hook.
- Position
- Below the diagonal: cli.run.install uses a module listed above it, which is the healthy direction.
26→21 cli.run.install uses cli.reporter✕
- Connections
- 1 pair of types, where a type in cli.run.install uses a type in cli.reporter.
- The types involved
prek.cli.run.install.install$module→prek.cli.reporter.HookInstallReporter
- Direction
- cli.run.install uses cli.reporter, so a change to cli.reporter can break cli.run.install, while a change to cli.run.install can't break cli.reporter.
- Position
- Below the diagonal: cli.run.install uses a module listed above it, which is the healthy direction.
27→2 cli.run.run uses printer✕
- Connections
- 3 pairs of types, where a type in cli.run.run uses a type in printer.
- The types involved
prek.cli.run.run.HookRunSession→prek.printer.Printerprek.cli.run.run.StatusPrinter→prek.printer.Printerprek.cli.run.run.run$module→prek.printer.Printer
- Direction
- cli.run.run uses printer, so a change to printer can break cli.run.run, while a change to cli.run.run can't break printer.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→3 cli.run.run uses cli✕
- Connections
- 2 pairs of types, where a type in cli.run.run uses a type in cli.
- The types involved
prek.cli.run.run.run$module→prek.cli.RunArgsprek.cli.run.run.run$module→prek.cli.RunExtraArgs
- Direction
- cli.run.run uses cli, so a change to cli can break cli.run.run, while a change to cli.run.run can't break cli.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→4 cli.run.run uses cli.run.selector✕
- Connections
- 1 pair of types, where a type in cli.run.run uses a type in cli.run.selector.
- The types involved
prek.cli.run.run.run$module→prek.cli.run.selector.Selectors
- Direction
- cli.run.run uses cli.run.selector, so a change to cli.run.selector can break cli.run.run, while a change to cli.run.run can't break cli.run.selector.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→8 cli.run.run uses store✕
- Connections
- 2 pairs of types, where a type in cli.run.run uses a type in store.
- The types involved
prek.cli.run.run.HookRunSession→prek.store.Storeprek.cli.run.run.run$module→prek.store.Store
- Direction
- cli.run.run uses store, so a change to store can break cli.run.run, while a change to cli.run.run can't break store.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→9 cli.run.run uses workspace✕
- Connections
- 6 pairs of types, where a type in cli.run.run uses a type in workspace.
- The types involved
prek.cli.run.run.HookRunSession→prek.workspace.Projectprek.cli.run.run.HookRunSession→prek.workspace.Workspaceprek.cli.run.run.ProjectHookInput→prek.workspace.Projectprek.cli.run.run.ProjectRun→prek.workspace.Projectprek.cli.run.run.ProjectRunResult→prek.workspace.Projectprek.cli.run.run.run$module→prek.workspace.Workspace
- Direction
- cli.run.run uses workspace, so a change to workspace can break cli.run.run, while a change to cli.run.run can't break workspace.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→10 cli.run.run uses cli.run.reporter✕
- Connections
- 2 pairs of types, where a type in cli.run.run uses a type in cli.run.reporter.
- The types involved
prek.cli.run.run.HookRunSession→prek.cli.run.reporter.HookRunReporterprek.cli.run.run.run$module→prek.cli.run.reporter.HookRunReporter
- Direction
- cli.run.run uses cli.run.reporter, so a change to cli.run.reporter can break cli.run.run, while a change to cli.run.run can't break cli.run.reporter.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→12 cli.run.run uses config.hook✕
- Connections
- 1 pair of types, where a type in cli.run.run uses a type in config.hook.
- The types involved
prek.cli.run.run.run$module→prek.config.hook.Stage
- Direction
- cli.run.run uses config.hook, so a change to config.hook can break cli.run.run, while a change to cli.run.run can't break config.hook.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→16 cli.run.run uses config✕
- Connections
- 1 pair of types, where a type in cli.run.run uses a type in config.
- The types involved
prek.cli.run.run.RunStatus→prek.config.HideStatus
- Direction
- cli.run.run uses config, so a change to config can break cli.run.run, while a change to cli.run.run can't break config.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→18 cli.run.run uses hook✕
- Connections
- 3 pairs of types, where a type in cli.run.run uses a type in hook.
- The types involved
prek.cli.run.run.ProjectHookInput→prek.hook.Hookprek.cli.run.run.run$module→prek.hook.Hookprek.cli.run.run.run$module→prek.hook.InstalledHook
- Direction
- cli.run.run uses hook, so a change to hook can break cli.run.run, while a change to cli.run.run can't break hook.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→19 cli.run.run uses settings✕
- Connections
- 1 pair of types, where a type in cli.run.run uses a type in settings.
- The types involved
prek.cli.run.run.run$module→prek.settings.FilesystemOptions
- Direction
- cli.run.run uses settings, so a change to settings can break cli.run.run, while a change to cli.run.run can't break settings.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→22 cli.run.run uses cli.run.filter✕
- Connections
- 9 pairs of types, where a type in cli.run.run uses a type in cli.run.filter.
- The types involved
prek.cli.run.run.HookRunSession→prek.cli.run.filter.FileTagCacheprek.cli.run.run.HookRunSession→prek.cli.run.filter.RunFileIndexprek.cli.run.run.HookRunSession→prek.cli.run.filter.RunInputprek.cli.run.run.ProjectHookInput→prek.cli.run.filter.FileTagCacheprek.cli.run.run.ProjectHookInput→prek.cli.run.filter.RunFileIndexprek.cli.run.run.ProjectHookInput→prek.cli.run.filter.RunInputprek.cli.run.run.run$module→prek.cli.run.filter.FileTagCacheprek.cli.run.run.run$module→prek.cli.run.filter.RunFileIndexprek.cli.run.run.run$module→prek.cli.run.filter.RunInput
- Direction
- cli.run.run uses cli.run.filter, so a change to cli.run.filter can break cli.run.run, while a change to cli.run.run can't break cli.run.filter.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
27→24 cli.run.run uses hooks✕
- Connections
- 1 pair of types, where a type in cli.run.run uses a type in hooks.
- The types involved
prek.cli.run.run.HookRunResult→prek.hooks.FileChanges
- Direction
- cli.run.run uses hooks, so a change to hooks can break cli.run.run, while a change to cli.run.run can't break hooks.
- Position
- Below the diagonal: cli.run.run uses a module listed above it, which is the healthy direction.
28→1 hooks.meta_hooks uses config.pattern✕
- Connections
- 1 pair of types, where a type in hooks.meta_hooks uses a type in config.pattern.
- The types involved
prek.hooks.meta_hooks.meta_hooks$module→prek.config.pattern.FilePattern
- Direction
- hooks.meta_hooks uses config.pattern, so a change to config.pattern can break hooks.meta_hooks, while a change to hooks.meta_hooks can't break config.pattern.
- Position
- Below the diagonal: hooks.meta_hooks uses a module listed above it, which is the healthy direction.
28→8 hooks.meta_hooks uses store✕
- Connections
- 2 pairs of types, where a type in hooks.meta_hooks uses a type in store.
- The types involved
prek.hooks.meta_hooks.MetaHooks→prek.store.Storeprek.hooks.meta_hooks.meta_hooks$module→prek.store.Store
- Direction
- hooks.meta_hooks uses store, so a change to store can break hooks.meta_hooks, while a change to hooks.meta_hooks can't break store.
- Position
- Below the diagonal: hooks.meta_hooks uses a module listed above it, which is the healthy direction.
28→10 hooks.meta_hooks uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in hooks.meta_hooks uses a type in cli.run.reporter.
- The types involved
prek.hooks.meta_hooks.MetaHooks→prek.cli.run.reporter.HookRunReporter
- Direction
- hooks.meta_hooks uses cli.run.reporter, so a change to cli.run.reporter can break hooks.meta_hooks, while a change to hooks.meta_hooks can't break cli.run.reporter.
- Position
- Below the diagonal: hooks.meta_hooks uses a module listed above it, which is the healthy direction.
28→18 hooks.meta_hooks uses hook✕
- Connections
- 2 pairs of types, where a type in hooks.meta_hooks uses a type in hook.
- The types involved
prek.hooks.meta_hooks.MetaHooks→prek.hook.Hookprek.hooks.meta_hooks.meta_hooks$module→prek.hook.Hook
- Direction
- hooks.meta_hooks uses hook, so a change to hook can break hooks.meta_hooks, while a change to hooks.meta_hooks can't break hook.
- Position
- Below the diagonal: hooks.meta_hooks uses a module listed above it, which is the healthy direction.
28→24 hooks.meta_hooks uses hooks✕
- Connections
- 1 pair of types, where a type in hooks.meta_hooks uses a type in hooks.
- The types involved
prek.hooks.meta_hooks.meta_hooks$module→prek.hooks.HookOutput
- Direction
- hooks.meta_hooks uses hooks, so a change to hooks can break hooks.meta_hooks, while a change to hooks.meta_hooks can't break hooks.
- Position
- Below the diagonal: hooks.meta_hooks uses a module listed above it, which is the healthy direction.
29→7 languages.docker uses process✕
- Connections
- 1 pair of types, where a type in languages.docker uses a type in process.
- The types involved
prek.languages.docker.Docker→prek.process.Cmd
- Direction
- languages.docker uses process, so a change to process can break languages.docker, while a change to languages.docker can't break process.
- Position
- Below the diagonal: languages.docker uses a module listed above it, which is the healthy direction.
29→8 languages.docker uses store✕
- Connections
- 1 pair of types, where a type in languages.docker uses a type in store.
- The types involved
prek.languages.docker.Docker→prek.store.Store
- Direction
- languages.docker uses store, so a change to store can break languages.docker, while a change to languages.docker can't break store.
- Position
- Below the diagonal: languages.docker uses a module listed above it, which is the healthy direction.
29→10 languages.docker uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in languages.docker uses a type in cli.run.reporter.
- The types involved
prek.languages.docker.Docker→prek.cli.run.reporter.HookRunReporter
- Direction
- languages.docker uses cli.run.reporter, so a change to cli.run.reporter can break languages.docker, while a change to languages.docker can't break cli.run.reporter.
- Position
- Below the diagonal: languages.docker uses a module listed above it, which is the healthy direction.
29→11 languages.docker uses languages✕
- Connections
- 1 pair of types, where a type in languages.docker uses a type in languages.
- The types involved
prek.languages.docker.Docker→prek.languages.LanguageBackend
- Direction
- languages.docker uses languages, so a change to languages can break languages.docker, while a change to languages.docker can't break languages.
- Position
- Below the diagonal: languages.docker uses a module listed above it, which is the healthy direction.
29→18 languages.docker uses hook✕
- Connections
- 3 pairs of types, where a type in languages.docker uses a type in hook.
- The types involved
prek.languages.docker.Docker→prek.hook.Hookprek.languages.docker.Docker→prek.hook.InstallInfoprek.languages.docker.Docker→prek.hook.InstalledHook
- Direction
- languages.docker uses hook, so a change to hook can break languages.docker, while a change to languages.docker can't break hook.
- Position
- Below the diagonal: languages.docker uses a module listed above it, which is the healthy direction.
29→21 languages.docker uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.docker uses a type in cli.reporter.
- The types involved
prek.languages.docker.Docker→prek.cli.reporter.HookInstallReporter
- Direction
- languages.docker uses cli.reporter, so a change to cli.reporter can break languages.docker, while a change to languages.docker can't break cli.reporter.
- Position
- Below the diagonal: languages.docker uses a module listed above it, which is the healthy direction.
30→8 languages.docker_image uses store✕
- Connections
- 1 pair of types, where a type in languages.docker_image uses a type in store.
- The types involved
prek.languages.docker_image.DockerImage→prek.store.Store
- Direction
- languages.docker_image uses store, so a change to store can break languages.docker_image, while a change to languages.docker_image can't break store.
- Position
- Below the diagonal: languages.docker_image uses a module listed above it, which is the healthy direction.
30→10 languages.docker_image uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in languages.docker_image uses a type in cli.run.reporter.
- The types involved
prek.languages.docker_image.DockerImage→prek.cli.run.reporter.HookRunReporter
- Direction
- languages.docker_image uses cli.run.reporter, so a change to cli.run.reporter can break languages.docker_image, while a change to languages.docker_image can't break cli.run.reporter.
- Position
- Below the diagonal: languages.docker_image uses a module listed above it, which is the healthy direction.
30→11 languages.docker_image uses languages✕
- Connections
- 1 pair of types, where a type in languages.docker_image uses a type in languages.
- The types involved
prek.languages.docker_image.DockerImage→prek.languages.LanguageBackend
- Direction
- languages.docker_image uses languages, so a change to languages can break languages.docker_image, while a change to languages.docker_image can't break languages.
- Position
- Below the diagonal: languages.docker_image uses a module listed above it, which is the healthy direction.
30→18 languages.docker_image uses hook✕
- Connections
- 3 pairs of types, where a type in languages.docker_image uses a type in hook.
- The types involved
prek.languages.docker_image.DockerImage→prek.hook.Hookprek.languages.docker_image.DockerImage→prek.hook.InstallInfoprek.languages.docker_image.DockerImage→prek.hook.InstalledHook
- Direction
- languages.docker_image uses hook, so a change to hook can break languages.docker_image, while a change to languages.docker_image can't break hook.
- Position
- Below the diagonal: languages.docker_image uses a module listed above it, which is the healthy direction.
30→21 languages.docker_image uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.docker_image uses a type in cli.reporter.
- The types involved
prek.languages.docker_image.DockerImage→prek.cli.reporter.HookInstallReporter
- Direction
- languages.docker_image uses cli.reporter, so a change to cli.reporter can break languages.docker_image, while a change to languages.docker_image can't break cli.reporter.
- Position
- Below the diagonal: languages.docker_image uses a module listed above it, which is the healthy direction.
31→8 languages.fail uses store✕
- Connections
- 1 pair of types, where a type in languages.fail uses a type in store.
- The types involved
prek.languages.fail.Fail→prek.store.Store
- Direction
- languages.fail uses store, so a change to store can break languages.fail, while a change to languages.fail can't break store.
- Position
- Below the diagonal: languages.fail uses a module listed above it, which is the healthy direction.
31→10 languages.fail uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in languages.fail uses a type in cli.run.reporter.
- The types involved
prek.languages.fail.Fail→prek.cli.run.reporter.HookRunReporter
- Direction
- languages.fail uses cli.run.reporter, so a change to cli.run.reporter can break languages.fail, while a change to languages.fail can't break cli.run.reporter.
- Position
- Below the diagonal: languages.fail uses a module listed above it, which is the healthy direction.
31→11 languages.fail uses languages✕
- Connections
- 1 pair of types, where a type in languages.fail uses a type in languages.
- The types involved
prek.languages.fail.Fail→prek.languages.LanguageBackend
- Direction
- languages.fail uses languages, so a change to languages can break languages.fail, while a change to languages.fail can't break languages.
- Position
- Below the diagonal: languages.fail uses a module listed above it, which is the healthy direction.
31→18 languages.fail uses hook✕
- Connections
- 3 pairs of types, where a type in languages.fail uses a type in hook.
- The types involved
prek.languages.fail.Fail→prek.hook.Hookprek.languages.fail.Fail→prek.hook.InstallInfoprek.languages.fail.Fail→prek.hook.InstalledHook
- Direction
- languages.fail uses hook, so a change to hook can break languages.fail, while a change to languages.fail can't break hook.
- Position
- Below the diagonal: languages.fail uses a module listed above it, which is the healthy direction.
31→21 languages.fail uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.fail uses a type in cli.reporter.
- The types involved
prek.languages.fail.Fail→prek.cli.reporter.HookInstallReporter
- Direction
- languages.fail uses cli.reporter, so a change to cli.reporter can break languages.fail, while a change to languages.fail can't break cli.reporter.
- Position
- Below the diagonal: languages.fail uses a module listed above it, which is the healthy direction.
32→8 languages.julia uses store✕
- Connections
- 1 pair of types, where a type in languages.julia uses a type in store.
- The types involved
prek.languages.julia.Julia→prek.store.Store
- Direction
- languages.julia uses store, so a change to store can break languages.julia, while a change to languages.julia can't break store.
- Position
- Below the diagonal: languages.julia uses a module listed above it, which is the healthy direction.
32→10 languages.julia uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in languages.julia uses a type in cli.run.reporter.
- The types involved
prek.languages.julia.Julia→prek.cli.run.reporter.HookRunReporter
- Direction
- languages.julia uses cli.run.reporter, so a change to cli.run.reporter can break languages.julia, while a change to languages.julia can't break cli.run.reporter.
- Position
- Below the diagonal: languages.julia uses a module listed above it, which is the healthy direction.
32→11 languages.julia uses languages✕
- Connections
- 1 pair of types, where a type in languages.julia uses a type in languages.
- The types involved
prek.languages.julia.Julia→prek.languages.LanguageBackend
- Direction
- languages.julia uses languages, so a change to languages can break languages.julia, while a change to languages.julia can't break languages.
- Position
- Below the diagonal: languages.julia uses a module listed above it, which is the healthy direction.
32→18 languages.julia uses hook✕
- Connections
- 3 pairs of types, where a type in languages.julia uses a type in hook.
- The types involved
prek.languages.julia.Julia→prek.hook.Hookprek.languages.julia.Julia→prek.hook.InstallInfoprek.languages.julia.Julia→prek.hook.InstalledHook
- Direction
- languages.julia uses hook, so a change to hook can break languages.julia, while a change to languages.julia can't break hook.
- Position
- Below the diagonal: languages.julia uses a module listed above it, which is the healthy direction.
32→21 languages.julia uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.julia uses a type in cli.reporter.
- The types involved
prek.languages.julia.Julia→prek.cli.reporter.HookInstallReporter
- Direction
- languages.julia uses cli.reporter, so a change to cli.reporter can break languages.julia, while a change to languages.julia can't break cli.reporter.
- Position
- Below the diagonal: languages.julia uses a module listed above it, which is the healthy direction.
33→7 languages.node.node uses process✕
- Connections
- 1 pair of types, where a type in languages.node.node uses a type in process.
- The types involved
prek.languages.node.node.Npm→prek.process.Cmd
- Direction
- languages.node.node uses process, so a change to process can break languages.node.node, while a change to languages.node.node can't break process.
- Position
- Below the diagonal: languages.node.node uses a module listed above it, which is the healthy direction.
33→8 languages.node.node uses store✕
- Connections
- 1 pair of types, where a type in languages.node.node uses a type in store.
- The types involved
prek.languages.node.node.Node→prek.store.Store
- Direction
- languages.node.node uses store, so a change to store can break languages.node.node, while a change to languages.node.node can't break store.
- Position
- Below the diagonal: languages.node.node uses a module listed above it, which is the healthy direction.
33→11 languages.node.node uses languages✕
- Connections
- 1 pair of types, where a type in languages.node.node uses a type in languages.
- The types involved
prek.languages.node.node.Node→prek.languages.LanguageBackend
- Direction
- languages.node.node uses languages, so a change to languages can break languages.node.node, while a change to languages.node.node can't break languages.
- Position
- Below the diagonal: languages.node.node uses a module listed above it, which is the healthy direction.
33→18 languages.node.node uses hook✕
- Connections
- 4 pairs of types, where a type in languages.node.node uses a type in hook.
- The types involved
prek.languages.node.node.Node→prek.hook.Hookprek.languages.node.node.Node→prek.hook.InstallInfoprek.languages.node.node.Node→prek.hook.InstalledHookprek.languages.node.node.node$module→prek.hook.Hook
- Direction
- languages.node.node uses hook, so a change to hook can break languages.node.node, while a change to languages.node.node can't break hook.
- Position
- Below the diagonal: languages.node.node uses a module listed above it, which is the healthy direction.
33→21 languages.node.node uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.node.node uses a type in cli.reporter.
- The types involved
prek.languages.node.node.Node→prek.cli.reporter.HookInstallReporter
- Direction
- languages.node.node uses cli.reporter, so a change to cli.reporter can break languages.node.node, while a change to languages.node.node can't break cli.reporter.
- Position
- Below the diagonal: languages.node.node uses a module listed above it, which is the healthy direction.
34→7 languages.php uses process✕
- Connections
- 1 pair of types, where a type in languages.php uses a type in process.
- The types involved
prek.languages.php.php$module→prek.process.Cmd
- Direction
- languages.php uses process, so a change to process can break languages.php, while a change to languages.php can't break process.
- Position
- Below the diagonal: languages.php uses a module listed above it, which is the healthy direction.
34→8 languages.php uses store✕
- Connections
- 1 pair of types, where a type in languages.php uses a type in store.
- The types involved
prek.languages.php.Php→prek.store.Store
- Direction
- languages.php uses store, so a change to store can break languages.php, while a change to languages.php can't break store.
- Position
- Below the diagonal: languages.php uses a module listed above it, which is the healthy direction.
34→11 languages.php uses languages✕
- Connections
- 1 pair of types, where a type in languages.php uses a type in languages.
- The types involved
prek.languages.php.Php→prek.languages.LanguageBackend
- Direction
- languages.php uses languages, so a change to languages can break languages.php, while a change to languages.php can't break languages.
- Position
- Below the diagonal: languages.php uses a module listed above it, which is the healthy direction.
34→18 languages.php uses hook✕
- Connections
- 3 pairs of types, where a type in languages.php uses a type in hook.
- The types involved
prek.languages.php.Php→prek.hook.Hookprek.languages.php.Php→prek.hook.InstallInfoprek.languages.php.Php→prek.hook.InstalledHook
- Direction
- languages.php uses hook, so a change to hook can break languages.php, while a change to languages.php can't break hook.
- Position
- Below the diagonal: languages.php uses a module listed above it, which is the healthy direction.
34→21 languages.php uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.php uses a type in cli.reporter.
- The types involved
prek.languages.php.Php→prek.cli.reporter.HookInstallReporter
- Direction
- languages.php uses cli.reporter, so a change to cli.reporter can break languages.php, while a change to languages.php can't break cli.reporter.
- Position
- Below the diagonal: languages.php uses a module listed above it, which is the healthy direction.
35→8 languages.pygrep.pygrep uses store✕
- Connections
- 1 pair of types, where a type in languages.pygrep.pygrep uses a type in store.
- The types involved
prek.languages.pygrep.pygrep.Pygrep→prek.store.Store
- Direction
- languages.pygrep.pygrep uses store, so a change to store can break languages.pygrep.pygrep, while a change to languages.pygrep.pygrep can't break store.
- Position
- Below the diagonal: languages.pygrep.pygrep uses a module listed above it, which is the healthy direction.
35→10 languages.pygrep.pygrep uses cli.run.reporter✕
- Connections
- 1 pair of types, where a type in languages.pygrep.pygrep uses a type in cli.run.reporter.
- The types involved
prek.languages.pygrep.pygrep.Pygrep→prek.cli.run.reporter.HookRunReporter
- Direction
- languages.pygrep.pygrep uses cli.run.reporter, so a change to cli.run.reporter can break languages.pygrep.pygrep, while a change to languages.pygrep.pygrep can't break cli.run.reporter.
- Position
- Below the diagonal: languages.pygrep.pygrep uses a module listed above it, which is the healthy direction.
35→11 languages.pygrep.pygrep uses languages✕
- Connections
- 1 pair of types, where a type in languages.pygrep.pygrep uses a type in languages.
- The types involved
prek.languages.pygrep.pygrep.Pygrep→prek.languages.LanguageBackend
- Direction
- languages.pygrep.pygrep uses languages, so a change to languages can break languages.pygrep.pygrep, while a change to languages.pygrep.pygrep can't break languages.
- Position
- Below the diagonal: languages.pygrep.pygrep uses a module listed above it, which is the healthy direction.
35→18 languages.pygrep.pygrep uses hook✕
- Connections
- 3 pairs of types, where a type in languages.pygrep.pygrep uses a type in hook.
- The types involved
prek.languages.pygrep.pygrep.Pygrep→prek.hook.Hookprek.languages.pygrep.pygrep.Pygrep→prek.hook.InstallInfoprek.languages.pygrep.pygrep.Pygrep→prek.hook.InstalledHook
- Direction
- languages.pygrep.pygrep uses hook, so a change to hook can break languages.pygrep.pygrep, while a change to languages.pygrep.pygrep can't break hook.
- Position
- Below the diagonal: languages.pygrep.pygrep uses a module listed above it, which is the healthy direction.
35→21 languages.pygrep.pygrep uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.pygrep.pygrep uses a type in cli.reporter.
- The types involved
prek.languages.pygrep.pygrep.Pygrep→prek.cli.reporter.HookInstallReporter
- Direction
- languages.pygrep.pygrep uses cli.reporter, so a change to cli.reporter can break languages.pygrep.pygrep, while a change to languages.pygrep.pygrep can't break cli.reporter.
- Position
- Below the diagonal: languages.pygrep.pygrep uses a module listed above it, which is the healthy direction.
36→8 languages.r uses store✕
- Connections
- 1 pair of types, where a type in languages.r uses a type in store.
- The types involved
prek.languages.r.R→prek.store.Store
- Direction
- languages.r uses store, so a change to store can break languages.r, while a change to languages.r can't break store.
- Position
- Below the diagonal: languages.r uses a module listed above it, which is the healthy direction.
36→11 languages.r uses languages✕
- Connections
- 2 pairs of types, where a type in languages.r uses a type in languages.
- The types involved
prek.languages.r.R→prek.languages.ExecutionEnvironmentprek.languages.r.R→prek.languages.LanguageBackend
- Direction
- languages.r uses languages, so a change to languages can break languages.r, while a change to languages.r can't break languages.
- Position
- Below the diagonal: languages.r uses a module listed above it, which is the healthy direction.
36→18 languages.r uses hook✕
- Connections
- 4 pairs of types, where a type in languages.r uses a type in hook.
- The types involved
prek.languages.r.R→prek.hook.Hookprek.languages.r.R→prek.hook.InstallInfoprek.languages.r.R→prek.hook.InstalledHookprek.languages.r.r$module→prek.hook.InstalledHook
- Direction
- languages.r uses hook, so a change to hook can break languages.r, while a change to languages.r can't break hook.
- Position
- Below the diagonal: languages.r uses a module listed above it, which is the healthy direction.
36→21 languages.r uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.r uses a type in cli.reporter.
- The types involved
prek.languages.r.R→prek.cli.reporter.HookInstallReporter
- Direction
- languages.r uses cli.reporter, so a change to cli.reporter can break languages.r, while a change to languages.r can't break cli.reporter.
- Position
- Below the diagonal: languages.r uses a module listed above it, which is the healthy direction.
37→7 languages.rust.rust uses process✕
- Connections
- 1 pair of types, where a type in languages.rust.rust uses a type in process.
- The types involved
prek.languages.rust.rust.CargoInstaller→prek.process.Cmd
- Direction
- languages.rust.rust uses process, so a change to process can break languages.rust.rust, while a change to languages.rust.rust can't break process.
- Position
- Below the diagonal: languages.rust.rust uses a module listed above it, which is the healthy direction.
37→8 languages.rust.rust uses store✕
- Connections
- 1 pair of types, where a type in languages.rust.rust uses a type in store.
- The types involved
prek.languages.rust.rust.Rust→prek.store.Store
- Direction
- languages.rust.rust uses store, so a change to store can break languages.rust.rust, while a change to languages.rust.rust can't break store.
- Position
- Below the diagonal: languages.rust.rust uses a module listed above it, which is the healthy direction.
37→11 languages.rust.rust uses languages✕
- Connections
- 1 pair of types, where a type in languages.rust.rust uses a type in languages.
- The types involved
prek.languages.rust.rust.Rust→prek.languages.LanguageBackend
- Direction
- languages.rust.rust uses languages, so a change to languages can break languages.rust.rust, while a change to languages.rust.rust can't break languages.
- Position
- Below the diagonal: languages.rust.rust uses a module listed above it, which is the healthy direction.
37→18 languages.rust.rust uses hook✕
- Connections
- 4 pairs of types, where a type in languages.rust.rust uses a type in hook.
- The types involved
prek.languages.rust.rust.Rust→prek.hook.Hookprek.languages.rust.rust.Rust→prek.hook.InstallInfoprek.languages.rust.rust.Rust→prek.hook.InstalledHookprek.languages.rust.rust.rust$module→prek.hook.InstallInfo
- Direction
- languages.rust.rust uses hook, so a change to hook can break languages.rust.rust, while a change to languages.rust.rust can't break hook.
- Position
- Below the diagonal: languages.rust.rust uses a module listed above it, which is the healthy direction.
37→21 languages.rust.rust uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.rust.rust uses a type in cli.reporter.
- The types involved
prek.languages.rust.rust.Rust→prek.cli.reporter.HookInstallReporter
- Direction
- languages.rust.rust uses cli.reporter, so a change to cli.reporter can break languages.rust.rust, while a change to languages.rust.rust can't break cli.reporter.
- Position
- Below the diagonal: languages.rust.rust uses a module listed above it, which is the healthy direction.
38→36 archive uses languages.r✕
- Connections
- 1 pair of types, where a type in archive uses a type in languages.r.
- The types involved
prek.archive.archive$module→prek.languages.r.R
- Direction
- archive uses languages.r, so a change to languages.r can break archive, while a change to archive can't break languages.r.
- Position
- Below the diagonal: archive uses a module listed above it, which is the healthy direction.
39→7 languages.python.uv uses process✕
- Connections
- 1 pair of types, where a type in languages.python.uv uses a type in process.
- The types involved
prek.languages.python.uv.Uv→prek.process.Cmd
- Direction
- languages.python.uv uses process, so a change to process can break languages.python.uv, while a change to languages.python.uv can't break process.
- Position
- Below the diagonal: languages.python.uv uses a module listed above it, which is the healthy direction.
39→8 languages.python.uv uses store✕
- Connections
- 2 pairs of types, where a type in languages.python.uv uses a type in store.
- The types involved
prek.languages.python.uv.InstallSource→prek.store.Storeprek.languages.python.uv.Uv→prek.store.Store
- Direction
- languages.python.uv uses store, so a change to store can break languages.python.uv, while a change to languages.python.uv can't break store.
- Position
- Below the diagonal: languages.python.uv uses a module listed above it, which is the healthy direction.
39→38 languages.python.uv uses archive✕
- Connections
- 1 pair of types, where a type in languages.python.uv uses a type in archive.
- The types involved
prek.languages.python.uv.uv$module→prek.archive.Error
- Direction
- languages.python.uv uses archive, so a change to archive can break languages.python.uv, while a change to languages.python.uv can't break archive.
- Position
- Below the diagonal: languages.python.uv uses a module listed above it, which is the healthy direction.
40→7 languages.python.python uses process✕
- Connections
- 1 pair of types, where a type in languages.python.python uses a type in process.
- The types involved
prek.languages.python.python.Python→prek.process.Cmd
- Direction
- languages.python.python uses process, so a change to process can break languages.python.python, while a change to languages.python.python can't break process.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
40→8 languages.python.python uses store✕
- Connections
- 1 pair of types, where a type in languages.python.python uses a type in store.
- The types involved
prek.languages.python.python.Python→prek.store.Store
- Direction
- languages.python.python uses store, so a change to store can break languages.python.python, while a change to languages.python.python can't break store.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
40→11 languages.python.python uses languages✕
- Connections
- 1 pair of types, where a type in languages.python.python uses a type in languages.
- The types involved
prek.languages.python.python.Python→prek.languages.LanguageBackend
- Direction
- languages.python.python uses languages, so a change to languages can break languages.python.python, while a change to languages.python.python can't break languages.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
40→17 languages.python.python uses languages.version✕
- Connections
- 2 pairs of types, where a type in languages.python.python uses a type in languages.version.
- The types involved
prek.languages.python.python.Python→prek.languages.version.LanguageRequestprek.languages.python.python.python$module→prek.languages.version.LanguageRequest
- Direction
- languages.python.python uses languages.version, so a change to languages.version can break languages.python.python, while a change to languages.python.python can't break languages.version.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
40→18 languages.python.python uses hook✕
- Connections
- 3 pairs of types, where a type in languages.python.python uses a type in hook.
- The types involved
prek.languages.python.python.Python→prek.hook.Hookprek.languages.python.python.Python→prek.hook.InstallInfoprek.languages.python.python.Python→prek.hook.InstalledHook
- Direction
- languages.python.python uses hook, so a change to hook can break languages.python.python, while a change to languages.python.python can't break hook.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
40→21 languages.python.python uses cli.reporter✕
- Connections
- 1 pair of types, where a type in languages.python.python uses a type in cli.reporter.
- The types involved
prek.languages.python.python.Python→prek.cli.reporter.HookInstallReporter
- Direction
- languages.python.python uses cli.reporter, so a change to cli.reporter can break languages.python.python, while a change to languages.python.python can't break cli.reporter.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
40→38 languages.python.python uses archive✕
- Connections
- 1 pair of types, where a type in languages.python.python uses a type in archive.
- The types involved
prek.languages.python.python.Python→prek.archive.Error
- Direction
- languages.python.python uses archive, so a change to archive can break languages.python.python, while a change to languages.python.python can't break archive.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
40→39 languages.python.python uses languages.python.uv✕
- Connections
- 1 pair of types, where a type in languages.python.python uses a type in languages.python.uv.
- The types involved
prek.languages.python.python.Python→prek.languages.python.uv.Uv
- Direction
- languages.python.python uses languages.python.uv, so a change to languages.python.uv can break languages.python.python, while a change to languages.python.python can't break languages.python.uv.
- Position
- Below the diagonal: languages.python.python uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
First, enable automated dependency review and establish a tested disaster recovery procedure with documented recovery objectives. Next, resolve the missing architecture decision records by documenting key design choices and their consequences. Finally, fix the widespread issues with interpolated log messages to ensure proper structured logging.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Enable Dependabot/Renovate or a dependency-review gate. | +4.4 pts | Medium | Security & performance tooling |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +4.4 pts | Medium | DR & Backup |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.1 pts | Low | ADR Quality |
| 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. | +1.9 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +1.7 pts | Medium | Structured logging |
| Bring the 37 bodies over 15 down to 15 or less in Cognitive Complexity — start with prek::schema::strip_null_acceptance (cognitive 51), prek::cli::update::display::apply_repo_updates (cognitive 41), prek::cli::update::display::write_display_events (cognitive 36). | +1.1 pts | High | Cognitive Complexity |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.0 pts | Medium | Documentation (README) |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). | +0.4 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/prek/src/cli/run/run.rs | 5.5 | Mixed | Cyclomatic Complexity: prek::cli::run::run::run (cyclomatic 27) |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unsound): REDACTED |
| crates/prek/src/languages/python/uv.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/prek/src/languages/golang/gomod.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/prek/src/cli/run/filter.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/prek/src/cli/list.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/prek/src/hook.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/prek/src/cli/sample_config.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/prek/src/cli/cache_gc.rs | 7.0 | Near-clean | Cyclomatic Complexity: prek::cli::cache_gc::cache_gc (cyclomatic 18) |
| crates/prek/src/languages/bun/installer.rs | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens) |
| crates/prek/src/config/hook.rs | 7.1 | Near-clean | Cyclomatic Complexity: HookOptions::update (cyclomatic 24) |
| crates/prek/src/workspace.rs | 7.2 | Near-clean | Cognitive Complexity: Project::find_configs (cognitive 24) |
| crates/prek/src/languages/docker.rs | 7.2 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| crates/prek/src/languages/conda.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| crates/prek/src/languages/python/version.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| crates/prek/src/languages/mise/mise.rs | 7.3 | 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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 61 of 61 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 61 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, 209 of 224 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (.github/codecov.yml) and a coverage step in CI (`cargo llvm-cov`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 151 test files), but it was not re-run: the Cargo suite did not finish re-running within its tier budget. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python REDACTED/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (119 contributor(s) across 2257 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 118 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ve: ubuntu:26.04@sha256:c098726dd9b9733f3e885f8de0ef375206a311b0a317eadc40d347b1115fb944: failed to resolve source metadata for docker.io/library/ubuntu:26.04@sha256:c098726dd9b9733f3e885f8de0ef375206a311b0a317eadc40d347b1115fb944: failed to do request: Head "https://registry-1.docker.io/v2/library/ubuntu/manifests/sha256:c098726dd9b9733f3e885f8de0ef375206a311b0a317eadc40d347b1115fb944": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was prek::run at 43. A further 7 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being BuiltinHook::from_id at 31 — they are counted neither in the figure above nor in this dimension's score. 6 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/prek/src/hooks/builtin_hooks/mod.rs (BuiltinHook::from_id at 31), crates/prek/src/languages/mod.rs (Language::backend at 25), crates/prek/src/hooks/pre_commit_hooks/mod.rs (PreCommitHooks::run at 22), crates/prek/src/languages/golang/installer.rs (GoInstaller::download at 18), crates/prek/src/languages/python/uv.rs (prek::languages::python::uv::wheel_platform_tag_for_host at 18), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with prek::run (cyclomatic 43). — Refactoring it lifts Cyclomatic Complexity from 7.9 to about 8.2/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
37 method(s) exceeded the cognitive complexity threshold of 15; the worst was prek::schema::strip_null_acceptance at 51.
What to do
- Bring the 37 bodies over 15 down to 15 or less in Cognitive Complexity — start with prek::schema::strip_null_acceptance (cognitive 51), prek::cli::update::display::apply_repo_updates (cognitive 41), prek::cli::update::display::write_display_events (cognitive 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 37 together lifts Cognitive Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
16 god class(es) detected.
What to do
- Resolve the 10 FileTooLong finding(s) in God Classes — start with mod.rs (2), hook.rs (2), run.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with main.rs, run.rs, cache_gc.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
39 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with uv.rs, git.rs, cache_gc.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with hook.rs, installer.rs, version.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with docker.rs, self_update.rs, installer.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 4 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 80 classes have LCOM4 above 3.
D9 · Test Distribution
1236 test methods: 657 unit, 579 integration, 0 BDD, 0 e2e. The Rust suite contributes 1236 `#[test]` function(s) across 151 file(s) declaring at least one; its unit/integration split is Cargo's own — 58 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
6 outdated, 0 yanked direct Cargo dependencies. 70 of 72 direct crates were graded against crates.io (0 not published there, 2 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 341 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python REDACTED/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: crates/prek/src/cli/run/run.rs (30×27=810); crates/prek/src/main.rs (15×43=645); crates/prek/src/hooks/builtin_hooks/mod.rs (9×31=279)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with run.rs, main.rs, mod.rs. — One of this dimension's main actionable groups (7 warning-level).
D17 · Explicit Debt
23 deducted task-comment markers across 51575 LoC (0.0/KLoC) → score 9.9. 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 version.rs (5), mod.rs (4), conda.rs (2). — One of this dimension's main actionable groups (23 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 30 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 7 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. semgrep hit a parse error in 6 file(s) — `crates/prek/src/cli/update/mod.rs` (line 487), `crates/prek/src/languages/bun/installer.rs` (line 60, line 221), `crates/prek/src/languages/mod.rs` (line 130), `crates/prek/src/languages/python/uv.rs` (line 347, line 481), `crates/prek/src/languages/rust/installer.rs` (line 134, line 136), … (+1 more) — 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 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 0 high, 5 medium, 0 low.
What to do
- Resolve the 4 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
1 of 144 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is python/prek/_find_prek.py. Counted over 144 of the 170 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: node.rs↔ruby.rs 55%; run.rs↔system.rs 50%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with node.rs, run.rs. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
Build pipeline generates provenance, signs artifacts and produces an SBOM.
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
DM4 · Rich vs anemic domain model
DM5 · Encapsulated state
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 6 project(s) that lack one — worth up to 1 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
- `sort_schema` is public and takes `value: Any` from its caller, and it calls itself at line 91 (`sort_schema`) with a piece of `value` (and at line 93) — and nowhere in `sort_schema` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `sort_schema` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — scripts/update-schemastore-schema.py:91
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 50 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek-ignore/src/dir.rs:50
- `debug!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek-ignore/src/dir.rs:104
- `debug!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek-ignore/src/dir.rs:128
- `debug!` at line 172 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek-ignore/src/gitignore.rs:172
- `info!` at line 38 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek-consts/src/env_vars.rs:38
- `info!` at line 65 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek-consts/src/env_vars.rs:65
- `warn!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/archive.rs:185
- `trace!` at line 306 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/concurrency.rs:306
- `error!` at line 288 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/fs.rs:288
- `trace!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/fs.rs:391
- `trace!` at line 399 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/fs.rs:399
- `trace!` at line 414 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/fs.rs:414
- `trace!` at line 422 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/fs.rs:422
- `trace!` at line 433 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/fs.rs:433
- `debug!` at line 79 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/git.rs:79
- `trace!` at line 505 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/hook.rs:505
- `warn!` at line 62 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/install_source.rs:62
- `debug!` at line 200 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/main.rs:200
- `warn!` at line 206 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/main.rs:206
- `debug!` at line 219 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/main.rs:219
- `debug!` at line 223 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/main.rs:223
- `trace!` at line 642 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/process.rs:642
- `error!` at line 12 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/profiler.rs:12
- `error!` at line 33 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/profiler.rs:33
- `error!` at line 37 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/profiler.rs:37
- `warn!` at line 356 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/store.rs:356
- `debug!` at line 343 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:343
- `debug!` at line 542 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:542
- `debug!` at line 618 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:618
- `debug!` at line 625 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:625
- `debug!` at line 680 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:680
- `debug!` at line 724 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:724
- `debug!` at line 752 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:752
- `error!` at line 791 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:791
- `error!` at line 850 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/workspace.rs:850
- `debug!` at line 276 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/languages/dart.rs:276
- `debug!` at line 282 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/languages/dart.rs:282
- `trace!` at line 158 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/languages/docker.rs:158
- `warn!` at line 238 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/languages/docker.rs:238
- `warn!` at line 242 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/prek/src/languages/docker.rs:242
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Strong | Solid. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 75% | Strong | Solid. |
| Readiness | 65% | Strong | Largest drag on the score — prioritise here. |
| Security | 85% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 89% | Exemplary | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · 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.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 62 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ve: ubuntu:26.04@sha256:c098726dd9b9733f3e885f8de0ef375206a311b0a317eadc40d347b1115fb944: failed to resolve source metadata for docker.io/library/ubuntu:26.04@sha256:c098726dd9b9733f3e885f8de0ef375206a311b0a317eadc40d347b1115fb944: failed to do request: Head "https://registry-1.docker.io/v2/library/ubuntu/manifests/sha256:c098726dd9b9733f3e885f8de0ef375206a311b0a317eadc40d347b1115fb944": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~27846 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 30 current-state document(s) make no claim of a kind M4 checks. 72 claim(s) of kinds M4 does not check were not checked (path 17, command argument 3, environment variable 43, setting 9); M4 checks only links and versions.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 165 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 150 finding(s)
- prek::schema::strip_null_acceptance (cognitive 51) crates/prek/src/schema.rs:17
- prek::cli::update::display::apply_repo_updates (cognitive 41) crates/prek/src/cli/update/display.rs:201
- prek::cli::update::display::write_display_events (cognitive 36) crates/prek/src/cli/update/display.rs:114
- prek::cli::run::run::run (cognitive 35) crates/prek/src/cli/run/run.rs:77
- prek::hooks::pre_commit_hooks::check_merge_conflict::check_file (cognitive 35) crates/prek/src/hooks/pre_commit_hooks/check_merge_conflict.rs:62
- prek::cli::cache_gc::sweep_dir_by_name (cognitive 34) crates/prek/src/cli/cache_gc.rs:546
- prek::cli::cache_gc::cache_gc (cognitive 32) crates/prek/src/cli/cache_gc.rs:145
- prek::archive::unzip (cognitive 31) crates/prek/src/archive.rs:151
- prek::cli::install::install_hook_script (cognitive 31) crates/prek/src/cli/install.rs:220
- prek::cli::cache_gc::sweep_stale_patch_files (cognitive 28) crates/prek/src/cli/cache_gc.rs:632
- prek::cli::cache_gc::hook_env_requirements_from_config (cognitive 27) crates/prek/src/cli/cache_gc.rs:360
- prek::hooks::builtin_hooks::check_commit_trailers::check_message (cognitive 27) crates/prek/src/hooks/builtin_hooks/check_commit_trailers.rs:219
- prek::cli::cache_gc::sweep_tool_bucket_versions (cognitive 26) crates/prek/src/cli/cache_gc.rs:470
- prek::languages::golang::gomod::parse_go_mod_directives (cognitive 26) crates/prek/src/languages/golang/gomod.rs:11
- prek::hooks::meta_hooks::check_useless_excludes (cognitive 25) crates/prek/src/hooks/meta_hooks.rs:227
- prek::languages::rust::rust::install_local_project (cognitive 25) crates/prek/src/languages/rust/rust.rs:299
- prek::run (cognitive 24) crates/prek/src/main.rs:155
- prek::cli::hook_impl::hook_impl (cognitive 24) crates/prek/src/cli/hook_impl.rs:25
- prek::hooks::meta_hooks::check_hooks_apply (cognitive 23) crates/prek/src/hooks/meta_hooks.rs:108
- prek::cli::run::run::select_runnable_env_hooks (cognitive 21) crates/prek/src/cli/run/run.rs:484
- prek::cli::list::list (cognitive 20) crates/prek/src/cli/list.rs:28
- prek::cli::install::uninstall (cognitive 19) crates/prek/src/cli/install.rs:402
- prek::hooks::pre_commit_hooks::fix_trailing_whitespace::fix_file (cognitive 18) crates/prek/src/hooks/pre_commit_hooks/fix_trailing_whitespace.rs:93
- prek::cli::run::run::set_env_vars (cognitive 16) crates/prek/src/cli/run/run.rs:367
- TodoComment crates/prek/src/hook.rs:658
- TodoComment crates/prek/src/languages/conda.rs:48
- TodoComment crates/prek/src/languages/conda.rs:84
- TodoComment crates/prek/src/languages/version.rs:93
- TodoComment crates/prek/src/languages/python/uv.rs:224
- TodoComment crates/prek/src/languages/python/uv.rs:225
- TodoComment crates/prek/src/languages/python/version.rs:29
- TodoComment crates/prek/src/languages/python/version.rs:192
- TodoComment crates/prek/src/languages/pygrep/pygrep.rs:220
- TodoComment crates/prek/src/languages/node/installer.rs:198
- TodoComment crates/prek/src/languages/mise/mise.rs:97
- TodoComment crates/prek/src/languages/mise/mise.rs:200
- TodoComment crates/prek/src/languages/golang/gomod.rs:66
- TodoComment crates/prek/src/languages/golang/version.rs:30
- TodoComment crates/prek/src/languages/golang/version.rs:52
- TodoComment crates/prek/src/hooks/mod.rs:84
- TodoComment crates/prek/src/hooks/pre_commit_hooks/check_yaml.rs:143
- TodoComment crates/prek/src/hooks/pre_commit_hooks/mod.rs:144
- TodoComment crates/prek/src/config/mod.rs:45
- TodoComment crates/prek/src/cli/list.rs:74
- TodoComment crates/prek/src/cli/sample_config.rs:75
- TodoComment crates/prek/src/cli/update/mod.rs:451
- TodoComment crates/prek/src/cli/run/filter.rs:743
- prek::run (cyclomatic 43) crates/prek/src/main.rs:155
- prek::cli::run::run::run (cyclomatic 27) crates/prek/src/cli/run/run.rs:77
- prek::schema::strip_null_acceptance (cyclomatic 27) crates/prek/src/schema.rs:17
- prek::hooks::pre_commit_hooks::check_merge_conflict::check_file (cyclomatic 20) crates/prek/src/hooks/pre_commit_hooks/check_merge_conflict.rs:62
- prek::cli::cache_gc::cache_gc (cyclomatic 18) crates/prek/src/cli/cache_gc.rs:145
- prek::archive::unzip (cyclomatic 17) crates/prek/src/archive.rs:151
- prek::cli::cache_gc::sweep_dir_by_name (cyclomatic 17) crates/prek/src/cli/cache_gc.rs:546
- prek::cli::install::install_hook_script (cyclomatic 17) crates/prek/src/cli/install.rs:220
- prek::cli::cache_gc::sweep_stale_patch_files (cyclomatic 16) crates/prek/src/cli/cache_gc.rs:632
- prek::cli::run::run::set_env_vars (cyclomatic 16) crates/prek/src/cli/run/run.rs:367
- FileTooLong: run/run.rs crates/prek/src/cli/run/run.rs
- FileTooLong: src/git.rs crates/prek/src/git.rs
- FileTooLong: cli/mod.rs crates/prek/src/cli/mod.rs
- FileTooLong: config/hook.rs crates/prek/src/config/hook.rs
- FileTooLong: src/workspace.rs crates/prek/src/workspace.rs
- FileTooLong: src/hook.rs crates/prek/src/hook.rs
- FileTooLong: run/selector.rs crates/prek/src/cli/run/selector.rs
- FileTooLong: languages/mod.rs crates/prek/src/languages/mod.rs
- FileTooLong: cli/cache_gc.rs crates/prek/src/cli/cache_gc.rs
- FileTooLong: run/reporter.rs crates/prek/src/cli/run/reporter.rs
- Hotspot: crates/prek/src/cli/run/run.rs crates/prek/src/cli/run/run.rs:77
- Hotspot: crates/prek/src/main.rs crates/prek/src/main.rs:155
- Hotspot: crates/prek/src/hooks/builtin_hooks/mod.rs crates/prek/src/hooks/builtin_hooks/mod.rs:165
- Hotspot: crates/prek/src/config/hook.rs crates/prek/src/config/hook.rs:532
- Hotspot: crates/prek/src/hooks/pre_commit_hooks/check_merge_conflict.rs crates/prek/src/hooks/pre_commit_hooks/check_merge_conflict.rs:62
- Hotspot: crates/prek/src/languages/node/installer.rs crates/prek/src/languages/node/installer.rs:200
- Hotspot: crates/prek/src/cli/install.rs crates/prek/src/cli/install.rs:220
- FunctionTooLong: prek::run crates/prek/src/main.rs:155
- FunctionTooLong: prek::cli::run::run::run crates/prek/src/cli/run/run.rs:77
- FunctionTooLong: prek::cli::cache_gc::cache_gc crates/prek/src/cli/cache_gc.rs:145
- FunctionTooLong: prek::cli::update::display::apply_repo_updates crates/prek/src/cli/update/display.rs:201
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) crates/prek/src/languages/python/uv.rs:619
- Duplicated block (11 lines × 2) crates/prek/src/git.rs:785
- Duplicated block (11 lines × 2) crates/prek/src/cli/cache_gc.rs:534
- Duplicated block (10 lines × 2) crates/prek/src/config/hook.rs:673
- Duplicated block (10 lines × 2) crates/prek/src/languages/bun/installer.rs:218
- Duplicated block (10 lines × 2) crates/prek/src/languages/bun/version.rs:105
- Duplicated block (8 lines × 2) crates/prek/src/languages/docker.rs:447
- Duplicated block (8 lines × 2) crates/prek/src/cli/self_update.rs:62
- Duplicated block (8 lines × 2) crates/prek/src/languages/dotnet/installer.rs:275
- Duplicated block (5 lines × 2) crates/prek/src/hooks/pre_commit_hooks/check_executables_have_shebangs.rs:16
- Duplicated block (5 lines × 2) crates/prek/src/cli/sample_config.rs:95
- Duplicated block (5 lines × 2) crates/prek/src/languages/coursier.rs:69
- Duplicated block (7 lines × 2) crates/prek/src/languages/bun/installer.rs:293
- Duplicated block (7 lines × 2) crates/prek/src/hooks/pre_commit_hooks/check_json.rs:27
- Duplicated block (7 lines × 2) crates/prek/src/languages/python/uv.rs:593
- Duplicated block (6 lines × 2) crates/prek/src/languages/mod.rs:91
- Duplicated block (6 lines × 2) crates/prek/src/languages/bun/installer.rs:217
- Duplicated block (6 lines × 2) crates/prek/src/languages/bun/bun.rs:48
- Duplicated block (9 lines × 2) crates/prek/src/cli/cache_gc.rs:527
- Duplicated block (9 lines × 2) crates/prek/src/languages/golang/installer.rs:214
- Duplicated block (9 lines × 2) scripts/update-macports-portfile.py:113
- Project::find_configs (cognitive 24) crates/prek/src/workspace.rs:252
- Project::build_hooks (cognitive 21) crates/prek/src/workspace.rs:415
- HookRunSession::render_priority_group (cognitive 23) crates/prek/src/cli/run/run.rs:1032
- HookRunSession::render_hook_details (cognitive 20) crates/prek/src/cli/run/run.rs:1105
- Change coupling: node.rs ↔ ruby.rs crates/prek/src/languages/node/node.rs:1
- Change coupling: run.rs ↔ system.rs crates/prek/src/cli/run/run.rs:1
- Duplicated block (16 lines × 2) crates/prek/src/cli/validate.rs:24
- Duplicated block (16 lines × 2) crates/prek/src/config/hook.rs:867
- Off the main sequence: prek-identify
- Off the main sequence: prek-pty
- HookOptions::update (cyclomatic 24) crates/prek/src/config/hook.rs:532
- Repo::deserialize (cyclomatic 21) crates/prek/src/config/repo.rs:236
- HookRunSession::render_hook_details (cyclomatic 17) crates/prek/src/cli/run/run.rs:1105
- HookOptions::update (cognitive 27) crates/prek/src/config/hook.rs:532
- ProjectFiles::visit_for_project (cognitive 24) crates/prek/src/cli/run/filter.rs:218
- Repo::deserialize (cognitive 21) crates/prek/src/config/repo.rs:236
- ParsedRequirements::parse (cognitive 18) crates/prek/src/hooks/pre_commit_hooks/requirements_txt_fixer.rs:110
- CargoCliDependency::from_str (cognitive 18) crates/prek/src/languages/rust/rust.rs:50
- Store::clone_repos (cognitive 18) crates/prek/src/store.rs:156
- SelectorCompleter::project_candidates (cognitive 17) crates/prek/src/cli/completion.rs:143
- Selectors::matches_path (cognitive 17) crates/prek/src/cli/run/selector.rs:384
- Workspace::discover (cognitive 16) crates/prek/src/workspace.rs:686
- MethodTooLong: BuiltinHook.from_id crates/prek/src/hooks/builtin_hooks/mod.rs:165
- TooManyMethods: Cmd crates/prek/src/process.rs:128
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) crates/prek/src/languages/bun/installer.rs:124
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/prek/src/languages/docker.rs:446
- Duplicated block (15–16 lines × 2) crates/prek/src/cli/cache_gc.rs:492
- Duplicated block (15 lines × 2) crates/prek/src/cli/run/selector.rs:359
- Duplicated block (10–14 lines × 2) crates/prek/src/hooks/meta_hooks.rs:113
- Duplicated block (13 lines × 4) crates/prek/src/languages/docker.rs:480
- Duplicated block (11 lines × 5) crates/prek/src/languages/bun/installer.rs:125
- Duplicated block (6–8 lines × 2) crates/prek/src/languages/docker.rs:463
- Duplicated block (7 lines × 4) crates/prek/src/languages/bun/installer.rs:140
- Duplicated block (5–6 lines × 2) crates/prek/src/languages/bun/installer.rs:56
- Duplicated block (10 lines × 4) crates/prek/src/hooks/pre_commit_hooks/check_json.rs:13
- Duplicated block (10 lines × 3) crates/prek/src/hooks/pre_commit_hooks/fix_byte_order_marker.rs:13
- Duplicated block (12 lines × 2) crates/prek/src/languages/bun/installer.rs:156
- Duplicated block (10 lines × 6) crates/prek/src/languages/bun/installer.rs:126
- Duplicated block (8 lines × 4) crates/prek/src/languages/bun/installer.rs:221
- Duplicated block (6 lines × 3) crates/prek/src/languages/bun/bun.rs:46
- Duplicated block (5 lines × 7) crates/prek/src/languages/bun/installer.rs:98
- Duplicated block (18 lines × 2) scripts/update-macports-portfile.py:183
- Coverage collected but not gated
- Recursive walk over a caller-supplied document has no depth cap scripts/update-schemastore-schema.py:91
Minor — 54 finding(s)
- Interpolated log message defeats structured logging crates/prek-ignore/src/dir.rs:50
- Interpolated log message defeats structured logging crates/prek-ignore/src/dir.rs:104
- Interpolated log message defeats structured logging crates/prek-ignore/src/dir.rs:128
- Interpolated log message defeats structured logging crates/prek-ignore/src/gitignore.rs:172
- Interpolated log message defeats structured logging crates/prek-consts/src/env_vars.rs:38
- Interpolated log message defeats structured logging crates/prek-consts/src/env_vars.rs:65
- Interpolated log message defeats structured logging crates/prek/src/archive.rs:185
- Interpolated log message defeats structured logging crates/prek/src/concurrency.rs:306
- Interpolated log message defeats structured logging crates/prek/src/fs.rs:288
- Interpolated log message defeats structured logging crates/prek/src/fs.rs:391
- Interpolated log message defeats structured logging crates/prek/src/fs.rs:399
- Interpolated log message defeats structured logging crates/prek/src/fs.rs:414
- Interpolated log message defeats structured logging crates/prek/src/fs.rs:422
- Interpolated log message defeats structured logging crates/prek/src/fs.rs:433
- Interpolated log message defeats structured logging crates/prek/src/git.rs:79
- Interpolated log message defeats structured logging crates/prek/src/hook.rs:505
- Interpolated log message defeats structured logging crates/prek/src/install_source.rs:62
- Interpolated log message defeats structured logging crates/prek/src/main.rs:200
- Interpolated log message defeats structured logging crates/prek/src/main.rs:206
- Interpolated log message defeats structured logging crates/prek/src/main.rs:219
- Interpolated log message defeats structured logging crates/prek/src/main.rs:223
- Interpolated log message defeats structured logging crates/prek/src/process.rs:642
- Interpolated log message defeats structured logging crates/prek/src/profiler.rs:12
- Interpolated log message defeats structured logging crates/prek/src/profiler.rs:33
- Interpolated log message defeats structured logging crates/prek/src/profiler.rs:37
- Silent fallback default on Err crates/prek/src/http.rs:39
- Silent fallback default on Err crates/prek/src/cli/run/selector.rs:837
- Silent fallback default on Err crates/prek/src/languages/rust/rustup.rs:38
- Silent fallback default on Err crates/prek/src/version.rs:92
- Duplicated predicate scripts/update-macports-portfile.py:197
- Duplicated predicate crates/prek/src/languages/bun/version.rs:108
- Duplicated predicate crates/prek/src/languages/bun/version.rs:110
- No ADRs found
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- Orphaned file python/prek/_find_prek.py:1
- REDACTED
- No ADRs
- Logging is not universal
Minor — 6 finding(s)
- Outdated: annotate-snippets
- Outdated: asyncband
- Outdated: json5
- Outdated: rustix
- Outdated: self-replace
- Outdated: webpki-root-certs
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-26733571124f4478b4ab87bdf6fdf273/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-26733571124f4478b4ab87bdf6fdf273/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 12 | 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 . | 5 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |