Executive summary
mozilla/sccache meets our standard for a preview release, though it has pipeline tools referenced by a changeable name. It scores 69 out of 100 and is rated Strong, and 59 of its 61 critical findings are security problems.
Security and Compliance, at 59, is the weakest lens and counts most in the score. The best first step is moving the keys out of the code, worth about 7 points. Fixing the four pipeline jobs with more access than they need would lift Security and Compliance itself, worth about 3 points. Raising Security and Compliance to 68 would lift the score to about 73.
Forty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and four pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Updating the vulnerable packages would fix the three packages with a known security hole, and the two pipeline steps that run downloads without checking them need each download checked against a known checksum first. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 43,630 lines, about €68,000 to rebuild.
If Security and Compliance rose from 59 to 68, the lowest score rated Strong, the score would rise from 69 to about 73.
New since the last survey: 30 findings
- God Classes · FunctionTooLong: sccache::compiler::diab::parse_arguments src/compiler/diab.rs
- Code Duplication · Near-duplicate member pair (61 shared lines) src/compiler/diab.rs
- Code Duplication · Duplicated block (12 lines × 2) src/compiler/diab.rs
- Test Reliability · Flaky test: sccache::system.test_assembler_affects_cache::with_preprocessor_cache
- Churn × Complexity Hotspots · Hotspot: src/bin/sccache-dist/main.rs src/bin/sccache-dist/main.rs
- Churn × Complexity Hotspots · Hotspot: src/compiler/diab.rs src/compiler/diab.rs
- Churn × Complexity Hotspots · Hotspot: src/compiler/tasking_vx.rs src/compiler/tasking_vx.rs
- Explicit Debt · TodoComment src/util.rs
- Explicit Debt · TodoComment src/compiler/msvc.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 12 findings
- Cyclomatic Complexity · MultiLevelStorage::from_config (cyclomatic 24) src/cache/multilevel.rs
- Cognitive Complexity · MultiLevelStorage::get (cognitive 31) src/cache/multilevel.rs
- God Classes · MethodTooLong: MultiLevelStorage.from_config src/cache/multilevel.rs
- Code Duplication · Near-duplicate member pair (62 shared lines) src/compiler/diab.rs
- Code Duplication · Duplicated block (13 lines × 2) src/compiler/diab.rs
- Test Reliability · Flaky test: sccache::sccache_cargo.test_rust_cargo_run_with_env_dep_parsing
- Churn × Complexity Hotspots · Hotspot: src/server.rs src/server.rs
- Churn × Complexity Hotspots · Hotspot: src/cache/multilevel.rs src/cache/multilevel.rs
- Explicit Debt · TodoComment src/util.rs
- Explicit Debt · TodoComment src/util.rs
- Explicit Debt · TodoComment src/compiler/msvc.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €68,000 · Estimate
| Cost to rebuild | €22,000 to €110,000, for 374 to 1,186 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 69. 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: 43,630 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 config | 2 dist.path_transform | 3 net | 4 compiler.preprocessor_cache | 5 cache.cache_io | 6 compiler.args | 7 cache.cache | 8 lru_disk_cache.lru_cache | 9 protocol | 10 cache.disk | 11 cache.multilevel | 12 cache.readonly | 13 client | 14 lru_disk_cache | 15 cache.ipc_storage | 16 dist.cache | 17 dist | 18 dist.cache.client | 19 dist.http.client | 20 dist.http.server | 21 server | 22 compiler.compiler | 23 bin.sccache-dist.build_freebsd | 24 compiler.c | 25 bin.sccache-dist.cmdline | 26 compiler.cicc | 27 compiler.clang | 28 compiler.cudafe | 29 compiler.diab | 30 compiler.gcc | 31 compiler.msvc | 32 compiler.nvcc | 33 compiler.nvhpc | 34 compiler.ptxas | 35 compiler.rust | 36 compiler.tasking_vx | 37 bin.sccache-dist.main | 38 commands | 39 jobserver | 40 mock_command |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 config | ||||||||||||||||||||||||||||||||||||||||
| 2 dist.path_transform | ||||||||||||||||||||||||||||||||||||||||
| 3 net | ||||||||||||||||||||||||||||||||||||||||
| 4 compiler.preprocessor_cache | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 cache.cache_io | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 compiler.args | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 cache.cache | 3 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 8 lru_disk_cache.lru_cache | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 protocol | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 cache.disk | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 11 cache.multilevel | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 cache.readonly | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 client | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 lru_disk_cache | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 cache.ipc_storage | 1 | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 16 dist.cache | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 dist | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 18 dist.cache.client | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 dist.http.client | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 dist.http.server | 3 | 1 | 2 | 11 | 2 | |||||||||||||||||||||||||||||||||||
| 21 server | 5 | 2 | 1 | 3 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 22 compiler.compiler | 3 | 6 | ||||||||||||||||||||||||||||||||||||||
| 23 bin.sccache-dist.build_freebsd | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 compiler.c | 1 | 3 | 12 | |||||||||||||||||||||||||||||||||||||
| 25 bin.sccache-dist.cmdline | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 compiler.cicc | 2 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 27 compiler.clang | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 28 compiler.cudafe | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 29 compiler.diab | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 30 compiler.gcc | 2 | 3 | 6 | |||||||||||||||||||||||||||||||||||||
| 31 compiler.msvc | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 32 compiler.nvcc | 1 | 1 | 1 | 2 | 3 | 4 | ||||||||||||||||||||||||||||||||||
| 33 compiler.nvhpc | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 34 compiler.ptxas | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 35 compiler.rust | 3 | 16 | 2 | 11 | 1 | |||||||||||||||||||||||||||||||||||
| 36 compiler.tasking_vx | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 37 bin.sccache-dist.main | 1 | 16 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 commands | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 39 jobserver | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 mock_command | 1 | 5 | 1 | 1 |
4→1 compiler.preprocessor_cache uses config✕
- Connections
- 2 pairs of types, where a type in compiler.preprocessor_cache uses a type in config.
- The types involved
sccache.compiler.preprocessor_cache.PreprocessorCacheEntry→sccache.config.PreprocessorCacheModeConfigsccache.compiler.preprocessor_cache.preprocessor_cache$module→sccache.config.PreprocessorCacheModeConfig
- Direction
- compiler.preprocessor_cache uses config, so a change to config can break compiler.preprocessor_cache, while a change to compiler.preprocessor_cache can't break config.
- Position
- Below the diagonal: compiler.preprocessor_cache uses a module listed above it, which is the healthy direction.
4→22 compiler.preprocessor_cache uses compiler.compiler part of a loop✕
- Connections
- 1 pair of types, where a type in compiler.preprocessor_cache uses a type in compiler.compiler.
- The types involved
sccache.compiler.preprocessor_cache.preprocessor_cache$module→sccache.compiler.compiler.Language
- Direction
- compiler.preprocessor_cache uses compiler.compiler, so a change to compiler.compiler can break compiler.preprocessor_cache, while a change to compiler.preprocessor_cache can't break compiler.compiler.
- 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→1 cache.cache_io uses config✕
- Connections
- 1 pair of types, where a type in cache.cache_io uses a type in config.
- The types involved
sccache.cache.cache_io.CacheMode→sccache.config.CacheModeConfig
- Direction
- cache.cache_io uses config, so a change to config can break cache.cache_io, while a change to cache.cache_io can't break config.
- Position
- Below the diagonal: cache.cache_io uses a module listed above it, which is the healthy direction.
5→4 cache.cache_io uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in cache.cache_io uses a type in compiler.preprocessor_cache.
- The types involved
sccache.cache.cache_io.DecompressionFailure→sccache.compiler.preprocessor_cache.Error
- Direction
- cache.cache_io uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break cache.cache_io, while a change to cache.cache_io can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: cache.cache_io uses a module listed above it, which is the healthy direction.
6→4 compiler.args uses compiler.preprocessor_cache✕
- Connections
- 2 pairs of types, where a type in compiler.args uses a type in compiler.preprocessor_cache.
- The types involved
sccache.compiler.args.ArgParseError→sccache.compiler.preprocessor_cache.Errorsccache.compiler.args.ArgToStringError→sccache.compiler.preprocessor_cache.Error
- Direction
- compiler.args uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break compiler.args, while a change to compiler.args can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: compiler.args uses a module listed above it, which is the healthy direction.
7→1 cache.cache uses config✕
- Connections
- 3 pairs of types, where a type in cache.cache uses a type in config.
- The types involved
sccache.cache.cache.Storage→sccache.config.PreprocessorCacheModeConfigsccache.cache.cache.cache$module→sccache.config.CacheTypesccache.cache.cache.cache$module→sccache.config.Config
- Direction
- cache.cache uses config, so a change to config can break cache.cache, while a change to cache.cache can't break config.
- Position
- Below the diagonal: cache.cache uses a module listed above it, which is the healthy direction.
7→4 cache.cache uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in cache.cache uses a type in compiler.preprocessor_cache.
- The types involved
sccache.cache.cache.Storage→sccache.compiler.preprocessor_cache.PreprocessorCacheEntry
- Direction
- cache.cache uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break cache.cache, while a change to cache.cache can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: cache.cache uses a module listed above it, which is the healthy direction.
7→5 cache.cache uses cache.cache_io✕
- Connections
- 3 pairs of types, where a type in cache.cache uses a type in cache.cache_io.
- The types involved
sccache.cache.cache.RemoteStorage→sccache.cache.cache_io.CacheModesccache.cache.cache.RemoteStorage→sccache.cache.cache_io.CacheWritesccache.cache.cache.Storage→sccache.cache.cache_io.CacheWrite
- Direction
- cache.cache uses cache.cache_io, so a change to cache.cache_io can break cache.cache, while a change to cache.cache can't break cache.cache_io.
- Position
- Below the diagonal: cache.cache uses a module listed above it, which is the healthy direction.
7→11 cache.cache uses cache.multilevel part of a loop✕
- Connections
- 1 pair of types, where a type in cache.cache uses a type in cache.multilevel.
- The types involved
sccache.cache.cache.Storage→sccache.cache.multilevel.MultiLevelStats
- Direction
- cache.cache uses cache.multilevel, so a change to cache.multilevel can break cache.cache, while a change to cache.cache can't break cache.multilevel.
- 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→6 lru_disk_cache.lru_cache uses compiler.args✕
- Connections
- 2 pairs of types, where a type in lru_disk_cache.lru_cache uses a type in compiler.args.
- The types involved
sccache.lru_disk_cache.lru_cache.Iter→sccache.compiler.args.Itersccache.lru_disk_cache.lru_cache.LruCache→sccache.compiler.args.Iter
- Direction
- lru_disk_cache.lru_cache uses compiler.args, so a change to compiler.args can break lru_disk_cache.lru_cache, while a change to lru_disk_cache.lru_cache can't break compiler.args.
- Position
- Below the diagonal: lru_disk_cache.lru_cache uses a module listed above it, which is the healthy direction.
9→1 protocol uses config✕
- Connections
- 1 pair of types, where a type in protocol uses a type in config.
- The types involved
sccache.protocol.StorageHandshakeInfo→sccache.config.PreprocessorCacheModeConfig
- Direction
- protocol uses config, so a change to config can break protocol, while a change to protocol can't break config.
- Position
- Below the diagonal: protocol uses a module listed above it, which is the healthy direction.
9→5 protocol uses cache.cache_io✕
- Connections
- 1 pair of types, where a type in protocol uses a type in cache.cache_io.
- The types involved
sccache.protocol.StorageHandshakeInfo→sccache.cache.cache_io.CacheMode
- Direction
- protocol uses cache.cache_io, so a change to cache.cache_io can break protocol, while a change to protocol can't break cache.cache_io.
- Position
- Below the diagonal: protocol uses a module listed above it, which is the healthy direction.
9→22 protocol uses compiler.compiler part of a loop✕
- Connections
- 1 pair of types, where a type in protocol uses a type in compiler.compiler.
- The types involved
sccache.protocol.CompileFinished→sccache.compiler.compiler.ColorMode
- Direction
- protocol uses compiler.compiler, so a change to compiler.compiler can break protocol, while a change to protocol can't break compiler.compiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 cache.disk uses config✕
- Connections
- 1 pair of types, where a type in cache.disk uses a type in config.
- The types involved
sccache.cache.disk.DiskCache→sccache.config.PreprocessorCacheModeConfig
- Direction
- cache.disk uses config, so a change to config can break cache.disk, while a change to cache.disk can't break config.
- Position
- Below the diagonal: cache.disk uses a module listed above it, which is the healthy direction.
10→4 cache.disk uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in cache.disk uses a type in compiler.preprocessor_cache.
- The types involved
sccache.cache.disk.DiskCache→sccache.compiler.preprocessor_cache.PreprocessorCacheEntry
- Direction
- cache.disk uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break cache.disk, while a change to cache.disk can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: cache.disk uses a module listed above it, which is the healthy direction.
10→5 cache.disk uses cache.cache_io✕
- Connections
- 2 pairs of types, where a type in cache.disk uses a type in cache.cache_io.
- The types involved
sccache.cache.disk.DiskCache→sccache.cache.cache_io.CacheModesccache.cache.disk.DiskCache→sccache.cache.cache_io.CacheWrite
- Direction
- cache.disk uses cache.cache_io, so a change to cache.cache_io can break cache.disk, while a change to cache.disk can't break cache.cache_io.
- Position
- Below the diagonal: cache.disk uses a module listed above it, which is the healthy direction.
10→7 cache.disk uses cache.cache✕
- Connections
- 2 pairs of types, where a type in cache.disk uses a type in cache.cache.
- The types involved
sccache.cache.disk.DiskCache→sccache.cache.cache.GetPathResultsccache.cache.disk.DiskCache→sccache.cache.cache.Storage
- Direction
- cache.disk uses cache.cache, so a change to cache.cache can break cache.disk, while a change to cache.disk can't break cache.cache.
- Position
- Below the diagonal: cache.disk uses a module listed above it, which is the healthy direction.
11→1 cache.multilevel uses config✕
- Connections
- 3 pairs of types, where a type in cache.multilevel uses a type in config.
- The types involved
sccache.cache.multilevel.MultiLevelStorage→sccache.config.Configsccache.cache.multilevel.MultiLevelStorage→sccache.config.PreprocessorCacheModeConfigsccache.cache.multilevel.MultiLevelStorage→sccache.config.WriteErrorPolicy
- Direction
- cache.multilevel uses config, so a change to config can break cache.multilevel, while a change to cache.multilevel can't break config.
- Position
- Below the diagonal: cache.multilevel uses a module listed above it, which is the healthy direction.
11→4 cache.multilevel uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in cache.multilevel uses a type in compiler.preprocessor_cache.
- The types involved
sccache.cache.multilevel.MultiLevelStorage→sccache.compiler.preprocessor_cache.PreprocessorCacheEntry
- Direction
- cache.multilevel uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break cache.multilevel, while a change to cache.multilevel can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: cache.multilevel uses a module listed above it, which is the healthy direction.
11→5 cache.multilevel uses cache.cache_io✕
- Connections
- 1 pair of types, where a type in cache.multilevel uses a type in cache.cache_io.
- The types involved
sccache.cache.multilevel.MultiLevelStorage→sccache.cache.cache_io.CacheWrite
- Direction
- cache.multilevel uses cache.cache_io, so a change to cache.cache_io can break cache.multilevel, while a change to cache.multilevel can't break cache.cache_io.
- Position
- Below the diagonal: cache.multilevel uses a module listed above it, which is the healthy direction.
11→7 cache.multilevel uses cache.cache✕
- Connections
- 1 pair of types, where a type in cache.multilevel uses a type in cache.cache.
- The types involved
sccache.cache.multilevel.MultiLevelStorage→sccache.cache.cache.Storage
- Direction
- cache.multilevel uses cache.cache, so a change to cache.cache can break cache.multilevel, while a change to cache.multilevel can't break cache.cache.
- Position
- Below the diagonal: cache.multilevel uses a module listed above it, which is the healthy direction.
12→1 cache.readonly uses config✕
- Connections
- 1 pair of types, where a type in cache.readonly uses a type in config.
- The types involved
sccache.cache.readonly.ReadOnlyStorage→sccache.config.PreprocessorCacheModeConfig
- Direction
- cache.readonly uses config, so a change to config can break cache.readonly, while a change to cache.readonly can't break config.
- Position
- Below the diagonal: cache.readonly uses a module listed above it, which is the healthy direction.
12→4 cache.readonly uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in cache.readonly uses a type in compiler.preprocessor_cache.
- The types involved
sccache.cache.readonly.ReadOnlyStorage→sccache.compiler.preprocessor_cache.PreprocessorCacheEntry
- Direction
- cache.readonly uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break cache.readonly, while a change to cache.readonly can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: cache.readonly uses a module listed above it, which is the healthy direction.
12→5 cache.readonly uses cache.cache_io✕
- Connections
- 1 pair of types, where a type in cache.readonly uses a type in cache.cache_io.
- The types involved
sccache.cache.readonly.ReadOnlyStorage→sccache.cache.cache_io.CacheWrite
- Direction
- cache.readonly uses cache.cache_io, so a change to cache.cache_io can break cache.readonly, while a change to cache.readonly can't break cache.cache_io.
- Position
- Below the diagonal: cache.readonly uses a module listed above it, which is the healthy direction.
12→7 cache.readonly uses cache.cache✕
- Connections
- 1 pair of types, where a type in cache.readonly uses a type in cache.cache.
- The types involved
sccache.cache.readonly.ReadOnlyStorage→sccache.cache.cache.Storage
- Direction
- cache.readonly uses cache.cache, so a change to cache.cache can break cache.readonly, while a change to cache.readonly can't break cache.cache.
- Position
- Below the diagonal: cache.readonly uses a module listed above it, which is the healthy direction.
13→3 client uses net✕
- Connections
- 1 pair of types, where a type in client uses a type in net.
- The types involved
sccache.client.client$module→sccache.net.SocketAddr
- Direction
- client uses net, so a change to net can break client, while a change to client can't break net.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
13→9 client uses protocol✕
- Connections
- 1 pair of types, where a type in client uses a type in protocol.
- The types involved
sccache.client.ServerConnection→sccache.protocol.Request
- Direction
- client uses protocol, so a change to protocol can break client, while a change to client can't break protocol.
- Position
- Below the diagonal: client uses a module listed above it, which is the healthy direction.
14→4 lru_disk_cache uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in lru_disk_cache uses a type in compiler.preprocessor_cache.
- The types involved
sccache.lru_disk_cache.Error→sccache.compiler.preprocessor_cache.Error
- Direction
- lru_disk_cache uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break lru_disk_cache, while a change to lru_disk_cache can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: lru_disk_cache uses a module listed above it, which is the healthy direction.
14→8 lru_disk_cache uses lru_disk_cache.lru_cache✕
- Connections
- 2 pairs of types, where a type in lru_disk_cache uses a type in lru_disk_cache.lru_cache.
- The types involved
sccache.lru_disk_cache.FileSize→sccache.lru_disk_cache.lru_cache.Metersccache.lru_disk_cache.LruDiskCache→sccache.lru_disk_cache.lru_cache.LruCache
- Direction
- lru_disk_cache uses lru_disk_cache.lru_cache, so a change to lru_disk_cache.lru_cache can break lru_disk_cache, while a change to lru_disk_cache can't break lru_disk_cache.lru_cache.
- Position
- Below the diagonal: lru_disk_cache uses a module listed above it, which is the healthy direction.
15→1 cache.ipc_storage uses config✕
- Connections
- 1 pair of types, where a type in cache.ipc_storage uses a type in config.
- The types involved
sccache.cache.ipc_storage.IpcStorage→sccache.config.PreprocessorCacheModeConfig
- Direction
- cache.ipc_storage uses config, so a change to config can break cache.ipc_storage, while a change to cache.ipc_storage can't break config.
- Position
- Below the diagonal: cache.ipc_storage uses a module listed above it, which is the healthy direction.
15→4 cache.ipc_storage uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in cache.ipc_storage uses a type in compiler.preprocessor_cache.
- The types involved
sccache.cache.ipc_storage.IpcStorage→sccache.compiler.preprocessor_cache.PreprocessorCacheEntry
- Direction
- cache.ipc_storage uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break cache.ipc_storage, while a change to cache.ipc_storage can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: cache.ipc_storage uses a module listed above it, which is the healthy direction.
15→5 cache.ipc_storage uses cache.cache_io✕
- Connections
- 1 pair of types, where a type in cache.ipc_storage uses a type in cache.cache_io.
- The types involved
sccache.cache.ipc_storage.IpcStorage→sccache.cache.cache_io.CacheWrite
- Direction
- cache.ipc_storage uses cache.cache_io, so a change to cache.cache_io can break cache.ipc_storage, while a change to cache.ipc_storage can't break cache.cache_io.
- Position
- Below the diagonal: cache.ipc_storage uses a module listed above it, which is the healthy direction.
15→7 cache.ipc_storage uses cache.cache✕
- Connections
- 2 pairs of types, where a type in cache.ipc_storage uses a type in cache.cache.
- The types involved
sccache.cache.ipc_storage.IpcStorage→sccache.cache.cache.GetPathResultsccache.cache.ipc_storage.IpcStorage→sccache.cache.cache.Storage
- Direction
- cache.ipc_storage uses cache.cache, so a change to cache.cache can break cache.ipc_storage, while a change to cache.ipc_storage can't break cache.cache.
- Position
- Below the diagonal: cache.ipc_storage uses a module listed above it, which is the healthy direction.
15→9 cache.ipc_storage uses protocol✕
- Connections
- 2 pairs of types, where a type in cache.ipc_storage uses a type in protocol.
- The types involved
sccache.cache.ipc_storage.IpcStorage→sccache.protocol.Requestsccache.cache.ipc_storage.IpcStorage→sccache.protocol.StorageHandshakeInfo
- Direction
- cache.ipc_storage uses protocol, so a change to protocol can break cache.ipc_storage, while a change to cache.ipc_storage can't break protocol.
- Position
- Below the diagonal: cache.ipc_storage uses a module listed above it, which is the healthy direction.
15→13 cache.ipc_storage uses client✕
- Connections
- 1 pair of types, where a type in cache.ipc_storage uses a type in client.
- The types involved
sccache.cache.ipc_storage.IpcStorage→sccache.client.ServerConnection
- Direction
- cache.ipc_storage uses client, so a change to client can break cache.ipc_storage, while a change to cache.ipc_storage can't break client.
- Position
- Below the diagonal: cache.ipc_storage uses a module listed above it, which is the healthy direction.
16→14 dist.cache uses lru_disk_cache✕
- Connections
- 1 pair of types, where a type in dist.cache uses a type in lru_disk_cache.
- The types involved
sccache.dist.cache.TcCache→sccache.lru_disk_cache.LruDiskCache
- Direction
- dist.cache uses lru_disk_cache, so a change to lru_disk_cache can break dist.cache, while a change to dist.cache can't break lru_disk_cache.
- Position
- Below the diagonal: dist.cache uses a module listed above it, which is the healthy direction.
16→17 dist.cache uses dist part of a loop✕
- Connections
- 1 pair of types, where a type in dist.cache uses a type in dist.
- The types involved
sccache.dist.cache.TcCache→sccache.dist.Toolchain
- Direction
- dist.cache uses dist, so a change to dist can break dist.cache, while a change to dist.cache can't break dist.
- 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.
17→3 dist uses net✕
- Connections
- 1 pair of types, where a type in dist uses a type in net.
- The types involved
sccache.dist.ServerId→sccache.net.SocketAddr
- Direction
- dist uses net, so a change to net can break dist, while a change to dist can't break net.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
17→16 dist uses dist.cache✕
- Connections
- 1 pair of types, where a type in dist uses a type in dist.cache.
- The types involved
sccache.dist.BuilderIncoming→sccache.dist.cache.TcCache
- Direction
- dist uses dist.cache, so a change to dist.cache can break dist, while a change to dist can't break dist.cache.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
17→22 dist uses compiler.compiler part of a loop✕
- Connections
- 5 pairs of types, where a type in dist uses a type in compiler.compiler.
- The types involved
sccache.dist.BuilderIncoming→sccache.compiler.compiler.CompileCommandsccache.dist.Client→sccache.compiler.compiler.CompileCommandsccache.dist.ServerIncoming→sccache.compiler.compiler.CompileCommandsccache.dist.dist$module→sccache.compiler.compiler.CompileCommandsccache.dist.dist$module→sccache.compiler.compiler.SingleCompileCommand
- Direction
- dist uses compiler.compiler, so a change to compiler.compiler can break dist, while a change to dist can't break compiler.compiler.
- 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→16 dist.cache.client uses dist.cache✕
- Connections
- 1 pair of types, where a type in dist.cache.client uses a type in dist.cache.
- The types involved
sccache.dist.cache.client.ClientToolchains→sccache.dist.cache.TcCache
- Direction
- dist.cache.client uses dist.cache, so a change to dist.cache can break dist.cache.client, while a change to dist.cache.client can't break dist.cache.
- Position
- Below the diagonal: dist.cache.client uses a module listed above it, which is the healthy direction.
18→17 dist.cache.client uses dist✕
- Connections
- 1 pair of types, where a type in dist.cache.client uses a type in dist.
- The types involved
sccache.dist.cache.client.ClientToolchains→sccache.dist.Toolchain
- Direction
- dist.cache.client uses dist, so a change to dist can break dist.cache.client, while a change to dist.cache.client can't break dist.
- Position
- Below the diagonal: dist.cache.client uses a module listed above it, which is the healthy direction.
19→17 dist.http.client uses dist✕
- Connections
- 2 pairs of types, where a type in dist.http.client uses a type in dist.
- The types involved
sccache.dist.http.client.Client→sccache.dist.JobAllocsccache.dist.http.client.Client→sccache.dist.Toolchain
- Direction
- dist.http.client uses dist, so a change to dist can break dist.http.client, while a change to dist.http.client can't break dist.
- Position
- Below the diagonal: dist.http.client uses a module listed above it, which is the healthy direction.
19→18 dist.http.client uses dist.cache.client✕
- Connections
- 1 pair of types, where a type in dist.http.client uses a type in dist.cache.client.
- The types involved
sccache.dist.http.client.Client→sccache.dist.cache.client.ClientToolchains
- Direction
- dist.http.client uses dist.cache.client, so a change to dist.cache.client can break dist.http.client, while a change to dist.http.client can't break dist.cache.client.
- Position
- Below the diagonal: dist.http.client uses a module listed above it, which is the healthy direction.
19→22 dist.http.client uses compiler.compiler part of a loop✕
- Connections
- 1 pair of types, where a type in dist.http.client uses a type in compiler.compiler.
- The types involved
sccache.dist.http.client.Client→sccache.compiler.compiler.CompileCommand
- Direction
- dist.http.client uses compiler.compiler, so a change to compiler.compiler can break dist.http.client, while a change to dist.http.client can't break compiler.compiler.
- 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.
20→3 dist.http.server uses net✕
- Connections
- 3 pairs of types, where a type in dist.http.server uses a type in net.
- The types involved
sccache.dist.http.server.Scheduler→sccache.net.SocketAddrsccache.dist.http.server.Server→sccache.net.SocketAddrsccache.dist.http.server.server$module→sccache.net.SocketAddr
- Direction
- dist.http.server uses net, so a change to net can break dist.http.server, while a change to dist.http.server can't break net.
- Position
- Below the diagonal: dist.http.server uses a module listed above it, which is the healthy direction.
20→4 dist.http.server uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in dist.http.server uses a type in compiler.preprocessor_cache.
- The types involved
sccache.dist.http.server.RouilleBincodeError→sccache.compiler.preprocessor_cache.Error
- Direction
- dist.http.server uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break dist.http.server, while a change to dist.http.server can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: dist.http.server uses a module listed above it, which is the healthy direction.
20→9 dist.http.server uses protocol✕
- Connections
- 2 pairs of types, where a type in dist.http.server uses a type in protocol.
- The types involved
sccache.dist.http.server.server$module→sccache.protocol.Requestsccache.dist.http.server.server$module→sccache.protocol.Response
- Direction
- dist.http.server uses protocol, so a change to protocol can break dist.http.server, while a change to dist.http.server can't break protocol.
- Position
- Below the diagonal: dist.http.server uses a module listed above it, which is the healthy direction.
20→17 dist.http.server uses dist✕
- Connections
- 11 pairs of types, where a type in dist.http.server uses a type in dist.
- The types involved
sccache.dist.http.server.JWTJobAuthorizer→sccache.dist.JobAuthorizersccache.dist.http.server.JWTJobAuthorizer→sccache.dist.JobIdsccache.dist.http.server.JobJwt→sccache.dist.JobIdsccache.dist.http.server.SchedulerRequester→sccache.dist.JobIdsccache.dist.http.server.SchedulerRequester→sccache.dist.SchedulerOutgoingsccache.dist.http.server.SchedulerRequester→sccache.dist.ServerIdsccache.dist.http.server.SchedulerRequester→sccache.dist.Toolchainsccache.dist.http.server.Server→sccache.dist.ServerNoncesccache.dist.http.server.ServerRequester→sccache.dist.JobIdsccache.dist.http.server.ServerRequester→sccache.dist.JobStatesccache.dist.http.server.ServerRequester→sccache.dist.ServerOutgoing
- Direction
- dist.http.server uses dist, so a change to dist can break dist.http.server, while a change to dist.http.server can't break dist.
- Position
- Below the diagonal: dist.http.server uses a module listed above it, which is the healthy direction.
20→19 dist.http.server uses dist.http.client✕
- Connections
- 2 pairs of types, where a type in dist.http.server uses a type in dist.http.client.
- The types involved
sccache.dist.http.server.SchedulerRequester→sccache.dist.http.client.Clientsccache.dist.http.server.ServerRequester→sccache.dist.http.client.Client
- Direction
- dist.http.server uses dist.http.client, so a change to dist.http.client can break dist.http.server, while a change to dist.http.server can't break dist.http.client.
- Position
- Below the diagonal: dist.http.server uses a module listed above it, which is the healthy direction.
21→1 server uses config✕
- Connections
- 5 pairs of types, where a type in server uses a type in config.
- The types involved
sccache.server.DistClientConfig→sccache.config.DistAuthsccache.server.DistClientConfig→sccache.config.DistToolchainConfigsccache.server.DistClientConfig→sccache.config.HTTPUrlsccache.server.DistClientContainer→sccache.config.Configsccache.server.server$module→sccache.config.Config
- Direction
- server uses config, so a change to config can break server, while a change to server can't break config.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
21→3 server uses net✕
- Connections
- 2 pairs of types, where a type in server uses a type in net.
- The types involved
sccache.server.SccacheServer→sccache.net.SocketAddrsccache.server.server$module→sccache.net.SocketAddr
- Direction
- server uses net, so a change to net can break server, while a change to server can't break net.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
21→4 server uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in server uses a type in compiler.preprocessor_cache.
- The types involved
sccache.server.server$module→sccache.compiler.preprocessor_cache.Error
- Direction
- server uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break server, while a change to server can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
21→5 server uses cache.cache_io✕
- Connections
- 3 pairs of types, where a type in server uses a type in cache.cache_io.
- The types involved
sccache.server.SccacheServer→sccache.cache.cache_io.CacheModesccache.server.SccacheService→sccache.cache.cache_io.CacheModesccache.server.ServerInfo→sccache.cache.cache_io.CacheMode
- Direction
- server uses cache.cache_io, so a change to cache.cache_io can break server, while a change to server can't break cache.cache_io.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
21→9 server uses protocol✕
- Connections
- 1 pair of types, where a type in server uses a type in protocol.
- The types involved
sccache.server.SccacheService→sccache.protocol.Compile
- Direction
- server uses protocol, so a change to protocol can break server, while a change to server can't break protocol.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
21→11 server uses cache.multilevel✕
- Connections
- 1 pair of types, where a type in server uses a type in cache.multilevel.
- The types involved
sccache.server.ServerStats→sccache.cache.multilevel.MultiLevelStats
- Direction
- server uses cache.multilevel, so a change to cache.multilevel can break server, while a change to server can't break cache.multilevel.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
21→19 server uses dist.http.client✕
- Connections
- 2 pairs of types, where a type in server uses a type in dist.http.client.
- The types involved
sccache.server.SccacheServer→sccache.dist.http.client.Clientsccache.server.SccacheService→sccache.dist.http.client.Client
- Direction
- server uses dist.http.client, so a change to dist.http.client can break server, while a change to server can't break dist.http.client.
- Position
- Below the diagonal: server uses a module listed above it, which is the healthy direction.
21→22 server uses compiler.compiler part of a loop✕
- Connections
- 2 pairs of types, where a type in server uses a type in compiler.compiler.
- The types involved
sccache.server.PerLanguageCount→sccache.compiler.compiler.CompilerKindsccache.server.PerLanguageCount→sccache.compiler.compiler.Language
- Direction
- server uses compiler.compiler, so a change to compiler.compiler can break server, while a change to server can't break compiler.compiler.
- 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.
22→2 compiler.compiler uses dist.path_transform✕
- Connections
- 3 pairs of types, where a type in compiler.compiler uses a type in dist.path_transform.
- The types involved
sccache.compiler.compiler.Compilation→sccache.dist.path_transform.PathTransformersccache.compiler.compiler.NoopOutputsRewriter→sccache.dist.path_transform.PathTransformersccache.compiler.compiler.OutputsRewriter→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.compiler uses dist.path_transform, so a change to dist.path_transform can break compiler.compiler, while a change to compiler.compiler can't break dist.path_transform.
- Position
- Below the diagonal: compiler.compiler uses a module listed above it, which is the healthy direction.
22→21 compiler.compiler uses server✕
- Connections
- 6 pairs of types, where a type in compiler.compiler uses a type in server.
- The types involved
sccache.compiler.compiler.CCompileCommand→sccache.server.SccacheServicesccache.compiler.compiler.CompileCommand→sccache.server.SccacheServicesccache.compiler.compiler.CompileCommandImpl→sccache.server.SccacheServicesccache.compiler.compiler.CompilerHasher→sccache.server.SccacheServicesccache.compiler.compiler.SingleCompileCommand→sccache.server.SccacheServicesccache.compiler.compiler.compiler$module→sccache.server.SccacheService
- Direction
- compiler.compiler uses server, so a change to server can break compiler.compiler, while a change to compiler.compiler can't break server.
- Position
- Below the diagonal: compiler.compiler uses a module listed above it, which is the healthy direction.
23→16 bin.sccache-dist.build_freebsd uses dist.cache✕
- Connections
- 1 pair of types, where a type in bin.sccache-dist.build_freebsd uses a type in dist.cache.
- The types involved
sccache.bin.sccache-dist.build_freebsd.PotBuilder→sccache.dist.cache.TcCache
- Direction
- bin.sccache-dist.build_freebsd uses dist.cache, so a change to dist.cache can break bin.sccache-dist.build_freebsd, while a change to bin.sccache-dist.build_freebsd can't break dist.cache.
- Position
- Below the diagonal: bin.sccache-dist.build_freebsd uses a module listed above it, which is the healthy direction.
23→17 bin.sccache-dist.build_freebsd uses dist✕
- Connections
- 3 pairs of types, where a type in bin.sccache-dist.build_freebsd uses a type in dist.
- The types involved
sccache.bin.sccache-dist.build_freebsd.PotBuilder→sccache.dist.BuilderIncomingsccache.bin.sccache-dist.build_freebsd.PotBuilder→sccache.dist.InputsReadersccache.bin.sccache-dist.build_freebsd.PotBuilder→sccache.dist.Toolchain
- Direction
- bin.sccache-dist.build_freebsd uses dist, so a change to dist can break bin.sccache-dist.build_freebsd, while a change to bin.sccache-dist.build_freebsd can't break dist.
- Position
- Below the diagonal: bin.sccache-dist.build_freebsd uses a module listed above it, which is the healthy direction.
23→22 bin.sccache-dist.build_freebsd uses compiler.compiler✕
- Connections
- 1 pair of types, where a type in bin.sccache-dist.build_freebsd uses a type in compiler.compiler.
- The types involved
sccache.bin.sccache-dist.build_freebsd.PotBuilder→sccache.compiler.compiler.CompileCommand
- Direction
- bin.sccache-dist.build_freebsd uses compiler.compiler, so a change to compiler.compiler can break bin.sccache-dist.build_freebsd, while a change to bin.sccache-dist.build_freebsd can't break compiler.compiler.
- Position
- Below the diagonal: bin.sccache-dist.build_freebsd uses a module listed above it, which is the healthy direction.
24→1 compiler.c uses config✕
- Connections
- 1 pair of types, where a type in compiler.c uses a type in config.
- The types involved
sccache.compiler.c.c$module→sccache.config.PreprocessorCacheModeConfig
- Direction
- compiler.c uses config, so a change to config can break compiler.c, while a change to compiler.c can't break config.
- Position
- Below the diagonal: compiler.c uses a module listed above it, which is the healthy direction.
24→2 compiler.c uses dist.path_transform✕
- Connections
- 3 pairs of types, where a type in compiler.c uses a type in dist.path_transform.
- The types involved
sccache.compiler.c.CCompilation→sccache.dist.path_transform.PathTransformersccache.compiler.c.CCompilerImpl→sccache.dist.path_transform.PathTransformersccache.compiler.c.CInputsPackager→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.c uses dist.path_transform, so a change to dist.path_transform can break compiler.c, while a change to compiler.c can't break dist.path_transform.
- Position
- Below the diagonal: compiler.c uses a module listed above it, which is the healthy direction.
24→22 compiler.c uses compiler.compiler✕
- Connections
- 12 pairs of types, where a type in compiler.c uses a type in compiler.compiler.
- The types involved
sccache.compiler.c.CCompilation→sccache.compiler.compiler.Compilationsccache.compiler.c.CCompiler→sccache.compiler.compiler.Compilersccache.compiler.c.CCompiler→sccache.compiler.compiler.CompilerArgumentssccache.compiler.c.CCompiler→sccache.compiler.compiler.CompilerKindsccache.compiler.c.CCompilerHasher→sccache.compiler.compiler.CacheControlsccache.compiler.c.CCompilerHasher→sccache.compiler.compiler.ColorModesccache.compiler.c.CCompilerHasher→sccache.compiler.compiler.CompilerHashersccache.compiler.c.CCompilerHasher→sccache.compiler.compiler.Languagesccache.compiler.c.CCompilerImpl→sccache.compiler.compiler.CompilerArgumentssccache.compiler.c.HashKeyParams→sccache.compiler.compiler.Languagesccache.compiler.c.ParsedArguments→sccache.compiler.compiler.ColorModesccache.compiler.c.ParsedArguments→sccache.compiler.compiler.Language
- Direction
- compiler.c uses compiler.compiler, so a change to compiler.compiler can break compiler.c, while a change to compiler.c can't break compiler.compiler.
- Position
- Below the diagonal: compiler.c uses a module listed above it, which is the healthy direction.
25→23 bin.sccache-dist.cmdline uses bin.sccache-dist.build_freebsd✕
- Connections
- 1 pair of types, where a type in bin.sccache-dist.cmdline uses a type in bin.sccache-dist.build_freebsd.
- The types involved
sccache.bin.sccache-dist.cmdline.Command→sccache.bin.sccache-dist.build_freebsd.CommandExt
- Direction
- bin.sccache-dist.cmdline uses bin.sccache-dist.build_freebsd, so a change to bin.sccache-dist.build_freebsd can break bin.sccache-dist.cmdline, while a change to bin.sccache-dist.cmdline can't break bin.sccache-dist.build_freebsd.
- Position
- Below the diagonal: bin.sccache-dist.cmdline uses a module listed above it, which is the healthy direction.
26→2 compiler.cicc uses dist.path_transform✕
- Connections
- 2 pairs of types, where a type in compiler.cicc uses a type in dist.path_transform.
- The types involved
sccache.compiler.cicc.Cicc→sccache.dist.path_transform.PathTransformersccache.compiler.cicc.cicc$module→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.cicc uses dist.path_transform, so a change to dist.path_transform can break compiler.cicc, while a change to compiler.cicc can't break dist.path_transform.
- Position
- Below the diagonal: compiler.cicc uses a module listed above it, which is the healthy direction.
26→22 compiler.cicc uses compiler.compiler✕
- Connections
- 3 pairs of types, where a type in compiler.cicc uses a type in compiler.compiler.
- The types involved
sccache.compiler.cicc.Cicc→sccache.compiler.compiler.CompilerArgumentssccache.compiler.cicc.cicc$module→sccache.compiler.compiler.CompilerArgumentssccache.compiler.cicc.cicc$module→sccache.compiler.compiler.Language
- Direction
- compiler.cicc uses compiler.compiler, so a change to compiler.compiler can break compiler.cicc, while a change to compiler.cicc can't break compiler.compiler.
- Position
- Below the diagonal: compiler.cicc uses a module listed above it, which is the healthy direction.
26→24 compiler.cicc uses compiler.c✕
- Connections
- 4 pairs of types, where a type in compiler.cicc uses a type in compiler.c.
- The types involved
sccache.compiler.cicc.Cicc→sccache.compiler.c.CCompilerImplsccache.compiler.cicc.Cicc→sccache.compiler.c.CCompilerKindsccache.compiler.cicc.Cicc→sccache.compiler.c.ParsedArgumentssccache.compiler.cicc.cicc$module→sccache.compiler.c.ParsedArguments
- Direction
- compiler.cicc uses compiler.c, so a change to compiler.c can break compiler.cicc, while a change to compiler.cicc can't break compiler.c.
- Position
- Below the diagonal: compiler.cicc uses a module listed above it, which is the healthy direction.
27→2 compiler.clang uses dist.path_transform✕
- Connections
- 1 pair of types, where a type in compiler.clang uses a type in dist.path_transform.
- The types involved
sccache.compiler.clang.Clang→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.clang uses dist.path_transform, so a change to dist.path_transform can break compiler.clang, while a change to compiler.clang can't break dist.path_transform.
- Position
- Below the diagonal: compiler.clang uses a module listed above it, which is the healthy direction.
27→22 compiler.clang uses compiler.compiler✕
- Connections
- 2 pairs of types, where a type in compiler.clang uses a type in compiler.compiler.
- The types involved
sccache.compiler.clang.Clang→sccache.compiler.compiler.CompilerArgumentssccache.compiler.clang.clang$module→sccache.compiler.compiler.Language
- Direction
- compiler.clang uses compiler.compiler, so a change to compiler.compiler can break compiler.clang, while a change to compiler.clang can't break compiler.compiler.
- Position
- Below the diagonal: compiler.clang uses a module listed above it, which is the healthy direction.
27→24 compiler.clang uses compiler.c✕
- Connections
- 3 pairs of types, where a type in compiler.clang uses a type in compiler.c.
- The types involved
sccache.compiler.clang.Clang→sccache.compiler.c.CCompilerImplsccache.compiler.clang.Clang→sccache.compiler.c.CCompilerKindsccache.compiler.clang.Clang→sccache.compiler.c.ParsedArguments
- Direction
- compiler.clang uses compiler.c, so a change to compiler.c can break compiler.clang, while a change to compiler.clang can't break compiler.c.
- Position
- Below the diagonal: compiler.clang uses a module listed above it, which is the healthy direction.
28→2 compiler.cudafe uses dist.path_transform✕
- Connections
- 2 pairs of types, where a type in compiler.cudafe uses a type in dist.path_transform.
- The types involved
sccache.compiler.cudafe.CudaFE→sccache.dist.path_transform.PathTransformersccache.compiler.cudafe.cudafe$module→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.cudafe uses dist.path_transform, so a change to dist.path_transform can break compiler.cudafe, while a change to compiler.cudafe can't break dist.path_transform.
- Position
- Below the diagonal: compiler.cudafe uses a module listed above it, which is the healthy direction.
28→22 compiler.cudafe uses compiler.compiler✕
- Connections
- 1 pair of types, where a type in compiler.cudafe uses a type in compiler.compiler.
- The types involved
sccache.compiler.cudafe.CudaFE→sccache.compiler.compiler.CompilerArguments
- Direction
- compiler.cudafe uses compiler.compiler, so a change to compiler.compiler can break compiler.cudafe, while a change to compiler.cudafe can't break compiler.compiler.
- Position
- Below the diagonal: compiler.cudafe uses a module listed above it, which is the healthy direction.
28→24 compiler.cudafe uses compiler.c✕
- Connections
- 4 pairs of types, where a type in compiler.cudafe uses a type in compiler.c.
- The types involved
sccache.compiler.cudafe.CudaFE→sccache.compiler.c.CCompilerImplsccache.compiler.cudafe.CudaFE→sccache.compiler.c.CCompilerKindsccache.compiler.cudafe.CudaFE→sccache.compiler.c.ParsedArgumentssccache.compiler.cudafe.cudafe$module→sccache.compiler.c.ParsedArguments
- Direction
- compiler.cudafe uses compiler.c, so a change to compiler.c can break compiler.cudafe, while a change to compiler.cudafe can't break compiler.c.
- Position
- Below the diagonal: compiler.cudafe uses a module listed above it, which is the healthy direction.
29→2 compiler.diab uses dist.path_transform✕
- Connections
- 2 pairs of types, where a type in compiler.diab uses a type in dist.path_transform.
- The types involved
sccache.compiler.diab.Diab→sccache.dist.path_transform.PathTransformersccache.compiler.diab.diab$module→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.diab uses dist.path_transform, so a change to dist.path_transform can break compiler.diab, while a change to compiler.diab can't break dist.path_transform.
- Position
- Below the diagonal: compiler.diab uses a module listed above it, which is the healthy direction.
29→22 compiler.diab uses compiler.compiler✕
- Connections
- 2 pairs of types, where a type in compiler.diab uses a type in compiler.compiler.
- The types involved
sccache.compiler.diab.Diab→sccache.compiler.compiler.CompilerArgumentssccache.compiler.diab.diab$module→sccache.compiler.compiler.CompilerArguments
- Direction
- compiler.diab uses compiler.compiler, so a change to compiler.compiler can break compiler.diab, while a change to compiler.diab can't break compiler.compiler.
- Position
- Below the diagonal: compiler.diab uses a module listed above it, which is the healthy direction.
29→24 compiler.diab uses compiler.c✕
- Connections
- 4 pairs of types, where a type in compiler.diab uses a type in compiler.c.
- The types involved
sccache.compiler.diab.Diab→sccache.compiler.c.CCompilerImplsccache.compiler.diab.Diab→sccache.compiler.c.CCompilerKindsccache.compiler.diab.Diab→sccache.compiler.c.ParsedArgumentssccache.compiler.diab.diab$module→sccache.compiler.c.ParsedArguments
- Direction
- compiler.diab uses compiler.c, so a change to compiler.c can break compiler.diab, while a change to compiler.diab can't break compiler.c.
- Position
- Below the diagonal: compiler.diab uses a module listed above it, which is the healthy direction.
30→2 compiler.gcc uses dist.path_transform✕
- Connections
- 2 pairs of types, where a type in compiler.gcc uses a type in dist.path_transform.
- The types involved
sccache.compiler.gcc.Gcc→sccache.dist.path_transform.PathTransformersccache.compiler.gcc.gcc$module→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.gcc uses dist.path_transform, so a change to dist.path_transform can break compiler.gcc, while a change to compiler.gcc can't break dist.path_transform.
- Position
- Below the diagonal: compiler.gcc uses a module listed above it, which is the healthy direction.
30→22 compiler.gcc uses compiler.compiler✕
- Connections
- 3 pairs of types, where a type in compiler.gcc uses a type in compiler.compiler.
- The types involved
sccache.compiler.gcc.Gcc→sccache.compiler.compiler.CompilerArgumentssccache.compiler.gcc.gcc$module→sccache.compiler.compiler.CompilerArgumentssccache.compiler.gcc.gcc$module→sccache.compiler.compiler.Language
- Direction
- compiler.gcc uses compiler.compiler, so a change to compiler.compiler can break compiler.gcc, while a change to compiler.gcc can't break compiler.compiler.
- Position
- Below the diagonal: compiler.gcc uses a module listed above it, which is the healthy direction.
30→24 compiler.gcc uses compiler.c✕
- Connections
- 6 pairs of types, where a type in compiler.gcc uses a type in compiler.c.
- The types involved
sccache.compiler.gcc.Gcc→sccache.compiler.c.CCompilerImplsccache.compiler.gcc.Gcc→sccache.compiler.c.CCompilerKindsccache.compiler.gcc.Gcc→sccache.compiler.c.ParsedArgumentssccache.compiler.gcc.gcc$module→sccache.compiler.c.ArtifactDescriptorsccache.compiler.gcc.gcc$module→sccache.compiler.c.CCompilerKindsccache.compiler.gcc.gcc$module→sccache.compiler.c.ParsedArguments
- Direction
- compiler.gcc uses compiler.c, so a change to compiler.c can break compiler.gcc, while a change to compiler.gcc can't break compiler.c.
- Position
- Below the diagonal: compiler.gcc uses a module listed above it, which is the healthy direction.
31→2 compiler.msvc uses dist.path_transform✕
- Connections
- 2 pairs of types, where a type in compiler.msvc uses a type in dist.path_transform.
- The types involved
sccache.compiler.msvc.Msvc→sccache.dist.path_transform.PathTransformersccache.compiler.msvc.msvc$module→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.msvc uses dist.path_transform, so a change to dist.path_transform can break compiler.msvc, while a change to compiler.msvc can't break dist.path_transform.
- Position
- Below the diagonal: compiler.msvc uses a module listed above it, which is the healthy direction.
31→22 compiler.msvc uses compiler.compiler✕
- Connections
- 2 pairs of types, where a type in compiler.msvc uses a type in compiler.compiler.
- The types involved
sccache.compiler.msvc.Msvc→sccache.compiler.compiler.CompilerArgumentssccache.compiler.msvc.msvc$module→sccache.compiler.compiler.CompilerArguments
- Direction
- compiler.msvc uses compiler.compiler, so a change to compiler.compiler can break compiler.msvc, while a change to compiler.msvc can't break compiler.compiler.
- Position
- Below the diagonal: compiler.msvc uses a module listed above it, which is the healthy direction.
31→24 compiler.msvc uses compiler.c✕
- Connections
- 4 pairs of types, where a type in compiler.msvc uses a type in compiler.c.
- The types involved
sccache.compiler.msvc.Msvc→sccache.compiler.c.CCompilerImplsccache.compiler.msvc.Msvc→sccache.compiler.c.CCompilerKindsccache.compiler.msvc.Msvc→sccache.compiler.c.ParsedArgumentssccache.compiler.msvc.msvc$module→sccache.compiler.c.ParsedArguments
- Direction
- compiler.msvc uses compiler.c, so a change to compiler.c can break compiler.msvc, while a change to compiler.msvc can't break compiler.c.
- Position
- Below the diagonal: compiler.msvc uses a module listed above it, which is the healthy direction.
32→2 compiler.nvcc uses dist.path_transform✕
- Connections
- 1 pair of types, where a type in compiler.nvcc uses a type in dist.path_transform.
- The types involved
sccache.compiler.nvcc.Nvcc→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.nvcc uses dist.path_transform, so a change to dist.path_transform can break compiler.nvcc, while a change to compiler.nvcc can't break dist.path_transform.
- Position
- Below the diagonal: compiler.nvcc uses a module listed above it, which is the healthy direction.
32→4 compiler.nvcc uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in compiler.nvcc uses a type in compiler.preprocessor_cache.
- The types involved
sccache.compiler.nvcc.nvcc$module→sccache.compiler.preprocessor_cache.Error
- Direction
- compiler.nvcc uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break compiler.nvcc, while a change to compiler.nvcc can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: compiler.nvcc uses a module listed above it, which is the healthy direction.
32→9 compiler.nvcc uses protocol✕
- Connections
- 1 pair of types, where a type in compiler.nvcc uses a type in protocol.
- The types involved
sccache.compiler.nvcc.nvcc$module→sccache.protocol.CompileFinished
- Direction
- compiler.nvcc uses protocol, so a change to protocol can break compiler.nvcc, while a change to compiler.nvcc can't break protocol.
- Position
- Below the diagonal: compiler.nvcc uses a module listed above it, which is the healthy direction.
32→21 compiler.nvcc uses server✕
- Connections
- 2 pairs of types, where a type in compiler.nvcc uses a type in server.
- The types involved
sccache.compiler.nvcc.NvccCompileCommand→sccache.server.SccacheServicesccache.compiler.nvcc.nvcc$module→sccache.server.SccacheService
- Direction
- compiler.nvcc uses server, so a change to server can break compiler.nvcc, while a change to compiler.nvcc can't break server.
- Position
- Below the diagonal: compiler.nvcc uses a module listed above it, which is the healthy direction.
32→22 compiler.nvcc uses compiler.compiler✕
- Connections
- 3 pairs of types, where a type in compiler.nvcc uses a type in compiler.compiler.
- The types involved
sccache.compiler.nvcc.Nvcc→sccache.compiler.compiler.CompilerArgumentssccache.compiler.nvcc.NvccCompileCommand→sccache.compiler.compiler.CompileCommandImplsccache.compiler.nvcc.NvccGeneratedSubcommand→sccache.compiler.compiler.Cacheable
- Direction
- compiler.nvcc uses compiler.compiler, so a change to compiler.compiler can break compiler.nvcc, while a change to compiler.nvcc can't break compiler.compiler.
- Position
- Below the diagonal: compiler.nvcc uses a module listed above it, which is the healthy direction.
32→24 compiler.nvcc uses compiler.c✕
- Connections
- 4 pairs of types, where a type in compiler.nvcc uses a type in compiler.c.
- The types involved
sccache.compiler.nvcc.Nvcc→sccache.compiler.c.CCompilerImplsccache.compiler.nvcc.Nvcc→sccache.compiler.c.CCompilerKindsccache.compiler.nvcc.Nvcc→sccache.compiler.c.ParsedArgumentssccache.compiler.nvcc.nvcc$module→sccache.compiler.c.ParsedArguments
- Direction
- compiler.nvcc uses compiler.c, so a change to compiler.c can break compiler.nvcc, while a change to compiler.nvcc can't break compiler.c.
- Position
- Below the diagonal: compiler.nvcc uses a module listed above it, which is the healthy direction.
33→2 compiler.nvhpc uses dist.path_transform✕
- Connections
- 1 pair of types, where a type in compiler.nvhpc uses a type in dist.path_transform.
- The types involved
sccache.compiler.nvhpc.Nvhpc→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.nvhpc uses dist.path_transform, so a change to dist.path_transform can break compiler.nvhpc, while a change to compiler.nvhpc can't break dist.path_transform.
- Position
- Below the diagonal: compiler.nvhpc uses a module listed above it, which is the healthy direction.
33→22 compiler.nvhpc uses compiler.compiler✕
- Connections
- 1 pair of types, where a type in compiler.nvhpc uses a type in compiler.compiler.
- The types involved
sccache.compiler.nvhpc.Nvhpc→sccache.compiler.compiler.CompilerArguments
- Direction
- compiler.nvhpc uses compiler.compiler, so a change to compiler.compiler can break compiler.nvhpc, while a change to compiler.nvhpc can't break compiler.compiler.
- Position
- Below the diagonal: compiler.nvhpc uses a module listed above it, which is the healthy direction.
33→24 compiler.nvhpc uses compiler.c✕
- Connections
- 3 pairs of types, where a type in compiler.nvhpc uses a type in compiler.c.
- The types involved
sccache.compiler.nvhpc.Nvhpc→sccache.compiler.c.CCompilerImplsccache.compiler.nvhpc.Nvhpc→sccache.compiler.c.CCompilerKindsccache.compiler.nvhpc.Nvhpc→sccache.compiler.c.ParsedArguments
- Direction
- compiler.nvhpc uses compiler.c, so a change to compiler.c can break compiler.nvhpc, while a change to compiler.nvhpc can't break compiler.c.
- Position
- Below the diagonal: compiler.nvhpc uses a module listed above it, which is the healthy direction.
34→2 compiler.ptxas uses dist.path_transform✕
- Connections
- 1 pair of types, where a type in compiler.ptxas uses a type in dist.path_transform.
- The types involved
sccache.compiler.ptxas.Ptxas→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.ptxas uses dist.path_transform, so a change to dist.path_transform can break compiler.ptxas, while a change to compiler.ptxas can't break dist.path_transform.
- Position
- Below the diagonal: compiler.ptxas uses a module listed above it, which is the healthy direction.
34→22 compiler.ptxas uses compiler.compiler✕
- Connections
- 1 pair of types, where a type in compiler.ptxas uses a type in compiler.compiler.
- The types involved
sccache.compiler.ptxas.Ptxas→sccache.compiler.compiler.CompilerArguments
- Direction
- compiler.ptxas uses compiler.compiler, so a change to compiler.compiler can break compiler.ptxas, while a change to compiler.ptxas can't break compiler.compiler.
- Position
- Below the diagonal: compiler.ptxas uses a module listed above it, which is the healthy direction.
34→24 compiler.ptxas uses compiler.c✕
- Connections
- 3 pairs of types, where a type in compiler.ptxas uses a type in compiler.c.
- The types involved
sccache.compiler.ptxas.Ptxas→sccache.compiler.c.CCompilerImplsccache.compiler.ptxas.Ptxas→sccache.compiler.c.CCompilerKindsccache.compiler.ptxas.Ptxas→sccache.compiler.c.ParsedArguments
- Direction
- compiler.ptxas uses compiler.c, so a change to compiler.c can break compiler.ptxas, while a change to compiler.ptxas can't break compiler.c.
- Position
- Below the diagonal: compiler.ptxas uses a module listed above it, which is the healthy direction.
35→2 compiler.rust uses dist.path_transform✕
- Connections
- 3 pairs of types, where a type in compiler.rust uses a type in dist.path_transform.
- The types involved
sccache.compiler.rust.RustCompilation→sccache.dist.path_transform.PathTransformersccache.compiler.rust.RustInputsPackager→sccache.dist.path_transform.PathTransformersccache.compiler.rust.rust$module→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.rust uses dist.path_transform, so a change to dist.path_transform can break compiler.rust, while a change to compiler.rust can't break dist.path_transform.
- Position
- Below the diagonal: compiler.rust uses a module listed above it, which is the healthy direction.
35→6 compiler.rust uses compiler.args✕
- Connections
- 16 pairs of types, where a type in compiler.rust uses a type in compiler.args.
- The types involved
sccache.compiler.rust.ArgCodegen→sccache.compiler.args.FromArgsccache.compiler.rust.ArgCodegen→sccache.compiler.args.IntoArgsccache.compiler.rust.ArgCrateTypes→sccache.compiler.args.FromArgsccache.compiler.rust.ArgCrateTypes→sccache.compiler.args.IntoArgsccache.compiler.rust.ArgExtern→sccache.compiler.args.FromArgsccache.compiler.rust.ArgExtern→sccache.compiler.args.IntoArgsccache.compiler.rust.ArgLinkLibrary→sccache.compiler.args.FromArgsccache.compiler.rust.ArgLinkLibrary→sccache.compiler.args.IntoArgsccache.compiler.rust.ArgLinkPath→sccache.compiler.args.FromArgsccache.compiler.rust.ArgLinkPath→sccache.compiler.args.IntoArgsccache.compiler.rust.ArgTarget→sccache.compiler.args.FromArgsccache.compiler.rust.ArgTarget→sccache.compiler.args.IntoArgsccache.compiler.rust.ArgUnstable→sccache.compiler.args.FromArgsccache.compiler.rust.ArgUnstable→sccache.compiler.args.IntoArgsccache.compiler.rust.ParsedArguments→sccache.compiler.args.Argumentsccache.compiler.rust.RustCompilation→sccache.compiler.args.Argument
- Direction
- compiler.rust uses compiler.args, so a change to compiler.args can break compiler.rust, while a change to compiler.rust can't break compiler.args.
- Position
- Below the diagonal: compiler.rust uses a module listed above it, which is the healthy direction.
35→8 compiler.rust uses lru_disk_cache.lru_cache✕
- Connections
- 2 pairs of types, where a type in compiler.rust uses a type in lru_disk_cache.lru_cache.
- The types involved
sccache.compiler.rust.DepsSize→sccache.lru_disk_cache.lru_cache.Metersccache.compiler.rust.RlibDepReader→sccache.lru_disk_cache.lru_cache.LruCache
- Direction
- compiler.rust uses lru_disk_cache.lru_cache, so a change to lru_disk_cache.lru_cache can break compiler.rust, while a change to compiler.rust can't break lru_disk_cache.lru_cache.
- Position
- Below the diagonal: compiler.rust uses a module listed above it, which is the healthy direction.
35→22 compiler.rust uses compiler.compiler✕
- Connections
- 11 pairs of types, where a type in compiler.rust uses a type in compiler.compiler.
- The types involved
sccache.compiler.rust.ParsedArguments→sccache.compiler.compiler.ColorModesccache.compiler.rust.Rust→sccache.compiler.compiler.Compilersccache.compiler.rust.Rust→sccache.compiler.compiler.CompilerArgumentssccache.compiler.rust.Rust→sccache.compiler.compiler.CompilerKindsccache.compiler.rust.RustCompilation→sccache.compiler.compiler.Compilationsccache.compiler.rust.RustHasher→sccache.compiler.compiler.CacheControlsccache.compiler.rust.RustHasher→sccache.compiler.compiler.ColorModesccache.compiler.rust.RustHasher→sccache.compiler.compiler.CompilerHashersccache.compiler.rust.RustHasher→sccache.compiler.compiler.Languagesccache.compiler.rust.RustupProxy→sccache.compiler.compiler.CompilerProxysccache.compiler.rust.rust$module→sccache.compiler.compiler.CompilerArguments
- Direction
- compiler.rust uses compiler.compiler, so a change to compiler.compiler can break compiler.rust, while a change to compiler.rust can't break compiler.compiler.
- Position
- Below the diagonal: compiler.rust uses a module listed above it, which is the healthy direction.
35→24 compiler.rust uses compiler.c✕
- Connections
- 1 pair of types, where a type in compiler.rust uses a type in compiler.c.
- The types involved
sccache.compiler.rust.RustHasher→sccache.compiler.c.ParsedArguments
- Direction
- compiler.rust uses compiler.c, so a change to compiler.c can break compiler.rust, while a change to compiler.rust can't break compiler.c.
- Position
- Below the diagonal: compiler.rust uses a module listed above it, which is the healthy direction.
36→2 compiler.tasking_vx uses dist.path_transform✕
- Connections
- 2 pairs of types, where a type in compiler.tasking_vx uses a type in dist.path_transform.
- The types involved
sccache.compiler.tasking_vx.TaskingVX→sccache.dist.path_transform.PathTransformersccache.compiler.tasking_vx.tasking_vx$module→sccache.dist.path_transform.PathTransformer
- Direction
- compiler.tasking_vx uses dist.path_transform, so a change to dist.path_transform can break compiler.tasking_vx, while a change to compiler.tasking_vx can't break dist.path_transform.
- Position
- Below the diagonal: compiler.tasking_vx uses a module listed above it, which is the healthy direction.
36→22 compiler.tasking_vx uses compiler.compiler✕
- Connections
- 2 pairs of types, where a type in compiler.tasking_vx uses a type in compiler.compiler.
- The types involved
sccache.compiler.tasking_vx.TaskingVX→sccache.compiler.compiler.CompilerArgumentssccache.compiler.tasking_vx.tasking_vx$module→sccache.compiler.compiler.CompilerArguments
- Direction
- compiler.tasking_vx uses compiler.compiler, so a change to compiler.compiler can break compiler.tasking_vx, while a change to compiler.tasking_vx can't break compiler.compiler.
- Position
- Below the diagonal: compiler.tasking_vx uses a module listed above it, which is the healthy direction.
36→24 compiler.tasking_vx uses compiler.c✕
- Connections
- 4 pairs of types, where a type in compiler.tasking_vx uses a type in compiler.c.
- The types involved
sccache.compiler.tasking_vx.TaskingVX→sccache.compiler.c.CCompilerImplsccache.compiler.tasking_vx.TaskingVX→sccache.compiler.c.CCompilerKindsccache.compiler.tasking_vx.TaskingVX→sccache.compiler.c.ParsedArgumentssccache.compiler.tasking_vx.tasking_vx$module→sccache.compiler.c.ParsedArguments
- Direction
- compiler.tasking_vx uses compiler.c, so a change to compiler.c can break compiler.tasking_vx, while a change to compiler.tasking_vx can't break compiler.c.
- Position
- Below the diagonal: compiler.tasking_vx uses a module listed above it, which is the healthy direction.
37→16 bin.sccache-dist.main uses dist.cache✕
- Connections
- 1 pair of types, where a type in bin.sccache-dist.main uses a type in dist.cache.
- The types involved
sccache.bin.sccache-dist.main.Server→sccache.dist.cache.TcCache
- Direction
- bin.sccache-dist.main uses dist.cache, so a change to dist.cache can break bin.sccache-dist.main, while a change to bin.sccache-dist.main can't break dist.cache.
- Position
- Below the diagonal: bin.sccache-dist.main uses a module listed above it, which is the healthy direction.
37→17 bin.sccache-dist.main uses dist✕
- Connections
- 16 pairs of types, where a type in bin.sccache-dist.main uses a type in dist.
- The types involved
sccache.bin.sccache-dist.main.JobDetail→sccache.dist.JobStatesccache.bin.sccache-dist.main.JobDetail→sccache.dist.ServerIdsccache.bin.sccache-dist.main.Scheduler→sccache.dist.JobIdsccache.bin.sccache-dist.main.Scheduler→sccache.dist.JobStatesccache.bin.sccache-dist.main.Scheduler→sccache.dist.SchedulerIncomingsccache.bin.sccache-dist.main.Scheduler→sccache.dist.ServerIdsccache.bin.sccache-dist.main.Scheduler→sccache.dist.ServerNoncesccache.bin.sccache-dist.main.Scheduler→sccache.dist.Toolchainsccache.bin.sccache-dist.main.Server→sccache.dist.InputsReadersccache.bin.sccache-dist.main.Server→sccache.dist.JobIdsccache.bin.sccache-dist.main.Server→sccache.dist.ServerIncomingsccache.bin.sccache-dist.main.Server→sccache.dist.Toolchainsccache.bin.sccache-dist.main.Server→sccache.dist.ToolchainReadersccache.bin.sccache-dist.main.ServerDetails→sccache.dist.ServerNoncesccache.bin.sccache-dist.main.ServerJwt→sccache.dist.ServerIdsccache.bin.sccache-dist.main.main$module→sccache.dist.ServerId
- Direction
- bin.sccache-dist.main uses dist, so a change to dist can break bin.sccache-dist.main, while a change to bin.sccache-dist.main can't break dist.
- Position
- Below the diagonal: bin.sccache-dist.main uses a module listed above it, which is the healthy direction.
37→22 bin.sccache-dist.main uses compiler.compiler✕
- Connections
- 1 pair of types, where a type in bin.sccache-dist.main uses a type in compiler.compiler.
- The types involved
sccache.bin.sccache-dist.main.Server→sccache.compiler.compiler.CompileCommand
- Direction
- bin.sccache-dist.main uses compiler.compiler, so a change to compiler.compiler can break bin.sccache-dist.main, while a change to bin.sccache-dist.main can't break compiler.compiler.
- Position
- Below the diagonal: bin.sccache-dist.main uses a module listed above it, which is the healthy direction.
37→25 bin.sccache-dist.main uses bin.sccache-dist.cmdline✕
- Connections
- 1 pair of types, where a type in bin.sccache-dist.main uses a type in bin.sccache-dist.cmdline.
- The types involved
sccache.bin.sccache-dist.main.main$module→sccache.bin.sccache-dist.cmdline.Command
- Direction
- bin.sccache-dist.main uses bin.sccache-dist.cmdline, so a change to bin.sccache-dist.cmdline can break bin.sccache-dist.main, while a change to bin.sccache-dist.main can't break bin.sccache-dist.cmdline.
- Position
- Below the diagonal: bin.sccache-dist.main uses a module listed above it, which is the healthy direction.
38→1 commands uses config✕
- Connections
- 1 pair of types, where a type in commands uses a type in config.
- The types involved
sccache.commands.commands$module→sccache.config.Config
- Direction
- commands uses config, so a change to config can break commands, while a change to commands can't break config.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→3 commands uses net✕
- Connections
- 1 pair of types, where a type in commands uses a type in net.
- The types involved
sccache.commands.commands$module→sccache.net.SocketAddr
- Direction
- commands uses net, so a change to net can break commands, while a change to commands can't break net.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→5 commands uses cache.cache_io✕
- Connections
- 1 pair of types, where a type in commands uses a type in cache.cache_io.
- The types involved
sccache.commands.StatsOutput→sccache.cache.cache_io.CacheMode
- Direction
- commands uses cache.cache_io, so a change to cache.cache_io can break commands, while a change to commands can't break cache.cache_io.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→9 commands uses protocol✕
- Connections
- 2 pairs of types, where a type in commands uses a type in protocol.
- The types involved
sccache.commands.commands$module→sccache.protocol.CompileFinishedsccache.commands.commands$module→sccache.protocol.CompileResponse
- Direction
- commands uses protocol, so a change to protocol can break commands, while a change to commands can't break protocol.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→13 commands uses client✕
- Connections
- 1 pair of types, where a type in commands uses a type in client.
- The types involved
sccache.commands.commands$module→sccache.client.ServerConnection
- Direction
- commands uses client, so a change to client can break commands, while a change to commands can't break client.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→19 commands uses dist.http.client✕
- Connections
- 1 pair of types, where a type in commands uses a type in dist.http.client.
- The types involved
sccache.commands.commands$module→sccache.dist.http.client.Client
- Direction
- commands uses dist.http.client, so a change to dist.http.client can break commands, while a change to commands can't break dist.http.client.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→21 commands uses server✕
- Connections
- 1 pair of types, where a type in commands uses a type in server.
- The types involved
sccache.commands.StatsOutput→sccache.server.ServerInfo
- Direction
- commands uses server, so a change to server can break commands, while a change to commands can't break server.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
38→25 commands uses bin.sccache-dist.cmdline✕
- Connections
- 1 pair of types, where a type in commands uses a type in bin.sccache-dist.cmdline.
- The types involved
sccache.commands.commands$module→sccache.bin.sccache-dist.cmdline.Command
- Direction
- commands uses bin.sccache-dist.cmdline, so a change to bin.sccache-dist.cmdline can break commands, while a change to commands can't break bin.sccache-dist.cmdline.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
39→19 jobserver uses dist.http.client✕
- Connections
- 1 pair of types, where a type in jobserver uses a type in dist.http.client.
- The types involved
sccache.jobserver.Client→sccache.dist.http.client.Client
- Direction
- jobserver uses dist.http.client, so a change to dist.http.client can break jobserver, while a change to jobserver can't break dist.http.client.
- Position
- Below the diagonal: jobserver uses a module listed above it, which is the healthy direction.
39→25 jobserver uses bin.sccache-dist.cmdline✕
- Connections
- 1 pair of types, where a type in jobserver uses a type in bin.sccache-dist.cmdline.
- The types involved
sccache.jobserver.Client→sccache.bin.sccache-dist.cmdline.Command
- Direction
- jobserver uses bin.sccache-dist.cmdline, so a change to bin.sccache-dist.cmdline can break jobserver, while a change to jobserver can't break bin.sccache-dist.cmdline.
- Position
- Below the diagonal: jobserver uses a module listed above it, which is the healthy direction.
40→4 mock_command uses compiler.preprocessor_cache✕
- Connections
- 1 pair of types, where a type in mock_command uses a type in compiler.preprocessor_cache.
- The types involved
sccache.mock_command.MockChild→sccache.compiler.preprocessor_cache.Error
- Direction
- mock_command uses compiler.preprocessor_cache, so a change to compiler.preprocessor_cache can break mock_command, while a change to mock_command can't break compiler.preprocessor_cache.
- Position
- Below the diagonal: mock_command uses a module listed above it, which is the healthy direction.
40→19 mock_command uses dist.http.client✕
- Connections
- 5 pairs of types, where a type in mock_command uses a type in dist.http.client.
- The types involved
sccache.mock_command.AsyncCommand→sccache.dist.http.client.Clientsccache.mock_command.CommandCreator→sccache.dist.http.client.Clientsccache.mock_command.CommandCreatorSync→sccache.dist.http.client.Clientsccache.mock_command.MockCommandCreator→sccache.dist.http.client.Clientsccache.mock_command.ProcessCommandCreator→sccache.dist.http.client.Client
- Direction
- mock_command uses dist.http.client, so a change to dist.http.client can break mock_command, while a change to mock_command can't break dist.http.client.
- Position
- Below the diagonal: mock_command uses a module listed above it, which is the healthy direction.
40→25 mock_command uses bin.sccache-dist.cmdline✕
- Connections
- 1 pair of types, where a type in mock_command uses a type in bin.sccache-dist.cmdline.
- The types involved
sccache.mock_command.AsyncCommand→sccache.bin.sccache-dist.cmdline.Command
- Direction
- mock_command uses bin.sccache-dist.cmdline, so a change to bin.sccache-dist.cmdline can break mock_command, while a change to mock_command can't break bin.sccache-dist.cmdline.
- Position
- Below the diagonal: mock_command uses a module listed above it, which is the healthy direction.
40→39 mock_command uses jobserver✕
- Connections
- 1 pair of types, where a type in mock_command uses a type in jobserver.
- The types involved
sccache.mock_command.Child→sccache.jobserver.Acquired
- Direction
- mock_command uses jobserver, so a change to jobserver can break mock_command, while a change to mock_command can't break jobserver.
- Position
- Below the diagonal: mock_command uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 55 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 49 | High / Critical |
Roadmap
Immediately secure cryptographic keys by moving them out of source code into configuration or secrets managers and rotating any previously committed material, while ensuring salts are generated per password. Address supply-chain risks by scoping long-lived secrets in CI workflows and resolve static analysis issues related to mutable container images. Finally, establish architectural decision records to document design choices and remediate medium-severity dependency vulnerabilities in the project lock file.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations. | +6.9 pts | Medium | Web-Security Posture |
| Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +3.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.3 pts | Low | ADR Quality |
| Resolve the 1 Flaky test finding(s) in Test Reliability. | +1.5 pts | Low | Test Reliability |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +1.4 pts | Low | Static Analysis (SAST) |
| Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED. | +2.7 pts | Medium | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 31 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). | +1.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/compiler/gcc.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/compiler/msvc.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/compiler/rust.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/config.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/compiler/c.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/server.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/commands.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/compiler/diab.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/compiler/compiler.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/compiler/nvcc.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/util.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tests/system.rs | 6.5 | Mixed | 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. 51 of 51 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 51 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 317 of 361 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 (`grcov .`) 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.
- 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (tests/integration/xcode/xcode-test.xcodeproj/project.pbxproj). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
27 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was sccache::compiler::gcc::parse_arguments at 104. A further 3 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Language::to_compiler_arg at 22 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with sccache::compiler::gcc::parse_arguments (cyclomatic 104), sccache::compiler::msvc::parse_arguments (cyclomatic 70), sccache::compiler::rust::parse_arguments (cyclomatic 56). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 5.7 to about 7.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
42 function(s) exceeded the cognitive complexity threshold of 15; the worst was sccache::compiler::gcc::parse_arguments at 84.
What to do
- Bring the 42 bodies over 15 down to 15 or less in Cognitive Complexity — start with sccache::compiler::gcc::parse_arguments (cognitive 84), sccache::compiler::rust::parse_arguments (cognitive 75), sccache::compiler::msvc::parse_arguments (cognitive 74). — 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 42 together lifts Cognitive Complexity from 4.9 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
37 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 15 FunctionTooLong finding(s) in God Classes — start with compiler.rs (2), nvcc.rs (2), gcc.rs. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 13 FileTooLong finding(s) in God Classes — start with rust.rs, server.rs, compiler.rs. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 8 MethodTooLong finding(s) in God Classes — start with rust.rs (2), server.rs (2), compiler.rs. — One of this dimension's main actionable groups (8 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
30 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 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with gcc.rs, server.rs, cache.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (6 lines × 3) finding(s) in Code Duplication — start with cache.rs (2), diab.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with client_auth.rs, main.rs. — One of this dimension's main actionable groups (2 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.
D6 · Cohesion (LCOM4)
0 of 58 classes have LCOM4 above 3.
D9 · Test Distribution
629 test methods: 590 unit, 39 integration, 0 BDD, 0 e2e. The Rust suite contributes 629 `#[test]` function(s) across 46 file(s) declaring at least one; its unit/integration split is Cargo's own — 10 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.
D11 · Test Reliability
1 flaky across 1 measured tier(s). Rust (repository root, 46 test files): measured (1 flaky).
What to do
- Resolve the 1 Flaky test finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
31 outdated, 0 yanked direct Cargo dependencies. 71 of 73 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 511 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 Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/compiler/msvc.rs (17×70=1190); src/compiler/rust.rs (20×56=1120); src/compiler/gcc.rs (7×104=728)
What to do
- Resolve the 12 Hotspot finding(s) in Churn × Complexity Hotspots — start with msvc.rs, rust.rs, gcc.rs. — One of this dimension's main actionable groups (12 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/cache/ipc_storage.rs. Counted over 38 of the 51 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
60 deducted task-comment markers across 43630 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 55 TodoComment finding(s) in Explicit Debt — start with rust.rs (7), mod.rs (6), server.rs (6). — One of this dimension's main actionable groups (55 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with lru_cache.rs, diab.rs, msvc.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 HackComment finding(s) in Explicit Debt — start with server.rs, nvcc.rs. — One of this dimension's main actionable groups (2 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. 24 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 1 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)
55 finding(s): 0 critical, 55 high, 0 medium, 0 low. 31 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `.github/actions/nvcc-toolchain/install-cuda.sh` (line 32) — 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 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 31 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (32 issue-level, 1 of them charged here).
D30 · Dependency Vulnerabilities
41 finding(s): 0 critical, 3 high, 38 medium, 0 low.
What to do
- Resolve the 13 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 10 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
3 of 38 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/lru_disk_cache/lru_cache.rs. Counted over 38 of the 51 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with lru_cache.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with nvhpc.rs, cmdline.rs. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
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
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — src/bin/sccache-dist/main.rs:131
What to do
- Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
- `len` is read from the bytes being parsed at line 62 (`BigEndian::read_u32`), then used to size a `vec![…; n]` at line 64 — and nowhere in its scope is `len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining and a maximum the format allows before allocating. — src/client.rs:64
- `len` is read from the bytes being parsed at line 86 (`BigEndian::read_u32`), then used to size a `vec![…; n]` at line 87 — and nowhere in its scope is `len` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining and a maximum the format allows before allocating. — src/commands.rs:87
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 86% | Strong | Solid. |
| Architecture | 87% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 73% | Strong | Solid. |
| Readiness | 73% | Strong | Solid. |
| Security | 59% | Adequate — gated by D29, D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Strongest area. |
Unscored — 2 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 — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — 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 — ~9351 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (21 value object(s))
- 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
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 61 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Flaky test: sccache::system.test_assembler_affects_cache::with_preprocessor_cache
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/lru_disk_cache/lru_cache.rs:1
- Cryptographic key material is a compile-time constant src/bin/sccache-dist/main.rs:131
Serious — 256 finding(s)
- TodoComment tests/system.rs:86
- TodoComment tests/system.rs:94
- TodoComment tests/system.rs:116
- TodoComment tests/system.rs:157
- TodoComment tests/system.rs:1950
- TodoComment tests/harness/mod.rs:192
- TodoComment src/util.rs:324
- TodoComment tests/harness/mod.rs:236
- TodoComment tests/harness/mod.rs:497
- TodoComment tests/harness/mod.rs:731
- TodoComment src/commands.rs:243
- TodoComment src/commands.rs:406
- TodoComment src/commands.rs:437
- TodoComment src/commands.rs:563
- TodoComment src/config.rs:217
- TodoComment src/config.rs:790
- TodoComment src/mock_command.rs:356
- TodoComment src/mock_command.rs:489
- TodoComment src/mock_command.rs:548
- TodoComment src/net.rs:167
- TodoComment src/server.rs:1309
- TodoComment src/server.rs:1404
- TodoComment src/server.rs:1405
- TodoComment src/server.rs:1716
- TodoComment src/server.rs:1731
- sccache::compiler::gcc::parse_arguments (cognitive 84) src/compiler/gcc.rs:291
- sccache::compiler::rust::parse_arguments (cognitive 75) src/compiler/rust.rs:1404
- sccache::compiler::msvc::parse_arguments (cognitive 74) src/compiler/msvc.rs:630
- sccache::cmdline::try_parse (cognitive 53) src/cmdline.rs:187
- sccache::compiler::nvcc::group_nvcc_subcommands_by_compilation_stage (cognitive 47) src/compiler/nvcc.rs:646
- sccache::config::config_from_env (cognitive 46) src/config.rs:896
- sccache::compiler::nvcc::generate_compile_commands (cognitive 39) src/compiler/nvcc.rs:316
- sccache::compiler::c::process_preprocessor_line (cognitive 32) src/compiler/c.rs:858
- sccache::compiler::c::process_preprocessed_file (cognitive 31) src/compiler/c.rs:738
- sccache::compiler::gcc::split_gnu_response_file_args (cognitive 28) src/compiler/gcc.rs:1252
- sccache::bin::sccache-dist::cmdline::parse::try_parse_from (cognitive 27) src/bin/sccache-dist/cmdline/parse.rs:176
- sccache::compiler::diab::parse_arguments (cognitive 26) src/compiler/diab.rs:174
- sccache::compiler::cicc::parse_arguments (cognitive 25) src/compiler/cicc.rs:115
- sccache::compiler::c::remember_include_file (cognitive 23) src/compiler/c.rs:1062
- sccache::compiler::compiler::dist_or_local_compile (cognitive 23) src/compiler/compiler.rs:908
- sccache::compiler::msvc::preprocess (cognitive 23) src/compiler/msvc.rs:1174
- sccache::compiler::tasking_vx::parse_arguments (cognitive 23) src/compiler/tasking_vx.rs:169
- sccache::commands::run_command (cognitive 21) src/commands.rs:797
- sccache::compiler::gcc::generate_compile_commands (cognitive 21) src/compiler/gcc.rs:1023
- sccache::compiler::nvcc::fold_env_vars_or_split_into_exe_and_args (cognitive 18) src/compiler/nvcc.rs:1056
- sccache::util::strip_basedirs (cognitive 18) src/util.rs:1251
- sccache::util::strip_basedirs_from_arg (cognitive 18) src/util.rs:1374
- sccache::compiler::nvcc::select_nvcc_subcommands (cognitive 17) src/compiler/nvcc.rs:936
- sccache::commands::handle_compile_response (cognitive 16) src/commands.rs:527
- sccache::compiler::gcc::parse_arguments (cyclomatic 104) src/compiler/gcc.rs:291
- sccache::compiler::msvc::parse_arguments (cyclomatic 70) src/compiler/msvc.rs:630
- sccache::compiler::rust::parse_arguments (cyclomatic 56) src/compiler/rust.rs:1404
- sccache::config::config_from_env (cyclomatic 34) src/config.rs:896
- sccache::cmdline::try_parse (cyclomatic 27) src/cmdline.rs:187
- sccache::commands::run_command (cyclomatic 24) src/commands.rs:797
- sccache::compiler::diab::parse_arguments (cyclomatic 24) src/compiler/diab.rs:174
- sccache::compiler::tasking_vx::parse_arguments (cyclomatic 24) src/compiler/tasking_vx.rs:169
- sccache::compiler::c::process_preprocessor_line (cyclomatic 23) src/compiler/c.rs:858
- sccache::compiler::c::remember_include_file (cyclomatic 21) src/compiler/c.rs:1062
- sccache::compiler::nvcc::group_nvcc_subcommands_by_compilation_stage (cyclomatic 21) src/compiler/nvcc.rs:646
- sccache::compiler::nvcc::generate_compile_commands (cyclomatic 20) src/compiler/nvcc.rs:316
- sccache::compiler::c::process_preprocessed_file (cyclomatic 18) src/compiler/c.rs:738
- sccache::compiler::cicc::parse_arguments (cyclomatic 18) src/compiler/cicc.rs:115
- sccache::compiler::compiler::dist_or_local_compile (cyclomatic 18) src/compiler/compiler.rs:908
- sccache::compiler::compiler::detect_c_compiler (cyclomatic 17) src/compiler/compiler.rs:1829
- sccache::bin::sccache-dist::main::run (cyclomatic 16) src/bin/sccache-dist/main.rs:147
- sccache::compiler::gcc::generate_compile_commands (cyclomatic 16) src/compiler/gcc.rs:1023
- FunctionTooLong: sccache::compiler::gcc::parse_arguments src/compiler/gcc.rs:291
- FunctionTooLong: sccache::compiler::msvc::parse_arguments src/compiler/msvc.rs:630
- FunctionTooLong: sccache::config::config_from_env src/config.rs:896
- FunctionTooLong: sccache::commands::run_command src/commands.rs:797
- FunctionTooLong: sccache::compiler::compiler::detect_c_compiler src/compiler/compiler.rs:1829
- FunctionTooLong: sccache::cache::cache::build_single_cache src/cache/cache.rs:389
- FunctionTooLong: sccache::compiler::compiler::dist_or_local_compile src/compiler/compiler.rs:908
- FunctionTooLong: sccache::compiler::rust::parse_arguments src/compiler/rust.rs:1404
- FunctionTooLong: sccache::compiler::nvcc::group_nvcc_subcommands_by_compilation_stage src/compiler/nvcc.rs:646
- FunctionTooLong: sccache::bin::sccache-dist::main::run src/bin/sccache-dist/main.rs:147
- FunctionTooLong: sccache::server::start_server src/server.rs:434
- FunctionTooLong: sccache::compiler::nvcc::generate_compile_commands src/compiler/nvcc.rs:316
- FunctionTooLong: sccache::compiler::cicc::parse_arguments src/compiler/cicc.rs:115
- FunctionTooLong: sccache::cmdline::try_parse src/cmdline.rs:187
- FunctionTooLong: sccache::compiler::diab::parse_arguments src/compiler/diab.rs:174
- FileTooLong: compiler/rust.rs src/compiler/rust.rs
- FileTooLong: src/server.rs src/server.rs
- FileTooLong: compiler/compiler.rs src/compiler/compiler.rs
- FileTooLong: src/config.rs src/config.rs
- FileTooLong: compiler/msvc.rs src/compiler/msvc.rs
- FileTooLong: compiler/c.rs src/compiler/c.rs
- FileTooLong: compiler/nvcc.rs src/compiler/nvcc.rs
- FileTooLong: dist/http.rs src/dist/http.rs
- FileTooLong: compiler/gcc.rs src/compiler/gcc.rs
- FileTooLong: src/util.rs src/util.rs
- FileTooLong: src/commands.rs src/commands.rs
- FileTooLong: sccache-dist/main.rs src/bin/sccache-dist/main.rs
- FileTooLong: cache/multilevel.rs src/cache/multilevel.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: src/compiler/msvc.rs src/compiler/msvc.rs:630
- Hotspot: src/compiler/rust.rs src/compiler/rust.rs:1404
- Hotspot: src/compiler/gcc.rs src/compiler/gcc.rs:291
- Hotspot: src/config.rs src/config.rs:896
- Hotspot: src/compiler/c.rs src/compiler/c.rs:396
- Hotspot: src/commands.rs src/commands.rs:797
- Hotspot: src/cache/cache.rs src/cache/cache.rs:389
- Hotspot: src/compiler/nvcc.rs src/compiler/nvcc.rs:646
- Hotspot: src/bin/sccache-dist/main.rs src/bin/sccache-dist/main.rs:147
- Hotspot: src/compiler/cicc.rs src/compiler/cicc.rs:115
- Hotspot: src/compiler/diab.rs src/compiler/diab.rs:174
- Hotspot: src/compiler/tasking_vx.rs src/compiler/tasking_vx.rs:169
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: RustHasher.generate_hash_key src/compiler/rust.rs:1677
- MethodTooLong: CompilerHasher.get_cached_or_compile src/compiler/compiler.rs:576
- MethodTooLong: SccacheService.start_compile_task src/server.rs:1507
- MethodTooLong: Scheduler.start src/dist/http.rs:676
- MethodTooLong: ServerStats.print src/server.rs:1967
- MethodTooLong: RustInputsPackager.write_inputs src/compiler/rust.rs:2483
- MethodTooLong: Scheduler.handle_alloc_job src/bin/sccache-dist/main.rs:452
- MethodTooLong: PreprocessorCacheEntry.result_matches src/compiler/preprocessor_cache.rs:194
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) src/compiler/gcc.rs:1184
- Duplicated block (6 lines × 2) src/server.rs:1979
- Duplicated block (6 lines × 2) src/cache/cache.rs:411
- Duplicated block (6 lines × 2) src/dist/client_auth.rs:206
- FixmeComment src/lru_disk_cache/lru_cache.rs:47
- FixmeComment src/compiler/diab.rs:317
- FixmeComment src/compiler/msvc.rs:1058
- Scheduler::handle_heartbeat_server (cognitive 36) src/bin/sccache-dist/main.rs:603
- Scheduler::handle_alloc_job (cognitive 33) src/bin/sccache-dist/main.rs:452
- Scheduler::handle_update_job_state (cognitive 16) src/bin/sccache-dist/main.rs:712
- Duplicated block (6 lines × 3) src/compiler/diab.rs:395
- Duplicated block (6 lines × 3) src/cache/cache.rs:543
- Duplicated block (6 lines × 3) src/cache/cache.rs:411
- HackComment src/server.rs:1532
- HackComment src/compiler/nvcc.rs:885
- SccacheService::start_compile_task (cognitive 34) src/server.rs:1507
- SccacheService::compiler_info (cognitive 20) src/server.rs:1269
- Duplicated block (5 lines × 2) src/dist/client_auth.rs:540
- Duplicated block (5 lines × 2) src/bin/sccache-dist/main.rs:71
- Duplicated block (9 lines × 2) src/compiler/clang.rs:103
- Duplicated block (9 lines × 2) src/compiler/tasking_vx.rs:319
- Length read from the parsed input is spent without ever being bounded src/client.rs:64
- Length read from the parsed input is spent without ever being bounded src/commands.rs:87
- RustInputsPackager::write_inputs (cyclomatic 30) src/compiler/rust.rs:2483
- CCompilerHasher::generate_hash_key (cyclomatic 28) src/compiler/c.rs:396
- RustHasher::generate_hash_key (cyclomatic 25) src/compiler/rust.rs:1677
- SccacheService::start_compile_task (cyclomatic 25) src/server.rs:1507
- PreprocessorCacheEntry::result_matches (cyclomatic 23) src/compiler/preprocessor_cache.rs:194
- ServerStats::print (cyclomatic 22) src/server.rs:1967
- CompilerHasher::get_cached_or_compile (cyclomatic 21) src/compiler/compiler.rs:576
- Scheduler::handle_heartbeat_server (cyclomatic 17) src/bin/sccache-dist/main.rs:603
- RustCompilation::generate_compile_commands (cyclomatic 17) src/compiler/rust.rs:2078
- CCompilerHasher::generate_hash_key (cognitive 62) src/compiler/c.rs:396
- PreprocessorCacheEntry::result_matches (cognitive 62) src/compiler/preprocessor_cache.rs:194
- RustInputsPackager::write_inputs (cognitive 55) src/compiler/rust.rs:2483
- MultiLevelStorage::put_raw (cognitive 38) src/cache/multilevel.rs:654
- ServerStats::print (cognitive 35) src/server.rs:1967
- RustHasher::generate_hash_key (cognitive 32) src/compiler/rust.rs:1677
- CompilerHasher::get_cached_or_compile (cognitive 29) src/compiler/compiler.rs:576
- RustCompilation::generate_compile_commands (cognitive 25) src/compiler/rust.rs:2078
- CacheRead::extract_objects (cognitive 18) src/cache/cache_io.rs:132
- ArgsIter::next (cognitive 17) src/compiler/args.rs:618
- ClientToolchains::new (cognitive 17) src/dist/cache.rs:58
- RustupProxy::find_proxy_executable (cognitive 16) src/compiler/rust.rs:902
- TimeMacroFinder::find_time_macros (cognitive 16) src/util.rs:251
- ClassTooLong: SccacheService src/server.rs:808
- REDACTED
- Near-duplicate member pair (61 shared lines) src/compiler/diab.rs:181
- Near-duplicate member pair (59 shared lines) src/compiler/cicc.rs:282
- Duplicated block (33 lines × 2) src/compiler/cicc.rs:302
- Duplicated block (31 lines × 2) src/compiler/diab.rs:256
- Duplicated block (25 lines × 2) src/compiler/diab.rs:196
- Duplicated block (15–18 lines × 2) src/cache/multilevel.rs:723
- Duplicated block (16 lines × 2) src/compiler/diab.rs:230
- Duplicated block (15 lines × 2) src/compiler/cicc.rs:284
- Duplicated block (13–14 lines × 3) src/compiler/diab.rs:254
- Duplicated block (14 lines × 2) src/compiler/diab.rs:374
- Duplicated block (12–14 lines × 2) src/compiler/gcc.rs:482
- Duplicated block (13 lines × 2) src/compiler/rust.rs:1059
- Duplicated block (12 lines × 2) src/compiler/diab.rs:310
- Duplicated block (11 lines × 3) src/compiler/cicc.rs:319
- Duplicated block (11 lines × 2) src/compiler/cicc.rs:338
- Duplicated block (10 lines × 2) src/compiler/msvc.rs:155
- Duplicated block (8 lines × 2) src/compiler/gcc.rs:518
- Duplicated block (7 lines × 5) src/compiler/cicc.rs:106
- Duplicated block (7 lines × 2) src/cache/cache.rs:560
- Duplicated block (5 lines × 4) src/cache/cache.rs:411
- Duplicated block (5 lines × 5) src/cache/cache.rs:412
- Coverage collected but not gated
Minor — 13 finding(s)
- Orphaned file src/compiler/nvhpc.rs:1
- Orphaned file src/cmdline.rs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No changelog
- Duplicated predicate src/cache/azure.rs:71
Minor — 31 finding(s)
- Outdated: anyhow
- Outdated: async-trait
- Outdated: blake3
- Outdated: bytes
- Outdated: chrono
- Outdated: clap
- Outdated: encoding_rs
- Outdated: env_logger
- Outdated: filetime
- Outdated: flate2
- Outdated: fs-err
- Outdated: futures
- Outdated: gzp
- Outdated: http-body-util
- Outdated: hyper
- Outdated: hyper-util
- Outdated: libc
- Outdated: log
- Outdated: memmap2
- Outdated: openssl
- Outdated: reqwest
- Outdated: semver
- Outdated: serde
- Outdated: strip-ansi-escapes
- Outdated: tar
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-f73a790665454519824f93707a84c8bc/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-f73a790665454519824f93707a84c8bc/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 . | 55 | 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 . | 41 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | 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 |