Executive summary
ruby-grape/grape falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 56 out of 100 and is rated Adequate, and all 21 of its critical findings are security problems.
Production Readiness, at 43, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6 points. Planning backups and recovery would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 65.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six secrets can leak from the build pipeline, and one password or key is open to anyone who can read the repository. Pinning each tool to an exact version, limiting each secret to its own step and replacing the exposed password or key would close these risks. The place where the code runs text as code or as a command needs a direct call instead. The unsafe setting in infrastructure or container files needs changing to safe values.
The product code is 11,863 lines, about €45,000 to rebuild.
If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 56 to about 65.
New since the last survey: 1 finding
- Cohesion (LCOM4) · Low cohesion: UndeclaredParams (LCOM4 4) lib/grape/validations/undeclared_params.rb
Fixed since the last survey: 1 finding
- Change Coupling · Change coupling: attributes_iterator.rb ↔ multiple_params_base.rb lib/grape/validations/attributes_iterator.rb
Rebuild cost: about €45,000 · Estimate
| Cost to rebuild | €15,000 to €75,000, for 250 to 793 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,863 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 (global) | 2 Grape.DSL.Declared | 3 Grape.DSL.Helpers | 4 Grape.Endpoint | 5 Grape.ErrorFormatter | 6 Grape.Formatter | 7 Grape.Middleware.Error | 8 Grape.Middleware.Stack | 9 Grape.Middleware.Versioner.Base | 10 Grape.ParamsBuilder | 11 Grape.Parser | 12 Grape.Presenters | 13 Grape.Router | 14 Grape.Router.RouteBuckets | 15 Grape.ServeStream | 16 Grape.Testing | 17 Grape.Util.InheritableSetting | 18 Grape.Util.Lazy | 19 Grape.Validations.ParamsScope | 20 Grape.Util | 21 Grape.ContentTypes | 22 Grape.DSL | 23 Grape.DryTypes | 24 Grape.Exceptions | 25 Grape.Middleware.Formatter | 26 Grape.Middleware.Versioner.Header | 27 Grape.Namespace | 28 Grape.Router.BaseRoute | 29 Grape.Router.Pattern | 30 Grape.Router.Pattern.Path | 31 Grape.Util.MediaType | 32 Grape.Validations.ParamsDocumentation | 33 Grape.Validations.Types | 34 Grape | 35 Grape.Middleware | 36 Grape.Validations | 37 Grape.Middleware.Auth | 38 Grape.Middleware.Versioner | 39 Grape.Validations.Validators | 40 Grape.API |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 Grape.DSL.Declared | ||||||||||||||||||||||||||||||||||||||||
| 3 Grape.DSL.Helpers | ||||||||||||||||||||||||||||||||||||||||
| 4 Grape.Endpoint | ||||||||||||||||||||||||||||||||||||||||
| 5 Grape.ErrorFormatter | ||||||||||||||||||||||||||||||||||||||||
| 6 Grape.Formatter | ||||||||||||||||||||||||||||||||||||||||
| 7 Grape.Middleware.Error | ||||||||||||||||||||||||||||||||||||||||
| 8 Grape.Middleware.Stack | ||||||||||||||||||||||||||||||||||||||||
| 9 Grape.Middleware.Versioner.Base | ||||||||||||||||||||||||||||||||||||||||
| 10 Grape.ParamsBuilder | ||||||||||||||||||||||||||||||||||||||||
| 11 Grape.Parser | ||||||||||||||||||||||||||||||||||||||||
| 12 Grape.Presenters | ||||||||||||||||||||||||||||||||||||||||
| 13 Grape.Router | ||||||||||||||||||||||||||||||||||||||||
| 14 Grape.Router.RouteBuckets | ||||||||||||||||||||||||||||||||||||||||
| 15 Grape.ServeStream | ||||||||||||||||||||||||||||||||||||||||
| 16 Grape.Testing | ||||||||||||||||||||||||||||||||||||||||
| 17 Grape.Util.InheritableSetting | ||||||||||||||||||||||||||||||||||||||||
| 18 Grape.Util.Lazy | ||||||||||||||||||||||||||||||||||||||||
| 19 Grape.Validations.ParamsScope | ||||||||||||||||||||||||||||||||||||||||
| 20 Grape.Util | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Grape.ContentTypes | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Grape.DSL | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 Grape.DryTypes | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 Grape.Exceptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Grape.Middleware.Formatter | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Grape.Middleware.Versioner.Header | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 Grape.Namespace | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Grape.Router.BaseRoute | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Grape.Router.Pattern | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Grape.Router.Pattern.Path | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Grape.Util.MediaType | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Grape.Validations.ParamsDocumentation | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 Grape.Validations.Types | 5 | |||||||||||||||||||||||||||||||||||||||
| 34 Grape | 1 | 5 | 3 | |||||||||||||||||||||||||||||||||||||
| 35 Grape.Middleware | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Grape.Validations | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Grape.Middleware.Auth | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 Grape.Middleware.Versioner | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 Grape.Validations.Validators | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 Grape.API | 11 | 2 | 1 |
20→18 Grape.Util uses Grape.Util.Lazy✕
- Connections
- 1 pair of types, where a type in Grape.Util uses a type in Grape.Util.Lazy.
- The types involved
Grape.Util.EndpointConfiguration→Grape.Util.Lazy.Value
- Direction
- Grape.Util uses Grape.Util.Lazy, so a change to Grape.Util.Lazy can break Grape.Util, while a change to Grape.Util can't break Grape.Util.Lazy.
- Position
- Below the diagonal: Grape.Util uses a module listed above it, which is the healthy direction.
21→20 Grape.ContentTypes uses Grape.Util✕
- Connections
- 2 pairs of types, where a type in Grape.ContentTypes uses a type in Grape.Util.
- The types involved
Grape.ContentTypes.LookupCache→Grape.Util.CacheGrape.ContentTypes.MimeTypesCache→Grape.Util.Cache
- Direction
- Grape.ContentTypes uses Grape.Util, so a change to Grape.Util can break Grape.ContentTypes, while a change to Grape.ContentTypes can't break Grape.Util.
- Position
- Below the diagonal: Grape.ContentTypes uses a module listed above it, which is the healthy direction.
22→15 Grape.DSL uses Grape.ServeStream✕
- Connections
- 1 pair of types, where a type in Grape.DSL uses a type in Grape.ServeStream.
- The types involved
Grape.DSL.InsideRoute→Grape.ServeStream.StreamResponse
- Direction
- Grape.DSL uses Grape.ServeStream, so a change to Grape.ServeStream can break Grape.DSL, while a change to Grape.DSL can't break Grape.ServeStream.
- Position
- Below the diagonal: Grape.DSL uses a module listed above it, which is the healthy direction.
22→20 Grape.DSL uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.DSL uses a type in Grape.Util.
- The types involved
Grape.DSL.Settings→Grape.Util.InheritableSetting
- Direction
- Grape.DSL uses Grape.Util, so a change to Grape.Util can break Grape.DSL, while a change to Grape.DSL can't break Grape.Util.
- Position
- Below the diagonal: Grape.DSL uses a module listed above it, which is the healthy direction.
23→20 Grape.DryTypes uses Grape.Util✕
- Connections
- 2 pairs of types, where a type in Grape.DryTypes uses a type in Grape.Util.
- The types involved
Grape.DryTypes.ParamsCache→Grape.Util.CacheGrape.DryTypes.StrictCache→Grape.Util.Cache
- Direction
- Grape.DryTypes uses Grape.Util, so a change to Grape.Util can break Grape.DryTypes, while a change to Grape.DryTypes can't break Grape.Util.
- Position
- Below the diagonal: Grape.DryTypes uses a module listed above it, which is the healthy direction.
24→20 Grape.Exceptions uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Exceptions uses a type in Grape.Util.
- The types involved
Grape.Exceptions.Base→Grape.Util.Translation
- Direction
- Grape.Exceptions uses Grape.Util, so a change to Grape.Util can break Grape.Exceptions, while a change to Grape.Exceptions can't break Grape.Util.
- Position
- Below the diagonal: Grape.Exceptions uses a module listed above it, which is the healthy direction.
25→20 Grape.Middleware.Formatter uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Middleware.Formatter uses a type in Grape.Util.
- The types involved
Grape.Middleware.Formatter.FormatForAcceptCache→Grape.Util.Cache
- Direction
- Grape.Middleware.Formatter uses Grape.Util, so a change to Grape.Util can break Grape.Middleware.Formatter, while a change to Grape.Middleware.Formatter can't break Grape.Util.
- Position
- Below the diagonal: Grape.Middleware.Formatter uses a module listed above it, which is the healthy direction.
26→20 Grape.Middleware.Versioner.Header uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Middleware.Versioner.Header uses a type in Grape.Util.
- The types involved
Grape.Middleware.Versioner.Header.MediaTypeForAcceptCache→Grape.Util.Cache
- Direction
- Grape.Middleware.Versioner.Header uses Grape.Util, so a change to Grape.Util can break Grape.Middleware.Versioner.Header, while a change to Grape.Middleware.Versioner.Header can't break Grape.Util.
- Position
- Below the diagonal: Grape.Middleware.Versioner.Header uses a module listed above it, which is the healthy direction.
27→20 Grape.Namespace uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Namespace uses a type in Grape.Util.
- The types involved
Grape.Namespace.JoinedSpaceCache→Grape.Util.Cache
- Direction
- Grape.Namespace uses Grape.Util, so a change to Grape.Util can break Grape.Namespace, while a change to Grape.Namespace can't break Grape.Util.
- Position
- Below the diagonal: Grape.Namespace uses a module listed above it, which is the healthy direction.
28→20 Grape.Router.BaseRoute uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Router.BaseRoute uses a type in Grape.Util.
- The types involved
Grape.Router.BaseRoute.CaptureIndexCache→Grape.Util.Cache
- Direction
- Grape.Router.BaseRoute uses Grape.Util, so a change to Grape.Util can break Grape.Router.BaseRoute, while a change to Grape.Router.BaseRoute can't break Grape.Util.
- Position
- Below the diagonal: Grape.Router.BaseRoute uses a module listed above it, which is the healthy direction.
29→20 Grape.Router.Pattern uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Router.Pattern uses a type in Grape.Util.
- The types involved
Grape.Router.Pattern.PatternCache→Grape.Util.Cache
- Direction
- Grape.Router.Pattern uses Grape.Util, so a change to Grape.Util can break Grape.Router.Pattern, while a change to Grape.Router.Pattern can't break Grape.Util.
- Position
- Below the diagonal: Grape.Router.Pattern uses a module listed above it, which is the healthy direction.
30→20 Grape.Router.Pattern.Path uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Router.Pattern.Path uses a type in Grape.Util.
- The types involved
Grape.Router.Pattern.Path.PartsCache→Grape.Util.Cache
- Direction
- Grape.Router.Pattern.Path uses Grape.Util, so a change to Grape.Util can break Grape.Router.Pattern.Path, while a change to Grape.Router.Pattern.Path can't break Grape.Util.
- Position
- Below the diagonal: Grape.Router.Pattern.Path uses a module listed above it, which is the healthy direction.
31→20 Grape.Util.MediaType uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Util.MediaType uses a type in Grape.Util.
- The types involved
Grape.Util.MediaType.VendorVersionHeaderRegexCache→Grape.Util.Cache
- Direction
- Grape.Util.MediaType uses Grape.Util, so a change to Grape.Util can break Grape.Util.MediaType, while a change to Grape.Util.MediaType can't break Grape.Util.
- Position
- Below the diagonal: Grape.Util.MediaType uses a module listed above it, which is the healthy direction.
32→20 Grape.Validations.ParamsDocumentation uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Validations.ParamsDocumentation uses a type in Grape.Util.
- The types involved
Grape.Validations.ParamsDocumentation.TypeCache→Grape.Util.Cache
- Direction
- Grape.Validations.ParamsDocumentation uses Grape.Util, so a change to Grape.Util can break Grape.Validations.ParamsDocumentation, while a change to Grape.Validations.ParamsDocumentation can't break Grape.Util.
- Position
- Below the diagonal: Grape.Validations.ParamsDocumentation uses a module listed above it, which is the healthy direction.
33→20 Grape.Validations.Types uses Grape.Util✕
- Connections
- 5 pairs of types, where a type in Grape.Validations.Types uses a type in Grape.Util.
- The types involved
Grape.Validations.Types.CoercerCache→Grape.Util.CacheGrape.Validations.Types.CustomTypeCoercer→Grape.Util.FreezeOnNewGrape.Validations.Types.DryTypeCoercer→Grape.Util.FreezeOnNewGrape.Validations.Types.MultipleTypeCoercer→Grape.Util.FreezeOnNewGrape.Validations.Types.VariantCollectionCoercer→Grape.Util.FreezeOnNew
- Direction
- Grape.Validations.Types uses Grape.Util, so a change to Grape.Util can break Grape.Validations.Types, while a change to Grape.Validations.Types can't break Grape.Util.
- Position
- Below the diagonal: Grape.Validations.Types uses a module listed above it, which is the healthy direction.
34→4 Grape uses Grape.Endpoint✕
- Connections
- 1 pair of types, where a type in Grape uses a type in Grape.Endpoint.
- The types involved
Grape.Endpoint→Grape.Endpoint.State
- Direction
- Grape uses Grape.Endpoint, so a change to Grape.Endpoint can break Grape, while a change to Grape can't break Grape.Endpoint.
- Position
- Below the diagonal: Grape uses a module listed above it, which is the healthy direction.
34→20 Grape uses Grape.Util✕
- Connections
- 5 pairs of types, where a type in Grape uses a type in Grape.Util.
- The types involved
Grape.ErrorFormatter→Grape.Util.RegistryGrape.Formatter→Grape.Util.RegistryGrape.ParamsBuilder→Grape.Util.RegistryGrape.Parser→Grape.Util.RegistryGrape.Validations→Grape.Util.Registry
- Direction
- Grape uses Grape.Util, so a change to Grape.Util can break Grape, while a change to Grape can't break Grape.Util.
- Position
- Below the diagonal: Grape uses a module listed above it, which is the healthy direction.
34→22 Grape uses Grape.DSL✕
- Connections
- 3 pairs of types, where a type in Grape uses a type in Grape.DSL.
- The types involved
Grape.Endpoint→Grape.DSL.HeadersGrape.Endpoint→Grape.DSL.InsideRouteGrape.Endpoint→Grape.DSL.Settings
- Direction
- Grape uses Grape.DSL, so a change to Grape.DSL can break Grape, while a change to Grape can't break Grape.DSL.
- Position
- Below the diagonal: Grape uses a module listed above it, which is the healthy direction.
35→20 Grape.Middleware uses Grape.Util✕
- Connections
- 1 pair of types, where a type in Grape.Middleware uses a type in Grape.Util.
- The types involved
Grape.Middleware.Versioner→Grape.Util.Registry
- Direction
- Grape.Middleware uses Grape.Util, so a change to Grape.Util can break Grape.Middleware, while a change to Grape.Middleware can't break Grape.Util.
- Position
- Below the diagonal: Grape.Middleware uses a module listed above it, which is the healthy direction.
35→22 Grape.Middleware uses Grape.DSL✕
- Connections
- 1 pair of types, where a type in Grape.Middleware uses a type in Grape.DSL.
- The types involved
Grape.Middleware.Base→Grape.DSL.Headers
- Direction
- Grape.Middleware uses Grape.DSL, so a change to Grape.DSL can break Grape.Middleware, while a change to Grape.Middleware can't break Grape.DSL.
- Position
- Below the diagonal: Grape.Middleware uses a module listed above it, which is the healthy direction.
36→20 Grape.Validations uses Grape.Util✕
- Connections
- 2 pairs of types, where a type in Grape.Validations uses a type in Grape.Util.
- The types involved
Grape.Validations.OneofCollector→Grape.Util.InheritableSettingGrape.Validations.UndeclaredParams→Grape.Util.FreezeOnNew
- Direction
- Grape.Validations uses Grape.Util, so a change to Grape.Util can break Grape.Validations, while a change to Grape.Validations can't break Grape.Util.
- Position
- Below the diagonal: Grape.Validations uses a module listed above it, which is the healthy direction.
36→22 Grape.Validations uses Grape.DSL✕
- Connections
- 1 pair of types, where a type in Grape.Validations uses a type in Grape.DSL.
- The types involved
Grape.Validations.ParamsScope→Grape.DSL.Parameters
- Direction
- Grape.Validations uses Grape.DSL, so a change to Grape.DSL can break Grape.Validations, while a change to Grape.Validations can't break Grape.DSL.
- Position
- Below the diagonal: Grape.Validations uses a module listed above it, which is the healthy direction.
37→35 Grape.Middleware.Auth uses Grape.Middleware✕
- Connections
- 1 pair of types, where a type in Grape.Middleware.Auth uses a type in Grape.Middleware.
- The types involved
Grape.Middleware.Auth.Base→Grape.Middleware.Base
- Direction
- Grape.Middleware.Auth uses Grape.Middleware, so a change to Grape.Middleware can break Grape.Middleware.Auth, while a change to Grape.Middleware.Auth can't break Grape.Middleware.
- Position
- Below the diagonal: Grape.Middleware.Auth uses a module listed above it, which is the healthy direction.
38→35 Grape.Middleware.Versioner uses Grape.Middleware✕
- Connections
- 2 pairs of types, where a type in Grape.Middleware.Versioner uses a type in Grape.Middleware.
- The types involved
Grape.Middleware.Versioner.Base→Grape.Middleware.BaseGrape.Middleware.Versioner.Base→Grape.Middleware.PrecomputedContentTypes
- Direction
- Grape.Middleware.Versioner uses Grape.Middleware, so a change to Grape.Middleware can break Grape.Middleware.Versioner, while a change to Grape.Middleware.Versioner can't break Grape.Middleware.
- Position
- Below the diagonal: Grape.Middleware.Versioner uses a module listed above it, which is the healthy direction.
39→20 Grape.Validations.Validators uses Grape.Util✕
- Connections
- 3 pairs of types, where a type in Grape.Validations.Validators uses a type in Grape.Util.
- The types involved
Grape.Validations.Validators.Base→Grape.Util.FreezeOnNewGrape.Validations.Validators.Base→Grape.Util.TranslationGrape.Validations.Validators.ContractScopeValidator→Grape.Util.FreezeOnNew
- Direction
- Grape.Validations.Validators uses Grape.Util, so a change to Grape.Util can break Grape.Validations.Validators, while a change to Grape.Validations.Validators can't break Grape.Util.
- Position
- Below the diagonal: Grape.Validations.Validators uses a module listed above it, which is the healthy direction.
39→36 Grape.Validations.Validators uses Grape.Validations✕
- Connections
- 1 pair of types, where a type in Grape.Validations.Validators uses a type in Grape.Validations.
- The types involved
Grape.Validations.Validators.Base→Grape.Validations.SharedOptions
- Direction
- Grape.Validations.Validators uses Grape.Validations, so a change to Grape.Validations can break Grape.Validations.Validators, while a change to Grape.Validations.Validators can't break Grape.Validations.
- Position
- Below the diagonal: Grape.Validations.Validators uses a module listed above it, which is the healthy direction.
40→22 Grape.API uses Grape.DSL✕
- Connections
- 11 pairs of types, where a type in Grape.API uses a type in Grape.DSL.
- The types involved
Grape.API.Instance→Grape.DSL.CallbacksGrape.API.Instance→Grape.DSL.DescGrape.API.Instance→Grape.DSL.HelpersGrape.API.Instance→Grape.DSL.LoggerGrape.API.Instance→Grape.DSL.MiddlewareGrape.API.Instance→Grape.DSL.MountingGrape.API.Instance→Grape.DSL.RequestResponseGrape.API.Instance→Grape.DSL.RoutingGrape.API.Instance→Grape.DSL.SettingsGrape.API.Instance→Grape.DSL.ValidationsGrape.API.Instance→Grape.DSL.Versioning
- Direction
- Grape.API uses Grape.DSL, so a change to Grape.DSL can break Grape.API, while a change to Grape.API can't break Grape.DSL.
- Position
- Below the diagonal: Grape.API uses a module listed above it, which is the healthy direction.
40→34 Grape.API uses Grape✕
- Connections
- 2 pairs of types, where a type in Grape.API uses a type in Grape.
- The types involved
Grape.API.Instance→Grape.MountableGrape.API.Instance→Grape.Router
- Direction
- Grape.API uses Grape, so a change to Grape can break Grape.API, while a change to Grape.API can't break Grape.
- Position
- Below the diagonal: Grape.API uses a module listed above it, which is the healthy direction.
40→37 Grape.API uses Grape.Middleware.Auth✕
- Connections
- 1 pair of types, where a type in Grape.API uses a type in Grape.Middleware.Auth.
- The types involved
Grape.API.Instance→Grape.Middleware.Auth.DSL
- Direction
- Grape.API uses Grape.Middleware.Auth, so a change to Grape.Middleware.Auth can break Grape.API, while a change to Grape.API can't break Grape.Middleware.Auth.
- Position
- Below the diagonal: Grape.API uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 25 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 finding(s) in DR & Backup; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with config.ru; Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with config.ru. | +6.4 pts | Low | ADR Quality |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +3.7 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +3.7 pts | Low | Bus Factor |
| Resolve the 1 finding(s) in DR & Backup. | +6.7 pts | Medium | DR & Backup |
| Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing. | +6.0 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.8 pts | Medium | Architecture documentation |
| 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.7 pts | Medium | Deployment & Rollback |
| 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. | +1.9 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| lib/grape/endpoint.rb | 7.0 | Mixed | God Classes: TooManyMethods: Endpoint |
| lib/grape/validations/params_scope.rb | 7.0 | Mixed | God Classes: TooManyMethods: ParamsScope |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| spec/grape/api_spec.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| lib/grape/util/inheritable_setting.rb | 8.5 | Near-clean | God Classes: TooManyMethods: InheritableSetting |
| lib/grape/middleware/error.rb | 8.5 | Near-clean | God Classes: TooManyMethods: Error |
| lib/grape/router.rb | 8.5 | Near-clean | God Classes: TooManyMethods: Router |
| lib/grape/router/route.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Route (LCOM4 5) |
| lib/grape/validations/undeclared_params.rb | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: UndeclaredParams (LCOM4 4) |
| lib/grape/validations/validators/presence_validator.rb | 8.5 | Near-clean | Change Coupling: Change coupling: presence_validator.rb ↔ regexp_validator.rb |
| lib/grape/middleware/versioner/accept_version_header.rb | 8.5 | Near-clean | Change Coupling: Change coupling: accept_version_header.rb ↔ header.rb |
| lib/grape/middleware/versioner/header.rb | 8.5 | Near-clean | Change Coupling: Change coupling: header.rb ↔ param.rb |
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 48 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 48 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, 59 of 69 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`coverallsapp/github-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rb), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (11238 LoC, 586 module-visible types across 24 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `lib/grape/dsl/routing.rb`, `lib/grape/validations/params_scope.rb` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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 DockerCompose (docker-compose.yml). the app booted but exposed no published HTTP port — nothing to crawl (publish the web service's port to unlock runtime evidence).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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. 178 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with inheritable_setting.rb, endpoint.rb, params_scope.rb. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 11,863) are in a reported copy.
D6 · Cohesion (LCOM4)
4 of 42 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with route.rb, params_scope.rb, endpoint.rb. — One of this dimension's main actionable groups (4 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Ruby (RSpec: repository root, 168 spec files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated direct gem(s), 0 pinning defect(s). 30 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 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 15 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 15 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.
D16 · Bus Factor
40 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/grape/util/inheritable_setting.rb. Counted over 46 of the 204 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 11863 LoC (0.0/KLoC) → score 10.0. 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 1 TodoComment finding(s) in Explicit Debt — start with api_spec.rb. — One of this dimension's main actionable groups (1 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with config.ru. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
25 finding(s): 0 critical, 19 high, 6 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `REDACTED` (lines 13–20), `lib/grape/dsl/routing.rb` (line 78), `lib/grape/validations/params_scope.rb` (line 424, line 440) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares. No known-vulnerable gem among the 29 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 30 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.
D31 · IaC & Container Security
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 46 of the 204 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: presence_validator.rb↔regexp_validator.rb 61%; accept_version_header.rb↔header.rb 50%; header.rb↔param.rb 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with presence_validator.rb, accept_version_header.rb, header.rb. — One of this dimension's main actionable groups (3 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious. No known-vulnerable gem among the 29 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 30 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 30 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
AX2 · Stateful singletons
- `PostPut` serves requests (Grape APIs run on a server thread per request — Puma's default — and every thread shares the class variables, globals and constants they write) but updates that shared state with a read-modify-write outside any lock (PostPut.rang; e.g. `PostPut.rang` in `a route block` at line 13). Two requests that interleave between the read and the write lose one update. — benchmark/grape_on_rack/api/post_put.rb:4
- `Endpoint` serves requests (a Rack app is one instance the server shares across every request thread, so its instance variables are shared along with its class variables and globals) but updates that shared state with a read-modify-write outside any lock (@state; e.g. `@state` in `options_route_enabled=` at line 41). Two requests that interleave between the read and the write lose one update. — lib/grape/endpoint.rb:8
- `Base` serves requests (a Rack app is one instance the server shares across every request thread, so its instance variables are shared along with its class variables and globals) but updates that shared state with a read-modify-write outside any lock (@app_response; e.g. `@app_response` in `response` at line 66). Two requests that interleave between the read and the write lose one update. — lib/grape/middleware/base.rb:5
What to do
- Ruby: keep class variables, globals and constants out of request handling — move counters and caches into a store built for concurrent access (the database, Rails.cache, Redis) or a Concurrent::AtomicFixnum / Concurrent::Map — or update them inside a shared Mutex's `synchronize` block; a Rack app's own instance variables are shared the same way.
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
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
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (Rails' /up (rails/health#show) or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — 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.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
PF1 · Benchmark discipline
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `initialize` is public, takes a document from its caller (line 32) and hands it to `declared_entries`, which walks `key` as a `Hash` and calls itself at line 69 (`self.declared_entries`) with a piece of `key` — and nowhere in `declared_entries` 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 `declared_entries` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/grape/validations/undeclared_params.rb:69
- `initialize` is public, takes a document from its caller (line 32) and hands it to `contract_entry`, which walks `spec` as a `Hash` and calls itself at line 79 (`self.contract_entry`) with a piece of `spec` — and nowhere in `contract_entry` 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 `contract_entry` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/grape/validations/undeclared_params.rb:79
- `validate_param!` is public, takes a document from its caller (line 20) and hands it to `copy_containers`, which walks `value` as a `Hash` and calls itself at line 47 (`self.copy_containers`) with a piece of `value` (and at line 50) — and nowhere in `copy_containers` 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 `copy_containers` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/grape/validations/validators/oneof_validator.rb:47
- `deep_freeze` is public and takes `obj` — which it walks as a `Hash` — from its caller, and it calls itself at line 19 (`self.deep_freeze`) with a piece of `obj` (and at line 20, line 24) — and nowhere in `deep_freeze` 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 `deep_freeze` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/grape/util/deep_freeze.rb:19
- `call` is public, takes a document from its caller (line 7) and hands it to `serialize`, which walks `object` as a `Hash` and calls itself at line 25 (`self.serialize`) with a piece of `object` — and nowhere in `serialize` 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 `serialize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — lib/grape/formatter/serializable_hash.rb:25
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
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 178 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 | 73% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82% | Strong | Solid. |
| Maturity | 55% | Adequate — gated by D16, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43% | Weak — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 95% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 4 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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 — the app booted but exposed no published HTTP port — nothing to crawl (publish the web service's port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (an ActiveRecord model, Sequel, pg, mysql2, Mongo) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (ActiveRecord, Sequel, pg, mysql2, mongo, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~32684 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.
- 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.
- D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
- 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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (20 value object(s))
- 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
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Ruby source (service entry point: lib/grape/railtie.rb:25 (< Grape::API))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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: 178 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's 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.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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)
Critical — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 34 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: InheritableSetting lib/grape/util/inheritable_setting.rb:20
- TooManyMethods: Endpoint lib/grape/endpoint.rb:8
- TooManyMethods: ParamsScope lib/grape/validations/params_scope.rb:5
- TooManyMethods: Error lib/grape/middleware/error.rb:5
- TooManyMethods: Router lib/grape/router.rb:4
- Recursive walk over a caller-supplied document has no depth cap lib/grape/validations/undeclared_params.rb:69
- Recursive walk over a caller-supplied document has no depth cap lib/grape/validations/undeclared_params.rb:79
- Recursive walk over a caller-supplied document has no depth cap lib/grape/validations/validators/oneof_validator.rb:47
- Recursive walk over a caller-supplied document has no depth cap lib/grape/util/deep_freeze.rb:19
- Recursive walk over a caller-supplied document has no depth cap lib/grape/formatter/serializable_hash.rb:25
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: Route (LCOM4 5) lib/grape/router/route.rb:5
- Low cohesion: ParamsScope (LCOM4 5) lib/grape/validations/params_scope.rb:5
- Low cohesion: Endpoint (LCOM4 4) lib/grape/endpoint.rb:8
- Low cohesion: UndeclaredParams (LCOM4 4) lib/grape/validations/undeclared_params.rb:15
- Stateful handler: PostPut benchmark/grape_on_rack/api/post_put.rb:4
- Stateful handler: Endpoint lib/grape/endpoint.rb:8
- Stateful handler: Base lib/grape/middleware/base.rb:5
- Change coupling: presence_validator.rb ↔ regexp_validator.rb lib/grape/validations/validators/presence_validator.rb:1
- Change coupling: accept_version_header.rb ↔ header.rb lib/grape/middleware/versioner/accept_version_header.rb:1
- Change coupling: header.rb ↔ param.rb lib/grape/middleware/versioner/header.rb:1
- TodoComment spec/grape/api_spec.rb:2700
- REDACTED
- REDACTED
- Coverage collected but not gated
- No DR/backup evidence
Minor — 14 finding(s)
- Duplicated predicate REDACTED:315
- Duplicated predicate lib/grape/validations/validators/except_values_validator.rb:26
- Duplicated predicate lib/grape/error_formatter/base.rb:17
- Duplicated predicate lib/grape/error_formatter/base.rb:18
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found benchmark/grape_on_rack/config.ru:1
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI build step not evidenced
- No SAST REDACTED:4
- 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-50a2b46072104f68940257c7c4b7bf1f/history.json --exit-code 0 --source . | 1 | 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-50a2b46072104f68940257c7c4b7bf1f/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 . | 25 | artifacts/raw/semgrep.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `lib/grape/dsl/routing.rb`, `lib/grape/validations/params_scope.rb` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | — |