Executive summary
openshift/cincinnati falls short of our standard for production because we found no access checks on the code's endpoints or handlers and three of the dependencies have a known vulnerability. It scores 48.1 out of 100 and is rated Weak, and six of its 14 critical findings are security problems.
Security and Compliance, at 37.5, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 8.5 points. Raising Security and Compliance to 70 would lift the score to about 56.2.
Three known security holes in the packages the code depends on can be used by attackers. Two settings leave the servers or containers unsafe, and one automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages, correcting the unsafe settings and setting a waiting period for automatic updates would close these risks.
The product code is 13,013 lines, about €13,000 to rebuild.
If Security and Compliance rose from 37.5 to 70, the lowest score rated Strong, the score would rise from 48.1 to about 56.2.
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,200 to €21,000, for 70 to 223 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 13,013 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 cincinnati.conditional_edges | 2 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3 | 3 commons.config | 4 commons.metrics | 5 graph_builder.config.options | 6 metadata_helper.config.options | 7 policy_engine.config.options | 8 quay.v1 | 9 cincinnati | 10 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg | 11 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model | 12 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry | 13 graph_builder.config.cli | 14 graph_builder.config.file | 15 metadata_helper.config.cli | 16 metadata_helper.config.file | 17 policy_engine.config.cli | 18 policy_engine.config.file | 19 cincinnati.plugins | 20 cincinnati.plugins.catalog | 21 cincinnati.plugins.internal.graph_builder.release | 22 graph_builder.config.settings | 23 metadata_helper | 24 metadata_helper.config.settings | 25 policy_engine | 26 policy_engine.config.settings | 27 cincinnati.plugins.internal.arch_filter | 28 cincinnati.plugins.internal.channel_filter | 29 cincinnati.plugins.internal.cincinnati_graph_fetch | 30 cincinnati.plugins.internal.edge_add_remove | 31 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin | 32 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin | 33 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin | 34 cincinnati.plugins.internal.metadata_fetch_quay | 35 cincinnati.plugins.internal.node_remove | 36 cincinnati.plugins.internal.versioned_graph | 37 graph_builder.graph | 38 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin | 39 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state | 40 policy_engine.graph |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cincinnati.conditional_edges | ||||||||||||||||||||||||||||||||||||||||
| 2 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3 | ||||||||||||||||||||||||||||||||||||||||
| 3 commons.config | ||||||||||||||||||||||||||||||||||||||||
| 4 commons.metrics | ||||||||||||||||||||||||||||||||||||||||
| 5 graph_builder.config.options | ||||||||||||||||||||||||||||||||||||||||
| 6 metadata_helper.config.options | ||||||||||||||||||||||||||||||||||||||||
| 7 policy_engine.config.options | ||||||||||||||||||||||||||||||||||||||||
| 8 quay.v1 | ||||||||||||||||||||||||||||||||||||||||
| 9 cincinnati | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 graph_builder.config.cli | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 graph_builder.config.file | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 metadata_helper.config.cli | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 metadata_helper.config.file | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 policy_engine.config.cli | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 policy_engine.config.file | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 cincinnati.plugins | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 cincinnati.plugins.catalog | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 cincinnati.plugins.internal.graph_builder.release | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 graph_builder.config.settings | 1 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 23 metadata_helper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 metadata_helper.config.settings | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 policy_engine | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 policy_engine.config.settings | 1 | 3 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 27 cincinnati.plugins.internal.arch_filter | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 cincinnati.plugins.internal.channel_filter | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 cincinnati.plugins.internal.cincinnati_graph_fetch | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 cincinnati.plugins.internal.edge_add_remove | 3 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 33 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 cincinnati.plugins.internal.metadata_fetch_quay | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 cincinnati.plugins.internal.node_remove | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 cincinnati.plugins.internal.versioned_graph | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 graph_builder.graph | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 policy_engine.graph | 1 | 1 | 1 |
9→1 cincinnati uses cincinnati.conditional_edges✕
- Connections
- 1 pair of types, where a type in cincinnati uses a type in cincinnati.conditional_edges.
- The types involved
cincinnati.Graph→cincinnati.conditional_edges.ConditionalEdge
- Direction
- cincinnati uses cincinnati.conditional_edges, so a change to cincinnati.conditional_edges can break cincinnati, while a change to cincinnati can't break cincinnati.conditional_edges.
- Position
- Below the diagonal: cincinnati uses a module listed above it, which is the healthy direction.
10→8 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg uses quay.v1✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg uses a type in quay.v1.
- The types involved
cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg.gpg$module→quay.v1.Client
- Direction
- cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg uses quay.v1, so a change to quay.v1 can break cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg, while a change to cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg can't break quay.v1.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.gpg uses a module listed above it, which is the healthy direction.
11→1 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model uses cincinnati.conditional_edges✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model uses a type in cincinnati.conditional_edges.
- The types involved
cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model.ConditionalEdgeYaml→cincinnati.conditional_edges.ClusterCondition
- Direction
- cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model uses cincinnati.conditional_edges, so a change to cincinnati.conditional_edges can break cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model, while a change to cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model can't break cincinnati.conditional_edges.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.graph_data_model uses a module listed above it, which is the healthy direction.
12→8 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry uses quay.v1✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry uses a type in quay.v1.
- The types involved
cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.registry$module→quay.v1.Client
- Direction
- cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry uses quay.v1, so a change to quay.v1 can break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, while a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can't break quay.v1.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry uses a module listed above it, which is the healthy direction.
13→5 graph_builder.config.cli uses graph_builder.config.options✕
- Connections
- 3 pairs of types, where a type in graph_builder.config.cli uses a type in graph_builder.config.options.
- The types involved
graph_builder.config.cli.CliOptions→graph_builder.config.options.DockerRegistryOptionsgraph_builder.config.cli.CliOptions→graph_builder.config.options.ServiceOptionsgraph_builder.config.cli.CliOptions→graph_builder.config.options.StatusOptions
- Direction
- graph_builder.config.cli uses graph_builder.config.options, so a change to graph_builder.config.options can break graph_builder.config.cli, while a change to graph_builder.config.cli can't break graph_builder.config.options.
- Position
- Below the diagonal: graph_builder.config.cli uses a module listed above it, which is the healthy direction.
14→5 graph_builder.config.file uses graph_builder.config.options✕
- Connections
- 3 pairs of types, where a type in graph_builder.config.file uses a type in graph_builder.config.options.
- The types involved
graph_builder.config.file.FileOptions→graph_builder.config.options.ServiceOptionsgraph_builder.config.file.FileOptions→graph_builder.config.options.StatusOptionsgraph_builder.config.file.UpstreamOptions→graph_builder.config.options.DockerRegistryOptions
- Direction
- graph_builder.config.file uses graph_builder.config.options, so a change to graph_builder.config.options can break graph_builder.config.file, while a change to graph_builder.config.file can't break graph_builder.config.options.
- Position
- Below the diagonal: graph_builder.config.file uses a module listed above it, which is the healthy direction.
15→6 metadata_helper.config.cli uses metadata_helper.config.options✕
- Connections
- 3 pairs of types, where a type in metadata_helper.config.cli uses a type in metadata_helper.config.options.
- The types involved
metadata_helper.config.cli.CliOptions→metadata_helper.config.options.ServiceOptionsmetadata_helper.config.cli.CliOptions→metadata_helper.config.options.SignaturesOptionsmetadata_helper.config.cli.CliOptions→metadata_helper.config.options.StatusOptions
- Direction
- metadata_helper.config.cli uses metadata_helper.config.options, so a change to metadata_helper.config.options can break metadata_helper.config.cli, while a change to metadata_helper.config.cli can't break metadata_helper.config.options.
- Position
- Below the diagonal: metadata_helper.config.cli uses a module listed above it, which is the healthy direction.
16→6 metadata_helper.config.file uses metadata_helper.config.options✕
- Connections
- 3 pairs of types, where a type in metadata_helper.config.file uses a type in metadata_helper.config.options.
- The types involved
metadata_helper.config.file.FileOptions→metadata_helper.config.options.ServiceOptionsmetadata_helper.config.file.FileOptions→metadata_helper.config.options.SignaturesOptionsmetadata_helper.config.file.FileOptions→metadata_helper.config.options.StatusOptions
- Direction
- metadata_helper.config.file uses metadata_helper.config.options, so a change to metadata_helper.config.options can break metadata_helper.config.file, while a change to metadata_helper.config.file can't break metadata_helper.config.options.
- Position
- Below the diagonal: metadata_helper.config.file uses a module listed above it, which is the healthy direction.
17→7 policy_engine.config.cli uses policy_engine.config.options✕
- Connections
- 3 pairs of types, where a type in policy_engine.config.cli uses a type in policy_engine.config.options.
- The types involved
policy_engine.config.cli.CliOptions→policy_engine.config.options.ServiceOptionspolicy_engine.config.cli.CliOptions→policy_engine.config.options.StatusOptionspolicy_engine.config.cli.CliOptions→policy_engine.config.options.UpCincinnatiOptions
- Direction
- policy_engine.config.cli uses policy_engine.config.options, so a change to policy_engine.config.options can break policy_engine.config.cli, while a change to policy_engine.config.cli can't break policy_engine.config.options.
- Position
- Below the diagonal: policy_engine.config.cli uses a module listed above it, which is the healthy direction.
18→7 policy_engine.config.file uses policy_engine.config.options✕
- Connections
- 3 pairs of types, where a type in policy_engine.config.file uses a type in policy_engine.config.options.
- The types involved
policy_engine.config.file.FileOptions→policy_engine.config.options.ServiceOptionspolicy_engine.config.file.FileOptions→policy_engine.config.options.StatusOptionspolicy_engine.config.file.UpstreamOptions→policy_engine.config.options.UpCincinnatiOptions
- Direction
- policy_engine.config.file uses policy_engine.config.options, so a change to policy_engine.config.options can break policy_engine.config.file, while a change to policy_engine.config.file can't break policy_engine.config.options.
- Position
- Below the diagonal: policy_engine.config.file uses a module listed above it, which is the healthy direction.
19→9 cincinnati.plugins uses cincinnati✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins uses a type in cincinnati.
- The types involved
cincinnati.plugins.InternalIO→cincinnati.Graph
- Direction
- cincinnati.plugins uses cincinnati, so a change to cincinnati can break cincinnati.plugins, while a change to cincinnati.plugins can't break cincinnati.
- Position
- Below the diagonal: cincinnati.plugins uses a module listed above it, which is the healthy direction.
20→12 cincinnati.plugins.catalog uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.catalog uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.catalog.PluginSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registrycincinnati.plugins.catalog.catalog$module→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.catalog uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.catalog, while a change to cincinnati.plugins.catalog can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.catalog uses a module listed above it, which is the healthy direction.
21→9 cincinnati.plugins.internal.graph_builder.release uses cincinnati✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.release uses a type in cincinnati.
- The types involved
cincinnati.plugins.internal.graph_builder.release.Release→cincinnati.Releasecincinnati.plugins.internal.graph_builder.release.release$module→cincinnati.Release
- Direction
- cincinnati.plugins.internal.graph_builder.release uses cincinnati, so a change to cincinnati can break cincinnati.plugins.internal.graph_builder.release, while a change to cincinnati.plugins.internal.graph_builder.release can't break cincinnati.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.release uses a module listed above it, which is the healthy direction.
22→3 graph_builder.config.settings uses commons.config✕
- Connections
- 1 pair of types, where a type in graph_builder.config.settings uses a type in commons.config.
- The types involved
graph_builder.config.settings.AppSettings→commons.config.MergeOptions
- Direction
- graph_builder.config.settings uses commons.config, so a change to commons.config can break graph_builder.config.settings, while a change to graph_builder.config.settings can't break commons.config.
- Position
- Below the diagonal: graph_builder.config.settings uses a module listed above it, which is the healthy direction.
22→5 graph_builder.config.settings uses graph_builder.config.options✕
- Connections
- 3 pairs of types, where a type in graph_builder.config.settings uses a type in graph_builder.config.options.
- The types involved
graph_builder.config.settings.AppSettings→graph_builder.config.options.DockerRegistryOptionsgraph_builder.config.settings.AppSettings→graph_builder.config.options.ServiceOptionsgraph_builder.config.settings.AppSettings→graph_builder.config.options.StatusOptions
- Direction
- graph_builder.config.settings uses graph_builder.config.options, so a change to graph_builder.config.options can break graph_builder.config.settings, while a change to graph_builder.config.settings can't break graph_builder.config.options.
- Position
- Below the diagonal: graph_builder.config.settings uses a module listed above it, which is the healthy direction.
22→12 graph_builder.config.settings uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in graph_builder.config.settings uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
graph_builder.config.settings.AppSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- graph_builder.config.settings uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break graph_builder.config.settings, while a change to graph_builder.config.settings can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: graph_builder.config.settings uses a module listed above it, which is the healthy direction.
22→13 graph_builder.config.settings uses graph_builder.config.cli✕
- Connections
- 1 pair of types, where a type in graph_builder.config.settings uses a type in graph_builder.config.cli.
- The types involved
graph_builder.config.settings.AppSettings→graph_builder.config.cli.CliOptions
- Direction
- graph_builder.config.settings uses graph_builder.config.cli, so a change to graph_builder.config.cli can break graph_builder.config.settings, while a change to graph_builder.config.settings can't break graph_builder.config.cli.
- Position
- Below the diagonal: graph_builder.config.settings uses a module listed above it, which is the healthy direction.
22→14 graph_builder.config.settings uses graph_builder.config.file✕
- Connections
- 2 pairs of types, where a type in graph_builder.config.settings uses a type in graph_builder.config.file.
- The types involved
graph_builder.config.settings.AppSettings→graph_builder.config.file.FileOptionsgraph_builder.config.settings.AppSettings→graph_builder.config.file.UpstreamOptions
- Direction
- graph_builder.config.settings uses graph_builder.config.file, so a change to graph_builder.config.file can break graph_builder.config.settings, while a change to graph_builder.config.settings can't break graph_builder.config.file.
- Position
- Below the diagonal: graph_builder.config.settings uses a module listed above it, which is the healthy direction.
23→4 metadata_helper uses commons.metrics✕
- Connections
- 1 pair of types, where a type in metadata_helper uses a type in commons.metrics.
- The types involved
metadata_helper.AppState→commons.metrics.HasRegistry
- Direction
- metadata_helper uses commons.metrics, so a change to commons.metrics can break metadata_helper, while a change to metadata_helper can't break commons.metrics.
- Position
- Below the diagonal: metadata_helper uses a module listed above it, which is the healthy direction.
23→12 metadata_helper uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in metadata_helper uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
metadata_helper.AppState→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- metadata_helper uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break metadata_helper, while a change to metadata_helper can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: metadata_helper uses a module listed above it, which is the healthy direction.
24→3 metadata_helper.config.settings uses commons.config✕
- Connections
- 1 pair of types, where a type in metadata_helper.config.settings uses a type in commons.config.
- The types involved
metadata_helper.config.settings.AppSettings→commons.config.MergeOptions
- Direction
- metadata_helper.config.settings uses commons.config, so a change to commons.config can break metadata_helper.config.settings, while a change to metadata_helper.config.settings can't break commons.config.
- Position
- Below the diagonal: metadata_helper.config.settings uses a module listed above it, which is the healthy direction.
24→6 metadata_helper.config.settings uses metadata_helper.config.options✕
- Connections
- 3 pairs of types, where a type in metadata_helper.config.settings uses a type in metadata_helper.config.options.
- The types involved
metadata_helper.config.settings.AppSettings→metadata_helper.config.options.ServiceOptionsmetadata_helper.config.settings.AppSettings→metadata_helper.config.options.SignaturesOptionsmetadata_helper.config.settings.AppSettings→metadata_helper.config.options.StatusOptions
- Direction
- metadata_helper.config.settings uses metadata_helper.config.options, so a change to metadata_helper.config.options can break metadata_helper.config.settings, while a change to metadata_helper.config.settings can't break metadata_helper.config.options.
- Position
- Below the diagonal: metadata_helper.config.settings uses a module listed above it, which is the healthy direction.
24→15 metadata_helper.config.settings uses metadata_helper.config.cli✕
- Connections
- 1 pair of types, where a type in metadata_helper.config.settings uses a type in metadata_helper.config.cli.
- The types involved
metadata_helper.config.settings.AppSettings→metadata_helper.config.cli.CliOptions
- Direction
- metadata_helper.config.settings uses metadata_helper.config.cli, so a change to metadata_helper.config.cli can break metadata_helper.config.settings, while a change to metadata_helper.config.settings can't break metadata_helper.config.cli.
- Position
- Below the diagonal: metadata_helper.config.settings uses a module listed above it, which is the healthy direction.
24→16 metadata_helper.config.settings uses metadata_helper.config.file✕
- Connections
- 1 pair of types, where a type in metadata_helper.config.settings uses a type in metadata_helper.config.file.
- The types involved
metadata_helper.config.settings.AppSettings→metadata_helper.config.file.FileOptions
- Direction
- metadata_helper.config.settings uses metadata_helper.config.file, so a change to metadata_helper.config.file can break metadata_helper.config.settings, while a change to metadata_helper.config.settings can't break metadata_helper.config.file.
- Position
- Below the diagonal: metadata_helper.config.settings uses a module listed above it, which is the healthy direction.
25→4 policy_engine uses commons.metrics✕
- Connections
- 1 pair of types, where a type in policy_engine uses a type in commons.metrics.
- The types involved
policy_engine.AppState→commons.metrics.HasRegistry
- Direction
- policy_engine uses commons.metrics, so a change to commons.metrics can break policy_engine, while a change to policy_engine can't break commons.metrics.
- Position
- Below the diagonal: policy_engine uses a module listed above it, which is the healthy direction.
25→12 policy_engine uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in policy_engine uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
policy_engine.AppState→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- policy_engine uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break policy_engine, while a change to policy_engine can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: policy_engine uses a module listed above it, which is the healthy direction.
26→3 policy_engine.config.settings uses commons.config✕
- Connections
- 1 pair of types, where a type in policy_engine.config.settings uses a type in commons.config.
- The types involved
policy_engine.config.settings.AppSettings→commons.config.MergeOptions
- Direction
- policy_engine.config.settings uses commons.config, so a change to commons.config can break policy_engine.config.settings, while a change to policy_engine.config.settings can't break commons.config.
- Position
- Below the diagonal: policy_engine.config.settings uses a module listed above it, which is the healthy direction.
26→7 policy_engine.config.settings uses policy_engine.config.options✕
- Connections
- 3 pairs of types, where a type in policy_engine.config.settings uses a type in policy_engine.config.options.
- The types involved
policy_engine.config.settings.AppSettings→policy_engine.config.options.ServiceOptionspolicy_engine.config.settings.AppSettings→policy_engine.config.options.StatusOptionspolicy_engine.config.settings.AppSettings→policy_engine.config.options.UpCincinnatiOptions
- Direction
- policy_engine.config.settings uses policy_engine.config.options, so a change to policy_engine.config.options can break policy_engine.config.settings, while a change to policy_engine.config.settings can't break policy_engine.config.options.
- Position
- Below the diagonal: policy_engine.config.settings uses a module listed above it, which is the healthy direction.
26→12 policy_engine.config.settings uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in policy_engine.config.settings uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
policy_engine.config.settings.AppSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- policy_engine.config.settings uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break policy_engine.config.settings, while a change to policy_engine.config.settings can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: policy_engine.config.settings uses a module listed above it, which is the healthy direction.
26→17 policy_engine.config.settings uses policy_engine.config.cli✕
- Connections
- 1 pair of types, where a type in policy_engine.config.settings uses a type in policy_engine.config.cli.
- The types involved
policy_engine.config.settings.AppSettings→policy_engine.config.cli.CliOptions
- Direction
- policy_engine.config.settings uses policy_engine.config.cli, so a change to policy_engine.config.cli can break policy_engine.config.settings, while a change to policy_engine.config.settings can't break policy_engine.config.cli.
- Position
- Below the diagonal: policy_engine.config.settings uses a module listed above it, which is the healthy direction.
26→18 policy_engine.config.settings uses policy_engine.config.file✕
- Connections
- 2 pairs of types, where a type in policy_engine.config.settings uses a type in policy_engine.config.file.
- The types involved
policy_engine.config.settings.AppSettings→policy_engine.config.file.FileOptionspolicy_engine.config.settings.AppSettings→policy_engine.config.file.UpstreamOptions
- Direction
- policy_engine.config.settings uses policy_engine.config.file, so a change to policy_engine.config.file can break policy_engine.config.settings, while a change to policy_engine.config.settings can't break policy_engine.config.file.
- Position
- Below the diagonal: policy_engine.config.settings uses a module listed above it, which is the healthy direction.
27→1 cincinnati.plugins.internal.arch_filter uses cincinnati.conditional_edges✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.arch_filter uses a type in cincinnati.conditional_edges.
- The types involved
cincinnati.plugins.internal.arch_filter.ArchFilterPlugin→cincinnati.conditional_edges.ConditionalEdge
- Direction
- cincinnati.plugins.internal.arch_filter uses cincinnati.conditional_edges, so a change to cincinnati.conditional_edges can break cincinnati.plugins.internal.arch_filter, while a change to cincinnati.plugins.internal.arch_filter can't break cincinnati.conditional_edges.
- Position
- Below the diagonal: cincinnati.plugins.internal.arch_filter uses a module listed above it, which is the healthy direction.
27→12 cincinnati.plugins.internal.arch_filter uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.arch_filter uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.arch_filter.ArchFilterPlugin→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.arch_filter uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.arch_filter, while a change to cincinnati.plugins.internal.arch_filter can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.arch_filter uses a module listed above it, which is the healthy direction.
27→19 cincinnati.plugins.internal.arch_filter uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.arch_filter uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.arch_filter.ArchFilterPlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.arch_filter.ArchFilterPlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.arch_filter uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.arch_filter, while a change to cincinnati.plugins.internal.arch_filter can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.arch_filter uses a module listed above it, which is the healthy direction.
27→20 cincinnati.plugins.internal.arch_filter uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.arch_filter uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.arch_filter.ArchFilterPlugin→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.arch_filter uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.arch_filter, while a change to cincinnati.plugins.internal.arch_filter can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.arch_filter uses a module listed above it, which is the healthy direction.
28→1 cincinnati.plugins.internal.channel_filter uses cincinnati.conditional_edges✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.channel_filter uses a type in cincinnati.conditional_edges.
- The types involved
cincinnati.plugins.internal.channel_filter.ChannelFilterPlugin→cincinnati.conditional_edges.ConditionalEdge
- Direction
- cincinnati.plugins.internal.channel_filter uses cincinnati.conditional_edges, so a change to cincinnati.conditional_edges can break cincinnati.plugins.internal.channel_filter, while a change to cincinnati.plugins.internal.channel_filter can't break cincinnati.conditional_edges.
- Position
- Below the diagonal: cincinnati.plugins.internal.channel_filter uses a module listed above it, which is the healthy direction.
28→12 cincinnati.plugins.internal.channel_filter uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.channel_filter uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.channel_filter.ChannelFilterPlugin→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.channel_filter uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.channel_filter, while a change to cincinnati.plugins.internal.channel_filter can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.channel_filter uses a module listed above it, which is the healthy direction.
28→19 cincinnati.plugins.internal.channel_filter uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.channel_filter uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.channel_filter.ChannelFilterPlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.channel_filter.ChannelFilterPlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.channel_filter uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.channel_filter, while a change to cincinnati.plugins.internal.channel_filter can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.channel_filter uses a module listed above it, which is the healthy direction.
28→20 cincinnati.plugins.internal.channel_filter uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.channel_filter uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.channel_filter.ChannelFilterPlugin→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.channel_filter uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.channel_filter, while a change to cincinnati.plugins.internal.channel_filter can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.channel_filter uses a module listed above it, which is the healthy direction.
29→8 cincinnati.plugins.internal.cincinnati_graph_fetch uses quay.v1✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.cincinnati_graph_fetch uses a type in quay.v1.
- The types involved
cincinnati.plugins.internal.cincinnati_graph_fetch.CincinnatiGraphFetchPlugin→quay.v1.Clientcincinnati.plugins.internal.cincinnati_graph_fetch.cincinnati_graph_fetch$module→quay.v1.Client
- Direction
- cincinnati.plugins.internal.cincinnati_graph_fetch uses quay.v1, so a change to quay.v1 can break cincinnati.plugins.internal.cincinnati_graph_fetch, while a change to cincinnati.plugins.internal.cincinnati_graph_fetch can't break quay.v1.
- Position
- Below the diagonal: cincinnati.plugins.internal.cincinnati_graph_fetch uses a module listed above it, which is the healthy direction.
29→12 cincinnati.plugins.internal.cincinnati_graph_fetch uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.cincinnati_graph_fetch uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.cincinnati_graph_fetch.CincinnatiGraphFetchPlugin→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registrycincinnati.plugins.internal.cincinnati_graph_fetch.CincinnatiGraphFetchSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.cincinnati_graph_fetch uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.cincinnati_graph_fetch, while a change to cincinnati.plugins.internal.cincinnati_graph_fetch can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.cincinnati_graph_fetch uses a module listed above it, which is the healthy direction.
29→19 cincinnati.plugins.internal.cincinnati_graph_fetch uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.cincinnati_graph_fetch uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.cincinnati_graph_fetch.CincinnatiGraphFetchPlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.cincinnati_graph_fetch.CincinnatiGraphFetchPlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.cincinnati_graph_fetch uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.cincinnati_graph_fetch, while a change to cincinnati.plugins.internal.cincinnati_graph_fetch can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.cincinnati_graph_fetch uses a module listed above it, which is the healthy direction.
29→20 cincinnati.plugins.internal.cincinnati_graph_fetch uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.cincinnati_graph_fetch uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.cincinnati_graph_fetch.CincinnatiGraphFetchSettings→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.cincinnati_graph_fetch uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.cincinnati_graph_fetch, while a change to cincinnati.plugins.internal.cincinnati_graph_fetch can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.cincinnati_graph_fetch uses a module listed above it, which is the healthy direction.
30→9 cincinnati.plugins.internal.edge_add_remove uses cincinnati✕
- Connections
- 3 pairs of types, where a type in cincinnati.plugins.internal.edge_add_remove uses a type in cincinnati.
- The types involved
cincinnati.plugins.internal.edge_add_remove.EdgeAddRemovePlugin→cincinnati.Graphcincinnati.plugins.internal.edge_add_remove.edge_add_remove$module→cincinnati.Graphcincinnati.plugins.internal.edge_add_remove.edge_add_remove$module→cincinnati.ReleaseId
- Direction
- cincinnati.plugins.internal.edge_add_remove uses cincinnati, so a change to cincinnati can break cincinnati.plugins.internal.edge_add_remove, while a change to cincinnati.plugins.internal.edge_add_remove can't break cincinnati.
- Position
- Below the diagonal: cincinnati.plugins.internal.edge_add_remove uses a module listed above it, which is the healthy direction.
30→12 cincinnati.plugins.internal.edge_add_remove uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.edge_add_remove uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.edge_add_remove.EdgeAddRemovePlugin→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.edge_add_remove uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.edge_add_remove, while a change to cincinnati.plugins.internal.edge_add_remove can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.edge_add_remove uses a module listed above it, which is the healthy direction.
30→19 cincinnati.plugins.internal.edge_add_remove uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.edge_add_remove uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.edge_add_remove.EdgeAddRemovePlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.edge_add_remove.EdgeAddRemovePlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.edge_add_remove uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.edge_add_remove, while a change to cincinnati.plugins.internal.edge_add_remove can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.edge_add_remove uses a module listed above it, which is the healthy direction.
30→20 cincinnati.plugins.internal.edge_add_remove uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.edge_add_remove uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.edge_add_remove.EdgeAddRemovePlugin→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.edge_add_remove uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.edge_add_remove, while a change to cincinnati.plugins.internal.edge_add_remove can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.edge_add_remove uses a module listed above it, which is the healthy direction.
31→8 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses quay.v1✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a type in quay.v1.
- The types involved
cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.DkrV2OpenshiftSecondaryMetadataScraperPlugin→quay.v1.Client
- Direction
- cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses quay.v1, so a change to quay.v1 can break cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin can't break quay.v1.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
31→12 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.DkrV2OpenshiftSecondaryMetadataScraperPlugin→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registrycincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.DkrV2OpenshiftSecondaryMetadataScraperSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
31→19 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.DkrV2OpenshiftSecondaryMetadataScraperPlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.DkrV2OpenshiftSecondaryMetadataScraperPlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
31→20 cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.DkrV2OpenshiftSecondaryMetadataScraperSettings→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
32→2 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a type in cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3.
- The types involved
cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin.GithubOpenshiftSecondaryMetadataScraperPlugin→cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3.Commitcincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin.State→cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3.Commit
- Direction
- cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3, so a change to cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3 can break cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin can't break cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.github_v3.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
32→8 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses quay.v1✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a type in quay.v1.
- The types involved
cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin.GithubOpenshiftSecondaryMetadataScraperPlugin→quay.v1.Client
- Direction
- cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses quay.v1, so a change to quay.v1 can break cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin can't break quay.v1.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
32→12 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin.GithubOpenshiftSecondaryMetadataScraperSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
32→19 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin.GithubOpenshiftSecondaryMetadataScraperPlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin.GithubOpenshiftSecondaryMetadataScraperPlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
32→20 cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin.GithubOpenshiftSecondaryMetadataScraperSettings→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin, while a change to cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.github_openshift_secondary_metadata_scraper.plugin uses a module listed above it, which is the healthy direction.
33→12 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin.ReleaseScrapeDockerv2Plugin→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registrycincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin.ReleaseScrapeDockerv2Settings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin, while a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses a module listed above it, which is the healthy direction.
33→19 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin.ReleaseScrapeDockerv2Plugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin.ReleaseScrapeDockerv2Plugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin, while a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses a module listed above it, which is the healthy direction.
33→20 cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin.ReleaseScrapeDockerv2Settings→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin, while a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.plugin uses a module listed above it, which is the healthy direction.
34→8 cincinnati.plugins.internal.metadata_fetch_quay uses quay.v1✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.metadata_fetch_quay uses a type in quay.v1.
- The types involved
cincinnati.plugins.internal.metadata_fetch_quay.QuayMetadataFetchPlugin→quay.v1.Client
- Direction
- cincinnati.plugins.internal.metadata_fetch_quay uses quay.v1, so a change to quay.v1 can break cincinnati.plugins.internal.metadata_fetch_quay, while a change to cincinnati.plugins.internal.metadata_fetch_quay can't break quay.v1.
- Position
- Below the diagonal: cincinnati.plugins.internal.metadata_fetch_quay uses a module listed above it, which is the healthy direction.
34→12 cincinnati.plugins.internal.metadata_fetch_quay uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.metadata_fetch_quay uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.metadata_fetch_quay.QuayMetadataSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.metadata_fetch_quay uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.metadata_fetch_quay, while a change to cincinnati.plugins.internal.metadata_fetch_quay can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.metadata_fetch_quay uses a module listed above it, which is the healthy direction.
34→19 cincinnati.plugins.internal.metadata_fetch_quay uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.metadata_fetch_quay uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.metadata_fetch_quay.QuayMetadataFetchPlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.metadata_fetch_quay.QuayMetadataFetchPlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.metadata_fetch_quay uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.metadata_fetch_quay, while a change to cincinnati.plugins.internal.metadata_fetch_quay can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.metadata_fetch_quay uses a module listed above it, which is the healthy direction.
34→20 cincinnati.plugins.internal.metadata_fetch_quay uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.metadata_fetch_quay uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.metadata_fetch_quay.QuayMetadataSettings→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.metadata_fetch_quay uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.metadata_fetch_quay, while a change to cincinnati.plugins.internal.metadata_fetch_quay can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.metadata_fetch_quay uses a module listed above it, which is the healthy direction.
35→12 cincinnati.plugins.internal.node_remove uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.node_remove uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.node_remove.NodeRemovePlugin→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.node_remove uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.node_remove, while a change to cincinnati.plugins.internal.node_remove can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.node_remove uses a module listed above it, which is the healthy direction.
35→19 cincinnati.plugins.internal.node_remove uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.node_remove uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.node_remove.NodeRemovePlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.node_remove.NodeRemovePlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.node_remove uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.node_remove, while a change to cincinnati.plugins.internal.node_remove can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.node_remove uses a module listed above it, which is the healthy direction.
35→20 cincinnati.plugins.internal.node_remove uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.node_remove uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.node_remove.NodeRemovePlugin→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.node_remove uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.node_remove, while a change to cincinnati.plugins.internal.node_remove can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.node_remove uses a module listed above it, which is the healthy direction.
36→9 cincinnati.plugins.internal.versioned_graph uses cincinnati✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.versioned_graph uses a type in cincinnati.
- The types involved
cincinnati.plugins.internal.versioned_graph.VersionedGraph→cincinnati.Graph
- Direction
- cincinnati.plugins.internal.versioned_graph uses cincinnati, so a change to cincinnati can break cincinnati.plugins.internal.versioned_graph, while a change to cincinnati.plugins.internal.versioned_graph can't break cincinnati.
- Position
- Below the diagonal: cincinnati.plugins.internal.versioned_graph uses a module listed above it, which is the healthy direction.
36→19 cincinnati.plugins.internal.versioned_graph uses cincinnati.plugins✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.versioned_graph uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.versioned_graph.VersionedGraph→cincinnati.plugins.InternalIO
- Direction
- cincinnati.plugins.internal.versioned_graph uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.versioned_graph, while a change to cincinnati.plugins.internal.versioned_graph can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.versioned_graph uses a module listed above it, which is the healthy direction.
37→4 graph_builder.graph uses commons.metrics✕
- Connections
- 1 pair of types, where a type in graph_builder.graph uses a type in commons.metrics.
- The types involved
graph_builder.graph.State→commons.metrics.HasRegistry
- Direction
- graph_builder.graph uses commons.metrics, so a change to commons.metrics can break graph_builder.graph, while a change to graph_builder.graph can't break commons.metrics.
- Position
- Below the diagonal: graph_builder.graph uses a module listed above it, which is the healthy direction.
37→12 graph_builder.graph uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 2 pairs of types, where a type in graph_builder.graph uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
graph_builder.graph.State→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registrygraph_builder.graph.graph$module→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- graph_builder.graph uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break graph_builder.graph, while a change to graph_builder.graph can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: graph_builder.graph uses a module listed above it, which is the healthy direction.
37→22 graph_builder.graph uses graph_builder.config.settings✕
- Connections
- 1 pair of types, where a type in graph_builder.graph uses a type in graph_builder.config.settings.
- The types involved
graph_builder.graph.graph$module→graph_builder.config.settings.AppSettings
- Direction
- graph_builder.graph uses graph_builder.config.settings, so a change to graph_builder.config.settings can break graph_builder.graph, while a change to graph_builder.graph can't break graph_builder.config.settings.
- Position
- Below the diagonal: graph_builder.graph uses a module listed above it, which is the healthy direction.
38→9 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a type in cincinnati.
- The types involved
cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.OpenshiftSecondaryMetadataParserPlugin→cincinnati.Graph
- Direction
- cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati, so a change to cincinnati can break cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin, while a change to cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin can't break cincinnati.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a module listed above it, which is the healthy direction.
38→12 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.OpenshiftSecondaryMetadataParserSettings→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin, while a change to cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a module listed above it, which is the healthy direction.
38→19 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins✕
- Connections
- 2 pairs of types, where a type in cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a type in cincinnati.plugins.
- The types involved
cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.OpenshiftSecondaryMetadataParserPlugin→cincinnati.plugins.InternalIOcincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.OpenshiftSecondaryMetadataParserPlugin→cincinnati.plugins.InternalPlugin
- Direction
- cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins, so a change to cincinnati.plugins can break cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin, while a change to cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin can't break cincinnati.plugins.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a module listed above it, which is the healthy direction.
38→20 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins.catalog✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a type in cincinnati.plugins.catalog.
- The types involved
cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.OpenshiftSecondaryMetadataParserSettings→cincinnati.plugins.catalog.PluginSettings
- Direction
- cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins.catalog, so a change to cincinnati.plugins.catalog can break cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin, while a change to cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin can't break cincinnati.plugins.catalog.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a module listed above it, which is the healthy direction.
38→31 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a type in cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.
- The types involved
cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.OpenshiftSecondaryMetadataParserPlugin→cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.State
- Direction
- cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin, so a change to cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin can break cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin, while a change to cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin can't break cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin uses a module listed above it, which is the healthy direction.
39→31 cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state uses cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin✕
- Connections
- 1 pair of types, where a type in cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state uses a type in cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.
- The types involved
cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state.state$module→cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.State
- Direction
- cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state uses cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin, so a change to cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin can break cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state, while a change to cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state can't break cincinnati.plugins.internal.graph_builder.dkrv2_openshift_secondary_metadata_scraper.plugin.
- Position
- Below the diagonal: cincinnati.plugins.internal.graph_builder.openshift_secondary_metadata_parser.plugin.state uses a module listed above it, which is the healthy direction.
40→12 policy_engine.graph uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry✕
- Connections
- 1 pair of types, where a type in policy_engine.graph uses a type in cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- The types involved
policy_engine.graph.graph$module→cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.Registry
- Direction
- policy_engine.graph uses cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry, so a change to cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry can break policy_engine.graph, while a change to policy_engine.graph can't break cincinnati.plugins.internal.graph_builder.release_scrape_dockerv2.registry.
- Position
- Below the diagonal: policy_engine.graph uses a module listed above it, which is the healthy direction.
40→19 policy_engine.graph uses cincinnati.plugins✕
- Connections
- 1 pair of types, where a type in policy_engine.graph uses a type in cincinnati.plugins.
- The types involved
policy_engine.graph.graph$module→cincinnati.plugins.InternalIO
- Direction
- policy_engine.graph uses cincinnati.plugins, so a change to cincinnati.plugins can break policy_engine.graph, while a change to policy_engine.graph can't break cincinnati.plugins.
- Position
- Below the diagonal: policy_engine.graph uses a module listed above it, which is the healthy direction.
40→36 policy_engine.graph uses cincinnati.plugins.internal.versioned_graph✕
- Connections
- 1 pair of types, where a type in policy_engine.graph uses a type in cincinnati.plugins.internal.versioned_graph.
- The types involved
policy_engine.graph.graph$module→cincinnati.plugins.internal.versioned_graph.VersionedGraph
- Direction
- policy_engine.graph uses cincinnati.plugins.internal.versioned_graph, so a change to cincinnati.plugins.internal.versioned_graph can break policy_engine.graph, while a change to policy_engine.graph can't break cincinnati.plugins.internal.versioned_graph.
- Position
- Below the diagonal: policy_engine.graph 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 — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 50 | High / Critical |
| A02:2025 — Security Misconfiguration | 33 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Add a CI workflow that builds and runs the test suite on every push/PR; Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +8.5 pts | Medium | Access Controls |
| Resolve the 1 No network policy finding(s) in Network Egress Confinement. | +2.0 pts | Low | Network Egress Confinement |
| Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. | +2.0 pts | Low | Kernel & Syscall Confinement |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +3.8 pts | Medium | CI/CD gates |
| Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only. | +3.2 pts | Medium | Web-Security Posture |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). | +1.2 pts | Low | Dependency Vulnerabilities |
| Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. | +1.2 pts | Low | IaC & Container Security |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| prometheus-query/src/v1/mod.rs | 4.4 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| metadata-helper/src/main.rs | 5.6 | Mixed | Code Duplication: Near-duplicate member pair (43 shared lines) |
| cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs | 5.6 | Mixed | Code Duplication: Duplicated block (20–22 lines × 2) |
| cincinnati/src/plugins/internal/edge_add_remove.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| cincinnati/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| graph-builder/src/config/settings.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| prometheus-query/src/v1/queries/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| graph-builder/src/main.rs | 6.3 | Mixed | Code Duplication: Duplicated block (6 lines × 3) |
| graph-builder/src/config/options.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| quay/src/v1/tag.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| commons/src/lib.rs | 6.9 | Mixed | Explicit Debt: FixmeComment |
| cincinnati/src/plugins/internal/graph_builder/commons.rs | 7.0 | Mixed | Cognitive Complexity: cincinnati::plugins::internal::graph_builder::commons::get_certs_from_dir (cognitive 45) |
| metadata-helper/src/config/settings.rs | 7.0 | Mixed | Code Duplication: Duplicated block (19 lines × 2) |
| metadata-helper/src/signatures.rs | 7.0 | Mixed | Code Duplication: Duplicated block (6 lines × 2) |
| cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/plugin.rs | 7.1 | Mixed | Cyclomatic Complexity: cincinnati::plugins::internal::graph_builder::openshift_secondary_metadata_parser::plugin::deserialize_directory_files (cyclomatic 31) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 59 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, 314 of 346 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- 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.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was cincinnati::plugins::internal::graph_builder::openshift_secondary_metadata_parser::plugin::deserialize_directory_files at 31.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with cincinnati::plugins::internal::graph_builder::openshift_secondary_metadata_parser::plugin::deserialize_directory_files (cyclomatic 31), EdgeAddRemovePlugin::remove_edges (cyclomatic 20). — 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 2 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was cincinnati::plugins::internal::graph_builder::openshift_secondary_metadata_parser::plugin::deserialize_directory_files at 101.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with cincinnati::plugins::internal::graph_builder::openshift_secondary_metadata_parser::plugin::deserialize_directory_files (cognitive 101). — Refactoring it lifts Cognitive Complexity from 7.3 to about 7.9/10.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with lib.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
29 duplicated block group(s) detected. 7.9 % of the production lines (1,026 of 13,013) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with plugin.rs, main.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with plugin.rs (2), main.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with mod.rs (2). — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
8 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 28 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (2). — One of this dimension's main actionable groups (2 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D8 · Code Coverage
Line coverage 51.6% — 25 file(s) below 50%. Measured from the Rust suite (repository root: `cargo nextest run` and the doc tests instrumented, 3 run(s), 58 production file(s)). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 25 Low coverage finding(s) in Code Coverage — start with main.rs (4), plugin.rs (3), mod.rs (3). — One of this dimension's main actionable groups (25 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 37 test files): measured (0 flaky).
D12 · Dependency Hygiene
21 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 476 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. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is quay/src/v1/manifest.rs. Counted over 39 of the 72 production source files in this repository: 24 are under the ~2,400-byte size floor this dimension measures over, and the remaining 9 have no attributable history left to measure.
D17 · Explicit Debt
16 deducted task-comment markers across 13013 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 13 TodoComment finding(s) in Explicit Debt — start with mod.rs (3), prometheus_query.rs (2), cincinnati_graph_fetch.rs (2). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with lib.rs (3). — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 7 document(s) read across 9 unit(s).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
0 of 9 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep hit a parse error in 1 file(s) — `cincinnati/src/plugins/interface.rs` (line 175, line 176, line 178, …) — 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
50 finding(s): 0 critical, 3 high, 47 medium, 0 low.
What to do
- Resolve the 21 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 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).
- 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).
D31 · IaC & Container Security
33 finding(s): 0 critical, 2 high, 26 medium, 5 low.
What to do
- Resolve the 26 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (23), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (26 warning-level).
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 5 Low IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
D34 · Knowledge Freshness
44 of 48 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is cincinnati/src/lib.rs. Counted over 48 of the 72 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 41 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (4), settings.rs (3), file.rs (3). — One of this dimension's main actionable groups (41 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with lib.rs, plugin.rs, edge_add_remove.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/1 workload(s) run every container under a seccomp profile; 0/1 declare an AppArmor/SELinux profile.
What to do
- Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. — 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
C2 · Access Controls
- This repository serves requests — a server (HttpServer::new) (policy-engine/src/main.rs:104) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — policy-engine/src/main.rs:104
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
ED1 · Handler temporal coupling
- `commons.get_certs_from_dir` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — cincinnati/src/plugins/internal/graph_builder/commons.rs:16
- `commons.get_certs_from_dir` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `File::open`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — cincinnati/src/plugins/internal/graph_builder/commons.rs:26
- `gpg.load_public_keys` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `File::open`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/gpg.rs:51
- `src.create_tar` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `File::create`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — commons/src/lib.rs:179
- `FileOptions.read_filepath` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `File::open`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×3) — graph-builder/src/config/file.rs:36, metadata-helper/src/config/file.rs:34, policy-engine/src/config/file.rs:37
- `src.main` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `thread::sleep`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — policy-engine/src/main.rs:181
What to do
- Use the awaited twin of each blocking call, or move the work off the loop with `tokio::task::spawn_blocking` — a synchronous handler cannot simply `.await` in place.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `init_tracer` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — commons/src/tracing.rs:9
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
M2 · Architecture documentation
- 1 ADR-shaped document(s) detected by content — `docs/design/cincinnati.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
- Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
- 1 public type in `cincinnati.plugins.internal.arch_filter` is marked as implementation by its own namespace, folder or name: `ArchFilterPlugin` (cincinnati/src/plugins/internal/arch_filter.rs:24, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cincinnati/src/plugins/internal/arch_filter.rs:24
- 1 public type in `cincinnati.plugins.internal.channel_filter` is marked as implementation by its own namespace, folder or name: `ChannelFilterPlugin` (cincinnati/src/plugins/internal/channel_filter.rs:19, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cincinnati/src/plugins/internal/channel_filter.rs:19
- 1 public type in `cincinnati.plugins.internal.cincinnati_graph_fetch` is marked as implementation by its own namespace, folder or name: `CincinnatiGraphFetchPlugin` (cincinnati/src/plugins/internal/cincinnati_graph_fetch.rs:41, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cincinnati/src/plugins/internal/cincinnati_graph_fetch.rs:41
- 1 public type in `cincinnati.plugins.internal.edge_add_remove` is marked as implementation by its own namespace, folder or name: `EdgeAddRemovePlugin` (cincinnati/src/plugins/internal/edge_add_remove.rs:15, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cincinnati/src/plugins/internal/edge_add_remove.rs:15
- 1 public type in `cincinnati.plugins.internal.metadata_fetch_quay` is marked as implementation by its own namespace, folder or name: `QuayMetadataFetchPlugin` (cincinnati/src/plugins/internal/metadata_fetch_quay.rs:38, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cincinnati/src/plugins/internal/metadata_fetch_quay.rs:38
- 1 public type in `cincinnati.plugins.internal.node_remove` is marked as implementation by its own namespace, folder or name: `NodeRemovePlugin` (cincinnati/src/plugins/internal/node_remove.rs:13, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cincinnati/src/plugins/internal/node_remove.rs:13
- 1 public type in `cincinnati.plugins.internal.versioned_graph` is marked as implementation by its own namespace, folder or name: `VersionedGraph` (cincinnati/src/plugins/internal/versioned_graph.rs:7, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — cincinnati/src/plugins/internal/versioned_graph.rs:7
What to do
- Hide `cincinnati.plugins.internal.arch_filter` (`ArchFilterPlugin`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `cincinnati.plugins.internal.channel_filter` (`ChannelFilterPlugin`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `cincinnati.plugins.internal.cincinnati_graph_fetch` (`CincinnatiGraphFetchPlugin`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `cincinnati.plugins.internal.edge_add_remove` (`EdgeAddRemovePlugin`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `cincinnati.plugins.internal.metadata_fetch_quay` (`QuayMetadataFetchPlugin`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `cincinnati.plugins.internal.node_remove` (`NodeRemovePlugin`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `cincinnati.plugins.internal.versioned_graph` (`VersionedGraph`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability
- Only 6/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `rh-manifest-generator`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- 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.
P7 · Outbound HTTP resilience
- `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs:200, quay/src/v1/mod.rs:83
- `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs:345
- `reqwest::blocking::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — prometheus-query/src/v1/mod.rs:92
- `reqwest::blocking::get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — rh-manifest-generator/src/main.rs:41
What to do
- Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF3 · Async & latency hygiene
- `main` is async and calls thread::sleep — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — policy-engine/src/main.rs:67
What to do
- Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
S1 · Web-Security Posture
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `HttpServer::new(` (policy-engine/src/main.rs:104).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `HttpServer::new(` (policy-engine/src/main.rs:104).
What to do
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
- This `async` body is polled on an executor's worker thread, and `std::thread::sleep` blocks that thread: for the whole delay no other task scheduled on it makes progress — the Rust form of blocking on a task. Use `tokio::time::sleep(…).await` (or the runtime's own timer), which suspends only this task. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the executor with `tokio::task::spawn_blocking(…).await`. — policy-engine/src/main.rs:181
What to do
- Blocking `thread::sleep` inside an `async` body
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `query` is public and takes a `Client` as its receiver from its caller, and it calls itself at line 33 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `query` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — prometheus-query/src/v1/queries/instant.rs:33
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
- `ClusterCondition.condition_type` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cincinnati/src/conditional_edges.rs:37
- `Branch.protected` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/github_v3.rs:19
- `Manifest.schema_version` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:710
- `Manifest.architecture` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:713
- `Manifest.fs_layers` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:715
- `Layer.blob_sum` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:722
- `CliOptions.upstream_method` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. (×2) — graph-builder/src/config/cli.rs:27, policy-engine/src/config/cli.rs:29
- `UpstreamOptions.method` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. (×2) — graph-builder/src/config/file.rs:83, policy-engine/src/config/file.rs:84
- `QuerySuccess.warnings` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — prometheus-query/src/v1/queries/mod.rs:18
- `QueryError.error_type` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — prometheus-query/src/v1/queries/mod.rs:31
- `QueryError.error` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — prometheus-query/src/v1/queries/mod.rs:32
- `QueryError.warnings` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — prometheus-query/src/v1/queries/mod.rs:33
- `VectorValue.time` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — prometheus-query/src/v1/queries/mod.rs:53
- `Label.media_type` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — quay/src/v1/manifest.rs:45
- `Label.id` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — quay/src/v1/manifest.rs:47
- `Label.source_type` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — quay/src/v1/manifest.rs:49
- `PaginatedTags.has_additional` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — quay/src/v1/tag.rs:14
- `PaginatedTags.page` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — quay/src/v1/tag.rs:17
- `Tag.manifest_digest` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — quay/src/v1/tag.rs:26
- `Tag.reversion` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — quay/src/v1/tag.rs:30
- `RegistryConfig.api` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — rh-manifest-generator/src/main.rs:36
What to do
- Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X27 · Collection changed while being enumerated
X5 · Nullable reference types
- `built::write_built_file()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — policy-engine/src/build.rs:2, metadata-helper/src/build.rs:4, graph-builder/src/build.rs:3
- `VersionedGraph::new(io)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `add_version_information` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — policy-engine/src/graph.rs:122
- `metrics::new_registry(Some(METRICS_PREFIX.to_string()))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `default` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — policy-engine/src/main.rs:260
- `serde_json::from_str(PARAM_TEMPLATE)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `add_mandatory_params` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — policy-engine/src/openapi.rs:71
- `tempfile::tempdir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — metadata-helper/src/main.rs:87
- `temp_dir.as_ref().to_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — metadata-helper/src/main.rs:88
- `params.get("ALGO_DIGEST")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `_index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — metadata-helper/src/signatures.rs:56
- `params.get("SIGNATURE")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `_index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — metadata-helper/src/signatures.rs:68
- `tempfile::tempdir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `default_openshift_plugin_settings` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — graph-builder/src/config/settings.rs:140
- `HeaderValue::to_str(&accept_default)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `validate_content_type` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/lib.rs:163
- `HeaderValue::to_str(&accept_default).unwrap().parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `validate_content_type` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/lib.rs:165
- `a.parse()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `validate_content_type` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/lib.rs:168
- `HeaderValue::from_str("user-agent not available")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `format_request` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/lib.rs:192
- `HeaderValue::from_str("accept value not available")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `format_request` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/lib.rs:193
- `req.headers().get("user-agent").unwrap_or(&no_user_agent).to_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `format_request` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/lib.rs:202
- `req.headers().get("accept").unwrap_or(&no_accept_type).to_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `format_request` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/lib.rs:208
- `v.as_object_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:31
- `obj.get_mut("nodes")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:39
- `nodes.as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — commons/src/testing.rs:42, commons/src/testing.rs:59
- `node.get("version")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — commons/src/testing.rs:46, commons/src/testing.rs:63
- `node.get("version").unwrap().as_str()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — commons/src/testing.rs:46, commons/src/testing.rs:63
- `nodes.as_array_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:50
- `a.get("version")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:52
- `b.get("version")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:54
- `from` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — commons/src/testing.rs:71, commons/src/testing.rs:74
- `to` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — commons/src/testing.rs:72, commons/src/testing.rs:74
- `obj.get_mut("edges")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — commons/src/testing.rs:80, commons/src/testing.rs:108
- `obj.get_mut("edges").unwrap().as_array_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:82
- `edge.as_array()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:85
- `edge.get_mut($edge_index)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:91
- `old.as_u64()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:93
- `index_map.get(&old_usize)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `sort_json_graph_by_version` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — commons/src/testing.rs:94
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80.7 | Strong | Solid. |
| Architecture | 93.2 | Exemplary | Strongest area. |
| Maturity | 67.7 | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40.0 | Weak — gated by P1, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 37.5 | Weak — gated by C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 66.8 | Adequate | Acceptable, with room to improve. |
| Performance | 85.0 | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- 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 — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- 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 — no interface, protocol or abstract type declares an operation an implementer must write
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — 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.
- 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 — ~885 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 — N/A — too few peers to establish a naming convention (1074 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- 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.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (8 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
- P12 CI test-gate honesty — no CI workflow found
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 58 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's 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.
- 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 — 14 finding(s)
- Blocking call on the event loop: commons.get_certs_from_dir calls `std::fs::read_dir` cincinnati/src/plugins/internal/graph_builder/commons.rs:16
- Blocking call on the event loop: commons.get_certs_from_dir calls `File::open` cincinnati/src/plugins/internal/graph_builder/commons.rs:26
- Blocking call on the event loop: gpg.load_public_keys calls `File::open` cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/gpg.rs:51
- Blocking call on the event loop: src.create_tar calls `File::create` commons/src/lib.rs:179
- Blocking call on the event loop: FileOptions.read_filepath calls `File::open` graph-builder/src/config/file.rs:36
- Blocking call on the event loop: FileOptions.read_filepath calls `File::open` metadata-helper/src/config/file.rs:34
- Blocking call on the event loop: FileOptions.read_filepath calls `File::open` policy-engine/src/config/file.rs:37
- Blocking call on the event loop: src.main calls `thread::sleep` policy-engine/src/main.rs:181
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 244 finding(s)
- Symbol treated as nullable, then dereferenced unguarded policy-engine/src/build.rs:2
- Symbol treated as nullable, then dereferenced unguarded policy-engine/src/graph.rs:122
- Symbol treated as nullable, then dereferenced unguarded policy-engine/src/main.rs:260
- Symbol treated as nullable, then dereferenced unguarded policy-engine/src/openapi.rs:71
- Symbol treated as nullable, then dereferenced unguarded metadata-helper/src/build.rs:4
- Symbol treated as nullable, then dereferenced unguarded metadata-helper/src/main.rs:87
- Symbol treated as nullable, then dereferenced unguarded metadata-helper/src/main.rs:88
- Symbol treated as nullable, then dereferenced unguarded metadata-helper/src/signatures.rs:56
- Symbol treated as nullable, then dereferenced unguarded metadata-helper/src/signatures.rs:68
- Symbol treated as nullable, then dereferenced unguarded graph-builder/src/build.rs:3
- Symbol treated as nullable, then dereferenced unguarded graph-builder/src/config/settings.rs:140
- Symbol treated as nullable, then dereferenced unguarded commons/src/lib.rs:163
- Symbol treated as nullable, then dereferenced unguarded commons/src/lib.rs:165
- Symbol treated as nullable, then dereferenced unguarded commons/src/lib.rs:168
- Symbol treated as nullable, then dereferenced unguarded commons/src/lib.rs:192
- Symbol treated as nullable, then dereferenced unguarded commons/src/lib.rs:193
- Symbol treated as nullable, then dereferenced unguarded commons/src/lib.rs:202
- Symbol treated as nullable, then dereferenced unguarded commons/src/lib.rs:208
- Symbol treated as nullable, then dereferenced unguarded commons/src/testing.rs:31
- Symbol treated as nullable, then dereferenced unguarded commons/src/testing.rs:39
- Symbol treated as nullable, then dereferenced unguarded commons/src/testing.rs:42
- Symbol treated as nullable, then dereferenced unguarded commons/src/testing.rs:46
- Symbol treated as nullable, then dereferenced unguarded commons/src/testing.rs:46
- Symbol treated as nullable, then dereferenced unguarded commons/src/testing.rs:50
- Symbol treated as nullable, then dereferenced unguarded commons/src/testing.rs:52
- 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
- Low coverage: cincinnati/src/plugins/internal/graph_builder/commons.rs cincinnati/src/plugins/internal/graph_builder/commons.rs:1
- Low coverage: cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/gpg.rs cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/gpg.rs:1
- Low coverage: cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs:1
- Low coverage: cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/github_v3.rs cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/github_v3.rs:1
- Low coverage: cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs:1
- Low coverage: cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/plugin.rs cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/plugin.rs:1
- Low coverage: cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:1
- Low coverage: commons/src/testing.rs commons/src/testing.rs:1
- Low coverage: commons/src/tracing.rs commons/src/tracing.rs:1
- Low coverage: graph-builder/src/config/settings.rs graph-builder/src/config/settings.rs:1
- Low coverage: graph-builder/src/graph.rs graph-builder/src/graph.rs:1
- Low coverage: graph-builder/src/main.rs graph-builder/src/main.rs:1
- Low coverage: metadata-helper/src/config/settings.rs metadata-helper/src/config/settings.rs:1
- Low coverage: metadata-helper/src/main.rs metadata-helper/src/main.rs:1
- Low coverage: metadata-helper/src/signatures.rs metadata-helper/src/signatures.rs:1
- Low coverage: metadata-helper/src/status.rs metadata-helper/src/status.rs:1
- Low coverage: policy-engine/src/main.rs policy-engine/src/main.rs:1
- Low coverage: policy-engine/src/status.rs policy-engine/src/status.rs:1
- Low coverage: prometheus-query/src/v1/mod.rs prometheus-query/src/v1/mod.rs:1
- Low coverage: prometheus-query/src/v1/queries/instant.rs prometheus-query/src/v1/queries/instant.rs:1
- Low coverage: prometheus-query/src/v1/queries/mod.rs prometheus-query/src/v1/queries/mod.rs:1
- Low coverage: quay/src/lib.rs quay/src/lib.rs:1
- Low coverage: quay/src/v1/manifest.rs quay/src/v1/manifest.rs:1
- Low coverage: quay/src/v1/tag.rs quay/src/v1/tag.rs:1
- Low coverage: rh-manifest-generator/src/main.rs rh-manifest-generator/src/main.rs:1
- Configuration option is read nowhere cincinnati/src/conditional_edges.rs:37
- Configuration option is read nowhere cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/github_v3.rs:19
- Configuration option is read nowhere cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:710
- Configuration option is read nowhere cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:713
- Configuration option is read nowhere cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:715
- Configuration option is read nowhere cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:722
- Configuration option is read nowhere graph-builder/src/config/cli.rs:27
- Configuration option is read nowhere graph-builder/src/config/file.rs:83
- Configuration option is read nowhere policy-engine/src/config/cli.rs:29
- Configuration option is read nowhere policy-engine/src/config/file.rs:84
- Configuration option is read nowhere prometheus-query/src/v1/queries/mod.rs:18
- Configuration option is read nowhere prometheus-query/src/v1/queries/mod.rs:31
- Configuration option is read nowhere prometheus-query/src/v1/queries/mod.rs:32
- Configuration option is read nowhere prometheus-query/src/v1/queries/mod.rs:33
- Configuration option is read nowhere prometheus-query/src/v1/queries/mod.rs:53
- Configuration option is read nowhere quay/src/v1/manifest.rs:45
- Configuration option is read nowhere quay/src/v1/manifest.rs:47
- Configuration option is read nowhere quay/src/v1/manifest.rs:49
- Configuration option is read nowhere quay/src/v1/tag.rs:14
- Configuration option is read nowhere quay/src/v1/tag.rs:17
- Configuration option is read nowhere quay/src/v1/tag.rs:26
- Configuration option is read nowhere quay/src/v1/tag.rs:30
- Configuration option is read nowhere rh-manifest-generator/src/main.rs:36
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment quay/src/v1/tag.rs:43
- TodoComment prometheus-query/src/v1/queries/mod.rs:41
- TodoComment prometheus-query/src/v1/queries/mod.rs:42
- TodoComment graph-builder/src/config/options.rs:11
- TodoComment graph-builder/src/config/settings.rs:49
- TodoComment e2e/tests/prometheus_query.rs:19
- TodoComment e2e/tests/prometheus_query.rs:48
- TodoComment cincinnati/src/lib.rs:775
- TodoComment cincinnati/src/plugins/internal/cincinnati_graph_fetch.rs:228
- TodoComment cincinnati/src/plugins/internal/cincinnati_graph_fetch.rs:294
- TodoComment cincinnati/src/plugins/internal/edge_add_remove.rs:947
- TodoComment cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:376
- TodoComment cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/plugin/network_tests.rs:266
- 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
- Outbound HTTP without resilience cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs:200
- Outbound HTTP without resilience cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs:345
- Outbound HTTP without resilience prometheus-query/src/v1/mod.rs:92
- Outbound HTTP without resilience quay/src/v1/mod.rs:83
- Outbound HTTP without resilience rh-manifest-generator/src/main.rs:41
- FixmeComment commons/src/lib.rs:154
- FixmeComment commons/src/lib.rs:294
- FixmeComment commons/src/lib.rs:346
- cincinnati::plugins::internal::graph_builder::openshift_secondary_metadata_parser::plugin::deserialize_directory_files (cognitive 101) cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/plugin.rs:195
- cincinnati::plugins::internal::graph_builder::commons::get_certs_from_dir (cognitive 45) cincinnati/src/plugins/internal/graph_builder/commons.rs:11
- cincinnati::plugins::internal::graph_builder::release_scrape_dockerv2::registry::fetch_releases (cognitive 16) cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:300
- Duplicated block (12 lines × 2) cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs:173
- Duplicated block (12 lines × 2) metadata-helper/src/main.rs:69
- Duplicated block (12 lines × 2) prometheus-query/src/v1/mod.rs:36
- Duplicated block (11 lines × 2) cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs:194
- Duplicated block (11 lines × 2) metadata-helper/src/main.rs:129
- Duplicated block (11 lines × 2) cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/plugin.rs:496
- EdgeAddRemovePlugin::remove_edges (cognitive 38) cincinnati/src/plugins/internal/edge_add_remove.rs:97
- EdgeAddRemovePlugin::add_edges (cognitive 27) cincinnati/src/plugins/internal/edge_add_remove.rs:238
- FileTooLong: src/lib.rs cincinnati/src/lib.rs
- FileTooLong: registry/mod.rs cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs
- Edited copy of a member (16 corresponding lines) prometheus-query/src/v1/mod.rs:89
- Edited copy of a member (16 corresponding lines) cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:124
- Edited copy of a member (14 corresponding lines) prometheus-query/src/v1/mod.rs:33
- Edited copy of a member (14 corresponding lines) cincinnati/src/lib.rs:370
- Duplicated block (17 lines × 2) cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs:261
- Duplicated block (17 lines × 2) cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs:350
- Duplicated block (10–11 lines × 2) cincinnati/src/plugins/internal/edge_add_remove.rs:348
- Duplicated block (10–11 lines × 2) cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:127
- Duplicated block (9 lines × 2) cincinnati/src/plugins/internal/arch_filter.rs:156
- Duplicated block (9 lines × 2) graph-builder/src/config/file.rs:68
- Duplicated block (7 lines × 3) graph-builder/src/config/cli.rs:35
- Duplicated block (7 lines × 3) graph-builder/src/config/options.rs:124
- Low cohesion: ClientBuilder (LCOM4 5) prometheus-query/src/v1/mod.rs:52
- Low cohesion: ClientBuilder (LCOM4 4) quay/src/v1/mod.rs:51
- No authorization policy-engine/src/main.rs:104
- cincinnati::plugins::internal::graph_builder::openshift_secondary_metadata_parser::plugin::deserialize_directory_files (cyclomatic 31) cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/plugin.rs:195
- EdgeAddRemovePlugin::remove_edges (cyclomatic 20) cincinnati/src/plugins/internal/edge_add_remove.rs:97
- graph.run (cognitive 18) hack/graph.py:9
- Graph::deserialize (cognitive 17) cincinnati/src/lib.rs:542
- FunctionTooLong: cincinnati::plugins::internal::graph_builder::release_scrape_dockerv2::registry::fetch_releases cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/registry/mod.rs:300
- Near-duplicate member pair (43 shared lines) metadata-helper/src/main.rs:68
- Edited copy of a member (104 corresponding lines) cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/plugin.rs:426
- Edited copy of a member (19 corresponding lines) metadata-helper/src/config/options.rs:81
- Edited copy of a member (12 corresponding lines) cincinnati/src/plugins/internal/arch_filter.rs:61
- Edited copies of one member (3 members, 13+ corresponding lines) graph-builder/src/config/cli.rs:34
- Edited copies of one member (3 members, 9+ corresponding lines) graph-builder/src/config/file.rs:55
- Edited copy of a member (11 corresponding lines) graph-builder/src/config/settings.rs:113
- Edited copies of one member (4 members, 8+ corresponding lines) cincinnati/src/plugins/internal/arch_filter.rs:46
- Duplicated block (20–22 lines × 2) cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/plugin.rs:217
- Duplicated block (21–22 lines × 2) cincinnati/src/plugins/internal/graph_builder/release.rs:115
- Duplicated block (20–21 lines × 2) cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/plugin.rs:441
- Duplicated block (19 lines × 2) metadata-helper/src/config/settings.rs:60
- Duplicated block (16–17 lines × 2) cincinnati/src/plugins/internal/edge_add_remove.rs:252
- Duplicated block (16 lines × 3) graph-builder/src/config/file.rs:36
- Duplicated block (15 lines × 2) metadata-helper/src/config/options.rs:82
- Duplicated block (13 lines × 2) metadata-helper/src/main.rs:146
- Duplicated block (10 lines × 3) cincinnati/src/plugins/internal/edge_add_remove.rs:111
- Duplicated block (8 lines × 3) cincinnati/src/plugins/internal/edge_add_remove.rs:210
- Duplicated block (7 lines × 2) metadata-helper/src/main.rs:106
- Duplicated block (6 lines × 3) graph-builder/src/main.rs:107
- Duplicated block (20 lines × 3) graph-builder/src/status.rs:11
- Duplicated block (6 lines × 2) metadata-helper/src/signatures.rs:29
- Duplicated block (5 lines × 2) graph-builder/src/main.rs:109
- Off the main sequence: quay
- Hollow method — returns a constant without doing the work commons/src/tracing.rs:9
- No CI pipeline
- Sync-over-async blocking policy-engine/src/main.rs:67
- Blocking `thread::sleep` inside an `async` body policy-engine/src/main.rs:181
- Recursive walk over a caller-supplied document has no depth cap prometheus-query/src/v1/queries/instant.rs:33
Minor — 67 finding(s)
- Orphaned file cincinnati/src/plugins/mod.rs:1
- Orphaned file cincinnati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs:1
- Orphaned file policy-engine/src/graph.rs:1
- Orphaned file cincinnati/src/plugins/internal/channel_filter.rs:1
- Orphaned file cincinnati/src/plugins/internal/metadata_fetch_quay.rs:1
- Orphaned file cincinnati/src/plugins/internal/cincinnati_graph_fetch.rs:1
- Orphaned file commons/src/lib.rs:1
- Orphaned file cincinnati/src/plugins/internal/arch_filter.rs:1
- Orphaned file graph-builder/src/graph.rs:1
- Orphaned file cincinnati/src/plugins/internal/graph_builder/release.rs:1
- Orphaned file policy-engine/src/main.rs:1
- Orphaned file policy-engine/src/openapi.rs:1
- Orphaned file cincinnati/src/plugins/internal/graph_builder/release_scrape_dockerv2/plugin.rs:1
- Orphaned file metadata-helper/src/main.rs:1
- Orphaned file graph-builder/src/config/settings.rs:1
- Orphaned file policy-engine/src/config/file.rs:1
- Orphaned file policy-engine/src/config/settings.rs:1
- Orphaned file graph-builder/src/config/options.rs:1
- Orphaned file commons/src/errors.rs:1
- Orphaned file graph-builder/src/config/file.rs:1
- Orphaned file policy-engine/src/config/options.rs:1
- Orphaned file cincinnati/src/plugins/macros.rs:1
- Orphaned file cincinnati/src/plugins/catalog.rs:1
- Orphaned file cincinnati/src/plugins/internal/graph_builder/dkrv2_openshift_secondary_metadata_scraper/gpg.rs:1
- Orphaned file cincinnati/src/plugins/external/web.rs:1
- Implementation type on the public API cincinnati/src/plugins/internal/arch_filter.rs:24
- Implementation type on the public API cincinnati/src/plugins/internal/channel_filter.rs:19
- Implementation type on the public API cincinnati/src/plugins/internal/cincinnati_graph_fetch.rs:41
- Implementation type on the public API cincinnati/src/plugins/internal/edge_add_remove.rs:15
- Implementation type on the public API cincinnati/src/plugins/internal/metadata_fetch_quay.rs:38
- Implementation type on the public API cincinnati/src/plugins/internal/node_remove.rs:13
- Implementation type on the public API cincinnati/src/plugins/internal/versioned_graph.rs:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file cincinnati/src/lib.rs:1
- Most significant orphaned file cincinnati/src/plugins/internal/graph_builder/openshift_secondary_metadata_parser/plugin.rs:1
- Most significant orphaned file cincinnati/src/plugins/internal/edge_add_remove.rs:1
- Off-boarding risk: anonymized user #1
- Concentrated knowledge decay
- No network policy
- No seccomp profile REDACTED:3
- ADRs not easily discoverable
- Logging is not universal
- No SAST
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Duplicated predicate metadata-helper/src/config/settings.rs:82
Minor — 21 finding(s)
- Outdated: actix
- Outdated: actix-web
- Outdated: anyhow
- Outdated: async-trait
- Outdated: bytes
- Outdated: chrono
- Outdated: flate2
- Outdated: futures
- Outdated: hyper
- Outdated: lazy_static
- Outdated: log
- Outdated: openapiv3
- Outdated: regex
- Outdated: serde
- Outdated: serde_derive
- Outdated: serde_json
- Outdated: tar
- Outdated: tempfile
- Outdated: tokio
- Outdated: tokio-stream
- Outdated: url
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-a9357c8bf99b499193febfa9c695ab87/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-a9357c8bf99b499193febfa9c695ab87/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1120" --report-format json --report-path /tmp/watchdog-gitleaks-a9357c8bf99b499193febfa9c695ab87/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a9357c8bf99b499193febfa9c695ab87/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude dist/grafana/dashboards . | 1 | 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 . | 50 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 33 | 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 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 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 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 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 |