Executive summary
rubyonjets/jets falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 50 out of 100 and is rated Adequate, and both of its critical findings are security problems in its code.
Production Readiness, at 42, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 36 files no active contributor knows, worth about 9 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 57.
One place in the code runs text as code, which an attacker could use. One weakness in the code could be used by an attacker. Replacing text run as code with direct calls and fixing the weaknesses the scanner points to would close both risks.
The product code is 10,509 lines, about €10,000 to rebuild.
If Production Readiness rose from 42 to 70, the lowest score rated Strong, the score would rise from 50 to about 57.
Rebuild cost: about €10,000 · Estimate
| Cost to rebuild | €3,400 to €17,000, for 57 to 179 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 50. 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: 10,509 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Jets.Api.Error | 2 Jets.CLI.Exec.Repl | 3 Jets.CLI.Group | 4 Jets.Util | 5 Jets.AwsServices | 6 Jets.CLI.Curl.Adapter.Cookies | 7 Jets.CLI.Generate | 8 Jets.Cfn.Builder | 9 Jets.Cfn.Resource | 10 Jets.Core.Config | 11 Jets.Stack | 12 Jets.Thor | 13 Jets | 14 Jets.Api | 15 Jets.CLI.Lambda | 16 Jets.Cfn.Builder.Parent | 17 Jets.Cfn.Stack | 18 Jets.Cfn.Teardown | 19 Jets.Dotenv | 20 Jets.Lambda | 21 Jets.Remote | 22 Jets.CLI.Ci | 23 Jets.Cfn | 24 Jets.Event | 25 (global) | 26 Jets.CLI | 27 Jets.Cfn.Resource.Codebuild | 28 Jets.Cfn.Resource.S3 | 29 Jets.CLI.Concurrency | 30 Jets.CLI.Curl | 31 Jets.CLI.Env | 32 Jets.CLI.Exec | 33 Jets.CLI.Git | 34 Jets.CLI.Maintenance | 35 Jets.CLI.Maintenance.Worker | 36 Jets.CLI.Package | 37 Jets.CLI.Release | 38 Jets.CLI.Schedule | 39 Jets.CLI.Waf | 40 Jets.CLI.Dotenv |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Jets.Api.Error | ||||||||||||||||||||||||||||||||||||||||
| 2 Jets.CLI.Exec.Repl | ||||||||||||||||||||||||||||||||||||||||
| 3 Jets.CLI.Group | ||||||||||||||||||||||||||||||||||||||||
| 4 Jets.Util | ||||||||||||||||||||||||||||||||||||||||
| 5 Jets.AwsServices | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 Jets.CLI.Curl.Adapter.Cookies | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Jets.CLI.Generate | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Jets.Cfn.Builder | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Jets.Cfn.Resource | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Jets.Core.Config | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Jets.Stack | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Jets.Thor | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Jets | 4 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 Jets.Api | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 Jets.CLI.Lambda | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 Jets.Cfn.Builder.Parent | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 Jets.Cfn.Stack | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 Jets.Cfn.Teardown | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Jets.Dotenv | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 Jets.Lambda | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Jets.Remote | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Jets.CLI.Ci | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 23 Jets.Cfn | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 Jets.Event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 (global) | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Jets.CLI | 1 | 4 | 1 | 11 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 27 Jets.Cfn.Resource.Codebuild | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 Jets.Cfn.Resource.S3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Jets.CLI.Concurrency | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Jets.CLI.Curl | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Jets.CLI.Env | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Jets.CLI.Exec | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 Jets.CLI.Git | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 Jets.CLI.Maintenance | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Jets.CLI.Maintenance.Worker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Jets.CLI.Package | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 Jets.CLI.Release | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Jets.CLI.Schedule | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 Jets.CLI.Waf | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Jets.CLI.Dotenv | 1 | 1 | 1 | 1 |
5→13 Jets.AwsServices uses Jets part of a loop✕
- Connections
- 3 pairs of types, where a type in Jets.AwsServices uses a type in Jets.
- The types involved
Jets.AwsServices.AwsHelpers→Jets.AwsServicesJets.AwsServices.AwsInfo→Jets.AwsServicesJets.AwsServices.S3Bucket→Jets.AwsServices
- Direction
- Jets.AwsServices uses Jets, so a change to Jets can break Jets.AwsServices, while a change to Jets.AwsServices can't break Jets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→4 Jets.CLI.Curl.Adapter.Cookies uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Curl.Adapter.Cookies uses a type in Jets.Util.
- The types involved
Jets.CLI.Curl.Adapter.Cookies.Jar→Jets.Util.Logging
- Direction
- Jets.CLI.Curl.Adapter.Cookies uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Curl.Adapter.Cookies, while a change to Jets.CLI.Curl.Adapter.Cookies can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Curl.Adapter.Cookies uses a module listed above it, which is the healthy direction.
7→3 Jets.CLI.Generate uses Jets.CLI.Group✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Generate uses a type in Jets.CLI.Group.
- The types involved
Jets.CLI.Generate.Event→Jets.CLI.Group.Base
- Direction
- Jets.CLI.Generate uses Jets.CLI.Group, so a change to Jets.CLI.Group can break Jets.CLI.Generate, while a change to Jets.CLI.Generate can't break Jets.CLI.Group.
- Position
- Below the diagonal: Jets.CLI.Generate uses a module listed above it, which is the healthy direction.
8→4 Jets.Cfn.Builder uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Builder uses a type in Jets.Util.
- The types involved
Jets.Cfn.Builder.Interface→Jets.Util.Camelize
- Direction
- Jets.Cfn.Builder uses Jets.Util, so a change to Jets.Util can break Jets.Cfn.Builder, while a change to Jets.Cfn.Builder can't break Jets.Util.
- Position
- Below the diagonal: Jets.Cfn.Builder uses a module listed above it, which is the healthy direction.
9→4 Jets.Cfn.Resource uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Resource uses a type in Jets.Util.
- The types involved
Jets.Cfn.Resource.Standardizer→Jets.Util.Camelize
- Direction
- Jets.Cfn.Resource uses Jets.Util, so a change to Jets.Util can break Jets.Cfn.Resource, while a change to Jets.Cfn.Resource can't break Jets.Util.
- Position
- Below the diagonal: Jets.Cfn.Resource uses a module listed above it, which is the healthy direction.
10→4 Jets.Core.Config uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Core.Config uses a type in Jets.Util.
- The types involved
Jets.Core.Config.Base→Jets.Util.Camelize
- Direction
- Jets.Core.Config uses Jets.Util, so a change to Jets.Util can break Jets.Core.Config, while a change to Jets.Core.Config can't break Jets.Util.
- Position
- Below the diagonal: Jets.Core.Config uses a module listed above it, which is the healthy direction.
11→13 Jets.Stack uses Jets part of a loop✕
- Connections
- 1 pair of types, where a type in Jets.Stack uses a type in Jets.
- The types involved
Jets.Stack.Outputs→Jets.AwsServices
- Direction
- Jets.Stack uses Jets, so a change to Jets can break Jets.Stack, while a change to Jets.Stack can't break Jets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→13 Jets.Thor uses Jets part of a loop✕
- Connections
- 1 pair of types, where a type in Jets.Thor uses a type in Jets.
- The types involved
Jets.Thor.Base→Jets.Thor
- Direction
- Jets.Thor uses Jets, so a change to Jets can break Jets.Thor, while a change to Jets.Thor can't break Jets.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→4 Jets uses Jets.Util✕
- Connections
- 4 pairs of types, where a type in Jets uses a type in Jets.Util.
- The types involved
Jets.Code→Jets.Util.LoggingJets.Code→Jets.Util.ShJets.Dotenv→Jets.Util.LoggingJets.Prewarm→Jets.Util.Logging
- Direction
- Jets uses Jets.Util, so a change to Jets.Util can break Jets, while a change to Jets can't break Jets.Util.
- Position
- Below the diagonal: Jets uses a module listed above it, which is the healthy direction.
13→5 Jets uses Jets.AwsServices✕
- Connections
- 2 pairs of types, where a type in Jets uses a type in Jets.AwsServices.
- The types involved
Jets.AwsServices→Jets.AwsServices.GlobalMemoistJets.AwsServices→Jets.AwsServices.StackStatus
- Direction
- Jets uses Jets.AwsServices, so a change to Jets.AwsServices can break Jets, while a change to Jets can't break Jets.AwsServices.
- Position
- Below the diagonal: Jets uses a module listed above it, which is the healthy direction.
13→11 Jets uses Jets.Stack✕
- Connections
- 1 pair of types, where a type in Jets uses a type in Jets.Stack.
- The types involved
Jets.Stack→Jets.Stack.Dsl
- Direction
- Jets uses Jets.Stack, so a change to Jets.Stack can break Jets, while a change to Jets can't break Jets.Stack.
- Position
- Below the diagonal: Jets uses a module listed above it, which is the healthy direction.
13→12 Jets uses Jets.Thor✕
- Connections
- 1 pair of types, where a type in Jets uses a type in Jets.Thor.
- The types involved
Jets.CLI→Jets.Thor.Base
- Direction
- Jets uses Jets.Thor, so a change to Jets.Thor can break Jets, while a change to Jets can't break Jets.Thor.
- Position
- Below the diagonal: Jets uses a module listed above it, which is the healthy direction.
14→1 Jets.Api uses Jets.Api.Error✕
- Connections
- 1 pair of types, where a type in Jets.Api uses a type in Jets.Api.Error.
- The types involved
Jets.Api.Client→Jets.Api.Error.Handlers
- Direction
- Jets.Api uses Jets.Api.Error, so a change to Jets.Api.Error can break Jets.Api, while a change to Jets.Api can't break Jets.Api.Error.
- Position
- Below the diagonal: Jets.Api uses a module listed above it, which is the healthy direction.
14→4 Jets.Api uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Api uses a type in Jets.Util.
- The types involved
Jets.Api.Client→Jets.Util.Logging
- Direction
- Jets.Api uses Jets.Util, so a change to Jets.Util can break Jets.Api, while a change to Jets.Api can't break Jets.Util.
- Position
- Below the diagonal: Jets.Api uses a module listed above it, which is the healthy direction.
14→13 Jets.Api uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Api uses a type in Jets.
- The types involved
Jets.Api.Base→Jets.Api
- Direction
- Jets.Api uses Jets, so a change to Jets can break Jets.Api, while a change to Jets.Api can't break Jets.
- Position
- Below the diagonal: Jets.Api uses a module listed above it, which is the healthy direction.
15→13 Jets.CLI.Lambda uses Jets✕
- Connections
- 2 pairs of types, where a type in Jets.CLI.Lambda uses a type in Jets.
- The types involved
Jets.CLI.Lambda.Function→Jets.AwsServicesJets.CLI.Lambda.Lookup→Jets.AwsServices
- Direction
- Jets.CLI.Lambda uses Jets, so a change to Jets can break Jets.CLI.Lambda, while a change to Jets.CLI.Lambda can't break Jets.
- Position
- Below the diagonal: Jets.CLI.Lambda uses a module listed above it, which is the healthy direction.
16→4 Jets.Cfn.Builder.Parent uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Builder.Parent uses a type in Jets.Util.
- The types involved
Jets.Cfn.Builder.Parent.Genesis→Jets.Util.Logging
- Direction
- Jets.Cfn.Builder.Parent uses Jets.Util, so a change to Jets.Util can break Jets.Cfn.Builder.Parent, while a change to Jets.Cfn.Builder.Parent can't break Jets.Util.
- Position
- Below the diagonal: Jets.Cfn.Builder.Parent uses a module listed above it, which is the healthy direction.
16→8 Jets.Cfn.Builder.Parent uses Jets.Cfn.Builder✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Builder.Parent uses a type in Jets.Cfn.Builder.
- The types involved
Jets.Cfn.Builder.Parent.Genesis→Jets.Cfn.Builder.Interface
- Direction
- Jets.Cfn.Builder.Parent uses Jets.Cfn.Builder, so a change to Jets.Cfn.Builder can break Jets.Cfn.Builder.Parent, while a change to Jets.Cfn.Builder.Parent can't break Jets.Cfn.Builder.
- Position
- Below the diagonal: Jets.Cfn.Builder.Parent uses a module listed above it, which is the healthy direction.
16→13 Jets.Cfn.Builder.Parent uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Builder.Parent uses a type in Jets.
- The types involved
Jets.Cfn.Builder.Parent.Genesis→Jets.AwsServices
- Direction
- Jets.Cfn.Builder.Parent uses Jets, so a change to Jets can break Jets.Cfn.Builder.Parent, while a change to Jets.Cfn.Builder.Parent can't break Jets.
- Position
- Below the diagonal: Jets.Cfn.Builder.Parent uses a module listed above it, which is the healthy direction.
17→4 Jets.Cfn.Stack uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Stack uses a type in Jets.Util.
- The types involved
Jets.Cfn.Stack.Rollback→Jets.Util.Logging
- Direction
- Jets.Cfn.Stack uses Jets.Util, so a change to Jets.Util can break Jets.Cfn.Stack, while a change to Jets.Cfn.Stack can't break Jets.Util.
- Position
- Below the diagonal: Jets.Cfn.Stack uses a module listed above it, which is the healthy direction.
17→5 Jets.Cfn.Stack uses Jets.AwsServices✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Stack uses a type in Jets.AwsServices.
- The types involved
Jets.Cfn.Stack.Rollback→Jets.AwsServices.AwsHelpers
- Direction
- Jets.Cfn.Stack uses Jets.AwsServices, so a change to Jets.AwsServices can break Jets.Cfn.Stack, while a change to Jets.Cfn.Stack can't break Jets.AwsServices.
- Position
- Below the diagonal: Jets.Cfn.Stack uses a module listed above it, which is the healthy direction.
17→13 Jets.Cfn.Stack uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Stack uses a type in Jets.
- The types involved
Jets.Cfn.Stack.Template→Jets.AwsServices
- Direction
- Jets.Cfn.Stack uses Jets, so a change to Jets can break Jets.Cfn.Stack, while a change to Jets.Cfn.Stack can't break Jets.
- Position
- Below the diagonal: Jets.Cfn.Stack uses a module listed above it, which is the healthy direction.
18→4 Jets.Cfn.Teardown uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Teardown uses a type in Jets.Util.
- The types involved
Jets.Cfn.Teardown.Bucket→Jets.Util.Logging
- Direction
- Jets.Cfn.Teardown uses Jets.Util, so a change to Jets.Util can break Jets.Cfn.Teardown, while a change to Jets.Cfn.Teardown can't break Jets.Util.
- Position
- Below the diagonal: Jets.Cfn.Teardown uses a module listed above it, which is the healthy direction.
18→13 Jets.Cfn.Teardown uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Teardown uses a type in Jets.
- The types involved
Jets.Cfn.Teardown.Bucket→Jets.AwsServices
- Direction
- Jets.Cfn.Teardown uses Jets, so a change to Jets can break Jets.Cfn.Teardown, while a change to Jets.Cfn.Teardown can't break Jets.
- Position
- Below the diagonal: Jets.Cfn.Teardown uses a module listed above it, which is the healthy direction.
19→4 Jets.Dotenv uses Jets.Util✕
- Connections
- 2 pairs of types, where a type in Jets.Dotenv uses a type in Jets.Util.
- The types involved
Jets.Dotenv.Ssm→Jets.Util.LoggingJets.Dotenv.Var→Jets.Util.Logging
- Direction
- Jets.Dotenv uses Jets.Util, so a change to Jets.Util can break Jets.Dotenv, while a change to Jets.Dotenv can't break Jets.Util.
- Position
- Below the diagonal: Jets.Dotenv uses a module listed above it, which is the healthy direction.
19→13 Jets.Dotenv uses Jets✕
- Connections
- 2 pairs of types, where a type in Jets.Dotenv uses a type in Jets.
- The types involved
Jets.Dotenv.Ssm→Jets.AwsServicesJets.Dotenv.Var→Jets.AwsServices
- Direction
- Jets.Dotenv uses Jets, so a change to Jets can break Jets.Dotenv, while a change to Jets.Dotenv can't break Jets.
- Position
- Below the diagonal: Jets.Dotenv uses a module listed above it, which is the healthy direction.
20→4 Jets.Lambda uses Jets.Util✕
- Connections
- 2 pairs of types, where a type in Jets.Lambda uses a type in Jets.Util.
- The types involved
Jets.Lambda.Definition→Jets.Util.CamelizeJets.Lambda.Functions→Jets.Util.Logging
- Direction
- Jets.Lambda uses Jets.Util, so a change to Jets.Util can break Jets.Lambda, while a change to Jets.Lambda can't break Jets.Util.
- Position
- Below the diagonal: Jets.Lambda uses a module listed above it, which is the healthy direction.
20→13 Jets.Lambda uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Lambda uses a type in Jets.
- The types involved
Jets.Lambda.Functions→Jets.ExceptionReporting
- Direction
- Jets.Lambda uses Jets, so a change to Jets can break Jets.Lambda, while a change to Jets.Lambda can't break Jets.
- Position
- Below the diagonal: Jets.Lambda uses a module listed above it, which is the healthy direction.
21→4 Jets.Remote uses Jets.Util✕
- Connections
- 2 pairs of types, where a type in Jets.Remote uses a type in Jets.Util.
- The types involved
Jets.Remote.Base→Jets.Util.LoggingJets.Remote.Tailer→Jets.Util.Pretty
- Direction
- Jets.Remote uses Jets.Util, so a change to Jets.Util can break Jets.Remote, while a change to Jets.Remote can't break Jets.Util.
- Position
- Below the diagonal: Jets.Remote uses a module listed above it, which is the healthy direction.
21→13 Jets.Remote uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Remote uses a type in Jets.
- The types involved
Jets.Remote.Base→Jets.AwsServices
- Direction
- Jets.Remote uses Jets, so a change to Jets can break Jets.Remote, while a change to Jets.Remote can't break Jets.
- Position
- Below the diagonal: Jets.Remote uses a module listed above it, which is the healthy direction.
22→3 Jets.CLI.Ci uses Jets.CLI.Group✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Ci uses a type in Jets.CLI.Group.
- The types involved
Jets.CLI.Ci.Init→Jets.CLI.Group.Base
- Direction
- Jets.CLI.Ci uses Jets.CLI.Group, so a change to Jets.CLI.Group can break Jets.CLI.Ci, while a change to Jets.CLI.Ci can't break Jets.CLI.Group.
- Position
- Below the diagonal: Jets.CLI.Ci uses a module listed above it, which is the healthy direction.
22→4 Jets.CLI.Ci uses Jets.Util✕
- Connections
- 2 pairs of types, where a type in Jets.CLI.Ci uses a type in Jets.Util.
- The types involved
Jets.CLI.Ci.Init→Jets.Util.SureJets.CLI.Ci.Status→Jets.Util.FormatTime
- Direction
- Jets.CLI.Ci uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Ci, while a change to Jets.CLI.Ci can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Ci uses a module listed above it, which is the healthy direction.
22→13 Jets.CLI.Ci uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Ci uses a type in Jets.
- The types involved
Jets.CLI.Ci.Info→Jets.AwsServices
- Direction
- Jets.CLI.Ci uses Jets, so a change to Jets can break Jets.CLI.Ci, while a change to Jets.CLI.Ci can't break Jets.
- Position
- Below the diagonal: Jets.CLI.Ci uses a module listed above it, which is the healthy direction.
22→21 Jets.CLI.Ci uses Jets.Remote✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Ci uses a type in Jets.Remote.
- The types involved
Jets.CLI.Ci.Tailer→Jets.Remote.Tailer
- Direction
- Jets.CLI.Ci uses Jets.Remote, so a change to Jets.Remote can break Jets.CLI.Ci, while a change to Jets.CLI.Ci can't break Jets.Remote.
- Position
- Below the diagonal: Jets.CLI.Ci uses a module listed above it, which is the healthy direction.
22→26 Jets.CLI.Ci uses Jets.CLI part of a loop✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Ci uses a type in Jets.CLI.
- The types involved
Jets.CLI.Ci.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Ci uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Ci, while a change to Jets.CLI.Ci can't break Jets.CLI.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→4 Jets.Cfn uses Jets.Util✕
- Connections
- 3 pairs of types, where a type in Jets.Cfn uses a type in Jets.Util.
- The types involved
Jets.Cfn.Base→Jets.Util.CamelizeJets.Cfn.Base→Jets.Util.LoggingJets.Cfn.Stack→Jets.Util.Logging
- Direction
- Jets.Cfn uses Jets.Util, so a change to Jets.Util can break Jets.Cfn, while a change to Jets.Cfn can't break Jets.Util.
- Position
- Below the diagonal: Jets.Cfn uses a module listed above it, which is the healthy direction.
23→13 Jets.Cfn uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Cfn uses a type in Jets.
- The types involved
Jets.Cfn.Stack→Jets.AwsServices
- Direction
- Jets.Cfn uses Jets, so a change to Jets can break Jets.Cfn, while a change to Jets.Cfn can't break Jets.
- Position
- Below the diagonal: Jets.Cfn uses a module listed above it, which is the healthy direction.
23→17 Jets.Cfn uses Jets.Cfn.Stack✕
- Connections
- 2 pairs of types, where a type in Jets.Cfn uses a type in Jets.Cfn.Stack.
- The types involved
Jets.Cfn.Stack→Jets.Cfn.Stack.DeployableJets.Cfn.Stack→Jets.Cfn.Stack.Rollback
- Direction
- Jets.Cfn uses Jets.Cfn.Stack, so a change to Jets.Cfn.Stack can break Jets.Cfn, while a change to Jets.Cfn can't break Jets.Cfn.Stack.
- Position
- Below the diagonal: Jets.Cfn uses a module listed above it, which is the healthy direction.
24→4 Jets.Event uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.Event uses a type in Jets.Util.
- The types involved
Jets.Event.Base→Jets.Util.Logging
- Direction
- Jets.Event uses Jets.Util, so a change to Jets.Util can break Jets.Event, while a change to Jets.Event can't break Jets.Util.
- Position
- Below the diagonal: Jets.Event uses a module listed above it, which is the healthy direction.
24→20 Jets.Event uses Jets.Lambda✕
- Connections
- 1 pair of types, where a type in Jets.Event uses a type in Jets.Lambda.
- The types involved
Jets.Event.Base→Jets.Lambda.Functions
- Direction
- Jets.Event uses Jets.Lambda, so a change to Jets.Lambda can break Jets.Event, while a change to Jets.Event can't break Jets.Lambda.
- Position
- Below the diagonal: Jets.Event uses a module listed above it, which is the healthy direction.
25→13 (global) uses Jets✕
- Connections
- 1 pair of types, where a type in (global) uses a type in Jets.
- The types involved
Jets→Jets.Core
- Direction
- (global) uses Jets, so a change to Jets can break (global), while a change to (global) can't break Jets.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
25→24 (global) uses Jets.Event✕
- Connections
- 1 pair of types, where a type in (global) uses a type in Jets.Event.
- The types involved
ApplicationEvent→Jets.Event.Base
- Direction
- (global) uses Jets.Event, so a change to Jets.Event can break (global), while a change to (global) can't break Jets.Event.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
26→3 Jets.CLI uses Jets.CLI.Group✕
- Connections
- 1 pair of types, where a type in Jets.CLI uses a type in Jets.CLI.Group.
- The types involved
Jets.CLI.Init→Jets.CLI.Group.Base
- Direction
- Jets.CLI uses Jets.CLI.Group, so a change to Jets.CLI.Group can break Jets.CLI, while a change to Jets.CLI can't break Jets.CLI.Group.
- Position
- Below the diagonal: Jets.CLI uses a module listed above it, which is the healthy direction.
26→4 Jets.CLI uses Jets.Util✕
- Connections
- 4 pairs of types, where a type in Jets.CLI uses a type in Jets.Util.
- The types involved
Jets.CLI.Base→Jets.Util.LoggingJets.CLI.Base→Jets.Util.SureJets.CLI.Call→Jets.Util.LoggingJets.CLI.Init→Jets.Util.Sure
- Direction
- Jets.CLI uses Jets.Util, so a change to Jets.Util can break Jets.CLI, while a change to Jets.CLI can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI uses a module listed above it, which is the healthy direction.
26→5 Jets.CLI uses Jets.AwsServices✕
- Connections
- 1 pair of types, where a type in Jets.CLI uses a type in Jets.AwsServices.
- The types involved
Jets.CLI.Logs→Jets.AwsServices.AwsHelpers
- Direction
- Jets.CLI uses Jets.AwsServices, so a change to Jets.AwsServices can break Jets.CLI, while a change to Jets.CLI can't break Jets.AwsServices.
- Position
- Below the diagonal: Jets.CLI uses a module listed above it, which is the healthy direction.
26→12 Jets.CLI uses Jets.Thor✕
- Connections
- 11 pairs of types, where a type in Jets.CLI uses a type in Jets.Thor.
- The types involved
Jets.CLI.Ci→Jets.Thor.BaseJets.CLI.Concurrency→Jets.Thor.BaseJets.CLI.Dotenv→Jets.Thor.BaseJets.CLI.Env→Jets.Thor.BaseJets.CLI.Generate→Jets.Thor.BaseJets.CLI.Git→Jets.Thor.BaseJets.CLI.Maintenance→Jets.Thor.BaseJets.CLI.Package→Jets.Thor.BaseJets.CLI.Release→Jets.Thor.BaseJets.CLI.Schedule→Jets.Thor.BaseJets.CLI.Waf→Jets.Thor.Base
- Direction
- Jets.CLI uses Jets.Thor, so a change to Jets.Thor can break Jets.CLI, while a change to Jets.CLI can't break Jets.Thor.
- Position
- Below the diagonal: Jets.CLI uses a module listed above it, which is the healthy direction.
26→13 Jets.CLI uses Jets✕
- Connections
- 3 pairs of types, where a type in Jets.CLI uses a type in Jets.
- The types involved
Jets.CLI.Base→Jets.ApiJets.CLI.Base→Jets.AwsServicesJets.CLI.Call→Jets.AwsServices
- Direction
- Jets.CLI uses Jets, so a change to Jets can break Jets.CLI, while a change to Jets.CLI can't break Jets.
- Position
- Below the diagonal: Jets.CLI uses a module listed above it, which is the healthy direction.
26→22 Jets.CLI uses Jets.CLI.Ci✕
- Connections
- 1 pair of types, where a type in Jets.CLI uses a type in Jets.CLI.Ci.
- The types involved
Jets.CLI.Stop→Jets.CLI.Ci.Base
- Direction
- Jets.CLI uses Jets.CLI.Ci, so a change to Jets.CLI.Ci can break Jets.CLI, while a change to Jets.CLI can't break Jets.CLI.Ci.
- Position
- Below the diagonal: Jets.CLI uses a module listed above it, which is the healthy direction.
27→23 Jets.Cfn.Resource.Codebuild uses Jets.Cfn✕
- Connections
- 2 pairs of types, where a type in Jets.Cfn.Resource.Codebuild uses a type in Jets.Cfn.
- The types involved
Jets.Cfn.Resource.Codebuild.Fleet→Jets.Cfn.BaseJets.Cfn.Resource.Codebuild.IamRole→Jets.Cfn.Base
- Direction
- Jets.Cfn.Resource.Codebuild uses Jets.Cfn, so a change to Jets.Cfn can break Jets.Cfn.Resource.Codebuild, while a change to Jets.Cfn.Resource.Codebuild can't break Jets.Cfn.
- Position
- Below the diagonal: Jets.Cfn.Resource.Codebuild uses a module listed above it, which is the healthy direction.
28→13 Jets.Cfn.Resource.S3 uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Resource.S3 uses a type in Jets.
- The types involved
Jets.Cfn.Resource.S3.JetsBucket→Jets.AwsServices
- Direction
- Jets.Cfn.Resource.S3 uses Jets, so a change to Jets can break Jets.Cfn.Resource.S3, while a change to Jets.Cfn.Resource.S3 can't break Jets.
- Position
- Below the diagonal: Jets.Cfn.Resource.S3 uses a module listed above it, which is the healthy direction.
28→23 Jets.Cfn.Resource.S3 uses Jets.Cfn✕
- Connections
- 1 pair of types, where a type in Jets.Cfn.Resource.S3 uses a type in Jets.Cfn.
- The types involved
Jets.Cfn.Resource.S3.Bucket→Jets.Cfn.Base
- Direction
- Jets.Cfn.Resource.S3 uses Jets.Cfn, so a change to Jets.Cfn can break Jets.Cfn.Resource.S3, while a change to Jets.Cfn.Resource.S3 can't break Jets.Cfn.
- Position
- Below the diagonal: Jets.Cfn.Resource.S3 uses a module listed above it, which is the healthy direction.
29→4 Jets.CLI.Concurrency uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Concurrency uses a type in Jets.Util.
- The types involved
Jets.CLI.Concurrency.Base→Jets.Util.Truthy
- Direction
- Jets.CLI.Concurrency uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Concurrency, while a change to Jets.CLI.Concurrency can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Concurrency uses a module listed above it, which is the healthy direction.
29→15 Jets.CLI.Concurrency uses Jets.CLI.Lambda✕
- Connections
- 3 pairs of types, where a type in Jets.CLI.Concurrency uses a type in Jets.CLI.Lambda.
- The types involved
Jets.CLI.Concurrency.Base→Jets.CLI.Lambda.ChecksJets.CLI.Concurrency.Get→Jets.CLI.Lambda.FunctionJets.CLI.Concurrency.Info→Jets.CLI.Lambda.Functions
- Direction
- Jets.CLI.Concurrency uses Jets.CLI.Lambda, so a change to Jets.CLI.Lambda can break Jets.CLI.Concurrency, while a change to Jets.CLI.Concurrency can't break Jets.CLI.Lambda.
- Position
- Below the diagonal: Jets.CLI.Concurrency uses a module listed above it, which is the healthy direction.
29→26 Jets.CLI.Concurrency uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Concurrency uses a type in Jets.CLI.
- The types involved
Jets.CLI.Concurrency.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Concurrency uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Concurrency, while a change to Jets.CLI.Concurrency can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Concurrency uses a module listed above it, which is the healthy direction.
30→26 Jets.CLI.Curl uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Curl uses a type in Jets.CLI.
- The types involved
Jets.CLI.Curl.Request→Jets.CLI.Call
- Direction
- Jets.CLI.Curl uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Curl, while a change to Jets.CLI.Curl can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Curl uses a module listed above it, which is the healthy direction.
31→4 Jets.CLI.Env uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Env uses a type in Jets.Util.
- The types involved
Jets.CLI.Env.Base→Jets.Util.Truthy
- Direction
- Jets.CLI.Env uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Env, while a change to Jets.CLI.Env can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Env uses a module listed above it, which is the healthy direction.
31→15 Jets.CLI.Env uses Jets.CLI.Lambda✕
- Connections
- 2 pairs of types, where a type in Jets.CLI.Env uses a type in Jets.CLI.Lambda.
- The types involved
Jets.CLI.Env.Base→Jets.CLI.Lambda.ChecksJets.CLI.Env.Base→Jets.CLI.Lambda.Function
- Direction
- Jets.CLI.Env uses Jets.CLI.Lambda, so a change to Jets.CLI.Lambda can break Jets.CLI.Env, while a change to Jets.CLI.Env can't break Jets.CLI.Lambda.
- Position
- Below the diagonal: Jets.CLI.Env uses a module listed above it, which is the healthy direction.
31→26 Jets.CLI.Env uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Env uses a type in Jets.CLI.
- The types involved
Jets.CLI.Env.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Env uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Env, while a change to Jets.CLI.Env can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Env uses a module listed above it, which is the healthy direction.
32→2 Jets.CLI.Exec uses Jets.CLI.Exec.Repl✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Exec uses a type in Jets.CLI.Exec.Repl.
- The types involved
Jets.CLI.Exec.Repl→Jets.CLI.Exec.Repl.History
- Direction
- Jets.CLI.Exec uses Jets.CLI.Exec.Repl, so a change to Jets.CLI.Exec.Repl can break Jets.CLI.Exec, while a change to Jets.CLI.Exec can't break Jets.CLI.Exec.Repl.
- Position
- Below the diagonal: Jets.CLI.Exec uses a module listed above it, which is the healthy direction.
32→4 Jets.CLI.Exec uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Exec uses a type in Jets.Util.
- The types involved
Jets.CLI.Exec.Repl→Jets.Util.Logging
- Direction
- Jets.CLI.Exec uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Exec, while a change to Jets.CLI.Exec can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Exec uses a module listed above it, which is the healthy direction.
32→26 Jets.CLI.Exec uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Exec uses a type in Jets.CLI.
- The types involved
Jets.CLI.Exec.Command→Jets.CLI.Call
- Direction
- Jets.CLI.Exec uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Exec, while a change to Jets.CLI.Exec can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Exec uses a module listed above it, which is the healthy direction.
33→26 Jets.CLI.Git uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Git uses a type in Jets.CLI.
- The types involved
Jets.CLI.Git.Push→Jets.CLI.Base
- Direction
- Jets.CLI.Git uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Git, while a change to Jets.CLI.Git can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Git uses a module listed above it, which is the healthy direction.
34→4 Jets.CLI.Maintenance uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Maintenance uses a type in Jets.Util.
- The types involved
Jets.CLI.Maintenance.Base→Jets.Util.Truthy
- Direction
- Jets.CLI.Maintenance uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Maintenance, while a change to Jets.CLI.Maintenance can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Maintenance uses a module listed above it, which is the healthy direction.
34→15 Jets.CLI.Maintenance uses Jets.CLI.Lambda✕
- Connections
- 2 pairs of types, where a type in Jets.CLI.Maintenance uses a type in Jets.CLI.Lambda.
- The types involved
Jets.CLI.Maintenance.Base→Jets.CLI.Lambda.ChecksJets.CLI.Maintenance.Web→Jets.CLI.Lambda.Function
- Direction
- Jets.CLI.Maintenance uses Jets.CLI.Lambda, so a change to Jets.CLI.Lambda can break Jets.CLI.Maintenance, while a change to Jets.CLI.Maintenance can't break Jets.CLI.Lambda.
- Position
- Below the diagonal: Jets.CLI.Maintenance uses a module listed above it, which is the healthy direction.
34→26 Jets.CLI.Maintenance uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Maintenance uses a type in Jets.CLI.
- The types involved
Jets.CLI.Maintenance.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Maintenance uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Maintenance, while a change to Jets.CLI.Maintenance can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Maintenance uses a module listed above it, which is the healthy direction.
35→15 Jets.CLI.Maintenance.Worker uses Jets.CLI.Lambda✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Maintenance.Worker uses a type in Jets.CLI.Lambda.
- The types involved
Jets.CLI.Maintenance.Worker.Base→Jets.CLI.Lambda.Functions
- Direction
- Jets.CLI.Maintenance.Worker uses Jets.CLI.Lambda, so a change to Jets.CLI.Lambda can break Jets.CLI.Maintenance.Worker, while a change to Jets.CLI.Maintenance.Worker can't break Jets.CLI.Lambda.
- Position
- Below the diagonal: Jets.CLI.Maintenance.Worker uses a module listed above it, which is the healthy direction.
35→26 Jets.CLI.Maintenance.Worker uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Maintenance.Worker uses a type in Jets.CLI.
- The types involved
Jets.CLI.Maintenance.Worker.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Maintenance.Worker uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Maintenance.Worker, while a change to Jets.CLI.Maintenance.Worker can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Maintenance.Worker uses a module listed above it, which is the healthy direction.
36→26 Jets.CLI.Package uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Package uses a type in Jets.CLI.
- The types involved
Jets.CLI.Package.Dockerfile→Jets.CLI.Base
- Direction
- Jets.CLI.Package uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Package, while a change to Jets.CLI.Package can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Package uses a module listed above it, which is the healthy direction.
37→4 Jets.CLI.Release uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Release uses a type in Jets.Util.
- The types involved
Jets.CLI.Release.History→Jets.Util.FormatTime
- Direction
- Jets.CLI.Release uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Release, while a change to Jets.CLI.Release can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Release uses a module listed above it, which is the healthy direction.
37→26 Jets.CLI.Release uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Release uses a type in Jets.CLI.
- The types involved
Jets.CLI.Release.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Release uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Release, while a change to Jets.CLI.Release can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Release uses a module listed above it, which is the healthy direction.
38→26 Jets.CLI.Schedule uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Schedule uses a type in Jets.CLI.
- The types involved
Jets.CLI.Schedule.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Schedule uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Schedule, while a change to Jets.CLI.Schedule can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Schedule uses a module listed above it, which is the healthy direction.
39→3 Jets.CLI.Waf uses Jets.CLI.Group✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Waf uses a type in Jets.CLI.Group.
- The types involved
Jets.CLI.Waf.Init→Jets.CLI.Group.Base
- Direction
- Jets.CLI.Waf uses Jets.CLI.Group, so a change to Jets.CLI.Group can break Jets.CLI.Waf, while a change to Jets.CLI.Waf can't break Jets.CLI.Group.
- Position
- Below the diagonal: Jets.CLI.Waf uses a module listed above it, which is the healthy direction.
39→4 Jets.CLI.Waf uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Waf uses a type in Jets.Util.
- The types involved
Jets.CLI.Waf.Init→Jets.Util.Sure
- Direction
- Jets.CLI.Waf uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Waf, while a change to Jets.CLI.Waf can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Waf uses a module listed above it, which is the healthy direction.
39→13 Jets.CLI.Waf uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Waf uses a type in Jets.
- The types involved
Jets.CLI.Waf.Info→Jets.AwsServices
- Direction
- Jets.CLI.Waf uses Jets, so a change to Jets can break Jets.CLI.Waf, while a change to Jets.CLI.Waf can't break Jets.
- Position
- Below the diagonal: Jets.CLI.Waf uses a module listed above it, which is the healthy direction.
39→26 Jets.CLI.Waf uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Waf uses a type in Jets.CLI.
- The types involved
Jets.CLI.Waf.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Waf uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Waf, while a change to Jets.CLI.Waf can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Waf uses a module listed above it, which is the healthy direction.
40→4 Jets.CLI.Dotenv uses Jets.Util✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Dotenv uses a type in Jets.Util.
- The types involved
Jets.CLI.Dotenv.Ssm→Jets.Util.Logging
- Direction
- Jets.CLI.Dotenv uses Jets.Util, so a change to Jets.Util can break Jets.CLI.Dotenv, while a change to Jets.CLI.Dotenv can't break Jets.Util.
- Position
- Below the diagonal: Jets.CLI.Dotenv uses a module listed above it, which is the healthy direction.
40→13 Jets.CLI.Dotenv uses Jets✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Dotenv uses a type in Jets.
- The types involved
Jets.CLI.Dotenv.Ssm→Jets.AwsServices
- Direction
- Jets.CLI.Dotenv uses Jets, so a change to Jets can break Jets.CLI.Dotenv, while a change to Jets.CLI.Dotenv can't break Jets.
- Position
- Below the diagonal: Jets.CLI.Dotenv uses a module listed above it, which is the healthy direction.
40→26 Jets.CLI.Dotenv uses Jets.CLI✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Dotenv uses a type in Jets.CLI.
- The types involved
Jets.CLI.Dotenv.Base→Jets.CLI.Base
- Direction
- Jets.CLI.Dotenv uses Jets.CLI, so a change to Jets.CLI can break Jets.CLI.Dotenv, while a change to Jets.CLI.Dotenv can't break Jets.CLI.
- Position
- Below the diagonal: Jets.CLI.Dotenv uses a module listed above it, which is the healthy direction.
40→31 Jets.CLI.Dotenv uses Jets.CLI.Env✕
- Connections
- 1 pair of types, where a type in Jets.CLI.Dotenv uses a type in Jets.CLI.Env.
- The types involved
Jets.CLI.Dotenv.Set→Jets.CLI.Env.Parse
- Direction
- Jets.CLI.Dotenv uses Jets.CLI.Env, so a change to Jets.CLI.Env can break Jets.CLI.Dotenv, while a change to Jets.CLI.Dotenv can't break Jets.CLI.Env.
- Position
- Below the diagonal: Jets.CLI.Dotenv 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 36 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), info.rb (2), init.rb (2); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 36 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), info.rb (2), init.rb (2). | +8.7 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.9 pts | Medium | Architecture documentation |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.6 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — 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. | +4.6 pts | Medium | Security & performance tooling |
| Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive. | +2.6 pts | Medium | Nullable reference types |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.1 pts | Low | Project Cohesion |
| 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. | +2.0 pts | Medium | Deployment & Rollback |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.8 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| lib/jets/lambda/dsl.rb | 6.7 | Mixed | Explicit Debt: TodoComment |
| lib/jets/cfn/builder/parent/genesis.rb | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| lib/jets/event/dsl.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/jets/cfn/resource/codebuild/project/ec2.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/jets/api/client.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/jets/aws_services/aws_info.rb | 8.5 | Near-clean | Cognitive Complexity: AwsInfo.region (cognitive 19) |
| lib/jets/cfn/resource/standardizer.rb | 8.5 | Near-clean | Cognitive Complexity: Standardizer.standarize (cognitive 16) |
| lib/jets/cli/ci/deploy.rb | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| lib/jets/git/bitbucket.rb | 8.5 | Near-clean | Code Duplication: Duplicated block (24 lines × 2) |
| lib/jets/cfn/stack.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Stack (LCOM4 4) |
| lib/jets/code.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Code (LCOM4 4) |
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 54 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 54 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, 67 of 74 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rb) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `spec_helper.rb`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `spec_helper.rb`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rb) and this repository declares a Ruby test suite (RSpec: repository root, 7 spec files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (89 contributor(s) across 3845 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 88 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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 on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — 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.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Hanami (dry-system), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — 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. Render strategy: boot via Dockerfile (lib/jets/cli/package/dockerfile.rb). docker build failed (exit 1) — #1 [internal] load build definition from dockerfile.rb #1 transferring dockerfile: 344B done #1 DONE 0.0s dockerfile.rb:1 -------------------- 1 | >>> class Jets::CLI::Package 2 | class Dockerfile < Jets::CLI::Base 3 | def run -------------------- ERROR: failed to solve: dockerfile parse error on line 1: unknown instruction: class; runtime evidence skipped.
- C1 Data Protection — 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. 'aws-sdk-dynamodb' is imported (lib/jets/aws_services.rb:5), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — 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. 'aws-sdk-dynamodb' is imported (lib/jets/aws_services.rb:5), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'aws-sdk-dynamodb' is imported (lib/jets/aws_services.rb:5), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'aws-sdk-dynamodb' is imported (lib/jets/aws_services.rb:5), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 282 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was AwsInfo.region at 19.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with AwsInfo.region (cognitive 19), Standardizer.standarize (cognitive 16). — 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 Cognitive Complexity from 9.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with dsl.rb. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with deploy.rb. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (24 lines × 2) finding(s) in Code Duplication — start with bitbucket.rb. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
3 of 40 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with genesis.rb, stack.rb, code.rb. — One of this dimension's main actionable groups (3 warning-level).
- Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D12 · Dependency Hygiene
0 outdated direct gem(s), 0 pinning defect(s). 45 declaration(s) graded against rubygems.org, none of them against a committed Gemfile.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 38 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 38 runtime gem(s) this repository declares. It commits no Gemfile.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
5 deducted task-comment markers across 10509 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with dsl.rb (2), ec2.rb, genesis.rb. — One of this dimension's main actionable groups (5 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 1 build units (Bundler) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
5 finding(s): 0 critical, 2 high, 3 medium, 0 low.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- 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
No known-vulnerable dependencies in any ecosystem this repository declares. No known-vulnerable gem among the 45 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 45 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.
D34 · Knowledge Freshness
36 of 36 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/jets/lambda/dsl.rb. Counted over 36 of the 282 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 36 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), info.rb (2), init.rb (2). — One of this dimension's main actionable groups (36 recommendation-level).
- Resolve the 1 Dormant codebase 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.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious. No known-vulnerable gem among the 45 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 45 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 45 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
- A placeholder string ("REPLACE_ME") is still in shipped code — typical of generated boilerplate that was never filled in. — lib/jets/cli/ci/init.rb:55
What to do
- Finish or delete the methods that still raise NotImplementedError where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- 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
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-ruby) and a health-check endpoint (Rails' /up (rails/health#show) or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — 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: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — 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.
- Enable Dependabot/Renovate or a dependency-review gate.
- 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
P7 · Outbound HTTP resilience
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `camelize` is public and takes `object` — which it walks as a `Hash` — from its caller, and it calls itself at line 7 (`self.camelize`) with a piece of `object` — and nowhere in `camelize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack 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. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `camelize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — REDACTED:7
- `trim!` is public and takes `hash` — which it walks as a `Hash` — from its caller, and it calls itself at line 47 (`self.trim!`) with a piece of `hash` — and nowhere in `trim!` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack 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. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `trim!` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/jets/cli/curl/request.rb:47
- `update_values` is public and takes `original` — which it walks as a `Hash` — from its caller, and it calls itself at line 31 (`self.update_values`) with a piece of `original` (and at line 34) — and nowhere in `update_values` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends stack 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. A walk like this one raises `SystemStackError` past about 3,800 levels on the main thread and about 1,000 on a `Thread` — where Puma serves requests and Sidekiq runs jobs (MRI 3.3 and 4.0). `JSON.parse` stops at 100 levels by default, but the other parsers a caller may use do not: `YAML.safe_load` builds 1,400 levels from 2.8 KB, `Oj.load` 100,000, REXML 200,000, and `JSON.load` on json 2.7 (Ruby 3.3's default) or `JSON.parse(…, max_nesting: false)` 58,000. `SystemStackError` is not a `StandardError`: a bare `rescue` or `rescue => e` around the call does not stop it. Thread a depth argument through `update_values` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/jets/cfn/resource/replacer.rb:31
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.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
- `capture_stdout_for_help` changes state that belongs to the whole process and changes it back at the end of the same body — the process's `$stdout` (changed at line 13, put back at line 15) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not an `ensure`, so it is skipped by any exception raised in between: the process then keeps the overwritten value for the rest of its life, and every later relative path, subprocess, write to the standard streams or warning in ANY thread or fiber resolves against it. That failure is silent and remote from its cause — the method that breaks is not the method that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `chdir:` and an environment hash to `system`/`spawn`/`Open3` (`system({'K' => v}, cmd, chdir: dir)`), an absolute path built with `File.join`/`File.expand_path`, an explicit IO to the code that writes. Where the global genuinely must move, use the block form `Dir.chdir(dir) { … }` or wrap it `begin`/`ensure` so the restore runs on every path. — lib/jets/thor/help.rb:10
What to do
- Each finding names the statement that changes the global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: `chdir:` and an environment hash passed to `system`/`spawn`/`Open3`, or an explicit IO handed to the code that writes, is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move, the block form `Dir.chdir(dir) { … }` or a `begin`/`ensure` is the least that makes the restore unconditional.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 37 is called with an argument built by `backtrace.join("\n")` (line 37), whose cost grows with the collection it walks. Ruby evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `debug?` test, no debug flag, no block the logger calls only when the level is on. — lib/jets/cli/base.rb:37
What to do
- In Ruby, hand the logger a block it calls only when the level is on (`logger.debug { "args: #{args.join(' ')}" }` — Logger, ActiveSupport, SemanticLogger and console all take one), or put the line behind `if logger.debug?`. Interpolating the value into the message is not the fix: Ruby builds the string, and every `map`, `join` or `to_json` inside its `#{…}`, before the call is entered.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `rescue` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — lib/jets/cli/schedule/validate.rb:75, lib/jets/aws_services/aws_info.rb:19, lib/jets/aws_services/s3_bucket.rb:28, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — lib/jets/aws_services/aws_info.rb:44
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 282 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
- Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 80% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 42% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 87% | Strong | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'aws-sdk-dynamodb' (lib/jets/aws_services.rb:5) but declares no persisted model this check reads (ActiveRecord and Sequel migration columns, db/schema.rb, Mongoid document fields). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'aws-sdk-dynamodb' (lib/jets/aws_services.rb:5) but declares no persisted model this check reads (ActiveRecord/Sequel migration and db/schema.rb columns, Mongoid document fields). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'aws-sdk-dynamodb' (lib/jets/aws_services.rb:5) but declares no persisted model this check reads (ActiveRecord migration and db/schema.rb columns, Sequel migration columns, Mongoid fields). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (10 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no class or module declares an abstract method
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — #1 [internal] load build definition from dockerfile.rb #1 transferring dockerfile: 344B done #1 DONE 0.0s dockerfile.rb:1 -------------------- 1 | >>> class Jets::CLI::Package 2 | class Dockerfile < Jets::CLI::Base 3 | def run -------------------- ERROR: failed to solve: dockerfile parse error on line 1: unknown instruction: class; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through 'aws-sdk-dynamodb' (lib/jets/aws_services.rb:5) but declares no persisted model this check reads (ActiveRecord migration and db/schema.rb columns, Sequel migration columns, Mongoid fields). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository draws no route and defines no request handler (no Rails routes.draw or controller, no Sinatra, Roda or Grape application, no Hanami action). Access control is therefore N/A here — a gem is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D10 Test Quality — ~357 lines of test source are present (.rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rb suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Ruby not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby 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 .rb, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this RubyGems build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.rb) 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- 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 — no coverage report found on disk — produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `spec_helper.rb`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a Gemfile or gemspec, 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 applicable: Ruby runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
- PF3 Async & latency hygiene — Not applicable: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: 282 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for Ruby: this reading covers the code's own cryptography and the TLS connections it opens as a client, and a Rails, Rack or Sinatra application's transport, header and validation settings are not modelled. Their absence here is not a finding about this repository.
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 26 finding(s)
- TodoComment lib/jets/lambda/dsl.rb:181
- TodoComment lib/jets/event/dsl.rb:28
- TodoComment lib/jets/cfn/resource/codebuild/project/ec2.rb:45
- TodoComment lib/jets/cfn/builder/parent/genesis.rb:78
- TodoComment lib/jets/api/client.rb:168
- Swallowed exception (caught, then discarded) lib/jets/cli/schedule/validate.rb:75
- Swallowed exception (caught, then discarded) lib/jets/aws_services/aws_info.rb:19
- Swallowed exception (caught, then discarded) lib/jets/aws_services/s3_bucket.rb:28
- Swallowed exception (caught, then discarded) lib/jets/api/client.rb:207
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: Genesis (LCOM4 4) lib/jets/cfn/builder/parent/genesis.rb:2
- Low cohesion: Stack (LCOM4 4) lib/jets/cfn/stack.rb:2
- Low cohesion: Code (LCOM4 4) lib/jets/code.rb:2
- Recursive walk over a caller-supplied document has no depth cap REDACTED:7
- Recursive walk over a caller-supplied document has no depth cap lib/jets/cli/curl/request.rb:47
- Recursive walk over a caller-supplied document has no depth cap lib/jets/cfn/resource/replacer.rb:31
- AwsInfo.region (cognitive 19) lib/jets/aws_services/aws_info.rb:6
- Standardizer.standarize (cognitive 16) lib/jets/cfn/resource/standardizer.rb:14
- TooManyMethods: ClassMethods lib/jets/lambda/dsl.rb:14
- Duplicated block (7 lines × 2) lib/jets/cli/ci/deploy.rb:4
- Duplicated block (24 lines × 2) lib/jets/git/bitbucket.rb:4
- No CI pipeline
- Process-global state is restored only on the happy path lib/jets/thor/help.rb:10
- Swallowed exception (empty catch) lib/jets/aws_services/aws_info.rb:44
Minor — 46 finding(s)
- Orphaned file lib/jets/lambda/dsl.rb:1
- Orphaned file lib/jets/remote/tailer.rb:1
- Orphaned file lib/jets/cli.rb:1
- Orphaned file lib/jets/api/client.rb:1
- Orphaned file lib/jets/cli/schedule/translate.rb:1
- Orphaned file lib/jets/cfn/deploy.rb:1
- Orphaned file lib/jets/aws_services/aws_info.rb:1
- Orphaned file lib/jets/shim/adapter/web.rb:1
- Orphaned file lib/jets/shim/response/base.rb:1
- Orphaned file lib/jets/cfn/builder/interface.rb:1
- Orphaned file lib/jets/lambda/definition.rb:1
- Orphaned file lib/jets/cli/call.rb:1
- Orphaned file lib/jets/cli/ci/start.rb:1
- Orphaned file lib/jets/code/stager.rb:1
- Orphaned file REDACTED:1
- Orphaned file lib/jets/core/config/project.rb:1
- Orphaned file lib/jets/cli/waf/info.rb:1
- Orphaned file lib/jets/cfn/iam/policy.rb:1
- Orphaned file lib/jets/thor/help.rb:1
- Orphaned file lib/jets/cfn/resource/codebuild/project/ec2.rb:1
- Orphaned file lib/jets/cfn/status.rb:1
- Orphaned file lib/jets/cli/lambda/function.rb:1
- Orphaned file lib/jets/cli/curl/adapter/lambda.rb:1
- Orphaned file lib/jets/bundle.rb:1
- Orphaned file lib/jets/core/config/bootstrap/codebuild.rb:1
- Duplicated predicate lib/jets/cli/ci/tailer.rb:10
- Duplicated predicate lib/jets/shim/adapter/alb.rb:7
- Projects may be oversized for their cohesion
- Dormant codebase
- Placeholder literal left in code lib/jets/cli/ci/init.rb:55
- No ADRs
- No architecture diagram/doc
- No SAST
- Diagnostic log message is built whether or not it is wanted lib/jets/cli/base.rb:37
- Ruby's type checker does not check nil everywhere
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 --report-format json --report-path /tmp/watchdog-gitleaks-bfd227c61c284192a09a04650a2def55/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bfd227c61c284192a09a04650a2def55/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 . | 5 | artifacts/raw/semgrep.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |