Executive summary
apicollective/apibuilder is rated At risk because critical security findings are open. Its score is held back in part because we found no recorded design decisions and no architecture document or diagram. It scores 40 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Maturity, at 31, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Having someone learn and document the 87 files no active contributor knows comes next, also worth about 8. Raising Maturity to 62 would lift the score to about 47.
Eight passwords or keys in the code's history and three in the code are open to anyone who can read the repository. Four places in the code run text as code, which an attacker could use, and three known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key, replacing text run as code with direct calls and updating the vulnerable packages would close these risks. Pinning each tool to an exact version would fix the three pipeline tools referenced by a changeable name, and fixing the weaknesses the scanner points to would deal with the three security weaknesses in the code. The two pages or frames without a title need a descriptive title.
The product code is 41,807 lines, about €48,000 to rebuild.
If Maturity rose from 31 to 62, the lowest score rated Strong, the score would rise from 40 to about 47.
New since the last survey: 2 findings
- REDACTED Scanning · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €48,000 · Estimate
| Cost to rebuild | €16,000 to €79,000, for 263 to 835 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.7 at a score of 40. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 41,807 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 io.apibuilder.api.v0.models.AppSortBy | 2 io.apibuilder.avro.ApiBuilder | 3 io.apibuilder.common.v0.models | 4 lib.Emails.Context | 5 lib.query | 6 util.BasicAuthorization | 7 db.Authorization | 8 io.apibuilder.api.json.v0.models | 9 io.apibuilder.task.v0.models | 10 io.apibuilder.api.json.v0.models.ParameterLocation | 11 io.apibuilder.api.v0 | 12 io.apibuilder.spec.v0.models | 13 db.generators | 14 models | 15 lib | 16 lib.Primitives | 17 db.generated | 18 db | 19 controllers | 20 io.apibuilder.api.v0.models | 21 io.apibuilder.generator.v0.models | 22 io.apibuilder.avro | 23 io.apibuilder.avro.SchemaType | 24 builder.api_json.templates | 25 core | 26 db.generated.generators | 27 io.apibuilder.api.json.v0.Bindables | 28 io.apibuilder.api.v0.Client | 29 io.apibuilder.generator.v0.Client | 30 io.apibuilder.spec.v0.mock | 31 io.apibuilder.swagger.translators | 32 builder.api_json | 33 io.apibuilder.generator.v0.mock | 34 builder.api_json.InternalDatatype | 35 builder.api_json.ServiceBuilder | 36 builder | 37 db.generated.ApplicationMovesTable | 38 io.apibuilder.swagger | 39 util | 40 processor |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 io.apibuilder.api.v0.models.AppSortBy | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 2 io.apibuilder.avro.ApiBuilder | 6 | |||||||||||||||||||||||||||||||||||||||
| 3 io.apibuilder.common.v0.models | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 lib.Emails.Context | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 lib.query | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 util.BasicAuthorization | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 7 db.Authorization | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 8 io.apibuilder.api.json.v0.models | 5 | 36 | ||||||||||||||||||||||||||||||||||||||
| 9 io.apibuilder.task.v0.models | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 io.apibuilder.api.json.v0.models.ParameterLocation | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 io.apibuilder.api.v0 | 3 | 1 | 1 | 1 | 1 | 1 | 13 | 27 | 38 | 1 | 36 | |||||||||||||||||||||||||||||
| 12 io.apibuilder.spec.v0.models | 6 | 3 | 63 | 3 | 35 | |||||||||||||||||||||||||||||||||||
| 13 db.generators | 1 | 2 | 2 | 3 | 1 | 9 | ||||||||||||||||||||||||||||||||||
| 14 models | 2 | 1 | 2 | 3 | 2 | 2 | 15 | 16 | 5 | |||||||||||||||||||||||||||||||
| 15 lib | 2 | 1 | 1 | 2 | 13 | 1 | 3 | 3 | 2 | 6 | 2 | 12 | 4 | 58 | 1 | 1 | ||||||||||||||||||||||||
| 16 lib.Primitives | 12 | |||||||||||||||||||||||||||||||||||||||
| 17 db.generated | 2 | 44 | 4 | 2 | 2 | 22 | 38 | 104 | ||||||||||||||||||||||||||||||||
| 18 db | 3 | 4 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 17 | 7 | 44 | 75 | ||||||||||||||||||||||||||
| 19 controllers | 4 | 3 | 4 | 1 | 3 | 2 | 3 | 16 | 15 | 55 | ||||||||||||||||||||||||||||||
| 20 io.apibuilder.api.v0.models | 6 | 19 | 2 | 3 | 7 | 2 | 1 | 1 | 3 | 3 | 50 | |||||||||||||||||||||||||||||
| 21 io.apibuilder.generator.v0.models | 1 | 2 | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||
| 22 io.apibuilder.avro | 4 | 3 | 4 | 2 | 1 | 6 | ||||||||||||||||||||||||||||||||||
| 23 io.apibuilder.avro.SchemaType | 14 | |||||||||||||||||||||||||||||||||||||||
| 24 builder.api_json.templates | 2 | 25 | 2 | 19 | ||||||||||||||||||||||||||||||||||||
| 25 core | 2 | 2 | 2 | 15 | ||||||||||||||||||||||||||||||||||||
| 26 db.generated.generators | 4 | 2 | 2 | 2 | 2 | 8 | ||||||||||||||||||||||||||||||||||
| 27 io.apibuilder.api.json.v0.Bindables | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 28 io.apibuilder.api.v0.Client | 3 | 1 | 1 | 1 | 1 | 1 | 13 | 24 | 38 | 1 | 35 | |||||||||||||||||||||||||||||
| 29 io.apibuilder.generator.v0.Client | 1 | 2 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 30 io.apibuilder.spec.v0.mock | 2 | 1 | 17 | 5 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 31 io.apibuilder.swagger.translators | 1 | 8 | 1 | 2 | 1 | 11 | ||||||||||||||||||||||||||||||||||
| 32 builder.api_json | 3 | 8 | 19 | 38 | 16 | 2 | ||||||||||||||||||||||||||||||||||
| 33 io.apibuilder.generator.v0.mock | 2 | 1 | 4 | 1 | 8 | 6 | 1 | |||||||||||||||||||||||||||||||||
| 34 builder.api_json.InternalDatatype | 6 | 3 | ||||||||||||||||||||||||||||||||||||||
| 35 builder.api_json.ServiceBuilder | 1 | 15 | 5 | 5 | 20 | |||||||||||||||||||||||||||||||||||
| 36 builder | 2 | 5 | 3 | 4 | 3 | 1 | 8 | 2 | 1 | |||||||||||||||||||||||||||||||
| 37 db.generated.ApplicationMovesTable | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 io.apibuilder.swagger | 9 | 2 | 2 | 3 | 3 | 2 | 13 | 1 | 2 | |||||||||||||||||||||||||||||||
| 39 util | 2 | 1 | 2 | 1 | 2 | 1 | 3 | 1 | 4 | 2 | 1 | 14 | 2 | |||||||||||||||||||||||||||
| 40 processor | 1 | 1 | 6 | 1 | 1 | 2 | 16 | 6 | 3 | 1 | 21 | 1 | 3 |
1→20 io.apibuilder.api.v0.models.AppSortBy uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 5 pairs of types, where a type in io.apibuilder.api.v0.models.AppSortBy uses a type in io.apibuilder.api.v0.models.
- The types involved
io.apibuilder.api.v0.models.AppSortBy.CreatedAt→io.apibuilder.api.v0.models.AppSortByio.apibuilder.api.v0.models.AppSortBy.Name→io.apibuilder.api.v0.models.AppSortByio.apibuilder.api.v0.models.AppSortBy.UNDEFINED→io.apibuilder.api.v0.models.AppSortByio.apibuilder.api.v0.models.AppSortBy.UpdatedAt→io.apibuilder.api.v0.models.AppSortByio.apibuilder.api.v0.models.AppSortBy.Visibility→io.apibuilder.api.v0.models.AppSortBy
- Direction
- io.apibuilder.api.v0.models.AppSortBy uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break io.apibuilder.api.v0.models.AppSortBy, while a change to io.apibuilder.api.v0.models.AppSortBy can't break io.apibuilder.api.v0.models.
- 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.
1→23 io.apibuilder.api.v0.models.AppSortBy uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.models.AppSortBy uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.api.v0.models.AppSortBy.UNDEFINED→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.api.v0.models.AppSortBy uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.api.v0.models.AppSortBy, while a change to io.apibuilder.api.v0.models.AppSortBy can't break io.apibuilder.avro.SchemaType.
- 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.
2→23 io.apibuilder.avro.ApiBuilder uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 6 pairs of types, where a type in io.apibuilder.avro.ApiBuilder uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.avro.ApiBuilder.SimpleType→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.avro.ApiBuilder.SimpleType→io.apibuilder.avro.SchemaType.Stringio.apibuilder.avro.ApiBuilder.Type→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.avro.ApiBuilder.Type→io.apibuilder.avro.SchemaType.Stringio.apibuilder.avro.ApiBuilder.UnionType→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.avro.ApiBuilder.UnionType→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.avro.ApiBuilder uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.avro.ApiBuilder, while a change to io.apibuilder.avro.ApiBuilder can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→23 io.apibuilder.common.v0.models uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.common.v0.models uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.common.v0.models.Healthcheck→io.apibuilder.avro.SchemaType.Stringio.apibuilder.common.v0.models.Reference→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.common.v0.models uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.common.v0.models, while a change to io.apibuilder.common.v0.models can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→18 lib.Emails.Context uses db part of a loop✕
- Connections
- 1 pair of types, where a type in lib.Emails.Context uses a type in db.
- The types involved
lib.Emails.Context.Application→db.InternalApplication
- Direction
- lib.Emails.Context uses db, so a change to db can break lib.Emails.Context, while a change to lib.Emails.Context can't break db.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→23 lib.query uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 2 pairs of types, where a type in lib.query uses a type in io.apibuilder.avro.SchemaType.
- The types involved
lib.query.Query→io.apibuilder.avro.SchemaType.Stringlib.query.QueryParser→io.apibuilder.avro.SchemaType.String
- Direction
- lib.query uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break lib.query, while a change to lib.query can't break io.apibuilder.avro.SchemaType.
- 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→18 util.BasicAuthorization uses db part of a loop✕
- Connections
- 3 pairs of types, where a type in util.BasicAuthorization uses a type in db.
- The types involved
util.BasicAuthorization.Session→db.Authorizationutil.BasicAuthorization.Token→db.Authorizationutil.BasicAuthorization.User→db.Authorization
- Direction
- util.BasicAuthorization uses db, so a change to db can break util.BasicAuthorization, while a change to util.BasicAuthorization can't break db.
- 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→23 util.BasicAuthorization uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 3 pairs of types, where a type in util.BasicAuthorization uses a type in io.apibuilder.avro.SchemaType.
- The types involved
util.BasicAuthorization.Session→io.apibuilder.avro.SchemaType.Stringutil.BasicAuthorization.Token→io.apibuilder.avro.SchemaType.Stringutil.BasicAuthorization.User→io.apibuilder.avro.SchemaType.String
- Direction
- util.BasicAuthorization uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break util.BasicAuthorization, while a change to util.BasicAuthorization can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→5 db.Authorization uses lib.query✕
- Connections
- 3 pairs of types, where a type in db.Authorization uses a type in lib.query.
- The types involved
db.Authorization.All→lib.query.Querydb.Authorization.PublicOnly→lib.query.Querydb.Authorization.User→lib.query.Query
- Direction
- db.Authorization uses lib.query, so a change to lib.query can break db.Authorization, while a change to db.Authorization can't break lib.query.
- Position
- Below the diagonal: db.Authorization uses a module listed above it, which is the healthy direction.
7→18 db.Authorization uses db part of a loop✕
- Connections
- 3 pairs of types, where a type in db.Authorization uses a type in db.
- The types involved
db.Authorization.All→db.Authorizationdb.Authorization.PublicOnly→db.Authorizationdb.Authorization.User→db.Authorization
- Direction
- db.Authorization uses db, so a change to db can break db.Authorization, while a change to db.Authorization can't break db.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→23 db.Authorization uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 3 pairs of types, where a type in db.Authorization uses a type in io.apibuilder.avro.SchemaType.
- The types involved
db.Authorization.All→io.apibuilder.avro.SchemaType.Stringdb.Authorization.PublicOnly→io.apibuilder.avro.SchemaType.Stringdb.Authorization.User→io.apibuilder.avro.SchemaType.String
- Direction
- db.Authorization uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break db.Authorization, while a change to db.Authorization can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→2 io.apibuilder.api.json.v0.models uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 5 pairs of types, where a type in io.apibuilder.api.json.v0.models uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
io.apibuilder.api.json.v0.models.Interface→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.api.json.v0.models.Model→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.api.json.v0.models.Union→io.apibuilder.avro.ApiBuilder.UnionTypeio.apibuilder.api.json.v0.models.json→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.api.json.v0.models.json→io.apibuilder.avro.ApiBuilder.UnionType
- Direction
- io.apibuilder.api.json.v0.models uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break io.apibuilder.api.json.v0.models, while a change to io.apibuilder.api.json.v0.models can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: io.apibuilder.api.json.v0.models uses a module listed above it, which is the healthy direction.
8→23 io.apibuilder.api.json.v0.models uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 36 pairs of types, where a type in io.apibuilder.api.json.v0.models uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.api.json.v0.models.Annotation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.ApiJson→io.apibuilder.avro.SchemaType.Enumio.apibuilder.api.json.v0.models.ApiJson→io.apibuilder.avro.SchemaType.Mapio.apibuilder.api.json.v0.models.ApiJson→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.ApiJson→io.apibuilder.avro.SchemaType.Unionio.apibuilder.api.json.v0.models.Attribute→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Body→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Contact→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Deprecation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Enum→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.EnumValue→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Field→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.json.v0.models.Field→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.json.v0.models.Field→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Header→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.json.v0.models.Header→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Import→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Interface→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.License→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Model→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Operation→io.apibuilder.avro.SchemaType.Mapio.apibuilder.api.json.v0.models.Operation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.models.Parameter→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.json.v0.models.Parameter→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.json.v0.models.Parameter→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.api.json.v0.models uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.api.json.v0.models, while a change to io.apibuilder.api.json.v0.models can't break io.apibuilder.avro.SchemaType.
- 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.
9→3 io.apibuilder.task.v0.models uses io.apibuilder.common.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.task.v0.models uses a type in io.apibuilder.common.v0.models.
- The types involved
io.apibuilder.task.v0.models.EmailDataMembershipRequestAccepted→io.apibuilder.common.v0.models.MembershipRole
- Direction
- io.apibuilder.task.v0.models uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break io.apibuilder.task.v0.models, while a change to io.apibuilder.task.v0.models can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: io.apibuilder.task.v0.models uses a module listed above it, which is the healthy direction.
9→23 io.apibuilder.task.v0.models uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 1 pair of types, where a type in io.apibuilder.task.v0.models uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.task.v0.models.EmailDataUndefinedType→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.task.v0.models uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.task.v0.models, while a change to io.apibuilder.task.v0.models can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→8 io.apibuilder.api.json.v0.models.ParameterLocation uses io.apibuilder.api.json.v0.models✕
- Connections
- 5 pairs of types, where a type in io.apibuilder.api.json.v0.models.ParameterLocation uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.api.json.v0.models.ParameterLocation.Form→io.apibuilder.api.json.v0.models.ParameterLocationio.apibuilder.api.json.v0.models.ParameterLocation.Header→io.apibuilder.api.json.v0.models.ParameterLocationio.apibuilder.api.json.v0.models.ParameterLocation.Path→io.apibuilder.api.json.v0.models.ParameterLocationio.apibuilder.api.json.v0.models.ParameterLocation.Query→io.apibuilder.api.json.v0.models.ParameterLocationio.apibuilder.api.json.v0.models.ParameterLocation.UNDEFINED→io.apibuilder.api.json.v0.models.ParameterLocation
- Direction
- io.apibuilder.api.json.v0.models.ParameterLocation uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.api.json.v0.models.ParameterLocation, while a change to io.apibuilder.api.json.v0.models.ParameterLocation can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.json.v0.models.ParameterLocation uses a module listed above it, which is the healthy direction.
10→23 io.apibuilder.api.json.v0.models.ParameterLocation uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.json.v0.models.ParameterLocation uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.api.json.v0.models.ParameterLocation.UNDEFINED→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.api.json.v0.models.ParameterLocation uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.api.json.v0.models.ParameterLocation, while a change to io.apibuilder.api.json.v0.models.ParameterLocation can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→3 io.apibuilder.api.v0 uses io.apibuilder.common.v0.models✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.api.v0 uses a type in io.apibuilder.common.v0.models.
- The types involved
io.apibuilder.api.v0.Healthchecks→io.apibuilder.common.v0.models.Healthcheckio.apibuilder.api.v0.MembershipRequests→io.apibuilder.common.v0.models.MembershipRoleio.apibuilder.api.v0.Memberships→io.apibuilder.common.v0.models.MembershipRole
- Direction
- io.apibuilder.api.v0 uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0 uses a module listed above it, which is the healthy direction.
11→4 io.apibuilder.api.v0 uses lib.Emails.Context✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0 uses a type in lib.Emails.Context.
- The types involved
io.apibuilder.api.v0.Applications→lib.Emails.Context.Application
- Direction
- io.apibuilder.api.v0 uses lib.Emails.Context, so a change to lib.Emails.Context can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break lib.Emails.Context.
- Position
- Below the diagonal: io.apibuilder.api.v0 uses a module listed above it, which is the healthy direction.
11→6 io.apibuilder.api.v0 uses util.BasicAuthorization✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0 uses a type in util.BasicAuthorization.
- The types involved
io.apibuilder.api.v0.Tokens→util.BasicAuthorization.Token
- Direction
- io.apibuilder.api.v0 uses util.BasicAuthorization, so a change to util.BasicAuthorization can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break util.BasicAuthorization.
- Position
- Below the diagonal: io.apibuilder.api.v0 uses a module listed above it, which is the healthy direction.
11→7 io.apibuilder.api.v0 uses db.Authorization✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0 uses a type in db.Authorization.
- The types involved
io.apibuilder.api.v0.Users→db.Authorization.User
- Direction
- io.apibuilder.api.v0 uses db.Authorization, so a change to db.Authorization can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break db.Authorization.
- Position
- Below the diagonal: io.apibuilder.api.v0 uses a module listed above it, which is the healthy direction.
11→8 io.apibuilder.api.v0 uses io.apibuilder.api.json.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0 uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.api.v0.Attributes→io.apibuilder.api.json.v0.models.Attribute
- Direction
- io.apibuilder.api.v0 uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0 uses a module listed above it, which is the healthy direction.
11→15 io.apibuilder.api.v0 uses lib part of a loop✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0 uses a type in lib.
- The types involved
io.apibuilder.api.v0.Validations→lib.Validation
- Direction
- io.apibuilder.api.v0 uses lib, so a change to lib can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break lib.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 io.apibuilder.api.v0 uses lib.Primitives part of a loop✕
- Connections
- 13 pairs of types, where a type in io.apibuilder.api.v0 uses a type in lib.Primitives.
- The types involved
io.apibuilder.api.v0.Applications→lib.Primitives.Unitio.apibuilder.api.v0.Attributes→lib.Primitives.Unitio.apibuilder.api.v0.Domains→lib.Primitives.Unitio.apibuilder.api.v0.EmailVerificationConfirmationForms→lib.Primitives.Unitio.apibuilder.api.v0.GeneratorServices→lib.Primitives.Unitio.apibuilder.api.v0.MembershipRequests→lib.Primitives.Unitio.apibuilder.api.v0.Memberships→lib.Primitives.Unitio.apibuilder.api.v0.Organizations→lib.Primitives.Unitio.apibuilder.api.v0.PasswordResetRequests→lib.Primitives.Unitio.apibuilder.api.v0.Subscriptions→lib.Primitives.Unitio.apibuilder.api.v0.Tokens→lib.Primitives.Unitio.apibuilder.api.v0.Versions→lib.Primitives.Unitio.apibuilder.api.v0.Watches→lib.Primitives.Unit
- Direction
- io.apibuilder.api.v0 uses lib.Primitives, so a change to lib.Primitives can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break lib.Primitives.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 io.apibuilder.api.v0 uses controllers part of a loop✕
- Connections
- 27 pairs of types, where a type in io.apibuilder.api.v0 uses a type in controllers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.api.v0.BatchDownloadApplications→controllers.BatchDownloadApplicationsio.apibuilder.api.v0.BatchVersionsLatest→controllers.BatchVersionsLatestio.apibuilder.api.v0.Client→controllers.Applicationsio.apibuilder.api.v0.Client→controllers.Attributesio.apibuilder.api.v0.Client→controllers.Authenticationsio.apibuilder.api.v0.Client→controllers.BatchDownloadApplicationsio.apibuilder.api.v0.Client→controllers.BatchVersionsLatestio.apibuilder.api.v0.Client→controllers.Changesio.apibuilder.api.v0.Client→controllers.Codeio.apibuilder.api.v0.Client→controllers.Domainsio.apibuilder.api.v0.Client→controllers.EmailVerificationConfirmationFormsio.apibuilder.api.v0.Client→controllers.GeneratorServicesio.apibuilder.api.v0.Client→controllers.GeneratorWithServicesio.apibuilder.api.v0.Client→controllers.Healthchecksio.apibuilder.api.v0.Client→controllers.Itemsio.apibuilder.api.v0.Client→controllers.MembershipRequestsio.apibuilder.api.v0.Client→controllers.Membershipsio.apibuilder.api.v0.Client→controllers.Organizationsio.apibuilder.api.v0.Client→controllers.PasswordResetRequestsio.apibuilder.api.v0.Client→controllers.PasswordResetsio.apibuilder.api.v0.Client→controllers.Subscriptionsio.apibuilder.api.v0.Client→controllers.Tokensio.apibuilder.api.v0.Client→controllers.Usersio.apibuilder.api.v0.Client→controllers.Validationsio.apibuilder.api.v0.Client→controllers.Versions
- Direction
- io.apibuilder.api.v0 uses controllers, so a change to controllers can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break controllers.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→20 io.apibuilder.api.v0 uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 38 pairs of types, where a type in io.apibuilder.api.v0 uses a type in io.apibuilder.api.v0.models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.api.v0.Applications→io.apibuilder.api.v0.models.AppSortByio.apibuilder.api.v0.Applications→io.apibuilder.api.v0.models.ApplicationFormio.apibuilder.api.v0.Applications→io.apibuilder.api.v0.models.ApplicationMetadataVersionio.apibuilder.api.v0.Applications→io.apibuilder.api.v0.models.MoveFormio.apibuilder.api.v0.Applications→io.apibuilder.api.v0.models.SortOrderio.apibuilder.api.v0.Attributes→io.apibuilder.api.v0.models.AttributeFormio.apibuilder.api.v0.Authentications→io.apibuilder.api.v0.models.Authenticationio.apibuilder.api.v0.BatchDownloadApplications→io.apibuilder.api.v0.models.BatchDownloadApplicationsFormio.apibuilder.api.v0.BatchVersionsLatest→io.apibuilder.api.v0.models.BatchVersionsLatestFormio.apibuilder.api.v0.Changes→io.apibuilder.api.v0.models.Changeio.apibuilder.api.v0.Code→io.apibuilder.api.v0.models.CodeFormio.apibuilder.api.v0.Domains→io.apibuilder.api.v0.models.Domainio.apibuilder.api.v0.EmailVerificationConfirmationForms→io.apibuilder.api.v0.models.EmailVerificationConfirmationFormio.apibuilder.api.v0.GeneratorServices→io.apibuilder.api.v0.models.GeneratorServiceio.apibuilder.api.v0.GeneratorServices→io.apibuilder.api.v0.models.GeneratorServiceFormio.apibuilder.api.v0.GeneratorWithServices→io.apibuilder.api.v0.models.GeneratorWithServiceio.apibuilder.api.v0.Items→io.apibuilder.api.v0.models.Itemio.apibuilder.api.v0.MembershipRequests→io.apibuilder.api.v0.models.MembershipRequestio.apibuilder.api.v0.Memberships→io.apibuilder.api.v0.models.Membershipio.apibuilder.api.v0.Organizations→io.apibuilder.api.v0.models.AttributeValueio.apibuilder.api.v0.Organizations→io.apibuilder.api.v0.models.AttributeValueFormio.apibuilder.api.v0.Organizations→io.apibuilder.api.v0.models.Organizationio.apibuilder.api.v0.Organizations→io.apibuilder.api.v0.models.OrganizationFormio.apibuilder.api.v0.PasswordResetRequests→io.apibuilder.api.v0.models.PasswordResetRequestio.apibuilder.api.v0.PasswordResets→io.apibuilder.api.v0.models.Authentication
- Direction
- io.apibuilder.api.v0 uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break io.apibuilder.api.v0.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→21 io.apibuilder.api.v0 uses io.apibuilder.generator.v0.models part of a loop✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0 uses a type in io.apibuilder.generator.v0.models.
- The types involved
io.apibuilder.api.v0.Code→io.apibuilder.generator.v0.models.InvocationForm
- Direction
- io.apibuilder.api.v0 uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break io.apibuilder.generator.v0.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→23 io.apibuilder.api.v0 uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 36 pairs of types, where a type in io.apibuilder.api.v0 uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.api.v0.Applications→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.v0.Applications→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Applications→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Attributes→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Attributes→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Authentications→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.BatchDownloadApplications→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.BatchVersionsLatest→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Changes→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Changes→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Code→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Domains→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.GeneratorServices→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.GeneratorServices→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.GeneratorWithServices→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.GeneratorWithServices→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Items→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Items→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.MembershipRequests→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.MembershipRequests→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Memberships→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Memberships→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Organizations→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Organizations→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.api.v0 uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.api.v0, while a change to io.apibuilder.api.v0 can't break io.apibuilder.avro.SchemaType.
- 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→2 io.apibuilder.spec.v0.models uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 6 pairs of types, where a type in io.apibuilder.spec.v0.models uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
io.apibuilder.spec.v0.models.Interface→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.spec.v0.models.Model→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.spec.v0.models.Union→io.apibuilder.avro.ApiBuilder.UnionTypeio.apibuilder.spec.v0.models.UnionType→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.spec.v0.models.json→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.spec.v0.models.json→io.apibuilder.avro.ApiBuilder.UnionType
- Direction
- io.apibuilder.spec.v0.models uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break io.apibuilder.spec.v0.models, while a change to io.apibuilder.spec.v0.models can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: io.apibuilder.spec.v0.models uses a module listed above it, which is the healthy direction.
12→4 io.apibuilder.spec.v0.models uses lib.Emails.Context✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.spec.v0.models uses a type in lib.Emails.Context.
- The types involved
io.apibuilder.spec.v0.models.Import→lib.Emails.Context.Applicationio.apibuilder.spec.v0.models.Service→lib.Emails.Context.Applicationio.apibuilder.spec.v0.models.json→lib.Emails.Context.Application
- Direction
- io.apibuilder.spec.v0.models uses lib.Emails.Context, so a change to lib.Emails.Context can break io.apibuilder.spec.v0.models, while a change to io.apibuilder.spec.v0.models can't break lib.Emails.Context.
- Position
- Below the diagonal: io.apibuilder.spec.v0.models uses a module listed above it, which is the healthy direction.
12→8 io.apibuilder.spec.v0.models uses io.apibuilder.api.json.v0.models✕
- Connections
- 63 pairs of types, where a type in io.apibuilder.spec.v0.models uses a type in io.apibuilder.api.json.v0.models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.spec.v0.models.Annotation→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Attribute→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Body→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.Body→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Enum→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.Enum→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Enum→io.apibuilder.api.json.v0.models.EnumValueio.apibuilder.spec.v0.models.EnumValue→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.EnumValue→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Field→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.Field→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Header→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.Header→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Import→io.apibuilder.api.json.v0.models.Annotationio.apibuilder.spec.v0.models.Info→io.apibuilder.api.json.v0.models.Contactio.apibuilder.spec.v0.models.Info→io.apibuilder.api.json.v0.models.Licenseio.apibuilder.spec.v0.models.Interface→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.Interface→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Model→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.Model→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Operation→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.models.Operation→io.apibuilder.api.json.v0.models.Bodyio.apibuilder.spec.v0.models.Operation→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.models.Operation→io.apibuilder.api.json.v0.models.Parameterio.apibuilder.spec.v0.models.Operation→io.apibuilder.api.json.v0.models.Response
- Direction
- io.apibuilder.spec.v0.models uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.spec.v0.models, while a change to io.apibuilder.spec.v0.models can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.spec.v0.models uses a module listed above it, which is the healthy direction.
12→20 io.apibuilder.spec.v0.models uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.spec.v0.models uses a type in io.apibuilder.api.v0.models.
- The types involved
io.apibuilder.spec.v0.models.Import→io.apibuilder.api.v0.models.Organizationio.apibuilder.spec.v0.models.Service→io.apibuilder.api.v0.models.Organizationio.apibuilder.spec.v0.models.json→io.apibuilder.api.v0.models.Organization
- Direction
- io.apibuilder.spec.v0.models uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break io.apibuilder.spec.v0.models, while a change to io.apibuilder.spec.v0.models can't break io.apibuilder.api.v0.models.
- 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→23 io.apibuilder.spec.v0.models uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 35 pairs of types, where a type in io.apibuilder.spec.v0.models uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.spec.v0.models.Annotation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Apidoc→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Application→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Attribute→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Body→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Contact→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Deprecation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Enum→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.EnumValue→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Field→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.spec.v0.models.Field→io.apibuilder.avro.SchemaType.Longio.apibuilder.spec.v0.models.Field→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Header→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.spec.v0.models.Header→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Import→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Interface→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.License→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Model→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Operation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Organization→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Parameter→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.spec.v0.models.Parameter→io.apibuilder.avro.SchemaType.Longio.apibuilder.spec.v0.models.Parameter→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Resource→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.models.Response→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.spec.v0.models uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.spec.v0.models, while a change to io.apibuilder.spec.v0.models can't break io.apibuilder.avro.SchemaType.
- 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→12 db.generators uses io.apibuilder.spec.v0.models✕
- Connections
- 1 pair of types, where a type in db.generators uses a type in io.apibuilder.spec.v0.models.
- The types involved
db.generators.InternalGeneratorService→io.apibuilder.spec.v0.models.Service
- Direction
- db.generators uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break db.generators, while a change to db.generators can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: db.generators uses a module listed above it, which is the healthy direction.
13→16 db.generators uses lib.Primitives part of a loop✕
- Connections
- 2 pairs of types, where a type in db.generators uses a type in lib.Primitives.
- The types involved
db.generators.InternalGeneratorServicesDao→lib.Primitives.Unitdb.generators.InternalGeneratorsDao→lib.Primitives.Unit
- Direction
- db.generators uses lib.Primitives, so a change to lib.Primitives can break db.generators, while a change to db.generators can't break lib.Primitives.
- 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→18 db.generators uses db part of a loop✕
- Connections
- 2 pairs of types, where a type in db.generators uses a type in db.
- The types involved
db.generators.InternalGeneratorServicesDao→db.InternalUserdb.generators.InternalGeneratorsDao→db.InternalUser
- Direction
- db.generators uses db, so a change to db can break db.generators, while a change to db.generators can't break db.
- 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→20 db.generators uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 3 pairs of types, where a type in db.generators uses a type in io.apibuilder.api.v0.models.
- The types involved
db.generators.InternalGeneratorServicesDao→io.apibuilder.api.v0.models.Errordb.generators.InternalGeneratorServicesDao→io.apibuilder.api.v0.models.GeneratorServiceFormdb.generators.InternalGeneratorsDao→io.apibuilder.api.v0.models.GeneratorForm
- Direction
- db.generators uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break db.generators, while a change to db.generators can't break io.apibuilder.api.v0.models.
- 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→21 db.generators uses io.apibuilder.generator.v0.models part of a loop✕
- Connections
- 1 pair of types, where a type in db.generators uses a type in io.apibuilder.generator.v0.models.
- The types involved
db.generators.InternalGenerator→io.apibuilder.generator.v0.models.Generator
- Direction
- db.generators uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break db.generators, while a change to db.generators can't break io.apibuilder.generator.v0.models.
- 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→23 db.generators uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 9 pairs of types, where a type in db.generators uses a type in io.apibuilder.avro.SchemaType.
- The types involved
db.generators.InternalGenerator→io.apibuilder.avro.SchemaType.Stringdb.generators.InternalGeneratorService→io.apibuilder.avro.SchemaType.Stringdb.generators.InternalGeneratorServicesDao→io.apibuilder.avro.SchemaType.Booleandb.generators.InternalGeneratorServicesDao→io.apibuilder.avro.SchemaType.Longdb.generators.InternalGeneratorServicesDao→io.apibuilder.avro.SchemaType.Stringdb.generators.InternalGeneratorsDao→io.apibuilder.avro.SchemaType.Booleandb.generators.InternalGeneratorsDao→io.apibuilder.avro.SchemaType.Longdb.generators.InternalGeneratorsDao→io.apibuilder.avro.SchemaType.Stringdb.generators.ValidatedGeneratorServiceForm→io.apibuilder.avro.SchemaType.String
- Direction
- db.generators uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break db.generators, while a change to db.generators can't break io.apibuilder.avro.SchemaType.
- 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.
14→4 models uses lib.Emails.Context✕
- Connections
- 2 pairs of types, where a type in models uses a type in lib.Emails.Context.
- The types involved
models.ApplicationsModel→lib.Emails.Context.Applicationmodels.MainTemplate→lib.Emails.Context.Application
- Direction
- models uses lib.Emails.Context, so a change to lib.Emails.Context can break models, while a change to models can't break lib.Emails.Context.
- Position
- Below the diagonal: models uses a module listed above it, which is the healthy direction.
14→6 models uses util.BasicAuthorization✕
- Connections
- 1 pair of types, where a type in models uses a type in util.BasicAuthorization.
- The types involved
models.TokensModel→util.BasicAuthorization.Token
- Direction
- models uses util.BasicAuthorization, so a change to util.BasicAuthorization can break models, while a change to models can't break util.BasicAuthorization.
- Position
- Below the diagonal: models uses a module listed above it, which is the healthy direction.
14→7 models uses db.Authorization✕
- Connections
- 2 pairs of types, where a type in models uses a type in db.Authorization.
- The types involved
models.MainTemplate→db.Authorization.Usermodels.UsersModel→db.Authorization.User
- Direction
- models uses db.Authorization, so a change to db.Authorization can break models, while a change to models can't break db.Authorization.
- Position
- Below the diagonal: models uses a module listed above it, which is the healthy direction.
14→8 models uses io.apibuilder.api.json.v0.models✕
- Connections
- 3 pairs of types, where a type in models uses a type in io.apibuilder.api.json.v0.models.
- The types involved
models.AttributesModel→io.apibuilder.api.json.v0.models.Attributemodels.MainTemplate→io.apibuilder.api.json.v0.models.Attributemodels.MainTemplate→io.apibuilder.api.json.v0.models.Resource
- Direction
- models uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break models, while a change to models can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: models uses a module listed above it, which is the healthy direction.
14→12 models uses io.apibuilder.spec.v0.models✕
- Connections
- 2 pairs of types, where a type in models uses a type in io.apibuilder.spec.v0.models.
- The types involved
models.MainTemplate→io.apibuilder.spec.v0.models.Servicemodels.VersionsModel→io.apibuilder.spec.v0.models.Service
- Direction
- models uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break models, while a change to models can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: models uses a module listed above it, which is the healthy direction.
14→13 models uses db.generators✕
- Connections
- 2 pairs of types, where a type in models uses a type in db.generators.
- The types involved
models.GeneratorServicesModel→db.generators.InternalGeneratorServicemodels.GeneratorWithServiceModel→db.generators.InternalGenerator
- Direction
- models uses db.generators, so a change to db.generators can break models, while a change to models can't break db.generators.
- Position
- Below the diagonal: models uses a module listed above it, which is the healthy direction.
14→18 models uses db part of a loop✕
- Connections
- 15 pairs of types, where a type in models uses a type in db.
- The types involved
models.ApplicationsModel→db.InternalApplicationmodels.AttributesModel→db.InternalAttributemodels.ChangesModel→db.InternalChangemodels.DomainsModel→db.InternalOrganizationDomainmodels.MembershipRequestsModel→db.InternalMembershipRequestmodels.MembershipsModel→db.InternalMembershipmodels.OrganizationAttributeValuesModel→db.InternalOrganizationAttributeValuemodels.OrganizationsModel→db.Authorizationmodels.OrganizationsModel→db.InternalOrganizationmodels.OriginalsModel→db.InternalOriginalmodels.SubscriptionModel→db.InternalSubscriptionmodels.TokensModel→db.InternalTokenmodels.UsersModel→db.InternalUsermodels.VersionsModel→db.InternalVersionmodels.WatchesModel→db.InternalWatch
- Direction
- models uses db, so a change to db can break models, while a change to models can't break db.
- 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.
14→20 models uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 16 pairs of types, where a type in models uses a type in io.apibuilder.api.v0.models.
- The types involved
models.ChangesModel→io.apibuilder.api.v0.models.Changemodels.DomainsModel→io.apibuilder.api.v0.models.Domainmodels.GeneratorServicesModel→io.apibuilder.api.v0.models.GeneratorServicemodels.GeneratorWithServiceModel→io.apibuilder.api.v0.models.GeneratorWithServicemodels.MainTemplate→io.apibuilder.api.v0.models.GeneratorServicemodels.MainTemplate→io.apibuilder.api.v0.models.GeneratorWithServicemodels.MainTemplate→io.apibuilder.api.v0.models.Organizationmodels.MainTemplate→io.apibuilder.api.v0.models.Versionmodels.MembershipRequestsModel→io.apibuilder.api.v0.models.MembershipRequestmodels.MembershipsModel→io.apibuilder.api.v0.models.Membershipmodels.OrganizationAttributeValuesModel→io.apibuilder.api.v0.models.AttributeValuemodels.OrganizationsModel→io.apibuilder.api.v0.models.Organizationmodels.OriginalsModel→io.apibuilder.api.v0.models.Originalmodels.SubscriptionModel→io.apibuilder.api.v0.models.Subscriptionmodels.VersionsModel→io.apibuilder.api.v0.models.Versionmodels.WatchesModel→io.apibuilder.api.v0.models.Watch
- Direction
- models uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break models, while a change to models can't break io.apibuilder.api.v0.models.
- 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.
14→23 models uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 5 pairs of types, where a type in models uses a type in io.apibuilder.avro.SchemaType.
- The types involved
models.MainTemplate→io.apibuilder.avro.SchemaType.Booleanmodels.MainTemplate→io.apibuilder.avro.SchemaType.Stringmodels.SettingSection→io.apibuilder.avro.SchemaType.Stringmodels.UserTimeZone→io.apibuilder.avro.SchemaType.Stringmodels.VersionsModel→io.apibuilder.avro.SchemaType.String
- Direction
- models uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break models, while a change to models can't break io.apibuilder.avro.SchemaType.
- 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.
15→2 lib uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 2 pairs of types, where a type in lib uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
lib.ServiceDiff→io.apibuilder.avro.ApiBuilder.Fieldlib.ServiceDiff→io.apibuilder.avro.ApiBuilder.UnionType
- Direction
- lib uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break lib, while a change to lib can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→3 lib uses io.apibuilder.common.v0.models✕
- Connections
- 1 pair of types, where a type in lib uses a type in io.apibuilder.common.v0.models.
- The types involved
lib.OrgAttributeUtil→io.apibuilder.common.v0.models.Reference
- Direction
- lib uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break lib, while a change to lib can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→4 lib uses lib.Emails.Context✕
- Connections
- 1 pair of types, where a type in lib uses a type in lib.Emails.Context.
- The types involved
lib.TypeLabel→lib.Emails.Context.Application
- Direction
- lib uses lib.Emails.Context, so a change to lib.Emails.Context can break lib, while a change to lib can't break lib.Emails.Context.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→7 lib uses db.Authorization✕
- Connections
- 2 pairs of types, where a type in lib uses a type in db.Authorization.
- The types involved
lib.ApiClientProvider→db.Authorization.Userlib.ApibuilderRequestData→db.Authorization.User
- Direction
- lib uses db.Authorization, so a change to db.Authorization can break lib, while a change to lib can't break db.Authorization.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→8 lib uses io.apibuilder.api.json.v0.models✕
- Connections
- 13 pairs of types, where a type in lib uses a type in io.apibuilder.api.json.v0.models.
- The types involved
lib.OrgAttributeUtil→io.apibuilder.api.json.v0.models.Attributelib.ServiceDiff→io.apibuilder.api.json.v0.models.Annotationlib.ServiceDiff→io.apibuilder.api.json.v0.models.Bodylib.ServiceDiff→io.apibuilder.api.json.v0.models.EnumValuelib.ServiceDiff→io.apibuilder.api.json.v0.models.Headerlib.ServiceDiff→io.apibuilder.api.json.v0.models.Importlib.ServiceDiff→io.apibuilder.api.json.v0.models.Interfacelib.ServiceDiff→io.apibuilder.api.json.v0.models.Modellib.ServiceDiff→io.apibuilder.api.json.v0.models.Operationlib.ServiceDiff→io.apibuilder.api.json.v0.models.Parameterlib.ServiceDiff→io.apibuilder.api.json.v0.models.Resourcelib.ServiceDiff→io.apibuilder.api.json.v0.models.Responselib.TypeLabel→io.apibuilder.api.json.v0.models.Import
- Direction
- lib uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break lib, while a change to lib can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→10 lib uses io.apibuilder.api.json.v0.models.ParameterLocation✕
- Connections
- 1 pair of types, where a type in lib uses a type in io.apibuilder.api.json.v0.models.ParameterLocation.
- The types involved
lib.EmailUtil→io.apibuilder.api.json.v0.models.ParameterLocation.Path
- Direction
- lib uses io.apibuilder.api.json.v0.models.ParameterLocation, so a change to io.apibuilder.api.json.v0.models.ParameterLocation can break lib, while a change to lib can't break io.apibuilder.api.json.v0.models.ParameterLocation.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→11 lib uses io.apibuilder.api.v0✕
- Connections
- 3 pairs of types, where a type in lib uses a type in io.apibuilder.api.v0.
- The types involved
lib.ApiClientProvider→io.apibuilder.api.v0.Clientlib.ApibuilderRequestData→io.apibuilder.api.v0.Clientlib.MemberDownload→io.apibuilder.api.v0.Client
- Direction
- lib uses io.apibuilder.api.v0, so a change to io.apibuilder.api.v0 can break lib, while a change to lib can't break io.apibuilder.api.v0.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→12 lib uses io.apibuilder.spec.v0.models✕
- Connections
- 3 pairs of types, where a type in lib uses a type in io.apibuilder.spec.v0.models.
- The types involved
lib.ExampleJson→io.apibuilder.spec.v0.models.Servicelib.ServiceDiff→io.apibuilder.spec.v0.models.Servicelib.TypeLabel→io.apibuilder.spec.v0.models.Service
- Direction
- lib uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break lib, while a change to lib can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→14 lib uses models✕
- Connections
- 2 pairs of types, where a type in lib uses a type in models.
- The types involved
lib.ApibuilderRequestData→models.MainTemplatelib.DateHelper→models.UserTimeZone
- Direction
- lib uses models, so a change to models can break lib, while a change to lib can't break models.
- Position
- Below the diagonal: lib uses a module listed above it, which is the healthy direction.
15→16 lib uses lib.Primitives part of a loop✕
- Connections
- 6 pairs of types, where a type in lib uses a type in lib.Primitives.
- The types involved
lib.EmailUtil→lib.Primitives.Unitlib.Pager→lib.Primitives.Unitlib.Text→lib.Primitives.Unitlib.UrlKey→lib.Primitives.Unitlib.ValidatedHelpers→lib.Primitives.Unitlib.Zipfile→lib.Primitives.Unit
- Direction
- lib uses lib.Primitives, so a change to lib.Primitives can break lib, while a change to lib can't break lib.Primitives.
- 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.
15→18 lib uses db part of a loop✕
- Connections
- 2 pairs of types, where a type in lib uses a type in db.
- The types involved
lib.DatabaseServiceFetcher→db.Authorizationlib.RequestAuthenticationUtil→db.InternalUser
- Direction
- lib uses db, so a change to db can break lib, while a change to lib can't break db.
- 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.
15→20 lib uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 12 pairs of types, where a type in lib uses a type in io.apibuilder.api.v0.models.
- The types involved
lib.ApibuilderRequestData→io.apibuilder.api.v0.models.Membershiplib.ApibuilderRequestData→io.apibuilder.api.v0.models.Organizationlib.AppOrderHelper→io.apibuilder.api.v0.models.AppSortBylib.AppOrderHelper→io.apibuilder.api.v0.models.SortOrderlib.Misc→io.apibuilder.api.v0.models.Errorlib.OriginalUtil→io.apibuilder.api.v0.models.Originallib.OriginalUtil→io.apibuilder.api.v0.models.OriginalFormlib.OriginalUtil→io.apibuilder.api.v0.models.OriginalTypelib.ServiceDiff→io.apibuilder.api.v0.models.Difflib.TypeLabel→io.apibuilder.api.v0.models.Organizationlib.Util→io.apibuilder.api.v0.models.ItemDetaillib.Validation→io.apibuilder.api.v0.models.Error
- Direction
- lib uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break lib, while a change to lib can't break io.apibuilder.api.v0.models.
- 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.
15→21 lib uses io.apibuilder.generator.v0.models part of a loop✕
- Connections
- 4 pairs of types, where a type in lib uses a type in io.apibuilder.generator.v0.models.
- The types involved
lib.FileUtils→io.apibuilder.generator.v0.models.Filelib.MemberDownload→io.apibuilder.generator.v0.models.Filelib.TarballFile→io.apibuilder.generator.v0.models.Filelib.Zipfile→io.apibuilder.generator.v0.models.File
- Direction
- lib uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break lib, while a change to lib can't break io.apibuilder.generator.v0.models.
- 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.
15→23 lib uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 58 pairs of types, where a type in lib uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
lib.ApiClientProvider→io.apibuilder.avro.SchemaType.Stringlib.ApibuilderRequestData→io.apibuilder.avro.SchemaType.Booleanlib.ApibuilderRequestData→io.apibuilder.avro.SchemaType.Stringlib.AppConfig→io.apibuilder.avro.SchemaType.Stringlib.Bytes→io.apibuilder.avro.SchemaType.Longlib.Bytes→io.apibuilder.avro.SchemaType.Stringlib.Config→io.apibuilder.avro.SchemaType.Booleanlib.Config→io.apibuilder.avro.SchemaType.Stringlib.Constants→io.apibuilder.avro.SchemaType.Stringlib.DatatypeResolver→io.apibuilder.avro.SchemaType.Booleanlib.DatatypeResolver→io.apibuilder.avro.SchemaType.Stringlib.DateHelper→io.apibuilder.avro.SchemaType.Stringlib.EmailUtil→io.apibuilder.avro.SchemaType.Stringlib.ExampleJson→io.apibuilder.avro.SchemaType.Stringlib.ExampleService→io.apibuilder.avro.SchemaType.Stringlib.FileUtils→io.apibuilder.avro.SchemaType.Stringlib.Github→io.apibuilder.avro.SchemaType.Stringlib.Href→io.apibuilder.avro.SchemaType.Stringlib.Markdown→io.apibuilder.avro.SchemaType.Stringlib.MemberDownload→io.apibuilder.avro.SchemaType.Stringlib.Methods→io.apibuilder.avro.SchemaType.Booleanlib.Methods→io.apibuilder.avro.SchemaType.Stringlib.Misc→io.apibuilder.avro.SchemaType.Stringlib.OrgAttributeUtil→io.apibuilder.avro.SchemaType.Stringlib.OriginalUtil→io.apibuilder.avro.SchemaType.String
- Direction
- lib uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break lib, while a change to lib can't break io.apibuilder.avro.SchemaType.
- 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.
15→25 lib uses core part of a loop✕
- Connections
- 1 pair of types, where a type in lib uses a type in core.
- The types involved
lib.DatabaseServiceFetcher→core.ServiceFetcher
- Direction
- lib uses core, so a change to core can break lib, while a change to lib can't break core.
- 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.
15→34 lib uses builder.api_json.InternalDatatype part of a loop✕
- Connections
- 1 pair of types, where a type in lib uses a type in builder.api_json.InternalDatatype.
- The types involved
lib.Labels→builder.api_json.InternalDatatype.List
- Direction
- lib uses builder.api_json.InternalDatatype, so a change to builder.api_json.InternalDatatype can break lib, while a change to lib can't break builder.api_json.InternalDatatype.
- 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.
16→15 lib.Primitives uses lib✕
- Connections
- 12 pairs of types, where a type in lib.Primitives uses a type in lib.
- The types involved
lib.Primitives.Boolean→lib.Primitiveslib.Primitives.DateIso8601→lib.Primitiveslib.Primitives.DateTimeIso8601→lib.Primitiveslib.Primitives.Decimal→lib.Primitiveslib.Primitives.Double→lib.Primitiveslib.Primitives.Integer→lib.Primitiveslib.Primitives.JsonValue→lib.Primitiveslib.Primitives.Long→lib.Primitiveslib.Primitives.Object→lib.Primitiveslib.Primitives.String→lib.Primitiveslib.Primitives.Unit→lib.Primitiveslib.Primitives.Uuid→lib.Primitives
- Direction
- lib.Primitives uses lib, so a change to lib can break lib.Primitives, while a change to lib.Primitives can't break lib.
- Position
- Below the diagonal: lib.Primitives uses a module listed above it, which is the healthy direction.
17→4 db.generated uses lib.Emails.Context✕
- Connections
- 2 pairs of types, where a type in db.generated uses a type in lib.Emails.Context.
- The types involved
db.generated.ApplicationsDao→lib.Emails.Context.Applicationdb.generated.BaseApplicationsDao→lib.Emails.Context.Application
- Direction
- db.generated uses lib.Emails.Context, so a change to lib.Emails.Context can break db.generated, while a change to db.generated can't break lib.Emails.Context.
- Position
- Below the diagonal: db.generated uses a module listed above it, which is the healthy direction.
17→5 db.generated uses lib.query✕
- Connections
- 44 pairs of types, where a type in db.generated uses a type in lib.query. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
db.generated.ApplicationMovesDao→lib.query.Querydb.generated.ApplicationsDao→lib.query.Querydb.generated.AttributesDao→lib.query.Querydb.generated.BaseApplicationMovesDao→lib.query.Querydb.generated.BaseApplicationsDao→lib.query.Querydb.generated.BaseAttributesDao→lib.query.Querydb.generated.BaseChangesDao→lib.query.Querydb.generated.BaseEmailVerificationConfirmationsDao→lib.query.Querydb.generated.BaseEmailVerificationsDao→lib.query.Querydb.generated.BaseGeneratorInvocationsDao→lib.query.Querydb.generated.BaseMembershipRequestsDao→lib.query.Querydb.generated.BaseMembershipsDao→lib.query.Querydb.generated.BaseOrganizationAttributeValuesDao→lib.query.Querydb.generated.BaseOrganizationDomainsDao→lib.query.Querydb.generated.BaseOrganizationsDao→lib.query.Querydb.generated.BaseOriginalsDao→lib.query.Querydb.generated.BasePasswordResetsDao→lib.query.Querydb.generated.BaseSessionsDao→lib.query.Querydb.generated.BaseSubscriptionsDao→lib.query.Querydb.generated.BaseTasksDao→lib.query.Querydb.generated.BaseTokensDao→lib.query.Querydb.generated.BaseUserPasswordsDao→lib.query.Querydb.generated.BaseUsersDao→lib.query.Querydb.generated.BaseVersionsDao→lib.query.Querydb.generated.BaseWatchesDao→lib.query.Query
- Direction
- db.generated uses lib.query, so a change to lib.query can break db.generated, while a change to db.generated can't break lib.query.
- Position
- Below the diagonal: db.generated uses a module listed above it, which is the healthy direction.
17→6 db.generated uses util.BasicAuthorization✕
- Connections
- 4 pairs of types, where a type in db.generated uses a type in util.BasicAuthorization.
- The types involved
db.generated.BaseSessionsDao→util.BasicAuthorization.Sessiondb.generated.BaseTokensDao→util.BasicAuthorization.Tokendb.generated.SessionsDao→util.BasicAuthorization.Sessiondb.generated.TokensDao→util.BasicAuthorization.Token
- Direction
- db.generated uses util.BasicAuthorization, so a change to util.BasicAuthorization can break db.generated, while a change to db.generated can't break util.BasicAuthorization.
- Position
- Below the diagonal: db.generated uses a module listed above it, which is the healthy direction.
17→7 db.generated uses db.Authorization✕
- Connections
- 2 pairs of types, where a type in db.generated uses a type in db.Authorization.
- The types involved
db.generated.BaseUsersDao→db.Authorization.Userdb.generated.UsersDao→db.Authorization.User
- Direction
- db.generated uses db.Authorization, so a change to db.Authorization can break db.generated, while a change to db.generated can't break db.Authorization.
- Position
- Below the diagonal: db.generated uses a module listed above it, which is the healthy direction.
17→8 db.generated uses io.apibuilder.api.json.v0.models✕
- Connections
- 2 pairs of types, where a type in db.generated uses a type in io.apibuilder.api.json.v0.models.
- The types involved
db.generated.AttributesDao→io.apibuilder.api.json.v0.models.Attributedb.generated.BaseAttributesDao→io.apibuilder.api.json.v0.models.Attribute
- Direction
- db.generated uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break db.generated, while a change to db.generated can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: db.generated uses a module listed above it, which is the healthy direction.
17→16 db.generated uses lib.Primitives✕
- Connections
- 22 pairs of types, where a type in db.generated uses a type in lib.Primitives.
- The types involved
db.generated.ApplicationMovesDao→lib.Primitives.Unitdb.generated.ApplicationsDao→lib.Primitives.Unitdb.generated.AttributesDao→lib.Primitives.Unitdb.generated.ChangesDao→lib.Primitives.Unitdb.generated.EmailVerificationConfirmationsDao→lib.Primitives.Unitdb.generated.EmailVerificationsDao→lib.Primitives.Unitdb.generated.GeneratorInvocationsDao→lib.Primitives.Unitdb.generated.MembershipRequestsDao→lib.Primitives.Unitdb.generated.MembershipsDao→lib.Primitives.Unitdb.generated.OrganizationAttributeValuesDao→lib.Primitives.Unitdb.generated.OrganizationDomainsDao→lib.Primitives.Unitdb.generated.OrganizationsDao→lib.Primitives.Unitdb.generated.OriginalsDao→lib.Primitives.Unitdb.generated.PasswordResetsDao→lib.Primitives.Unitdb.generated.SessionsDao→lib.Primitives.Unitdb.generated.SubscriptionsDao→lib.Primitives.Unitdb.generated.TasksDao→lib.Primitives.Unitdb.generated.TokensDao→lib.Primitives.Unitdb.generated.UserPasswordsDao→lib.Primitives.Unitdb.generated.UsersDao→lib.Primitives.Unitdb.generated.VersionsDao→lib.Primitives.Unitdb.generated.WatchesDao→lib.Primitives.Unit
- Direction
- db.generated uses lib.Primitives, so a change to lib.Primitives can break db.generated, while a change to db.generated can't break lib.Primitives.
- Position
- Below the diagonal: db.generated uses a module listed above it, which is the healthy direction.
17→20 db.generated uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 38 pairs of types, where a type in db.generated uses a type in io.apibuilder.api.v0.models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
db.generated.Application→io.apibuilder.api.v0.models.ApplicationFormdb.generated.ApplicationsDao→io.apibuilder.api.v0.models.ApplicationFormdb.generated.Attribute→io.apibuilder.api.v0.models.AttributeFormdb.generated.AttributesDao→io.apibuilder.api.v0.models.AttributeFormdb.generated.BaseChangesDao→io.apibuilder.api.v0.models.Changedb.generated.BaseMembershipRequestsDao→io.apibuilder.api.v0.models.MembershipRequestdb.generated.BaseMembershipsDao→io.apibuilder.api.v0.models.Membershipdb.generated.BaseOrganizationsDao→io.apibuilder.api.v0.models.Organizationdb.generated.BaseOriginalsDao→io.apibuilder.api.v0.models.Originaldb.generated.BasePasswordResetsDao→io.apibuilder.api.v0.models.PasswordResetdb.generated.BaseSubscriptionsDao→io.apibuilder.api.v0.models.Subscriptiondb.generated.BaseVersionsDao→io.apibuilder.api.v0.models.Versiondb.generated.BaseWatchesDao→io.apibuilder.api.v0.models.Watchdb.generated.ChangesDao→io.apibuilder.api.v0.models.Changedb.generated.EmailVerificationConfirmation→io.apibuilder.api.v0.models.EmailVerificationConfirmationFormdb.generated.EmailVerificationConfirmationsDao→io.apibuilder.api.v0.models.EmailVerificationConfirmationFormdb.generated.MembershipRequestsDao→io.apibuilder.api.v0.models.MembershipRequestdb.generated.MembershipsDao→io.apibuilder.api.v0.models.Membershipdb.generated.Organization→io.apibuilder.api.v0.models.OrganizationFormdb.generated.OrganizationsDao→io.apibuilder.api.v0.models.Organizationdb.generated.OrganizationsDao→io.apibuilder.api.v0.models.OrganizationFormdb.generated.Original→io.apibuilder.api.v0.models.OriginalFormdb.generated.OriginalsDao→io.apibuilder.api.v0.models.Originaldb.generated.OriginalsDao→io.apibuilder.api.v0.models.OriginalFormdb.generated.PasswordResetsDao→io.apibuilder.api.v0.models.PasswordReset
- Direction
- db.generated uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break db.generated, while a change to db.generated can't break io.apibuilder.api.v0.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→23 db.generated uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 104 pairs of types, where a type in db.generated uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
db.generated.Application→io.apibuilder.avro.SchemaType.Stringdb.generated.ApplicationForm→io.apibuilder.avro.SchemaType.Stringdb.generated.ApplicationMovesTable→io.apibuilder.avro.SchemaType.Stringdb.generated.ApplicationsTable→io.apibuilder.avro.SchemaType.Stringdb.generated.Attribute→io.apibuilder.avro.SchemaType.Stringdb.generated.AttributeForm→io.apibuilder.avro.SchemaType.Stringdb.generated.AttributesTable→io.apibuilder.avro.SchemaType.Stringdb.generated.BaseApplicationMovesDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseApplicationsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseAttributesDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseChangesDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseEmailVerificationConfirmationsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseEmailVerificationsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseEmailVerificationsDao→io.apibuilder.avro.SchemaType.Stringdb.generated.BaseGeneratorInvocationsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseGeneratorInvocationsDao→io.apibuilder.avro.SchemaType.Stringdb.generated.BaseMembershipRequestsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseMembershipsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseOrganizationAttributeValuesDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseOrganizationDomainsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseOrganizationDomainsDao→io.apibuilder.avro.SchemaType.Stringdb.generated.BaseOrganizationsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BaseOriginalsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BasePasswordResetsDao→io.apibuilder.avro.SchemaType.Longdb.generated.BasePasswordResetsDao→io.apibuilder.avro.SchemaType.String
- Direction
- db.generated uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break db.generated, while a change to db.generated can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 db uses io.apibuilder.api.v0.models.AppSortBy✕
- Connections
- 3 pairs of types, where a type in db uses a type in io.apibuilder.api.v0.models.AppSortBy.
- The types involved
db.InternalApplication→io.apibuilder.api.v0.models.AppSortBy.Visibilitydb.InternalApplicationsDao→io.apibuilder.api.v0.models.AppSortBy.Visibilitydb.InternalOrganization→io.apibuilder.api.v0.models.AppSortBy.Visibility
- Direction
- db uses io.apibuilder.api.v0.models.AppSortBy, so a change to io.apibuilder.api.v0.models.AppSortBy can break db, while a change to db can't break io.apibuilder.api.v0.models.AppSortBy.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→3 db uses io.apibuilder.common.v0.models✕
- Connections
- 4 pairs of types, where a type in db uses a type in io.apibuilder.common.v0.models.
- The types involved
db.InternalMembership→io.apibuilder.common.v0.models.MembershipRoledb.InternalMembershipRequest→io.apibuilder.common.v0.models.MembershipRoledb.InternalMembershipRequestsDao→io.apibuilder.common.v0.models.MembershipRoledb.InternalMembershipsDao→io.apibuilder.common.v0.models.MembershipRole
- Direction
- db uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break db, while a change to db can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→4 db uses lib.Emails.Context✕
- Connections
- 1 pair of types, where a type in db uses a type in lib.Emails.Context.
- The types involved
db.InternalApplication→lib.Emails.Context.Application
- Direction
- db uses lib.Emails.Context, so a change to lib.Emails.Context can break db, while a change to db can't break lib.Emails.Context.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→5 db uses lib.query✕
- Connections
- 2 pairs of types, where a type in db uses a type in lib.query.
- The types involved
db.Authorization→lib.query.Querydb.ItemsDao→lib.query.Query
- Direction
- db uses lib.query, so a change to lib.query can break db, while a change to db can't break lib.query.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→6 db uses util.BasicAuthorization✕
- Connections
- 1 pair of types, where a type in db uses a type in util.BasicAuthorization.
- The types involved
db.InternalToken→util.BasicAuthorization.Token
- Direction
- db uses util.BasicAuthorization, so a change to util.BasicAuthorization can break db, while a change to db can't break util.BasicAuthorization.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→7 db uses db.Authorization✕
- Connections
- 2 pairs of types, where a type in db uses a type in db.Authorization.
- The types involved
db.InternalUser→db.Authorization.Userdb.ValidatedSubscriptionForm→db.Authorization.User
- Direction
- db uses db.Authorization, so a change to db.Authorization can break db, while a change to db can't break db.Authorization.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→8 db uses io.apibuilder.api.json.v0.models✕
- Connections
- 1 pair of types, where a type in db uses a type in io.apibuilder.api.json.v0.models.
- The types involved
db.InternalAttribute→io.apibuilder.api.json.v0.models.Attribute
- Direction
- db uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break db, while a change to db can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→9 db uses io.apibuilder.task.v0.models✕
- Connections
- 1 pair of types, where a type in db uses a type in io.apibuilder.task.v0.models.
- The types involved
db.InternalTasksDao→io.apibuilder.task.v0.models.TaskType
- Direction
- db uses io.apibuilder.task.v0.models, so a change to io.apibuilder.task.v0.models can break db, while a change to db can't break io.apibuilder.task.v0.models.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→12 db uses io.apibuilder.spec.v0.models✕
- Connections
- 1 pair of types, where a type in db uses a type in io.apibuilder.spec.v0.models.
- The types involved
db.InternalVersionsDao→io.apibuilder.spec.v0.models.Service
- Direction
- db uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break db, while a change to db can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→15 db uses lib✕
- Connections
- 1 pair of types, where a type in db uses a type in lib.
- The types involved
db.InternalVersionsDao→lib.ValidatedHelpers
- Direction
- db uses lib, so a change to lib can break db, while a change to db can't break lib.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→16 db uses lib.Primitives✕
- Connections
- 17 pairs of types, where a type in db uses a type in lib.Primitives.
- The types involved
db.InternalApplicationsDao→lib.Primitives.Unitdb.InternalAttributesDao→lib.Primitives.Unitdb.InternalChangesDao→lib.Primitives.Unitdb.InternalEmailVerificationsDao→lib.Primitives.Unitdb.InternalMembershipRequestsDao→lib.Primitives.Unitdb.InternalMembershipsDao→lib.Primitives.Unitdb.InternalOrganizationAttributeValuesDao→lib.Primitives.Unitdb.InternalOrganizationDomainsDao→lib.Primitives.Unitdb.InternalOrganizationsDao→lib.Primitives.Unitdb.InternalOriginalsDao→lib.Primitives.Unitdb.InternalPasswordResetsDao→lib.Primitives.Unitdb.InternalTasksDao→lib.Primitives.Unitdb.InternalTokensDao→lib.Primitives.Unitdb.InternalUserPasswordsDao→lib.Primitives.Unitdb.InternalVersionsDao→lib.Primitives.Unitdb.InternalWatchesDao→lib.Primitives.Unitdb.ItemsDao→lib.Primitives.Unit
- Direction
- db uses lib.Primitives, so a change to lib.Primitives can break db, while a change to db can't break lib.Primitives.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→17 db uses db.generated✕
- Connections
- 7 pairs of types, where a type in db uses a type in db.generated.
- The types involved
db.InternalChangesDao→db.generated.ChangeFormdb.InternalEmailVerification→db.generated.EmailVerificationdb.InternalEmailVerificationConfirmation→db.generated.EmailVerificationConfirmationdb.InternalOrganizationAttributeValue→db.generated.OrganizationAttributeValuedb.InternalOrganizationDomain→db.generated.OrganizationDomaindb.InternalTasksDao→db.generated.Taskdb.InternalUserPassword→db.generated.UserPassword
- Direction
- db uses db.generated, so a change to db.generated can break db, while a change to db can't break db.generated.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
18→20 db uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 44 pairs of types, where a type in db uses a type in io.apibuilder.api.v0.models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
db.InternalApplicationsDao→io.apibuilder.api.v0.models.AppSortBydb.InternalApplicationsDao→io.apibuilder.api.v0.models.ApplicationFormdb.InternalApplicationsDao→io.apibuilder.api.v0.models.Errordb.InternalApplicationsDao→io.apibuilder.api.v0.models.MoveFormdb.InternalApplicationsDao→io.apibuilder.api.v0.models.SortOrderdb.InternalApplicationsDao→io.apibuilder.api.v0.models.Versiondb.InternalAttributesDao→io.apibuilder.api.v0.models.AttributeFormdb.InternalAttributesDao→io.apibuilder.api.v0.models.Errordb.InternalChange→io.apibuilder.api.v0.models.Changedb.InternalChange→io.apibuilder.api.v0.models.Diffdb.InternalChangesDao→io.apibuilder.api.v0.models.Diffdb.InternalChangesDao→io.apibuilder.api.v0.models.Versiondb.InternalMembership→io.apibuilder.api.v0.models.Membershipdb.InternalMembershipRequest→io.apibuilder.api.v0.models.MembershipRequestdb.InternalMembershipRequestsDao→io.apibuilder.api.v0.models.MembershipRequestdb.InternalOrganization→io.apibuilder.api.v0.models.Organizationdb.InternalOrganizationAttributeValuesDao→io.apibuilder.api.v0.models.AttributeValueFormdb.InternalOrganizationAttributeValuesDao→io.apibuilder.api.v0.models.Errordb.InternalOrganizationsDao→io.apibuilder.api.v0.models.Errordb.InternalOrganizationsDao→io.apibuilder.api.v0.models.OrganizationFormdb.InternalOriginal→io.apibuilder.api.v0.models.Originaldb.InternalOriginal→io.apibuilder.api.v0.models.OriginalTypedb.InternalOriginalsDao→io.apibuilder.api.v0.models.Originaldb.InternalPasswordReset→io.apibuilder.api.v0.models.PasswordResetdb.InternalPasswordResetsDao→io.apibuilder.api.v0.models.Error
- Direction
- db uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break db, while a change to db can't break io.apibuilder.api.v0.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→23 db uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 75 pairs of types, where a type in db uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
db.AuditsDao→io.apibuilder.avro.SchemaType.Stringdb.Authorization→io.apibuilder.avro.SchemaType.Stringdb.Filters→io.apibuilder.avro.SchemaType.Booleandb.Filters→io.apibuilder.avro.SchemaType.Stringdb.InternalApplication→io.apibuilder.avro.SchemaType.Stringdb.InternalApplicationsDao→io.apibuilder.avro.SchemaType.Booleandb.InternalApplicationsDao→io.apibuilder.avro.SchemaType.Longdb.InternalApplicationsDao→io.apibuilder.avro.SchemaType.Stringdb.InternalAttribute→io.apibuilder.avro.SchemaType.Stringdb.InternalAttributesDao→io.apibuilder.avro.SchemaType.Booleandb.InternalAttributesDao→io.apibuilder.avro.SchemaType.Longdb.InternalAttributesDao→io.apibuilder.avro.SchemaType.Stringdb.InternalChangesDao→io.apibuilder.avro.SchemaType.Booleandb.InternalChangesDao→io.apibuilder.avro.SchemaType.Longdb.InternalChangesDao→io.apibuilder.avro.SchemaType.Stringdb.InternalEmailVerification→io.apibuilder.avro.SchemaType.Stringdb.InternalEmailVerificationConfirmationsDao→io.apibuilder.avro.SchemaType.Booleandb.InternalEmailVerificationConfirmationsDao→io.apibuilder.avro.SchemaType.Longdb.InternalEmailVerificationsDao→io.apibuilder.avro.SchemaType.Booleandb.InternalEmailVerificationsDao→io.apibuilder.avro.SchemaType.Longdb.InternalEmailVerificationsDao→io.apibuilder.avro.SchemaType.Stringdb.InternalMembershipRequestsDao→io.apibuilder.avro.SchemaType.Booleandb.InternalMembershipRequestsDao→io.apibuilder.avro.SchemaType.Longdb.InternalMembershipRequestsDao→io.apibuilder.avro.SchemaType.Stringdb.InternalMembershipsDao→io.apibuilder.avro.SchemaType.Boolean
- Direction
- db uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break db, while a change to db can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→3 controllers uses io.apibuilder.common.v0.models✕
- Connections
- 4 pairs of types, where a type in controllers uses a type in io.apibuilder.common.v0.models.
- The types involved
controllers.ApiBuilderController→io.apibuilder.common.v0.models.MembershipRolecontrollers.Members→io.apibuilder.common.v0.models.MembershipRolecontrollers.MembershipRequests→io.apibuilder.common.v0.models.MembershipRolecontrollers.Memberships→io.apibuilder.common.v0.models.MembershipRole
- Direction
- controllers uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break controllers, while a change to controllers can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→7 controllers uses db.Authorization✕
- Connections
- 3 pairs of types, where a type in controllers uses a type in db.Authorization.
- The types involved
controllers.AnonymousOrgRequest→db.Authorization.Usercontrollers.IdentifiedOrgRequest→db.Authorization.Usercontrollers.IdentifiedRequest→db.Authorization.User
- Direction
- controllers uses db.Authorization, so a change to db.Authorization can break controllers, while a change to controllers can't break db.Authorization.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→11 controllers uses io.apibuilder.api.v0✕
- Connections
- 4 pairs of types, where a type in controllers uses a type in io.apibuilder.api.v0.
- The types involved
controllers.AnonymousOrgRequest→io.apibuilder.api.v0.Clientcontrollers.ApplicationSettings→io.apibuilder.api.v0.Clientcontrollers.IdentifiedOrgRequest→io.apibuilder.api.v0.Clientcontrollers.Members→io.apibuilder.api.v0.Client
- Direction
- controllers uses io.apibuilder.api.v0, so a change to io.apibuilder.api.v0 can break controllers, while a change to controllers can't break io.apibuilder.api.v0.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→12 controllers uses io.apibuilder.spec.v0.models✕
- Connections
- 1 pair of types, where a type in controllers uses a type in io.apibuilder.spec.v0.models.
- The types involved
controllers.Versions→io.apibuilder.spec.v0.models.Service
- Direction
- controllers uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break controllers, while a change to controllers can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→14 controllers uses models✕
- Connections
- 3 pairs of types, where a type in controllers uses a type in models.
- The types involved
controllers.AnonymousOrgRequest→models.MainTemplatecontrollers.ApplicationSettings→models.MainTemplatecontrollers.IdentifiedOrgRequest→models.MainTemplate
- Direction
- controllers uses models, so a change to models can break controllers, while a change to controllers can't break models.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→15 controllers uses lib✕
- Connections
- 2 pairs of types, where a type in controllers uses a type in lib.
- The types involved
controllers.AnonymousOrgRequest→lib.ApibuilderRequestDatacontrollers.IdentifiedOrgRequest→lib.ApibuilderRequestData
- Direction
- controllers uses lib, so a change to lib can break controllers, while a change to controllers can't break lib.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→16 controllers uses lib.Primitives✕
- Connections
- 3 pairs of types, where a type in controllers uses a type in lib.Primitives.
- The types involved
controllers.Code→lib.Primitives.Unitcontrollers.Members→lib.Primitives.Unitcontrollers.Users→lib.Primitives.Unit
- Direction
- controllers uses lib.Primitives, so a change to lib.Primitives can break controllers, while a change to controllers can't break lib.Primitives.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→18 controllers uses db✕
- Connections
- 16 pairs of types, where a type in controllers uses a type in db.
- The types involved
controllers.AnonymousRequest→db.Authorizationcontrollers.AnonymousRequest→db.InternalUsercontrollers.ApiBuilderController→db.Authorizationcontrollers.ApiBuilderController→db.InternalMembershipsDaocontrollers.ApiBuilderController→db.InternalOrganizationcontrollers.ApiBuilderController→db.InternalOrganizationsDaocontrollers.ApiBuilderController→db.InternalUsercontrollers.ApiBuilderControllerComponents→db.InternalMembershipsDaocontrollers.ApiBuilderControllerComponents→db.InternalOrganizationsDaocontrollers.ApiBuilderDefaultControllerComponents→db.InternalMembershipsDaocontrollers.ApiBuilderDefaultControllerComponents→db.InternalOrganizationsDaocontrollers.IdentifiedRequest→db.InternalUsercontrollers.Organizations→db.InternalAttributecontrollers.Users→db.InternalUsercontrollers.Versions→db.InternalOrganizationcontrollers.Versions→db.InternalUser
- Direction
- controllers uses db, so a change to db can break controllers, while a change to controllers can't break db.
- Position
- Below the diagonal: controllers uses a module listed above it, which is the healthy direction.
19→20 controllers uses io.apibuilder.api.v0.models part of a loop✕
- Connections
- 15 pairs of types, where a type in controllers uses a type in io.apibuilder.api.v0.models.
- The types involved
controllers.AnonymousOrgRequest→io.apibuilder.api.v0.models.Membershipcontrollers.AnonymousOrgRequest→io.apibuilder.api.v0.models.Organizationcontrollers.Applications→io.apibuilder.api.v0.models.AppSortBycontrollers.Applications→io.apibuilder.api.v0.models.SortOrdercontrollers.BatchDownloadApplications→io.apibuilder.api.v0.models.BatchDownloadApplicationsFormcontrollers.BatchVersionsLatest→io.apibuilder.api.v0.models.BatchVersionsLatestFormcontrollers.Code→io.apibuilder.api.v0.models.CodeFormcontrollers.IdentifiedOrgRequest→io.apibuilder.api.v0.models.Membershipcontrollers.IdentifiedOrgRequest→io.apibuilder.api.v0.models.Organizationcontrollers.Members→io.apibuilder.api.v0.models.Organizationcontrollers.Subscriptions→io.apibuilder.api.v0.models.Publicationcontrollers.Versions→io.apibuilder.api.v0.models.Errorcontrollers.Versions→io.apibuilder.api.v0.models.Originalcontrollers.Versions→io.apibuilder.api.v0.models.Versioncontrollers.Versions→io.apibuilder.api.v0.models.VersionForm
- Direction
- controllers uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break controllers, while a change to controllers can't break io.apibuilder.api.v0.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→23 controllers uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 55 pairs of types, where a type in controllers uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
controllers.AnonymousOrgRequest→io.apibuilder.avro.SchemaType.Stringcontrollers.ApiBuilderController→io.apibuilder.avro.SchemaType.Stringcontrollers.ApplicationController→io.apibuilder.avro.SchemaType.Intcontrollers.ApplicationController→io.apibuilder.avro.SchemaType.Stringcontrollers.ApplicationSettings→io.apibuilder.avro.SchemaType.Stringcontrollers.Applications→io.apibuilder.avro.SchemaType.Booleancontrollers.Applications→io.apibuilder.avro.SchemaType.Longcontrollers.Applications→io.apibuilder.avro.SchemaType.Stringcontrollers.Attributes→io.apibuilder.avro.SchemaType.Longcontrollers.Attributes→io.apibuilder.avro.SchemaType.Stringcontrollers.AttributesController→io.apibuilder.avro.SchemaType.Intcontrollers.AttributesController→io.apibuilder.avro.SchemaType.Stringcontrollers.Authentications→io.apibuilder.avro.SchemaType.Stringcontrollers.BatchDownloadApplications→io.apibuilder.avro.SchemaType.Stringcontrollers.BatchVersionsLatest→io.apibuilder.avro.SchemaType.Stringcontrollers.Changes→io.apibuilder.avro.SchemaType.Longcontrollers.Changes→io.apibuilder.avro.SchemaType.Stringcontrollers.Code→io.apibuilder.avro.SchemaType.Stringcontrollers.Domains→io.apibuilder.avro.SchemaType.Stringcontrollers.EmailVerifications→io.apibuilder.avro.SchemaType.Stringcontrollers.GeneratorServices→io.apibuilder.avro.SchemaType.Longcontrollers.GeneratorServices→io.apibuilder.avro.SchemaType.Stringcontrollers.GeneratorWithServices→io.apibuilder.avro.SchemaType.Longcontrollers.GeneratorWithServices→io.apibuilder.avro.SchemaType.Stringcontrollers.Generators→io.apibuilder.avro.SchemaType.Int
- Direction
- controllers uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break controllers, while a change to controllers can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 io.apibuilder.api.v0.models uses io.apibuilder.api.v0.models.AppSortBy✕
- Connections
- 6 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in io.apibuilder.api.v0.models.AppSortBy.
- The types involved
io.apibuilder.api.v0.models.Application→io.apibuilder.api.v0.models.AppSortBy.Visibilityio.apibuilder.api.v0.models.ApplicationForm→io.apibuilder.api.v0.models.AppSortBy.Visibilityio.apibuilder.api.v0.models.Organization→io.apibuilder.api.v0.models.AppSortBy.Visibilityio.apibuilder.api.v0.models.OrganizationForm→io.apibuilder.api.v0.models.AppSortBy.Visibilityio.apibuilder.api.v0.models.VersionForm→io.apibuilder.api.v0.models.AppSortBy.Visibilityio.apibuilder.api.v0.models.json→io.apibuilder.api.v0.models.AppSortBy.Visibility
- Direction
- io.apibuilder.api.v0.models uses io.apibuilder.api.v0.models.AppSortBy, so a change to io.apibuilder.api.v0.models.AppSortBy can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break io.apibuilder.api.v0.models.AppSortBy.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→3 io.apibuilder.api.v0.models uses io.apibuilder.common.v0.models✕
- Connections
- 19 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in io.apibuilder.common.v0.models.
- The types involved
io.apibuilder.api.v0.models.Application→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Application→io.apibuilder.common.v0.models.Referenceio.apibuilder.api.v0.models.ApplicationSummary→io.apibuilder.common.v0.models.Referenceio.apibuilder.api.v0.models.Attribute→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.AttributeValue→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Change→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Change→io.apibuilder.common.v0.models.Referenceio.apibuilder.api.v0.models.GeneratorService→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Membership→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Membership→io.apibuilder.common.v0.models.MembershipRoleio.apibuilder.api.v0.models.MembershipRequest→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.MembershipRequest→io.apibuilder.common.v0.models.MembershipRoleio.apibuilder.api.v0.models.Organization→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Subscription→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Token→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.User→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Version→io.apibuilder.common.v0.models.Auditio.apibuilder.api.v0.models.Version→io.apibuilder.common.v0.models.Referenceio.apibuilder.api.v0.models.Watch→io.apibuilder.common.v0.models.Audit
- Direction
- io.apibuilder.api.v0.models uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→4 io.apibuilder.api.v0.models uses lib.Emails.Context✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in lib.Emails.Context.
- The types involved
io.apibuilder.api.v0.models.Watch→lib.Emails.Context.Applicationio.apibuilder.api.v0.models.json→lib.Emails.Context.Application
- Direction
- io.apibuilder.api.v0.models uses lib.Emails.Context, so a change to lib.Emails.Context can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break lib.Emails.Context.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→6 io.apibuilder.api.v0.models uses util.BasicAuthorization✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in util.BasicAuthorization.
- The types involved
io.apibuilder.api.v0.models.Authentication→util.BasicAuthorization.Sessionio.apibuilder.api.v0.models.json→util.BasicAuthorization.Sessionio.apibuilder.api.v0.models.json→util.BasicAuthorization.Token
- Direction
- io.apibuilder.api.v0.models uses util.BasicAuthorization, so a change to util.BasicAuthorization can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break util.BasicAuthorization.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→7 io.apibuilder.api.v0.models uses db.Authorization✕
- Connections
- 7 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in db.Authorization.
- The types involved
io.apibuilder.api.v0.models.Authentication→db.Authorization.Userio.apibuilder.api.v0.models.Membership→db.Authorization.Userio.apibuilder.api.v0.models.MembershipRequest→db.Authorization.Userio.apibuilder.api.v0.models.Subscription→db.Authorization.Userio.apibuilder.api.v0.models.Token→db.Authorization.Userio.apibuilder.api.v0.models.Watch→db.Authorization.Userio.apibuilder.api.v0.models.json→db.Authorization.User
- Direction
- io.apibuilder.api.v0.models uses db.Authorization, so a change to db.Authorization can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break db.Authorization.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→8 io.apibuilder.api.v0.models uses io.apibuilder.api.json.v0.models✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.api.v0.models.CodeForm→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.api.v0.models.json→io.apibuilder.api.json.v0.models.Attribute
- Direction
- io.apibuilder.api.v0.models uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→12 io.apibuilder.api.v0.models uses io.apibuilder.spec.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.models uses a type in io.apibuilder.spec.v0.models.
- The types involved
io.apibuilder.api.v0.models.Version→io.apibuilder.spec.v0.models.Service
- Direction
- io.apibuilder.api.v0.models uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→15 io.apibuilder.api.v0.models uses lib✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.models uses a type in lib.
- The types involved
io.apibuilder.api.v0.models.json→lib.Validation
- Direction
- io.apibuilder.api.v0.models uses lib, so a change to lib can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break lib.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→19 io.apibuilder.api.v0.models uses controllers✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in controllers.
- The types involved
io.apibuilder.api.v0.models.json→controllers.BatchDownloadApplicationsio.apibuilder.api.v0.models.json→controllers.BatchVersionsLatestio.apibuilder.api.v0.models.json→controllers.Code
- Direction
- io.apibuilder.api.v0.models uses controllers, so a change to controllers can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break controllers.
- Position
- Below the diagonal: io.apibuilder.api.v0.models uses a module listed above it, which is the healthy direction.
20→21 io.apibuilder.api.v0.models uses io.apibuilder.generator.v0.models part of a loop✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in io.apibuilder.generator.v0.models.
- The types involved
io.apibuilder.api.v0.models.Code→io.apibuilder.generator.v0.models.Fileio.apibuilder.api.v0.models.GeneratorForm→io.apibuilder.generator.v0.models.Generatorio.apibuilder.api.v0.models.GeneratorWithService→io.apibuilder.generator.v0.models.Generator
- Direction
- io.apibuilder.api.v0.models uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break io.apibuilder.generator.v0.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→23 io.apibuilder.api.v0.models uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 50 pairs of types, where a type in io.apibuilder.api.v0.models uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.api.v0.models.Application→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.ApplicationForm→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.ApplicationMetadata→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.ApplicationMetadataVersion→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.ApplicationSummary→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.Attribute→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.AttributeForm→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.AttributeSummary→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.AttributeValue→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.AttributeValueForm→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.BatchDownloadApplicationForm→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.BatchVersionLatest→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.BatchVersionsLatestForm→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.ChangeVersion→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.CleartextToken→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.Code→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.Diff→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.v0.models.Diff→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.DiffBreaking→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.v0.models.DiffBreaking→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.DiffNonBreaking→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.v0.models.DiffNonBreaking→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.DiffUndefinedType→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.v0.models.DiffUndefinedType→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.models.Domain→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.api.v0.models uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.api.v0.models, while a change to io.apibuilder.api.v0.models can't break io.apibuilder.avro.SchemaType.
- 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.
21→3 io.apibuilder.generator.v0.models uses io.apibuilder.common.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.generator.v0.models uses a type in io.apibuilder.common.v0.models.
- The types involved
io.apibuilder.generator.v0.models.json→io.apibuilder.common.v0.models.Healthcheck
- Direction
- io.apibuilder.generator.v0.models uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break io.apibuilder.generator.v0.models, while a change to io.apibuilder.generator.v0.models can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.models uses a module listed above it, which is the healthy direction.
21→8 io.apibuilder.generator.v0.models uses io.apibuilder.api.json.v0.models✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.generator.v0.models uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.generator.v0.models.InvocationForm→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.generator.v0.models.json→io.apibuilder.api.json.v0.models.Attribute
- Direction
- io.apibuilder.generator.v0.models uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.generator.v0.models, while a change to io.apibuilder.generator.v0.models can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.models uses a module listed above it, which is the healthy direction.
21→12 io.apibuilder.generator.v0.models uses io.apibuilder.spec.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.generator.v0.models uses a type in io.apibuilder.spec.v0.models.
- The types involved
io.apibuilder.generator.v0.models.InvocationForm→io.apibuilder.spec.v0.models.Service
- Direction
- io.apibuilder.generator.v0.models uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break io.apibuilder.generator.v0.models, while a change to io.apibuilder.generator.v0.models can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.models uses a module listed above it, which is the healthy direction.
21→20 io.apibuilder.generator.v0.models uses io.apibuilder.api.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.generator.v0.models uses a type in io.apibuilder.api.v0.models.
- The types involved
io.apibuilder.generator.v0.models.json→io.apibuilder.api.v0.models.Error
- Direction
- io.apibuilder.generator.v0.models uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break io.apibuilder.generator.v0.models, while a change to io.apibuilder.generator.v0.models can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.models uses a module listed above it, which is the healthy direction.
21→23 io.apibuilder.generator.v0.models uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 7 pairs of types, where a type in io.apibuilder.generator.v0.models uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.generator.v0.models.Attribute→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.models.Error→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.models.File→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.models.Generator→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.models.Healthcheck→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.models.Invocation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.models.InvocationForm→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.generator.v0.models uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.generator.v0.models, while a change to io.apibuilder.generator.v0.models can't break io.apibuilder.avro.SchemaType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→2 io.apibuilder.avro uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 4 pairs of types, where a type in io.apibuilder.avro uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
io.apibuilder.avro.ApiBuilder→io.apibuilder.avro.ApiBuilder.Typeio.apibuilder.avro.ApiBuilder→io.apibuilder.avro.ApiBuilder.UnionTypeio.apibuilder.avro.Builder→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.avro.Builder→io.apibuilder.avro.ApiBuilder.UnionType
- Direction
- io.apibuilder.avro uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break io.apibuilder.avro, while a change to io.apibuilder.avro can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: io.apibuilder.avro uses a module listed above it, which is the healthy direction.
22→12 io.apibuilder.avro uses io.apibuilder.spec.v0.models✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.avro uses a type in io.apibuilder.spec.v0.models.
- The types involved
io.apibuilder.avro.AvroIdlServiceValidator→io.apibuilder.spec.v0.models.Serviceio.apibuilder.avro.Builder→io.apibuilder.spec.v0.models.Serviceio.apibuilder.avro.Parser→io.apibuilder.spec.v0.models.Service
- Direction
- io.apibuilder.avro uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break io.apibuilder.avro, while a change to io.apibuilder.avro can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: io.apibuilder.avro uses a module listed above it, which is the healthy direction.
22→15 io.apibuilder.avro uses lib✕
- Connections
- 4 pairs of types, where a type in io.apibuilder.avro uses a type in lib.
- The types involved
io.apibuilder.avro.AvroIdlServiceValidator→lib.ServiceConfigurationio.apibuilder.avro.AvroIdlServiceValidator→lib.ServiceValidatorio.apibuilder.avro.Builder→lib.ServiceConfigurationio.apibuilder.avro.Parser→lib.ServiceConfiguration
- Direction
- io.apibuilder.avro uses lib, so a change to lib can break io.apibuilder.avro, while a change to io.apibuilder.avro can't break lib.
- Position
- Below the diagonal: io.apibuilder.avro uses a module listed above it, which is the healthy direction.
22→16 io.apibuilder.avro uses lib.Primitives✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.avro uses a type in lib.Primitives.
- The types involved
io.apibuilder.avro.Builder→lib.Primitives.Unitio.apibuilder.avro.Parser→lib.Primitives.Unit
- Direction
- io.apibuilder.avro uses lib.Primitives, so a change to lib.Primitives can break io.apibuilder.avro, while a change to io.apibuilder.avro can't break lib.Primitives.
- Position
- Below the diagonal: io.apibuilder.avro uses a module listed above it, which is the healthy direction.
22→21 io.apibuilder.avro uses io.apibuilder.generator.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.avro uses a type in io.apibuilder.generator.v0.models.
- The types involved
io.apibuilder.avro.Parser→io.apibuilder.generator.v0.models.File
- Direction
- io.apibuilder.avro uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break io.apibuilder.avro, while a change to io.apibuilder.avro can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: io.apibuilder.avro uses a module listed above it, which is the healthy direction.
22→23 io.apibuilder.avro uses io.apibuilder.avro.SchemaType part of a loop✕
- Connections
- 6 pairs of types, where a type in io.apibuilder.avro uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.avro.ApiBuilder→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.avro.AvroIdlServiceValidator→io.apibuilder.avro.SchemaType.Stringio.apibuilder.avro.Builder→io.apibuilder.avro.SchemaType.Intio.apibuilder.avro.Builder→io.apibuilder.avro.SchemaType.Stringio.apibuilder.avro.Parser→io.apibuilder.avro.SchemaType.Stringio.apibuilder.avro.Util→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.avro uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.avro, while a change to io.apibuilder.avro can't break io.apibuilder.avro.SchemaType.
- 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→22 io.apibuilder.avro.SchemaType uses io.apibuilder.avro✕
- Connections
- 14 pairs of types, where a type in io.apibuilder.avro.SchemaType uses a type in io.apibuilder.avro.
- The types involved
io.apibuilder.avro.SchemaType.Array→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Boolean→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Bytes→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Double→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Enum→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Fixed→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Float→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Int→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Long→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Map→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Null→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Record→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.String→io.apibuilder.avro.SchemaTypeio.apibuilder.avro.SchemaType.Union→io.apibuilder.avro.SchemaType
- Direction
- io.apibuilder.avro.SchemaType uses io.apibuilder.avro, so a change to io.apibuilder.avro can break io.apibuilder.avro.SchemaType, while a change to io.apibuilder.avro.SchemaType can't break io.apibuilder.avro.
- Position
- Below the diagonal: io.apibuilder.avro.SchemaType uses a module listed above it, which is the healthy direction.
24→2 builder.api_json.templates uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 2 pairs of types, where a type in builder.api_json.templates uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
builder.api_json.templates.ModelMerge→io.apibuilder.avro.ApiBuilder.Fieldbuilder.api_json.templates.RenameTypes→io.apibuilder.avro.ApiBuilder.Field
- Direction
- builder.api_json.templates uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break builder.api_json.templates, while a change to builder.api_json.templates can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: builder.api_json.templates uses a module listed above it, which is the healthy direction.
24→8 builder.api_json.templates uses io.apibuilder.api.json.v0.models✕
- Connections
- 25 pairs of types, where a type in builder.api_json.templates uses a type in io.apibuilder.api.json.v0.models.
- The types involved
builder.api_json.templates.AttributeMerge→io.apibuilder.api.json.v0.models.Attributebuilder.api_json.templates.HeaderMerge→io.apibuilder.api.json.v0.models.Headerbuilder.api_json.templates.JsMerge→io.apibuilder.api.json.v0.models.ApiJsonbuilder.api_json.templates.JsMerge→io.apibuilder.api.json.v0.models.Modelbuilder.api_json.templates.JsMerge→io.apibuilder.api.json.v0.models.Templatesbuilder.api_json.templates.ModelMerge→io.apibuilder.api.json.v0.models.Interfacebuilder.api_json.templates.ModelMerge→io.apibuilder.api.json.v0.models.Modelbuilder.api_json.templates.ModelMerge→io.apibuilder.api.json.v0.models.TemplateDeclarationbuilder.api_json.templates.ModelMergeData→io.apibuilder.api.json.v0.models.Interfacebuilder.api_json.templates.ModelMergeData→io.apibuilder.api.json.v0.models.Modelbuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.ApiJsonbuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.Bodybuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.Interfacebuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.Modelbuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.Operationbuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.Parameterbuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.Resourcebuilder.api_json.templates.RenameTypes→io.apibuilder.api.json.v0.models.Responsebuilder.api_json.templates.ResourceMerge→io.apibuilder.api.json.v0.models.Operationbuilder.api_json.templates.ResourceMerge→io.apibuilder.api.json.v0.models.Parameterbuilder.api_json.templates.ResourceMerge→io.apibuilder.api.json.v0.models.Resourcebuilder.api_json.templates.ResourceMerge→io.apibuilder.api.json.v0.models.Responsebuilder.api_json.templates.ResourceMerge→io.apibuilder.api.json.v0.models.TemplateDeclarationbuilder.api_json.templates.ResourceMergeData→io.apibuilder.api.json.v0.models.Resourcebuilder.api_json.templates.TemplateMerge→io.apibuilder.api.json.v0.models.TemplateDeclaration
- Direction
- builder.api_json.templates uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break builder.api_json.templates, while a change to builder.api_json.templates can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: builder.api_json.templates uses a module listed above it, which is the healthy direction.
24→16 builder.api_json.templates uses lib.Primitives✕
- Connections
- 2 pairs of types, where a type in builder.api_json.templates uses a type in lib.Primitives.
- The types involved
builder.api_json.templates.JsMerge→lib.Primitives.Unitbuilder.api_json.templates.ModelMerge→lib.Primitives.Unit
- Direction
- builder.api_json.templates uses lib.Primitives, so a change to lib.Primitives can break builder.api_json.templates, while a change to builder.api_json.templates can't break lib.Primitives.
- Position
- Below the diagonal: builder.api_json.templates uses a module listed above it, which is the healthy direction.
24→23 builder.api_json.templates uses io.apibuilder.avro.SchemaType✕
- Connections
- 19 pairs of types, where a type in builder.api_json.templates uses a type in io.apibuilder.avro.SchemaType.
- The types involved
builder.api_json.templates.ArrayMerge→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.JsMerge→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.JsMerge→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.MapMerge→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.MapMerge→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.ModelMerge→io.apibuilder.avro.SchemaType.Booleanbuilder.api_json.templates.ModelMerge→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.ModelMerge→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.ModelMergeData→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.ModelMergeData→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.RenameTypes→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.RenameTypes→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.ResourceMerge→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.ResourceMerge→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.ResourceMergeData→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.ResourceMergeData→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.TemplateMerge→io.apibuilder.avro.SchemaType.Mapbuilder.api_json.templates.TemplateMerge→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.templates.TemplateTypeCast→io.apibuilder.avro.SchemaType.String
- Direction
- builder.api_json.templates uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break builder.api_json.templates, while a change to builder.api_json.templates can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: builder.api_json.templates uses a module listed above it, which is the healthy direction.
25→12 core uses io.apibuilder.spec.v0.models✕
- Connections
- 2 pairs of types, where a type in core uses a type in io.apibuilder.spec.v0.models.
- The types involved
core.Importer→io.apibuilder.spec.v0.models.Servicecore.ServiceFetcher→io.apibuilder.spec.v0.models.Service
- Direction
- core uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break core, while a change to core can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
25→15 core uses lib✕
- Connections
- 2 pairs of types, where a type in core uses a type in lib.
- The types involved
core.TypeValidator→lib.Kindcore.TypesProvider→lib.DatatypeResolver
- Direction
- core uses lib, so a change to lib can break core, while a change to core can't break lib.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
25→16 core uses lib.Primitives✕
- Connections
- 2 pairs of types, where a type in core uses a type in lib.Primitives.
- The types involved
core.DuplicateJsonParser→lib.Primitives.Unitcore.Importer→lib.Primitives.Unit
- Direction
- core uses lib.Primitives, so a change to lib.Primitives can break core, while a change to core can't break lib.Primitives.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
25→23 core uses io.apibuilder.avro.SchemaType✕
- Connections
- 15 pairs of types, where a type in core uses a type in io.apibuilder.avro.SchemaType.
- The types involved
core.DuplicateJsonParser→io.apibuilder.avro.SchemaType.Stringcore.Importer→io.apibuilder.avro.SchemaType.Stringcore.ServiceFetcher→io.apibuilder.avro.SchemaType.Stringcore.TypeValidator→io.apibuilder.avro.SchemaType.Stringcore.TypesProviderEnum→io.apibuilder.avro.SchemaType.Stringcore.TypesProviderField→io.apibuilder.avro.SchemaType.Stringcore.TypesProviderInterface→io.apibuilder.avro.SchemaType.Stringcore.TypesProviderModel→io.apibuilder.avro.SchemaType.Stringcore.TypesProviderUnion→io.apibuilder.avro.SchemaType.Stringcore.TypesProviderUnionType→io.apibuilder.avro.SchemaType.Stringcore.TypesProviderWithName→io.apibuilder.avro.SchemaType.Stringcore.Util→io.apibuilder.avro.SchemaType.Booleancore.Util→io.apibuilder.avro.SchemaType.Enumcore.Util→io.apibuilder.avro.SchemaType.Stringcore.VersionMigration→io.apibuilder.avro.SchemaType.Boolean
- Direction
- core uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break core, while a change to core can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
26→5 db.generated.generators uses lib.query✕
- Connections
- 4 pairs of types, where a type in db.generated.generators uses a type in lib.query.
- The types involved
db.generated.generators.BaseGeneratorsDao→lib.query.Querydb.generated.generators.BaseServicesDao→lib.query.Querydb.generated.generators.GeneratorsDao→lib.query.Querydb.generated.generators.ServicesDao→lib.query.Query
- Direction
- db.generated.generators uses lib.query, so a change to lib.query can break db.generated.generators, while a change to db.generated.generators can't break lib.query.
- Position
- Below the diagonal: db.generated.generators uses a module listed above it, which is the healthy direction.
26→12 db.generated.generators uses io.apibuilder.spec.v0.models✕
- Connections
- 2 pairs of types, where a type in db.generated.generators uses a type in io.apibuilder.spec.v0.models.
- The types involved
db.generated.generators.BaseServicesDao→io.apibuilder.spec.v0.models.Servicedb.generated.generators.ServicesDao→io.apibuilder.spec.v0.models.Service
- Direction
- db.generated.generators uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break db.generated.generators, while a change to db.generated.generators can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: db.generated.generators uses a module listed above it, which is the healthy direction.
26→16 db.generated.generators uses lib.Primitives✕
- Connections
- 2 pairs of types, where a type in db.generated.generators uses a type in lib.Primitives.
- The types involved
db.generated.generators.GeneratorsDao→lib.Primitives.Unitdb.generated.generators.ServicesDao→lib.Primitives.Unit
- Direction
- db.generated.generators uses lib.Primitives, so a change to lib.Primitives can break db.generated.generators, while a change to db.generated.generators can't break lib.Primitives.
- Position
- Below the diagonal: db.generated.generators uses a module listed above it, which is the healthy direction.
26→20 db.generated.generators uses io.apibuilder.api.v0.models✕
- Connections
- 2 pairs of types, where a type in db.generated.generators uses a type in io.apibuilder.api.v0.models.
- The types involved
db.generated.generators.Generator→io.apibuilder.api.v0.models.GeneratorFormdb.generated.generators.GeneratorsDao→io.apibuilder.api.v0.models.GeneratorForm
- Direction
- db.generated.generators uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break db.generated.generators, while a change to db.generated.generators can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: db.generated.generators uses a module listed above it, which is the healthy direction.
26→21 db.generated.generators uses io.apibuilder.generator.v0.models✕
- Connections
- 2 pairs of types, where a type in db.generated.generators uses a type in io.apibuilder.generator.v0.models.
- The types involved
db.generated.generators.BaseGeneratorsDao→io.apibuilder.generator.v0.models.Generatordb.generated.generators.GeneratorsDao→io.apibuilder.generator.v0.models.Generator
- Direction
- db.generated.generators uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break db.generated.generators, while a change to db.generated.generators can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: db.generated.generators uses a module listed above it, which is the healthy direction.
26→23 db.generated.generators uses io.apibuilder.avro.SchemaType✕
- Connections
- 8 pairs of types, where a type in db.generated.generators uses a type in io.apibuilder.avro.SchemaType.
- The types involved
db.generated.generators.BaseGeneratorsDao→io.apibuilder.avro.SchemaType.Longdb.generated.generators.BaseServicesDao→io.apibuilder.avro.SchemaType.Longdb.generated.generators.Generator→io.apibuilder.avro.SchemaType.Stringdb.generated.generators.GeneratorForm→io.apibuilder.avro.SchemaType.Stringdb.generated.generators.GeneratorsTable→io.apibuilder.avro.SchemaType.Stringdb.generated.generators.Service→io.apibuilder.avro.SchemaType.Stringdb.generated.generators.ServiceForm→io.apibuilder.avro.SchemaType.Stringdb.generated.generators.ServicesTable→io.apibuilder.avro.SchemaType.String
- Direction
- db.generated.generators uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break db.generated.generators, while a change to db.generated.generators can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: db.generated.generators uses a module listed above it, which is the healthy direction.
27→8 io.apibuilder.api.json.v0.Bindables uses io.apibuilder.api.json.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.json.v0.Bindables uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.api.json.v0.Bindables.Models→io.apibuilder.api.json.v0.models.ParameterLocation
- Direction
- io.apibuilder.api.json.v0.Bindables uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.api.json.v0.Bindables, while a change to io.apibuilder.api.json.v0.Bindables can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.json.v0.Bindables uses a module listed above it, which is the healthy direction.
27→23 io.apibuilder.api.json.v0.Bindables uses io.apibuilder.avro.SchemaType✕
- Connections
- 6 pairs of types, where a type in io.apibuilder.api.json.v0.Bindables uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.api.json.v0.Bindables.ApibuilderPathBindable→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.Bindables.ApibuilderQueryStringBindable→io.apibuilder.avro.SchemaType.Mapio.apibuilder.api.json.v0.Bindables.ApibuilderQueryStringBindable→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.Bindables.ApibuilderTypeConverter→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.Bindables.Core→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.json.v0.Bindables.Models→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.api.json.v0.Bindables uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.api.json.v0.Bindables, while a change to io.apibuilder.api.json.v0.Bindables can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: io.apibuilder.api.json.v0.Bindables uses a module listed above it, which is the healthy direction.
28→3 io.apibuilder.api.v0.Client uses io.apibuilder.common.v0.models✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.api.v0.Client uses a type in io.apibuilder.common.v0.models.
- The types involved
io.apibuilder.api.v0.Client.Healthchecks→io.apibuilder.common.v0.models.Healthcheckio.apibuilder.api.v0.Client.MembershipRequests→io.apibuilder.common.v0.models.MembershipRoleio.apibuilder.api.v0.Client.Memberships→io.apibuilder.common.v0.models.MembershipRole
- Direction
- io.apibuilder.api.v0.Client uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→4 io.apibuilder.api.v0.Client uses lib.Emails.Context✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.Client uses a type in lib.Emails.Context.
- The types involved
io.apibuilder.api.v0.Client.Applications→lib.Emails.Context.Application
- Direction
- io.apibuilder.api.v0.Client uses lib.Emails.Context, so a change to lib.Emails.Context can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break lib.Emails.Context.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→6 io.apibuilder.api.v0.Client uses util.BasicAuthorization✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.Client uses a type in util.BasicAuthorization.
- The types involved
io.apibuilder.api.v0.Client.Tokens→util.BasicAuthorization.Token
- Direction
- io.apibuilder.api.v0.Client uses util.BasicAuthorization, so a change to util.BasicAuthorization can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break util.BasicAuthorization.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→7 io.apibuilder.api.v0.Client uses db.Authorization✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.Client uses a type in db.Authorization.
- The types involved
io.apibuilder.api.v0.Client.Users→db.Authorization.User
- Direction
- io.apibuilder.api.v0.Client uses db.Authorization, so a change to db.Authorization can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break db.Authorization.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→8 io.apibuilder.api.v0.Client uses io.apibuilder.api.json.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.Client uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.api.v0.Client.Attributes→io.apibuilder.api.json.v0.models.Attribute
- Direction
- io.apibuilder.api.v0.Client uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→15 io.apibuilder.api.v0.Client uses lib✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.Client uses a type in lib.
- The types involved
io.apibuilder.api.v0.Client.Validations→lib.Validation
- Direction
- io.apibuilder.api.v0.Client uses lib, so a change to lib can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break lib.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→16 io.apibuilder.api.v0.Client uses lib.Primitives✕
- Connections
- 13 pairs of types, where a type in io.apibuilder.api.v0.Client uses a type in lib.Primitives.
- The types involved
io.apibuilder.api.v0.Client.Applications→lib.Primitives.Unitio.apibuilder.api.v0.Client.Attributes→lib.Primitives.Unitio.apibuilder.api.v0.Client.Domains→lib.Primitives.Unitio.apibuilder.api.v0.Client.EmailVerificationConfirmationForms→lib.Primitives.Unitio.apibuilder.api.v0.Client.GeneratorServices→lib.Primitives.Unitio.apibuilder.api.v0.Client.MembershipRequests→lib.Primitives.Unitio.apibuilder.api.v0.Client.Memberships→lib.Primitives.Unitio.apibuilder.api.v0.Client.Organizations→lib.Primitives.Unitio.apibuilder.api.v0.Client.PasswordResetRequests→lib.Primitives.Unitio.apibuilder.api.v0.Client.Subscriptions→lib.Primitives.Unitio.apibuilder.api.v0.Client.Tokens→lib.Primitives.Unitio.apibuilder.api.v0.Client.Versions→lib.Primitives.Unitio.apibuilder.api.v0.Client.Watches→lib.Primitives.Unit
- Direction
- io.apibuilder.api.v0.Client uses lib.Primitives, so a change to lib.Primitives can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break lib.Primitives.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→19 io.apibuilder.api.v0.Client uses controllers✕
- Connections
- 24 pairs of types, where a type in io.apibuilder.api.v0.Client uses a type in controllers.
- The types involved
io.apibuilder.api.v0.Client.Applications→controllers.Applicationsio.apibuilder.api.v0.Client.Attributes→controllers.Attributesio.apibuilder.api.v0.Client.Authentications→controllers.Authenticationsio.apibuilder.api.v0.Client.BatchDownloadApplications→controllers.BatchDownloadApplicationsio.apibuilder.api.v0.Client.BatchVersionsLatest→controllers.BatchVersionsLatestio.apibuilder.api.v0.Client.Changes→controllers.Changesio.apibuilder.api.v0.Client.Code→controllers.Codeio.apibuilder.api.v0.Client.Domains→controllers.Domainsio.apibuilder.api.v0.Client.EmailVerificationConfirmationForms→controllers.EmailVerificationConfirmationFormsio.apibuilder.api.v0.Client.GeneratorServices→controllers.GeneratorServicesio.apibuilder.api.v0.Client.GeneratorWithServices→controllers.GeneratorWithServicesio.apibuilder.api.v0.Client.Healthchecks→controllers.Healthchecksio.apibuilder.api.v0.Client.Items→controllers.Itemsio.apibuilder.api.v0.Client.MembershipRequests→controllers.MembershipRequestsio.apibuilder.api.v0.Client.Memberships→controllers.Membershipsio.apibuilder.api.v0.Client.Organizations→controllers.Organizationsio.apibuilder.api.v0.Client.PasswordResetRequests→controllers.PasswordResetRequestsio.apibuilder.api.v0.Client.PasswordResets→controllers.PasswordResetsio.apibuilder.api.v0.Client.Subscriptions→controllers.Subscriptionsio.apibuilder.api.v0.Client.Tokens→controllers.Tokensio.apibuilder.api.v0.Client.Users→controllers.Usersio.apibuilder.api.v0.Client.Validations→controllers.Validationsio.apibuilder.api.v0.Client.Versions→controllers.Versionsio.apibuilder.api.v0.Client.Watches→controllers.Watches
- Direction
- io.apibuilder.api.v0.Client uses controllers, so a change to controllers can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break controllers.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→20 io.apibuilder.api.v0.Client uses io.apibuilder.api.v0.models✕
- Connections
- 38 pairs of types, where a type in io.apibuilder.api.v0.Client uses a type in io.apibuilder.api.v0.models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.api.v0.Client.Applications→io.apibuilder.api.v0.models.AppSortByio.apibuilder.api.v0.Client.Applications→io.apibuilder.api.v0.models.ApplicationFormio.apibuilder.api.v0.Client.Applications→io.apibuilder.api.v0.models.ApplicationMetadataVersionio.apibuilder.api.v0.Client.Applications→io.apibuilder.api.v0.models.MoveFormio.apibuilder.api.v0.Client.Applications→io.apibuilder.api.v0.models.SortOrderio.apibuilder.api.v0.Client.Attributes→io.apibuilder.api.v0.models.AttributeFormio.apibuilder.api.v0.Client.Authentications→io.apibuilder.api.v0.models.Authenticationio.apibuilder.api.v0.Client.BatchDownloadApplications→io.apibuilder.api.v0.models.BatchDownloadApplicationsFormio.apibuilder.api.v0.Client.BatchVersionsLatest→io.apibuilder.api.v0.models.BatchVersionsLatestFormio.apibuilder.api.v0.Client.Changes→io.apibuilder.api.v0.models.Changeio.apibuilder.api.v0.Client.Code→io.apibuilder.api.v0.models.CodeFormio.apibuilder.api.v0.Client.Domains→io.apibuilder.api.v0.models.Domainio.apibuilder.api.v0.Client.EmailVerificationConfirmationForms→io.apibuilder.api.v0.models.EmailVerificationConfirmationFormio.apibuilder.api.v0.Client.GeneratorServices→io.apibuilder.api.v0.models.GeneratorServiceio.apibuilder.api.v0.Client.GeneratorServices→io.apibuilder.api.v0.models.GeneratorServiceFormio.apibuilder.api.v0.Client.GeneratorWithServices→io.apibuilder.api.v0.models.GeneratorWithServiceio.apibuilder.api.v0.Client.Items→io.apibuilder.api.v0.models.Itemio.apibuilder.api.v0.Client.MembershipRequests→io.apibuilder.api.v0.models.MembershipRequestio.apibuilder.api.v0.Client.Memberships→io.apibuilder.api.v0.models.Membershipio.apibuilder.api.v0.Client.Organizations→io.apibuilder.api.v0.models.AttributeValueio.apibuilder.api.v0.Client.Organizations→io.apibuilder.api.v0.models.AttributeValueFormio.apibuilder.api.v0.Client.Organizations→io.apibuilder.api.v0.models.Organizationio.apibuilder.api.v0.Client.Organizations→io.apibuilder.api.v0.models.OrganizationFormio.apibuilder.api.v0.Client.PasswordResetRequests→io.apibuilder.api.v0.models.PasswordResetRequestio.apibuilder.api.v0.Client.PasswordResets→io.apibuilder.api.v0.models.Authentication
- Direction
- io.apibuilder.api.v0.Client uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→21 io.apibuilder.api.v0.Client uses io.apibuilder.generator.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.api.v0.Client uses a type in io.apibuilder.generator.v0.models.
- The types involved
io.apibuilder.api.v0.Client.Code→io.apibuilder.generator.v0.models.InvocationForm
- Direction
- io.apibuilder.api.v0.Client uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
28→23 io.apibuilder.api.v0.Client uses io.apibuilder.avro.SchemaType✕
- Connections
- 35 pairs of types, where a type in io.apibuilder.api.v0.Client uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
io.apibuilder.api.v0.Client.Applications→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.api.v0.Client.Applications→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.Applications→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Attributes→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.Attributes→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Authentications→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.BatchDownloadApplications→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.BatchVersionsLatest→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Changes→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.Changes→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Code→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Domains→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.GeneratorServices→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.GeneratorServices→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.GeneratorWithServices→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.GeneratorWithServices→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Items→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.Items→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.MembershipRequests→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.MembershipRequests→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Memberships→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.Memberships→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Organizations→io.apibuilder.avro.SchemaType.Longio.apibuilder.api.v0.Client.Organizations→io.apibuilder.avro.SchemaType.Stringio.apibuilder.api.v0.Client.Subscriptions→io.apibuilder.avro.SchemaType.Long
- Direction
- io.apibuilder.api.v0.Client uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.api.v0.Client, while a change to io.apibuilder.api.v0.Client can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: io.apibuilder.api.v0.Client uses a module listed above it, which is the healthy direction.
29→3 io.apibuilder.generator.v0.Client uses io.apibuilder.common.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.generator.v0.Client uses a type in io.apibuilder.common.v0.models.
- The types involved
io.apibuilder.generator.v0.Client.Healthchecks→io.apibuilder.common.v0.models.Healthcheck
- Direction
- io.apibuilder.generator.v0.Client uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break io.apibuilder.generator.v0.Client, while a change to io.apibuilder.generator.v0.Client can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.Client uses a module listed above it, which is the healthy direction.
29→19 io.apibuilder.generator.v0.Client uses controllers✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.generator.v0.Client uses a type in controllers.
- The types involved
io.apibuilder.generator.v0.Client.Generators→controllers.Generatorsio.apibuilder.generator.v0.Client.Healthchecks→controllers.Healthchecks
- Direction
- io.apibuilder.generator.v0.Client uses controllers, so a change to controllers can break io.apibuilder.generator.v0.Client, while a change to io.apibuilder.generator.v0.Client can't break controllers.
- Position
- Below the diagonal: io.apibuilder.generator.v0.Client uses a module listed above it, which is the healthy direction.
29→21 io.apibuilder.generator.v0.Client uses io.apibuilder.generator.v0.models✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.generator.v0.Client uses a type in io.apibuilder.generator.v0.models.
- The types involved
io.apibuilder.generator.v0.Client.Generators→io.apibuilder.generator.v0.models.Generatorio.apibuilder.generator.v0.Client.Invocations→io.apibuilder.generator.v0.models.Invocationio.apibuilder.generator.v0.Client.Invocations→io.apibuilder.generator.v0.models.InvocationForm
- Direction
- io.apibuilder.generator.v0.Client uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break io.apibuilder.generator.v0.Client, while a change to io.apibuilder.generator.v0.Client can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.Client uses a module listed above it, which is the healthy direction.
29→23 io.apibuilder.generator.v0.Client uses io.apibuilder.avro.SchemaType✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.generator.v0.Client uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.generator.v0.Client.Generators→io.apibuilder.avro.SchemaType.Intio.apibuilder.generator.v0.Client.Generators→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.Client.Invocations→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.generator.v0.Client uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.generator.v0.Client, while a change to io.apibuilder.generator.v0.Client can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: io.apibuilder.generator.v0.Client uses a module listed above it, which is the healthy direction.
30→2 io.apibuilder.spec.v0.mock uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.spec.v0.mock uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
io.apibuilder.spec.v0.mock.Factories→io.apibuilder.avro.ApiBuilder.Fieldio.apibuilder.spec.v0.mock.Factories→io.apibuilder.avro.ApiBuilder.UnionType
- Direction
- io.apibuilder.spec.v0.mock uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break io.apibuilder.spec.v0.mock, while a change to io.apibuilder.spec.v0.mock can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: io.apibuilder.spec.v0.mock uses a module listed above it, which is the healthy direction.
30→4 io.apibuilder.spec.v0.mock uses lib.Emails.Context✕
- Connections
- 1 pair of types, where a type in io.apibuilder.spec.v0.mock uses a type in lib.Emails.Context.
- The types involved
io.apibuilder.spec.v0.mock.Factories→lib.Emails.Context.Application
- Direction
- io.apibuilder.spec.v0.mock uses lib.Emails.Context, so a change to lib.Emails.Context can break io.apibuilder.spec.v0.mock, while a change to io.apibuilder.spec.v0.mock can't break lib.Emails.Context.
- Position
- Below the diagonal: io.apibuilder.spec.v0.mock uses a module listed above it, which is the healthy direction.
30→8 io.apibuilder.spec.v0.mock uses io.apibuilder.api.json.v0.models✕
- Connections
- 17 pairs of types, where a type in io.apibuilder.spec.v0.mock uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Annotationio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Bodyio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Contactio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Deprecationio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.EnumValueio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Headerio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Importio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Infoio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Interfaceio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Licenseio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Modelio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Operationio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Parameterio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.ParameterLocationio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Resourceio.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.json.v0.models.Response
- Direction
- io.apibuilder.spec.v0.mock uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.spec.v0.mock, while a change to io.apibuilder.spec.v0.mock can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.spec.v0.mock uses a module listed above it, which is the healthy direction.
30→12 io.apibuilder.spec.v0.mock uses io.apibuilder.spec.v0.models✕
- Connections
- 5 pairs of types, where a type in io.apibuilder.spec.v0.mock uses a type in io.apibuilder.spec.v0.models.
- The types involved
io.apibuilder.spec.v0.mock.Factories→io.apibuilder.spec.v0.models.Apidocio.apibuilder.spec.v0.mock.Factories→io.apibuilder.spec.v0.models.Methodio.apibuilder.spec.v0.mock.Factories→io.apibuilder.spec.v0.models.ResponseCodeio.apibuilder.spec.v0.mock.Factories→io.apibuilder.spec.v0.models.ResponseCodeOptionio.apibuilder.spec.v0.mock.Factories→io.apibuilder.spec.v0.models.Service
- Direction
- io.apibuilder.spec.v0.mock uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break io.apibuilder.spec.v0.mock, while a change to io.apibuilder.spec.v0.mock can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: io.apibuilder.spec.v0.mock uses a module listed above it, which is the healthy direction.
30→20 io.apibuilder.spec.v0.mock uses io.apibuilder.api.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.spec.v0.mock uses a type in io.apibuilder.api.v0.models.
- The types involved
io.apibuilder.spec.v0.mock.Factories→io.apibuilder.api.v0.models.Organization
- Direction
- io.apibuilder.spec.v0.mock uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break io.apibuilder.spec.v0.mock, while a change to io.apibuilder.spec.v0.mock can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: io.apibuilder.spec.v0.mock uses a module listed above it, which is the healthy direction.
30→23 io.apibuilder.spec.v0.mock uses io.apibuilder.avro.SchemaType✕
- Connections
- 4 pairs of types, where a type in io.apibuilder.spec.v0.mock uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.spec.v0.mock.Factories→io.apibuilder.avro.SchemaType.Enumio.apibuilder.spec.v0.mock.Factories→io.apibuilder.avro.SchemaType.Intio.apibuilder.spec.v0.mock.Factories→io.apibuilder.avro.SchemaType.Stringio.apibuilder.spec.v0.mock.Factories→io.apibuilder.avro.SchemaType.Union
- Direction
- io.apibuilder.spec.v0.mock uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.spec.v0.mock, while a change to io.apibuilder.spec.v0.mock can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: io.apibuilder.spec.v0.mock uses a module listed above it, which is the healthy direction.
31→2 io.apibuilder.swagger.translators uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 1 pair of types, where a type in io.apibuilder.swagger.translators uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
io.apibuilder.swagger.translators.Field→io.apibuilder.avro.ApiBuilder.Field
- Direction
- io.apibuilder.swagger.translators uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break io.apibuilder.swagger.translators, while a change to io.apibuilder.swagger.translators can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: io.apibuilder.swagger.translators uses a module listed above it, which is the healthy direction.
31→8 io.apibuilder.swagger.translators uses io.apibuilder.api.json.v0.models✕
- Connections
- 8 pairs of types, where a type in io.apibuilder.swagger.translators uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.swagger.translators.Body→io.apibuilder.api.json.v0.models.Bodyio.apibuilder.swagger.translators.Model→io.apibuilder.api.json.v0.models.Modelio.apibuilder.swagger.translators.Operation→io.apibuilder.api.json.v0.models.Operationio.apibuilder.swagger.translators.Parameter→io.apibuilder.api.json.v0.models.Parameterio.apibuilder.swagger.translators.Resolver→io.apibuilder.api.json.v0.models.Modelio.apibuilder.swagger.translators.Resource→io.apibuilder.api.json.v0.models.Modelio.apibuilder.swagger.translators.Resource→io.apibuilder.api.json.v0.models.Resourceio.apibuilder.swagger.translators.Response→io.apibuilder.api.json.v0.models.Response
- Direction
- io.apibuilder.swagger.translators uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.swagger.translators, while a change to io.apibuilder.swagger.translators can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.swagger.translators uses a module listed above it, which is the healthy direction.
31→10 io.apibuilder.swagger.translators uses io.apibuilder.api.json.v0.models.ParameterLocation✕
- Connections
- 1 pair of types, where a type in io.apibuilder.swagger.translators uses a type in io.apibuilder.api.json.v0.models.ParameterLocation.
- The types involved
io.apibuilder.swagger.translators.Resource→io.apibuilder.api.json.v0.models.ParameterLocation.Path
- Direction
- io.apibuilder.swagger.translators uses io.apibuilder.api.json.v0.models.ParameterLocation, so a change to io.apibuilder.api.json.v0.models.ParameterLocation can break io.apibuilder.swagger.translators, while a change to io.apibuilder.swagger.translators can't break io.apibuilder.api.json.v0.models.ParameterLocation.
- Position
- Below the diagonal: io.apibuilder.swagger.translators uses a module listed above it, which is the healthy direction.
31→12 io.apibuilder.swagger.translators uses io.apibuilder.spec.v0.models✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.swagger.translators uses a type in io.apibuilder.spec.v0.models.
- The types involved
io.apibuilder.swagger.translators.Operation→io.apibuilder.spec.v0.models.Methodio.apibuilder.swagger.translators.Parameter→io.apibuilder.spec.v0.models.Method
- Direction
- io.apibuilder.swagger.translators uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break io.apibuilder.swagger.translators, while a change to io.apibuilder.swagger.translators can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: io.apibuilder.swagger.translators uses a module listed above it, which is the healthy direction.
31→16 io.apibuilder.swagger.translators uses lib.Primitives✕
- Connections
- 1 pair of types, where a type in io.apibuilder.swagger.translators uses a type in lib.Primitives.
- The types involved
io.apibuilder.swagger.translators.Field→lib.Primitives.Integer
- Direction
- io.apibuilder.swagger.translators uses lib.Primitives, so a change to lib.Primitives can break io.apibuilder.swagger.translators, while a change to io.apibuilder.swagger.translators can't break lib.Primitives.
- Position
- Below the diagonal: io.apibuilder.swagger.translators uses a module listed above it, which is the healthy direction.
31→23 io.apibuilder.swagger.translators uses io.apibuilder.avro.SchemaType✕
- Connections
- 11 pairs of types, where a type in io.apibuilder.swagger.translators uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.swagger.translators.BaseUrl→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.ExternalDoc→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.Field→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.Model→io.apibuilder.avro.SchemaType.Enumio.apibuilder.swagger.translators.Model→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.Operation→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.Parameter→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.Resolver→io.apibuilder.avro.SchemaType.Enumio.apibuilder.swagger.translators.Resolver→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.Resource→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.translators.Response→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.swagger.translators uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.swagger.translators, while a change to io.apibuilder.swagger.translators can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: io.apibuilder.swagger.translators uses a module listed above it, which is the healthy direction.
32→12 builder.api_json uses io.apibuilder.spec.v0.models✕
- Connections
- 3 pairs of types, where a type in builder.api_json uses a type in io.apibuilder.spec.v0.models.
- The types involved
builder.api_json.ApiJsonServiceValidator→io.apibuilder.spec.v0.models.Servicebuilder.api_json.ServiceBuilder→io.apibuilder.spec.v0.models.Servicebuilder.api_json.ServiceJsonServiceValidator→io.apibuilder.spec.v0.models.Service
- Direction
- builder.api_json uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break builder.api_json, while a change to builder.api_json can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: builder.api_json uses a module listed above it, which is the healthy direction.
32→15 builder.api_json uses lib✕
- Connections
- 8 pairs of types, where a type in builder.api_json uses a type in lib.
- The types involved
builder.api_json.ApiJsonServiceValidator→lib.ServiceConfigurationbuilder.api_json.ApiJsonServiceValidator→lib.ServiceValidatorbuilder.api_json.ApiJsonServiceValidator→lib.ValidatedHelpersbuilder.api_json.AutoCreateUnionTypeModels→lib.DatatypeResolverbuilder.api_json.ServiceBuilder→lib.ServiceConfigurationbuilder.api_json.ServiceBuilder→lib.ValidatedHelpersbuilder.api_json.ServiceJsonServiceValidator→lib.ServiceValidatorbuilder.api_json.TypeResolver→lib.Kind
- Direction
- builder.api_json uses lib, so a change to lib can break builder.api_json, while a change to builder.api_json can't break lib.
- Position
- Below the diagonal: builder.api_json uses a module listed above it, which is the healthy direction.
32→16 builder.api_json uses lib.Primitives✕
- Connections
- 19 pairs of types, where a type in builder.api_json uses a type in lib.Primitives.
- The types involved
builder.api_json.ApiJsonServiceValidator→lib.Primitives.Unitbuilder.api_json.InternalAnnotationForm→lib.Primitives.Unitbuilder.api_json.InternalAttributeForm→lib.Primitives.Unitbuilder.api_json.InternalBodyForm→lib.Primitives.Unitbuilder.api_json.InternalEnumForm→lib.Primitives.Unitbuilder.api_json.InternalEnumValueForm→lib.Primitives.Unitbuilder.api_json.InternalFieldForm→lib.Primitives.Unitbuilder.api_json.InternalHeaderForm→lib.Primitives.Unitbuilder.api_json.InternalImportForm→lib.Primitives.Unitbuilder.api_json.InternalInfoForm→lib.Primitives.Unitbuilder.api_json.InternalInterfaceForm→lib.Primitives.Unitbuilder.api_json.InternalModelForm→lib.Primitives.Unitbuilder.api_json.InternalOperationForm→lib.Primitives.Unitbuilder.api_json.InternalParameterForm→lib.Primitives.Unitbuilder.api_json.InternalResourceForm→lib.Primitives.Unitbuilder.api_json.InternalResponseForm→lib.Primitives.Unitbuilder.api_json.InternalTemplateDeclarationForm→lib.Primitives.Unitbuilder.api_json.InternalUnionForm→lib.Primitives.Unitbuilder.api_json.InternalUnionTypeForm→lib.Primitives.Unit
- Direction
- builder.api_json uses lib.Primitives, so a change to lib.Primitives can break builder.api_json, while a change to builder.api_json can't break lib.Primitives.
- Position
- Below the diagonal: builder.api_json uses a module listed above it, which is the healthy direction.
32→23 builder.api_json uses io.apibuilder.avro.SchemaType✕
- Connections
- 38 pairs of types, where a type in builder.api_json uses a type in io.apibuilder.avro.SchemaType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
builder.api_json.ApiJsonServiceValidator→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.AutoCreateUnionTypeModels→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalAnnotationForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalApiJsonForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalApidocForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalAttributeForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalBodyForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalDatatype→io.apibuilder.avro.SchemaType.Booleanbuilder.api_json.InternalDatatype→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalDatatypeBuilder→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalDeprecationForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalEnumForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalEnumValueForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalFieldForm→io.apibuilder.avro.SchemaType.Booleanbuilder.api_json.InternalFieldForm→io.apibuilder.avro.SchemaType.Longbuilder.api_json.InternalFieldForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalHeaderForm→io.apibuilder.avro.SchemaType.Booleanbuilder.api_json.InternalHeaderForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalImportForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalInfoContactForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalInfoForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalInfoLicenseForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalInterfaceForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalModelForm→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalOperationForm→io.apibuilder.avro.SchemaType.String
- Direction
- builder.api_json uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break builder.api_json, while a change to builder.api_json can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: builder.api_json uses a module listed above it, which is the healthy direction.
32→25 builder.api_json uses core✕
- Connections
- 16 pairs of types, where a type in builder.api_json uses a type in core.
- The types involved
builder.api_json.ApiJsonServiceValidator→core.ServiceFetcherbuilder.api_json.ApiJsonServiceValidator→core.VersionMigrationbuilder.api_json.InternalApiJsonForm→core.ServiceFetcherbuilder.api_json.InternalApiJsonFormTypesProvider→core.TypesProviderbuilder.api_json.InternalApiJsonFormTypesProvider→core.TypesProviderEnumbuilder.api_json.InternalApiJsonFormTypesProvider→core.TypesProviderInterfacebuilder.api_json.InternalApiJsonFormTypesProvider→core.TypesProviderModelbuilder.api_json.InternalApiJsonFormTypesProvider→core.TypesProviderUnionbuilder.api_json.RecursiveTypesProvider→core.TypesProviderbuilder.api_json.RecursiveTypesProvider→core.TypesProviderEnumbuilder.api_json.RecursiveTypesProvider→core.TypesProviderInterfacebuilder.api_json.RecursiveTypesProvider→core.TypesProviderModelbuilder.api_json.RecursiveTypesProvider→core.TypesProviderUnionbuilder.api_json.ServiceBuilder→core.ServiceFetcherbuilder.api_json.ServiceBuilder→core.VersionMigrationbuilder.api_json.TypeResolver→core.TypesProvider
- Direction
- builder.api_json uses core, so a change to core can break builder.api_json, while a change to builder.api_json can't break core.
- Position
- Below the diagonal: builder.api_json uses a module listed above it, which is the healthy direction.
32→34 builder.api_json uses builder.api_json.InternalDatatype part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.api_json uses a type in builder.api_json.InternalDatatype.
- The types involved
builder.api_json.InternalDatatypeBuilder→builder.api_json.InternalDatatype.Listbuilder.api_json.RecursiveTypesProvider→builder.api_json.InternalDatatype.List
- Direction
- builder.api_json uses builder.api_json.InternalDatatype, so a change to builder.api_json.InternalDatatype can break builder.api_json, while a change to builder.api_json can't break builder.api_json.InternalDatatype.
- 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.
33→3 io.apibuilder.generator.v0.mock uses io.apibuilder.common.v0.models✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.generator.v0.mock uses a type in io.apibuilder.common.v0.models.
- The types involved
io.apibuilder.generator.v0.mock.Factories→io.apibuilder.common.v0.models.Healthcheckio.apibuilder.generator.v0.mock.MockHealthchecks→io.apibuilder.common.v0.models.Healthcheck
- Direction
- io.apibuilder.generator.v0.mock uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break io.apibuilder.generator.v0.mock, while a change to io.apibuilder.generator.v0.mock can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.mock uses a module listed above it, which is the healthy direction.
33→8 io.apibuilder.generator.v0.mock uses io.apibuilder.api.json.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.generator.v0.mock uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.generator.v0.mock.Factories→io.apibuilder.api.json.v0.models.Attribute
- Direction
- io.apibuilder.generator.v0.mock uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.generator.v0.mock, while a change to io.apibuilder.generator.v0.mock can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.mock uses a module listed above it, which is the healthy direction.
33→19 io.apibuilder.generator.v0.mock uses controllers✕
- Connections
- 4 pairs of types, where a type in io.apibuilder.generator.v0.mock uses a type in controllers.
- The types involved
io.apibuilder.generator.v0.mock.Client→controllers.Generatorsio.apibuilder.generator.v0.mock.Client→controllers.Healthchecksio.apibuilder.generator.v0.mock.MockGenerators→controllers.Generatorsio.apibuilder.generator.v0.mock.MockHealthchecks→controllers.Healthchecks
- Direction
- io.apibuilder.generator.v0.mock uses controllers, so a change to controllers can break io.apibuilder.generator.v0.mock, while a change to io.apibuilder.generator.v0.mock can't break controllers.
- Position
- Below the diagonal: io.apibuilder.generator.v0.mock uses a module listed above it, which is the healthy direction.
33→20 io.apibuilder.generator.v0.mock uses io.apibuilder.api.v0.models✕
- Connections
- 1 pair of types, where a type in io.apibuilder.generator.v0.mock uses a type in io.apibuilder.api.v0.models.
- The types involved
io.apibuilder.generator.v0.mock.Factories→io.apibuilder.api.v0.models.Error
- Direction
- io.apibuilder.generator.v0.mock uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break io.apibuilder.generator.v0.mock, while a change to io.apibuilder.generator.v0.mock can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.mock uses a module listed above it, which is the healthy direction.
33→21 io.apibuilder.generator.v0.mock uses io.apibuilder.generator.v0.models✕
- Connections
- 8 pairs of types, where a type in io.apibuilder.generator.v0.mock uses a type in io.apibuilder.generator.v0.models.
- The types involved
io.apibuilder.generator.v0.mock.Factories→io.apibuilder.generator.v0.models.Fileio.apibuilder.generator.v0.mock.Factories→io.apibuilder.generator.v0.models.FileFlagio.apibuilder.generator.v0.mock.Factories→io.apibuilder.generator.v0.models.Generatorio.apibuilder.generator.v0.mock.Factories→io.apibuilder.generator.v0.models.Invocationio.apibuilder.generator.v0.mock.Factories→io.apibuilder.generator.v0.models.InvocationFormio.apibuilder.generator.v0.mock.MockGenerators→io.apibuilder.generator.v0.models.Generatorio.apibuilder.generator.v0.mock.MockInvocations→io.apibuilder.generator.v0.models.Invocationio.apibuilder.generator.v0.mock.MockInvocations→io.apibuilder.generator.v0.models.InvocationForm
- Direction
- io.apibuilder.generator.v0.mock uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break io.apibuilder.generator.v0.mock, while a change to io.apibuilder.generator.v0.mock can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: io.apibuilder.generator.v0.mock uses a module listed above it, which is the healthy direction.
33→23 io.apibuilder.generator.v0.mock uses io.apibuilder.avro.SchemaType✕
- Connections
- 6 pairs of types, where a type in io.apibuilder.generator.v0.mock uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.generator.v0.mock.Client→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.mock.Factories→io.apibuilder.avro.SchemaType.Intio.apibuilder.generator.v0.mock.Factories→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.mock.MockGenerators→io.apibuilder.avro.SchemaType.Intio.apibuilder.generator.v0.mock.MockGenerators→io.apibuilder.avro.SchemaType.Stringio.apibuilder.generator.v0.mock.MockInvocations→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.generator.v0.mock uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.generator.v0.mock, while a change to io.apibuilder.generator.v0.mock can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: io.apibuilder.generator.v0.mock uses a module listed above it, which is the healthy direction.
33→29 io.apibuilder.generator.v0.mock uses io.apibuilder.generator.v0.Client✕
- Connections
- 1 pair of types, where a type in io.apibuilder.generator.v0.mock uses a type in io.apibuilder.generator.v0.Client.
- The types involved
io.apibuilder.generator.v0.mock.Client→io.apibuilder.generator.v0.Client.Invocations
- Direction
- io.apibuilder.generator.v0.mock uses io.apibuilder.generator.v0.Client, so a change to io.apibuilder.generator.v0.Client can break io.apibuilder.generator.v0.mock, while a change to io.apibuilder.generator.v0.mock can't break io.apibuilder.generator.v0.Client.
- Position
- Below the diagonal: io.apibuilder.generator.v0.mock uses a module listed above it, which is the healthy direction.
34→23 builder.api_json.InternalDatatype uses io.apibuilder.avro.SchemaType✕
- Connections
- 6 pairs of types, where a type in builder.api_json.InternalDatatype uses a type in io.apibuilder.avro.SchemaType.
- The types involved
builder.api_json.InternalDatatype.List→io.apibuilder.avro.SchemaType.Booleanbuilder.api_json.InternalDatatype.List→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalDatatype.Map→io.apibuilder.avro.SchemaType.Booleanbuilder.api_json.InternalDatatype.Map→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.InternalDatatype.Singleton→io.apibuilder.avro.SchemaType.Booleanbuilder.api_json.InternalDatatype.Singleton→io.apibuilder.avro.SchemaType.String
- Direction
- builder.api_json.InternalDatatype uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break builder.api_json.InternalDatatype, while a change to builder.api_json.InternalDatatype can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: builder.api_json.InternalDatatype uses a module listed above it, which is the healthy direction.
34→32 builder.api_json.InternalDatatype uses builder.api_json✕
- Connections
- 3 pairs of types, where a type in builder.api_json.InternalDatatype uses a type in builder.api_json.
- The types involved
builder.api_json.InternalDatatype.List→builder.api_json.InternalDatatypebuilder.api_json.InternalDatatype.Map→builder.api_json.InternalDatatypebuilder.api_json.InternalDatatype.Singleton→builder.api_json.InternalDatatype
- Direction
- builder.api_json.InternalDatatype uses builder.api_json, so a change to builder.api_json can break builder.api_json.InternalDatatype, while a change to builder.api_json.InternalDatatype can't break builder.api_json.
- Position
- Below the diagonal: builder.api_json.InternalDatatype uses a module listed above it, which is the healthy direction.
35→2 builder.api_json.ServiceBuilder uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 1 pair of types, where a type in builder.api_json.ServiceBuilder uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
builder.api_json.ServiceBuilder.FieldBuilder→io.apibuilder.avro.ApiBuilder.Field
- Direction
- builder.api_json.ServiceBuilder uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break builder.api_json.ServiceBuilder, while a change to builder.api_json.ServiceBuilder can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: builder.api_json.ServiceBuilder uses a module listed above it, which is the healthy direction.
35→8 builder.api_json.ServiceBuilder uses io.apibuilder.api.json.v0.models✕
- Connections
- 15 pairs of types, where a type in builder.api_json.ServiceBuilder uses a type in io.apibuilder.api.json.v0.models.
- The types involved
builder.api_json.ServiceBuilder.AnnotationsBuilder→io.apibuilder.api.json.v0.models.Annotationbuilder.api_json.ServiceBuilder.AttributeBuilder→io.apibuilder.api.json.v0.models.Attributebuilder.api_json.ServiceBuilder.BodyBuilder→io.apibuilder.api.json.v0.models.Bodybuilder.api_json.ServiceBuilder.DeprecationBuilder→io.apibuilder.api.json.v0.models.Deprecationbuilder.api_json.ServiceBuilder.HeaderBuilder→io.apibuilder.api.json.v0.models.Headerbuilder.api_json.ServiceBuilder.ImportBuilder→io.apibuilder.api.json.v0.models.Importbuilder.api_json.ServiceBuilder.InfoBuilder→io.apibuilder.api.json.v0.models.Infobuilder.api_json.ServiceBuilder.InterfaceBuilder→io.apibuilder.api.json.v0.models.Interfacebuilder.api_json.ServiceBuilder.ModelBuilder→io.apibuilder.api.json.v0.models.Modelbuilder.api_json.ServiceBuilder.OperationBuilder→io.apibuilder.api.json.v0.models.Operationbuilder.api_json.ServiceBuilder.OperationBuilder→io.apibuilder.api.json.v0.models.ParameterLocationbuilder.api_json.ServiceBuilder.ParameterBuilder→io.apibuilder.api.json.v0.models.Parameterbuilder.api_json.ServiceBuilder.ParameterBuilder→io.apibuilder.api.json.v0.models.ParameterLocationbuilder.api_json.ServiceBuilder.ResourceBuilder→io.apibuilder.api.json.v0.models.Resourcebuilder.api_json.ServiceBuilder.ResponseBuilder→io.apibuilder.api.json.v0.models.Response
- Direction
- builder.api_json.ServiceBuilder uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break builder.api_json.ServiceBuilder, while a change to builder.api_json.ServiceBuilder can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: builder.api_json.ServiceBuilder uses a module listed above it, which is the healthy direction.
35→23 builder.api_json.ServiceBuilder uses io.apibuilder.avro.SchemaType✕
- Connections
- 5 pairs of types, where a type in builder.api_json.ServiceBuilder uses a type in io.apibuilder.avro.SchemaType.
- The types involved
builder.api_json.ServiceBuilder.EnumBuilder→io.apibuilder.avro.SchemaType.Enumbuilder.api_json.ServiceBuilder.OperationBuilder→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.ServiceBuilder.ParameterBuilder→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.ServiceBuilder.ResourceBuilder→io.apibuilder.avro.SchemaType.Stringbuilder.api_json.ServiceBuilder.UnionBuilder→io.apibuilder.avro.SchemaType.Union
- Direction
- builder.api_json.ServiceBuilder uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break builder.api_json.ServiceBuilder, while a change to builder.api_json.ServiceBuilder can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: builder.api_json.ServiceBuilder uses a module listed above it, which is the healthy direction.
35→25 builder.api_json.ServiceBuilder uses core✕
- Connections
- 5 pairs of types, where a type in builder.api_json.ServiceBuilder uses a type in core.
- The types involved
builder.api_json.ServiceBuilder.ImportBuilder→core.ServiceFetcherbuilder.api_json.ServiceBuilder.OperationBuilder→core.TypesProviderbuilder.api_json.ServiceBuilder.OperationBuilder→core.TypesProviderModelbuilder.api_json.ServiceBuilder.OperationBuilder→core.TypesProviderUnionbuilder.api_json.ServiceBuilder.ResourceBuilder→core.TypesProvider
- Direction
- builder.api_json.ServiceBuilder uses core, so a change to core can break builder.api_json.ServiceBuilder, while a change to builder.api_json.ServiceBuilder can't break core.
- Position
- Below the diagonal: builder.api_json.ServiceBuilder uses a module listed above it, which is the healthy direction.
35→32 builder.api_json.ServiceBuilder uses builder.api_json✕
- Connections
- 20 pairs of types, where a type in builder.api_json.ServiceBuilder uses a type in builder.api_json.
- The types involved
builder.api_json.ServiceBuilder.AnnotationsBuilder→builder.api_json.InternalAnnotationFormbuilder.api_json.ServiceBuilder.AttributeBuilder→builder.api_json.InternalAttributeFormbuilder.api_json.ServiceBuilder.BodyBuilder→builder.api_json.InternalBodyFormbuilder.api_json.ServiceBuilder.DeprecationBuilder→builder.api_json.InternalDeprecationFormbuilder.api_json.ServiceBuilder.EnumBuilder→builder.api_json.InternalEnumFormbuilder.api_json.ServiceBuilder.FieldBuilder→builder.api_json.InternalFieldFormbuilder.api_json.ServiceBuilder.HeaderBuilder→builder.api_json.InternalHeaderFormbuilder.api_json.ServiceBuilder.HeaderBuilder→builder.api_json.TypeResolverbuilder.api_json.ServiceBuilder.ImportBuilder→builder.api_json.InternalImportFormbuilder.api_json.ServiceBuilder.InfoBuilder→builder.api_json.InternalInfoFormbuilder.api_json.ServiceBuilder.InterfaceBuilder→builder.api_json.InternalInterfaceFormbuilder.api_json.ServiceBuilder.ModelBuilder→builder.api_json.InternalModelFormbuilder.api_json.ServiceBuilder.OperationBuilder→builder.api_json.InternalOperationFormbuilder.api_json.ServiceBuilder.OperationBuilder→builder.api_json.TypeResolverbuilder.api_json.ServiceBuilder.ParameterBuilder→builder.api_json.InternalParameterFormbuilder.api_json.ServiceBuilder.ResourceBuilder→builder.api_json.InternalResourceFormbuilder.api_json.ServiceBuilder.ResourceBuilder→builder.api_json.TypeResolverbuilder.api_json.ServiceBuilder.ResponseBuilder→builder.api_json.InternalResponseFormbuilder.api_json.ServiceBuilder.ResponseBuilder→builder.api_json.TypeResolverbuilder.api_json.ServiceBuilder.UnionBuilder→builder.api_json.InternalUnionForm
- Direction
- builder.api_json.ServiceBuilder uses builder.api_json, so a change to builder.api_json can break builder.api_json.ServiceBuilder, while a change to builder.api_json.ServiceBuilder can't break builder.api_json.
- Position
- Below the diagonal: builder.api_json.ServiceBuilder uses a module listed above it, which is the healthy direction.
36→2 builder uses io.apibuilder.avro.ApiBuilder✕
- Connections
- 2 pairs of types, where a type in builder uses a type in io.apibuilder.avro.ApiBuilder.
- The types involved
builder.ServiceSpecValidator→io.apibuilder.avro.ApiBuilder.Fieldbuilder.ServiceSpecValidator→io.apibuilder.avro.ApiBuilder.UnionType
- Direction
- builder uses io.apibuilder.avro.ApiBuilder, so a change to io.apibuilder.avro.ApiBuilder can break builder, while a change to builder can't break io.apibuilder.avro.ApiBuilder.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→8 builder uses io.apibuilder.api.json.v0.models✕
- Connections
- 5 pairs of types, where a type in builder uses a type in io.apibuilder.api.json.v0.models.
- The types involved
builder.ServiceSpecValidator→io.apibuilder.api.json.v0.models.Headerbuilder.ServiceSpecValidator→io.apibuilder.api.json.v0.models.Interfacebuilder.ServiceSpecValidator→io.apibuilder.api.json.v0.models.Modelbuilder.ServiceSpecValidator→io.apibuilder.api.json.v0.models.Operationbuilder.ServiceSpecValidator→io.apibuilder.api.json.v0.models.Resource
- Direction
- builder uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break builder, while a change to builder can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→12 builder uses io.apibuilder.spec.v0.models✕
- Connections
- 3 pairs of types, where a type in builder uses a type in io.apibuilder.spec.v0.models.
- The types involved
builder.OriginalValidator→io.apibuilder.spec.v0.models.Servicebuilder.ServiceSpecValidator→io.apibuilder.spec.v0.models.ResponseCodebuilder.ServiceSpecValidator→io.apibuilder.spec.v0.models.Service
- Direction
- builder uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break builder, while a change to builder can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→15 builder uses lib✕
- Connections
- 4 pairs of types, where a type in builder uses a type in lib.
- The types involved
builder.OriginalValidator→lib.ServiceConfigurationbuilder.OriginalValidator→lib.ServiceValidatorbuilder.ServiceSpecValidator→lib.Kindbuilder.ServiceSpecValidator→lib.ValidatedHelpers
- Direction
- builder uses lib, so a change to lib can break builder, while a change to builder can't break lib.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→16 builder uses lib.Primitives✕
- Connections
- 3 pairs of types, where a type in builder uses a type in lib.Primitives.
- The types involved
builder.DuplicateErrorMessage→lib.Primitives.Unitbuilder.JsonUtil→lib.Primitives.Unitbuilder.ServiceSpecValidator→lib.Primitives.Unit
- Direction
- builder uses lib.Primitives, so a change to lib.Primitives can break builder, while a change to builder can't break lib.Primitives.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→20 builder uses io.apibuilder.api.v0.models✕
- Connections
- 1 pair of types, where a type in builder uses a type in io.apibuilder.api.v0.models.
- The types involved
builder.OriginalValidator→io.apibuilder.api.v0.models.OriginalType
- Direction
- builder uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break builder, while a change to builder can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→23 builder uses io.apibuilder.avro.SchemaType✕
- Connections
- 8 pairs of types, where a type in builder uses a type in io.apibuilder.avro.SchemaType.
- The types involved
builder.DuplicateErrorMessage→io.apibuilder.avro.SchemaType.Stringbuilder.JsonUtil→io.apibuilder.avro.SchemaType.Booleanbuilder.JsonUtil→io.apibuilder.avro.SchemaType.Longbuilder.JsonUtil→io.apibuilder.avro.SchemaType.Stringbuilder.ServiceSpecValidator→io.apibuilder.avro.SchemaType.Booleanbuilder.ServiceSpecValidator→io.apibuilder.avro.SchemaType.Longbuilder.ServiceSpecValidator→io.apibuilder.avro.SchemaType.Stringbuilder.ServiceSpecValidator→io.apibuilder.avro.SchemaType.Union
- Direction
- builder uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break builder, while a change to builder can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→25 builder uses core✕
- Connections
- 2 pairs of types, where a type in builder uses a type in core.
- The types involved
builder.OriginalValidator→core.ServiceFetcherbuilder.OriginalValidator→core.VersionMigration
- Direction
- builder uses core, so a change to core can break builder, while a change to builder can't break core.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
36→34 builder uses builder.api_json.InternalDatatype✕
- Connections
- 1 pair of types, where a type in builder uses a type in builder.api_json.InternalDatatype.
- The types involved
builder.DuplicateErrorMessage→builder.api_json.InternalDatatype.List
- Direction
- builder uses builder.api_json.InternalDatatype, so a change to builder.api_json.InternalDatatype can break builder, while a change to builder can't break builder.api_json.InternalDatatype.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
37→23 db.generated.ApplicationMovesTable uses io.apibuilder.avro.SchemaType✕
- Connections
- 1 pair of types, where a type in db.generated.ApplicationMovesTable uses a type in io.apibuilder.avro.SchemaType.
- The types involved
db.generated.ApplicationMovesTable.Column→io.apibuilder.avro.SchemaType.String
- Direction
- db.generated.ApplicationMovesTable uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break db.generated.ApplicationMovesTable, while a change to db.generated.ApplicationMovesTable can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: db.generated.ApplicationMovesTable uses a module listed above it, which is the healthy direction.
37→34 db.generated.ApplicationMovesTable uses builder.api_json.InternalDatatype✕
- Connections
- 1 pair of types, where a type in db.generated.ApplicationMovesTable uses a type in builder.api_json.InternalDatatype.
- The types involved
db.generated.ApplicationMovesTable.Columns→builder.api_json.InternalDatatype.List
- Direction
- db.generated.ApplicationMovesTable uses builder.api_json.InternalDatatype, so a change to builder.api_json.InternalDatatype can break db.generated.ApplicationMovesTable, while a change to db.generated.ApplicationMovesTable can't break builder.api_json.InternalDatatype.
- Position
- Below the diagonal: db.generated.ApplicationMovesTable uses a module listed above it, which is the healthy direction.
38→8 io.apibuilder.swagger uses io.apibuilder.api.json.v0.models✕
- Connections
- 9 pairs of types, where a type in io.apibuilder.swagger uses a type in io.apibuilder.api.json.v0.models.
- The types involved
io.apibuilder.swagger.ModelSelector→io.apibuilder.api.json.v0.models.Modelio.apibuilder.swagger.MyDefinition→io.apibuilder.api.json.v0.models.Modelio.apibuilder.swagger.Parser→io.apibuilder.api.json.v0.models.Modelio.apibuilder.swagger.Parser→io.apibuilder.api.json.v0.models.Resourceio.apibuilder.swagger.Parser→io.apibuilder.api.json.v0.models.Responseio.apibuilder.swagger.SwaggerData→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.swagger.Util→io.apibuilder.api.json.v0.models.Attributeio.apibuilder.swagger.Util→io.apibuilder.api.json.v0.models.Operationio.apibuilder.swagger.Util→io.apibuilder.api.json.v0.models.Parameter
- Direction
- io.apibuilder.swagger uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→10 io.apibuilder.swagger uses io.apibuilder.api.json.v0.models.ParameterLocation✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.swagger uses a type in io.apibuilder.api.json.v0.models.ParameterLocation.
- The types involved
io.apibuilder.swagger.Parser→io.apibuilder.api.json.v0.models.ParameterLocation.Pathio.apibuilder.swagger.Util→io.apibuilder.api.json.v0.models.ParameterLocation.Path
- Direction
- io.apibuilder.swagger uses io.apibuilder.api.json.v0.models.ParameterLocation, so a change to io.apibuilder.api.json.v0.models.ParameterLocation can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break io.apibuilder.api.json.v0.models.ParameterLocation.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→12 io.apibuilder.swagger uses io.apibuilder.spec.v0.models✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.swagger uses a type in io.apibuilder.spec.v0.models.
- The types involved
io.apibuilder.swagger.Parser→io.apibuilder.spec.v0.models.Serviceio.apibuilder.swagger.SwaggerServiceValidator→io.apibuilder.spec.v0.models.Service
- Direction
- io.apibuilder.swagger uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→15 io.apibuilder.swagger uses lib✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.swagger uses a type in lib.
- The types involved
io.apibuilder.swagger.Parser→lib.ServiceConfigurationio.apibuilder.swagger.SwaggerServiceValidator→lib.ServiceConfigurationio.apibuilder.swagger.SwaggerServiceValidator→lib.ServiceValidator
- Direction
- io.apibuilder.swagger uses lib, so a change to lib can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break lib.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→16 io.apibuilder.swagger uses lib.Primitives✕
- Connections
- 3 pairs of types, where a type in io.apibuilder.swagger uses a type in lib.Primitives.
- The types involved
io.apibuilder.swagger.SwaggerData→lib.Primitives.Objectio.apibuilder.swagger.Util→lib.Primitives.Objectio.apibuilder.swagger.Util→lib.Primitives.Unit
- Direction
- io.apibuilder.swagger uses lib.Primitives, so a change to lib.Primitives can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break lib.Primitives.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→21 io.apibuilder.swagger uses io.apibuilder.generator.v0.models✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.swagger uses a type in io.apibuilder.generator.v0.models.
- The types involved
io.apibuilder.swagger.Parser→io.apibuilder.generator.v0.models.Fileio.apibuilder.swagger.Util→io.apibuilder.generator.v0.models.File
- Direction
- io.apibuilder.swagger uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→23 io.apibuilder.swagger uses io.apibuilder.avro.SchemaType✕
- Connections
- 13 pairs of types, where a type in io.apibuilder.swagger uses a type in io.apibuilder.avro.SchemaType.
- The types involved
io.apibuilder.swagger.ModelSelector→io.apibuilder.avro.SchemaType.Mapio.apibuilder.swagger.ModelSelector→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.MyDefinition→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.Parser→io.apibuilder.avro.SchemaType.Enumio.apibuilder.swagger.Parser→io.apibuilder.avro.SchemaType.Mapio.apibuilder.swagger.Parser→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.SchemaType→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.SwaggerData→io.apibuilder.avro.SchemaType.Mapio.apibuilder.swagger.SwaggerData→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.SwaggerServiceValidator→io.apibuilder.avro.SchemaType.Stringio.apibuilder.swagger.Util→io.apibuilder.avro.SchemaType.Booleanio.apibuilder.swagger.Util→io.apibuilder.avro.SchemaType.Mapio.apibuilder.swagger.Util→io.apibuilder.avro.SchemaType.String
- Direction
- io.apibuilder.swagger uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→31 io.apibuilder.swagger uses io.apibuilder.swagger.translators✕
- Connections
- 1 pair of types, where a type in io.apibuilder.swagger uses a type in io.apibuilder.swagger.translators.
- The types involved
io.apibuilder.swagger.Parser→io.apibuilder.swagger.translators.Resolver
- Direction
- io.apibuilder.swagger uses io.apibuilder.swagger.translators, so a change to io.apibuilder.swagger.translators can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break io.apibuilder.swagger.translators.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
38→34 io.apibuilder.swagger uses builder.api_json.InternalDatatype✕
- Connections
- 2 pairs of types, where a type in io.apibuilder.swagger uses a type in builder.api_json.InternalDatatype.
- The types involved
io.apibuilder.swagger.SwaggerData→builder.api_json.InternalDatatype.Listio.apibuilder.swagger.Util→builder.api_json.InternalDatatype.List
- Direction
- io.apibuilder.swagger uses builder.api_json.InternalDatatype, so a change to builder.api_json.InternalDatatype can break io.apibuilder.swagger, while a change to io.apibuilder.swagger can't break builder.api_json.InternalDatatype.
- Position
- Below the diagonal: io.apibuilder.swagger uses a module listed above it, which is the healthy direction.
39→5 util uses lib.query✕
- Connections
- 2 pairs of types, where a type in util uses a type in lib.query.
- The types involved
util.OptionalQueryFilter→lib.query.Queryutil.QueryFilter→lib.query.Query
- Direction
- util uses lib.query, so a change to lib.query can break util, while a change to util can't break lib.query.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→6 util uses util.BasicAuthorization✕
- Connections
- 1 pair of types, where a type in util uses a type in util.BasicAuthorization.
- The types involved
util.Conversions→util.BasicAuthorization.Session
- Direction
- util uses util.BasicAuthorization, so a change to util.BasicAuthorization can break util, while a change to util can't break util.BasicAuthorization.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→8 util uses io.apibuilder.api.json.v0.models✕
- Connections
- 2 pairs of types, where a type in util uses a type in io.apibuilder.api.json.v0.models.
- The types involved
util.ApiBuilderServiceImportResolver→io.apibuilder.api.json.v0.models.Importutil.ServiceBuilder→io.apibuilder.api.json.v0.models.Import
- Direction
- util uses io.apibuilder.api.json.v0.models, so a change to io.apibuilder.api.json.v0.models can break util, while a change to util can't break io.apibuilder.api.json.v0.models.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→11 util uses io.apibuilder.api.v0✕
- Connections
- 1 pair of types, where a type in util uses a type in io.apibuilder.api.v0.
- The types involved
util.GeneratorServiceUtil→io.apibuilder.api.v0.Client
- Direction
- util uses io.apibuilder.api.v0, so a change to io.apibuilder.api.v0 can break util, while a change to util can't break io.apibuilder.api.v0.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→12 util uses io.apibuilder.spec.v0.models✕
- Connections
- 2 pairs of types, where a type in util uses a type in io.apibuilder.spec.v0.models.
- The types involved
util.ApiBuilderServiceImportResolver→io.apibuilder.spec.v0.models.Serviceutil.ServiceBuilder→io.apibuilder.spec.v0.models.Service
- Direction
- util uses io.apibuilder.spec.v0.models, so a change to io.apibuilder.spec.v0.models can break util, while a change to util can't break io.apibuilder.spec.v0.models.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→13 util uses db.generators✕
- Connections
- 1 pair of types, where a type in util uses a type in db.generators.
- The types involved
util.GeneratorServiceUtil→db.generators.InternalGeneratorService
- Direction
- util uses db.generators, so a change to db.generators can break util, while a change to util can't break db.generators.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→15 util uses lib✕
- Connections
- 3 pairs of types, where a type in util uses a type in lib.
- The types involved
util.ApiBuilderServiceImportResolver→lib.ServiceBuilderutil.GeneratorServiceUtil→lib.ValidatedHelpersutil.ServiceBuilder→lib.ServiceBuilder
- Direction
- util uses lib, so a change to lib can break util, while a change to util can't break lib.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→16 util uses lib.Primitives✕
- Connections
- 1 pair of types, where a type in util uses a type in lib.Primitives.
- The types involved
util.GeneratorServiceUtil→lib.Primitives.Unit
- Direction
- util uses lib.Primitives, so a change to lib.Primitives can break util, while a change to util can't break lib.Primitives.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→18 util uses db✕
- Connections
- 4 pairs of types, where a type in util uses a type in db.
- The types involved
util.ApiBuilderServiceImportResolver→db.Authorizationutil.BasicAuthorization→db.Authorizationutil.Conversions→db.InternalUserutil.SessionHelper→db.InternalUser
- Direction
- util uses db, so a change to db can break util, while a change to util can't break db.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→20 util uses io.apibuilder.api.v0.models✕
- Connections
- 2 pairs of types, where a type in util uses a type in io.apibuilder.api.v0.models.
- The types involved
util.Conversions→io.apibuilder.api.v0.models.Authenticationutil.SessionHelper→io.apibuilder.api.v0.models.Authentication
- Direction
- util uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break util, while a change to util can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→21 util uses io.apibuilder.generator.v0.models✕
- Connections
- 1 pair of types, where a type in util uses a type in io.apibuilder.generator.v0.models.
- The types involved
util.GeneratorServiceUtil→io.apibuilder.generator.v0.models.Generator
- Direction
- util uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break util, while a change to util can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→23 util uses io.apibuilder.avro.SchemaType✕
- Connections
- 14 pairs of types, where a type in util uses a type in io.apibuilder.avro.SchemaType.
- The types involved
util.BasicAuthorization→io.apibuilder.avro.SchemaType.Stringutil.GeneratorServiceUtil→io.apibuilder.avro.SchemaType.Intutil.GeneratorServiceUtil→io.apibuilder.avro.SchemaType.Longutil.LockUtil→io.apibuilder.avro.SchemaType.Booleanutil.LockUtil→io.apibuilder.avro.SchemaType.Stringutil.PrimaryKey→io.apibuilder.avro.SchemaType.Stringutil.Random→io.apibuilder.avro.SchemaType.Intutil.Random→io.apibuilder.avro.SchemaType.Longutil.Random→io.apibuilder.avro.SchemaType.Stringutil.ServiceBuilder→io.apibuilder.avro.SchemaType.Booleanutil.ServiceBuilder→io.apibuilder.avro.SchemaType.Stringutil.SessionIdGenerator→io.apibuilder.avro.SchemaType.Stringutil.Table→io.apibuilder.avro.SchemaType.Stringutil.UserAgent→io.apibuilder.avro.SchemaType.String
- Direction
- util uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break util, while a change to util can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
39→34 util uses builder.api_json.InternalDatatype✕
- Connections
- 2 pairs of types, where a type in util uses a type in builder.api_json.InternalDatatype.
- The types involved
util.ApiBuilderServiceImportResolver→builder.api_json.InternalDatatype.Listutil.GeneratorServiceUtil→builder.api_json.InternalDatatype.List
- Direction
- util uses builder.api_json.InternalDatatype, so a change to builder.api_json.InternalDatatype can break util, while a change to util can't break builder.api_json.InternalDatatype.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
40→3 processor uses io.apibuilder.common.v0.models✕
- Connections
- 1 pair of types, where a type in processor uses a type in io.apibuilder.common.v0.models.
- The types involved
processor.EmailProcessor→io.apibuilder.common.v0.models.MembershipRole
- Direction
- processor uses io.apibuilder.common.v0.models, so a change to io.apibuilder.common.v0.models can break processor, while a change to processor can't break io.apibuilder.common.v0.models.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→5 processor uses lib.query✕
- Connections
- 1 pair of types, where a type in processor uses a type in lib.query.
- The types involved
processor.PurgeDeletedProcessor→lib.query.Query
- Direction
- processor uses lib.query, so a change to lib.query can break processor, while a change to processor can't break lib.query.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→9 processor uses io.apibuilder.task.v0.models✕
- Connections
- 6 pairs of types, where a type in processor uses a type in io.apibuilder.task.v0.models.
- The types involved
processor.BaseTaskProcessor→io.apibuilder.task.v0.models.TaskTypeprocessor.DiffVersionProcessor→io.apibuilder.task.v0.models.DiffVersionDataprocessor.EmailProcessor→io.apibuilder.task.v0.models.EmailDataprocessor.EmailProcessorQueue→io.apibuilder.task.v0.models.EmailDataprocessor.TaskActorCompanion→io.apibuilder.task.v0.models.TaskTypeprocessor.TaskDispatchActorCompanion→io.apibuilder.task.v0.models.TaskType
- Direction
- processor uses io.apibuilder.task.v0.models, so a change to io.apibuilder.task.v0.models can break processor, while a change to processor can't break io.apibuilder.task.v0.models.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→11 processor uses io.apibuilder.api.v0✕
- Connections
- 1 pair of types, where a type in processor uses a type in io.apibuilder.api.v0.
- The types involved
processor.SyncGeneratorServiceProcessor→io.apibuilder.api.v0.Client
- Direction
- processor uses io.apibuilder.api.v0, so a change to io.apibuilder.api.v0 can break processor, while a change to processor can't break io.apibuilder.api.v0.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→13 processor uses db.generators✕
- Connections
- 1 pair of types, where a type in processor uses a type in db.generators.
- The types involved
processor.SyncGeneratorServiceProcessor→db.generators.InternalGeneratorService
- Direction
- processor uses db.generators, so a change to db.generators can break processor, while a change to processor can't break db.generators.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→15 processor uses lib✕
- Connections
- 2 pairs of types, where a type in processor uses a type in lib.
- The types involved
processor.ScheduleSyncGeneratorServicesProcessor→lib.ValidatedHelpersprocessor.SyncGeneratorServiceProcessor→lib.ValidatedHelpers
- Direction
- processor uses lib, so a change to lib can break processor, while a change to processor can't break lib.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→16 processor uses lib.Primitives✕
- Connections
- 16 pairs of types, where a type in processor uses a type in lib.Primitives.
- The types involved
processor.BaseTaskProcessor→lib.Primitives.Unitprocessor.CheckInvariantsProcessor→lib.Primitives.Unitprocessor.DiffVersionProcessor→lib.Primitives.Unitprocessor.EmailProcessor→lib.Primitives.Unitprocessor.EmailProcessorQueue→lib.Primitives.Unitprocessor.IndexApplicationProcessor→lib.Primitives.Unitprocessor.MigrateVersionProcessor→lib.Primitives.Unitprocessor.PurgeDeletedProcessor→lib.Primitives.Unitprocessor.ScheduleMigrateVersionsProcessor→lib.Primitives.Unitprocessor.ScheduleSyncGeneratorServicesProcessor→lib.Primitives.Unitprocessor.SyncGeneratorServiceProcessor→lib.Primitives.Unitprocessor.TaskActorCompanion→lib.Primitives.Unitprocessor.TaskProcessor→lib.Primitives.Unitprocessor.TaskProcessorWithData→lib.Primitives.Unitprocessor.TaskProcessorWithGuid→lib.Primitives.Unitprocessor.UserCreatedProcessor→lib.Primitives.Unit
- Direction
- processor uses lib.Primitives, so a change to lib.Primitives can break processor, while a change to processor can't break lib.Primitives.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→17 processor uses db.generated✕
- Connections
- 6 pairs of types, where a type in processor uses a type in db.generated.
- The types involved
processor.BaseTaskProcessor→db.generated.Taskprocessor.BaseTaskProcessor→db.generated.TaskFormprocessor.TaskProcessor→db.generated.Taskprocessor.TaskProcessorArgs→db.generated.TasksDaoprocessor.TaskProcessorWithData→db.generated.Taskprocessor.TaskProcessorWithGuid→db.generated.Task
- Direction
- processor uses db.generated, so a change to db.generated can break processor, while a change to processor can't break db.generated.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→20 processor uses io.apibuilder.api.v0.models✕
- Connections
- 3 pairs of types, where a type in processor uses a type in io.apibuilder.api.v0.models.
- The types involved
processor.DiffVersionProcessor→io.apibuilder.api.v0.models.Diffprocessor.DiffVersionProcessor→io.apibuilder.api.v0.models.Publicationprocessor.DiffVersionProcessor→io.apibuilder.api.v0.models.Version
- Direction
- processor uses io.apibuilder.api.v0.models, so a change to io.apibuilder.api.v0.models can break processor, while a change to processor can't break io.apibuilder.api.v0.models.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→21 processor uses io.apibuilder.generator.v0.models✕
- Connections
- 1 pair of types, where a type in processor uses a type in io.apibuilder.generator.v0.models.
- The types involved
processor.SyncGeneratorServiceProcessor→io.apibuilder.generator.v0.models.Generator
- Direction
- processor uses io.apibuilder.generator.v0.models, so a change to io.apibuilder.generator.v0.models can break processor, while a change to processor can't break io.apibuilder.generator.v0.models.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→23 processor uses io.apibuilder.avro.SchemaType✕
- Connections
- 21 pairs of types, where a type in processor uses a type in io.apibuilder.avro.SchemaType.
- The types involved
processor.BaseTaskProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.CheckInvariantsProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.DiffVersionProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.EmailProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.IndexApplicationProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.InvariantResult→io.apibuilder.avro.SchemaType.Longprocessor.MigrateVersion→io.apibuilder.avro.SchemaType.Stringprocessor.MigrateVersionProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.PurgeDeletedProcessor→io.apibuilder.avro.SchemaType.Booleanprocessor.PurgeDeletedProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.ScheduleMigrateVersionsProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.ScheduleSyncGeneratorServicesProcessor→io.apibuilder.avro.SchemaType.Longprocessor.ScheduleSyncGeneratorServicesProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.SyncGeneratorServiceProcessor→io.apibuilder.avro.SchemaType.Intprocessor.SyncGeneratorServiceProcessor→io.apibuilder.avro.SchemaType.Longprocessor.SyncGeneratorServiceProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.TaskActorCompanion→io.apibuilder.avro.SchemaType.Mapprocessor.TaskProcessor→io.apibuilder.avro.SchemaType.Stringprocessor.TaskProcessorWithData→io.apibuilder.avro.SchemaType.Stringprocessor.TaskProcessorWithGuid→io.apibuilder.avro.SchemaType.Stringprocessor.UserCreatedProcessor→io.apibuilder.avro.SchemaType.String
- Direction
- processor uses io.apibuilder.avro.SchemaType, so a change to io.apibuilder.avro.SchemaType can break processor, while a change to processor can't break io.apibuilder.avro.SchemaType.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→34 processor uses builder.api_json.InternalDatatype✕
- Connections
- 1 pair of types, where a type in processor uses a type in builder.api_json.InternalDatatype.
- The types involved
processor.SyncGeneratorServiceProcessor→builder.api_json.InternalDatatype.List
- Direction
- processor uses builder.api_json.InternalDatatype, so a change to builder.api_json.InternalDatatype can break processor, while a change to processor can't break builder.api_json.InternalDatatype.
- Position
- Below the diagonal: processor uses a module listed above it, which is the healthy direction.
40→39 processor uses util✕
- Connections
- 3 pairs of types, where a type in processor uses a type in util.
- The types involved
processor.PurgeDeletedProcessor→util.PrimaryKeyprocessor.PurgeDeletedProcessor→util.Tableprocessor.TaskProcessorArgs→util.LockUtil
- Direction
- processor uses util, so a change to util can break processor, while a change to processor can't break util.
- Position
- Below the diagonal: processor 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
Roadmap
Immediately address the three leaked secrets in REDACTED and resolve the 87 orphaned files, prioritizing Versions.scala, Organizations.scala, and Parser.scala. Establish a dedicated docs/adr folder to record significant design decisions with their dates, contexts, and consequences. Finally, expand the root README to include a getting-started guide, architecture overview, and project map to improve onboarding and clarity.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +8.0 pts | Low | ADR Quality |
| Resolve the 87 Orphaned file finding(s) in Knowledge Freshness — start with Versions.scala (2), Organizations.scala (2), Parser.scala (2). | +7.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.8 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +6.2 pts | Medium | Documentation (README) |
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). | +2.0 pts | Low | REDACTED Scanning |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.0 pts | Medium | Keyboard semantics |
| Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. | +1.7 pts | Medium | Web-Security Posture |
| Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED, REDACTED. | +0.8 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.3 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| api/app/controllers/Versions.scala | 5.7 | Mixed | Cognitive Complexity: Versions.postByVersion (cognitive 17) |
| swagger/src/main/scala/io/apibuilder/swagger/translators/Field.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| api/app/db/InternalOrganizationsDao.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/app/controllers/Versions.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| swagger/src/main/scala/io/apibuilder/swagger/Parser.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| api/app/db/InternalMembershipRequestsDao.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| generated/app/db/ApplicationMovesDao.scala | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (22 members, 50+ identical tokens) |
| api/app/controllers/Applications.scala | 7.0 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| generated/app/db/OriginalsDao.scala | 7.0 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| generated/app/db/EmailVerificationsDao.scala | 7.1 | Near-clean | Code Duplication: Duplicated block (12 lines × 3) |
| api/app/processor/SyncGeneratorServiceProcessor.scala | 7.2 | Near-clean | Code Duplication: Duplicated block (17 lines × 2) |
| generated/app/db/MembershipRequestsDao.scala | 7.2 | Near-clean | Code Duplication: Duplicated block (12 lines × 3) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 70 of 70 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 70 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, 301 of 340 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 127 test files), but it was not re-run: the analyzer environment could not run it. 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 (51 contributor(s) across 3936 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 50 hold 0.3% 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (project/plugins.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Guice and Play dependency injection, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 8 | COPY --from=builder /opt/play /opt/play -------------------- ERROR: failed to solve: flowcommerce/play_java17:latest: failed to resolve source metadata for docker.io/flowcommerce/play_java17:latest: failed to do request: Head "https://registry-1.docker.io/v2/flowcommerce/play_java17/manifests/latest": Forbidden; runtime evidence skipped.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'anorm' is imported (generated/app/db/ApplicationMovesDao.scala:82), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'anorm' is imported (generated/app/db/ApplicationMovesDao.scala:82), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'anorm' is imported (generated/app/db/ApplicationMovesDao.scala:82), 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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.
- 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TypeValidator.validate at 57.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TypeValidator.validate (cyclomatic 57), JsonUtil.validate (cyclomatic 43), Field.specialize (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was TypeValidator.validate at 80.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with TypeValidator.validate (cognitive 80), Versions.show (cognitive 47). — 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 7.5 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with InternalApiJsonForm.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
58 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 9 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with OriginalsDao.scala (5), ServiceDiff.scala, Code.scala. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with InternalApiJsonForm.scala, OriginalsDao.scala, VersionsDao.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with SyncGeneratorServiceProcessor.scala, Members.scala, Versions.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
14 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 2 module(s) off the main sequence, with abstractness counted on 7 of the 14 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
8 of 54 classes have LCOM4 above 3.
What to do
- Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with Organizations.scala (2), Applications.scala, MembershipRequests.scala. — One of this dimension's main actionable groups (8 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
798 test methods: 798 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 798 test case(s) across 122 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D12 · Dependency Hygiene
20 outdated direct sbt declarations. 24 of 27 direct declarations were graded against Maven Central (3 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 24 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 1 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. A further 3 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
31 deducted task-comment markers across 41807 LoC (0.1/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 31 TodoComment finding(s) in Explicit Debt — start with MainTemplate.scala (2), Field.scala (2), InternalMembershipsDao.scala (2). — One of this dimension's main actionable groups (31 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (sbt) 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)
8 finding(s): 0 critical, 8 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 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 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)
15 finding(s): 0 critical, 10 high, 5 medium, 0 low. 3 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 69 file(s) — `api/app/views/emails/applicationCreated.scala.html` (lines 1–5, line 11, line 15), `api/app/views/emails/emailVerificationCreated.scala.html` (lines 1–4), `api/app/views/emails/membershipCreated.scala.html` (lines 1–4), `api/app/views/emails/membershipRequestCreated.scala.html` (lines 1–4), `api/app/views/emails/passwordResetRequestCreated.scala.html` (lines 1–4), … (+64 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 2 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
8 finding(s): 0 critical, 2 high, 4 medium, 2 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
90 of 91 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/app/builder/ServiceSpecValidator.scala. Counted over 91 of the 249 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 87 Orphaned file finding(s) in Knowledge Freshness — start with Versions.scala (2), Organizations.scala (2), Parser.scala (2). — One of this dimension's main actionable groups (87 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ServiceSpecValidator.scala, InternalApiJsonForm.scala, ServiceBuilder.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×13) — app/app/views/account/profile/edit.scala.html:15, app/app/views/application_settings/form.scala.html:11, app/app/views/application_settings/move_form.scala.html:11, …
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — app/app/views/mainNavbar.scala.html:18
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — app/app/views/mainNavbar.scala.html:23
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×12) — app/app/views/attributes/index.scala.html:14, app/app/views/code/index.scala.html:18, app/app/views/doc/examples.scala.html:15, …
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — app/app/views/doc/index.scala.html:14
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — app/app/views/doc/main.scala.html:8, app/app/views/main.scala.html:7
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — app/app/views/doc/main.scala.html:8, app/app/views/main.scala.html:7
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×2) — app/app/views/versions/resources.scala.html:29, app/app/views/versions/resources.scala.html:30
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.nav-sidebar > .active > a` sets color: #fff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — app/public/stylesheets/main.css:73
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 79 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `Client` declares 25 abstract members: `baseUrl`, `applications`, `attributes`, `authentications`, `batchDownloadApplications`, `batchVersionsLatest`, `changes`, `code`, `domains`, `emailVerificationConfirmationForms`, `generatorServices`, `generatorWithServices`, `healthchecks`, `items`, `membershipRequests`, `memberships`, `organizations`, `passwordResetRequests`, `passwordResets`, `subscriptions`, `tokens`, `users`, `validations`, `versions`, `watches`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — generated/app/ApicollectiveApibuilderApiV0Client.scala:3940
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
- `description` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — generated/app/ApicollectiveApibuilderApiV0Client.scala:688
- `isMaterial` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — generated/app/ApicollectiveApibuilderApiV0Client.scala:689
- A placeholder string ("lorem ipsum") is still in shipped code — typical of generated boilerplate that was never filled in. — api/app/lib/ExampleJson.scala:337
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `description` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — generated/app/ApicollectiveApibuilderApiV0Client.scala:688
- `isMaterial` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — generated/app/ApicollectiveApibuilderApiV0Client.scala:689
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. (×3) — api/app/controllers/Code.scala:133, swagger/src/main/scala/io/apibuilder/swagger/Parser.scala:185, swagger/src/main/scala/io/apibuilder/swagger/translators/Response.scala:12
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
- The root README is 13 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 6 of 6 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- 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
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2791 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
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `csv` is async and calls Await.result — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — app/app/lib/MemberDownload.scala:16
What to do
- Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — api/app/util/LockUtil.scala:37
- This repository runs an HTTP server and nothing in its Scala source or committed configuration secures the transport: no HTTPS served (akka/pekko-http `ConnectionContext.httpsServer`/`enableHttps`, an http4s builder's `withTLS`, Jetty's `SslContextFactory`, zio-http's `SSLConfig`, Play's `https.port`), no `Strict-Transport-Security` header, HSTS middleware or Play `RedirectHttpsFilter`, no `X-Forwarded-Proto` read or Play `play.http.forwarded.trustedProxies` for a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: api/conf/routes:1 — a Play route table.
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: api/conf/routes:1 — a Play route table.
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
- Secure the server's transport: serve TLS itself (akka/pekko-http `ConnectionContext.httpsServer(sslContext)` with `newServerAt(…).enableHttps(…)`, an http4s server builder's `withTLS(…)`, Play's `https.port`), or run it behind a TLS-terminating proxy and trust it (`X-Forwarded-Proto`; Play `play.http.forwarded.trustedProxies`); send `Strict-Transport-Security` once it is HTTPS-only (http4s `HSTS(…)`, Play `RedirectHttpsFilter`).
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
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
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `href` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `action` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `href` at this site, or validate it against the shape the position accepts before interpolating it. (×2) — app/public/javascripts/util.js:8, app/public/javascripts/util.js:17
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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
- `case _: Throwable` 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. (×7) — api/app/lib/ExampleJson.scala:284, api/app/lib/ExampleJson.scala:292, api/app/lib/ExampleJson.scala:300, …
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- No build over this repository's 269 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 72% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 31% | Weak — gated by D34, M1, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Adequate — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 46% | Weak — gated by D28, D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 42% | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'anorm' (generated/app/db/ApplicationMovesDao.scala:82) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). 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 'anorm' (generated/app/db/ApplicationMovesDao.scala:82) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). 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 'anorm' (generated/app/db/ApplicationMovesDao.scala:82) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). 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 — 45 check(s) not relevant to this codebase
- 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
- 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
- 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) — 8 | COPY --from=builder /opt/play /opt/play -------------------- ERROR: failed to solve: flowcommerce/play_java17:latest: failed to resolve source metadata for docker.io/flowcommerce/play_java17:latest: failed to do request: Head "https://registry-1.docker.io/v2/flowcommerce/play_java17/manifests/latest": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~14028 lines of test source are present (.scala) 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 .scala 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.
- D21 Naming Consistency — Naming consistency is measured on C# only; Ruby, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rb, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 2 needed — the count is met but a required primary signal is absent): 532 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- 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 4 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Ruby source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Scala code has 44,427 production line(s), 6 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby and Scala were 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; a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- 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.
- 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 — 30 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Document without a <title> app/app/views/doc/main.scala.html:8
- Document without a <title> app/app/views/main.scala.html:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label app/app/views/mainNavbar.scala.html:18
- <button> with no accessible text app/app/views/mainNavbar.scala.html:23
- REDACTED
Serious — 178 finding(s)
- TodoComment swagger/src/test/scala/io/apibuilder/swagger/SwaggerServiceValidatorSpec.scala:40
- TodoComment swagger/src/main/scala/io/apibuilder/swagger/Parser.scala:30
- TodoComment swagger/src/main/scala/io/apibuilder/swagger/translators/Resolver.scala:50
- TodoComment lib/src/test/scala/TextSpec.scala:225
- TodoComment app/app/models/MainTemplate.scala:16
- TodoComment swagger/src/main/scala/io/apibuilder/swagger/SchemaType.scala:21
- TodoComment swagger/src/main/scala/io/apibuilder/swagger/translators/Field.scala:95
- TodoComment swagger/src/main/scala/io/apibuilder/swagger/translators/Field.scala:100
- TodoComment core/test/core/InterfaceImportsSpec.scala:45
- TodoComment core/test/core/ServiceMapSpec.scala:62
- TodoComment core/app/builder/ServiceSpecValidator.scala:188
- TodoComment core/app/builder/api_json/ApiJsonServiceValidator.scala:120
- TodoComment core/app/builder/api_json/upgrades/InterfacesToSupportResources.scala:7
- TodoComment app/app/models/MainTemplate.scala:66
- TodoComment app/app/controllers/OrganizationAttributesController.scala:23
- TodoComment app/app/controllers/Versions.scala:61
- TodoComment api/test/db/InternalEmailVerificationsDaoSpec.scala:21
- TodoComment api/test/controllers/GeneratorServicesSpec.scala:21
- TodoComment api/app/lib/Emails.scala:52
- TodoComment api/app/db/InternalMembershipRequestsDao.scala:133
- TodoComment api/app/db/InternalMembershipsDao.scala:167
- TodoComment api/app/db/InternalMembershipsDao.scala:74
- TodoComment api/app/db/InternalOrganizationsDao.scala:34
- TodoComment api/app/db/InternalOrganizationsDao.scala:154
- TodoComment api/app/db/InternalTasksDao.scala:20
- <fieldset> without a <legend> app/app/views/account/profile/edit.scala.html:15
- <fieldset> without a <legend> app/app/views/application_settings/form.scala.html:11
- <fieldset> without a <legend> app/app/views/application_settings/move_form.scala.html:11
- <fieldset> without a <legend> app/app/views/attributes/attributeForm.scala.html:5
- <fieldset> without a <legend> app/app/views/domains/form.scala.html:11
- <fieldset> without a <legend> app/app/views/generators/generatorForm.scala.html:5
- <fieldset> without a <legend> app/app/views/login/forgotPassword.scala.html:9
- <fieldset> without a <legend> app/app/views/login/legacy.scala.html:42
- <fieldset> without a <legend> app/app/views/login/resetPassword.scala.html:15
- <fieldset> without a <legend> app/app/views/members/add.scala.html:16
- <fieldset> without a <legend> app/app/views/organization_attributes/edit.scala.html:15
- <fieldset> without a <legend> app/app/views/organizations/orgForm.scala.html:9
- <fieldset> without a <legend> app/app/views/tokens/create.scala.html:14
- Data table has no header cells app/app/views/attributes/index.scala.html:14
- Data table has no header cells app/app/views/code/index.scala.html:18
- Data table has no header cells app/app/views/doc/examples.scala.html:15
- Data table has no header cells app/app/views/history/index.scala.html:37
- Data table has no header cells app/app/views/index.scala.html:32
- Data table has no header cells app/app/views/index.scala.html:56
- Data table has no header cells app/app/views/index.scala.html:84
- Data table has no header cells app/app/views/organization_attributes/index.scala.html:9
- Data table has no header cells app/app/views/organizations/membershipRequests.scala.html:10
- Data table has no header cells app/app/views/search/index.scala.html:14
- Data table has no header cells app/app/views/subscriptions/index.scala.html:10
- Data table has no header cells app/app/views/versions/imports.scala.html:3
- Duplicated block (6 lines × 2) api/app/lib/ServiceDiff.scala:174
- Duplicated block (6 lines × 2) app/app/controllers/Code.scala:32
- Duplicated block (6 lines × 2) core/app/builder/api_json/ServiceBuilder.scala:134
- Duplicated block (6 lines × 2) generated/app/db/MembershipRequestsDao.scala:542
- Duplicated block (6 lines × 2) generated/app/db/OriginalsDao.scala:273
- Duplicated block (6 lines × 2) generated/app/db/OriginalsDao.scala:403
- Duplicated block (6 lines × 2) generated/app/db/OriginalsDao.scala:423
- Duplicated block (6 lines × 2) generated/app/db/OriginalsDao.scala:443
- Duplicated block (6 lines × 2) generated/app/db/OriginalsDao.scala:463
- Low cohesion: Organizations (LCOM4 8) api/app/controllers/Organizations.scala:16
- Low cohesion: Applications (LCOM4 7) api/app/controllers/Applications.scala:16
- Low cohesion: MembershipRequests (LCOM4 4) api/app/controllers/MembershipRequests.scala:15
- Low cohesion: Tokens (LCOM4 4) api/app/controllers/Tokens.scala:15
- Low cohesion: Users (LCOM4 4) api/app/controllers/Users.scala:20
- Low cohesion: Versions (LCOM4 4) api/app/controllers/Versions.scala:17
- Low cohesion: LoginController (LCOM4 4) app/app/controllers/LoginController.scala:14
- Low cohesion: Organizations (LCOM4 4) app/app/controllers/Organizations.scala:16
- Swallowed exception (caught, then discarded) api/app/lib/ExampleJson.scala:284
- Swallowed exception (caught, then discarded) api/app/lib/ExampleJson.scala:292
- Swallowed exception (caught, then discarded) api/app/lib/ExampleJson.scala:300
- Swallowed exception (caught, then discarded) api/app/lib/ExampleJson.scala:308
- Swallowed exception (caught, then discarded) api/app/lib/ExampleJson.scala:316
- Swallowed exception (caught, then discarded) api/app/lib/ExampleJson.scala:324
- Swallowed exception (caught, then discarded) api/app/lib/ExampleJson.scala:332
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) core/app/builder/api_json/InternalApiJsonForm.scala:831
- Duplicated block (7 lines × 2) generated/app/db/OriginalsDao.scala:295
- Duplicated block (7 lines × 2) generated/app/db/VersionsDao.scala:144
- Duplicated block (7 lines × 2) generated/app/db/cache/ServicesDao.scala:148
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) api/app/processor/SyncGeneratorServiceProcessor.scala:42
- Duplicated block (13 lines × 2) app/app/controllers/Members.scala:120
- Duplicated block (13 lines × 2) app/app/controllers/Versions.scala:79
- Duplicated block (8 lines × 2) api/app/controllers/Applications.scala:50
- Duplicated block (8 lines × 2) api/app/lib/ServiceDiff.scala:519
- Duplicated block (8 lines × 2) generated/app/db/MembershipRequestsDao.scala:553
- Duplicated block (5 lines × 3) api/app/lib/ServiceDiff.scala:175
- Duplicated block (5 lines × 3) generated/app/db/EmailVerificationsDao.scala:124
- Duplicated block (5 lines × 3) generated/app/db/MembershipRequestsDao.scala:110
- Duplicated block (5 lines × 2) app/app/controllers/Members.scala:108
- Duplicated block (5 lines × 2) core/app/builder/api_json/InternalApiJsonForm.scala:515
- Duplicated block (5 lines × 2) avro/src/main/scala/io/apibuilder/avro/Parser.scala:122
- Duplicated block (6 lines × 3) generated/app/db/EmailVerificationsDao.scala:491
- Duplicated block (6 lines × 3) generated/app/db/EmailVerificationsDao.scala:511
- Duplicated block (6 lines × 3) generated/app/db/OriginalsDao.scala:362
- Page without a main landmark app/app/views/doc/main.scala.html:8
- Page without a main landmark app/app/views/main.scala.html:7
- Anchor without href app/app/views/versions/resources.scala.html:29
- Anchor without href app/app/views/versions/resources.scala.html:30
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 3) generated/app/db/EmailVerificationsDao.scala:142
- Duplicated block (12 lines × 3) generated/app/db/MembershipRequestsDao.scala:128
- Duplicated block (10 lines × 2) api/app/processor/SyncGeneratorServiceProcessor.scala:86
- Duplicated block (10 lines × 2) app/app/controllers/Versions.scala:301
- Duplicated block (9 lines × 2) generated/app/db/ApplicationMovesDao.scala:138
- Duplicated block (9 lines × 2) api/app/processor/SyncGeneratorServiceProcessor.scala:66
- Duplicated block (6 lines × 20) generated/app/db/ApplicationMovesDao.scala:467
- Duplicated block (6 lines × 20) generated/app/db/ApplicationMovesDao.scala:487
- Duplicated block (6 lines × 4) generated/app/db/ApplicationMovesDao.scala:507
- Duplicated block (6 lines × 4) generated/app/db/ApplicationMovesDao.scala:527
- Duplicated block (6 lines × 6) generated/app/db/ApplicationsDao.scala:485
- Duplicated block (6 lines × 6) generated/app/db/ApplicationsDao.scala:505
- Duplicated block (6 lines × 9) generated/app/db/EmailVerificationsDao.scala:531
- Duplicated block (6 lines × 9) generated/app/db/EmailVerificationsDao.scala:551
- Off the main sequence: lib
- Off the main sequence: generated
- Unfinished stub — body is `???` generated/app/ApicollectiveApibuilderApiV0Client.scala:688
- Unfinished stub — body is `???` generated/app/ApicollectiveApibuilderApiV0Client.scala:689
- Unfinished stub — body is ??? / NotImplementedError generated/app/ApicollectiveApibuilderApiV0Client.scala:688
- Unfinished stub — body is ??? / NotImplementedError generated/app/ApicollectiveApibuilderApiV0Client.scala:689
- Document value reaches a markup attribute unescaped app/public/javascripts/util.js:8
- Document value reaches a markup attribute unescaped app/public/javascripts/util.js:17
- Heading level jumps from h1 to h3 app/app/views/doc/index.scala.html:14
- Low contrast colour pair in CSS (3.6:1) app/public/stylesheets/main.css:73
- Accessibility enforcement below the top rung
- TypeValidator.validate (cyclomatic 57) core/app/TypeValidator.scala:174
- JsonUtil.validate (cyclomatic 43) core/app/builder/JsonUtil.scala:14
- Field.specialize (cyclomatic 18) swagger/src/main/scala/io/apibuilder/swagger/translators/Field.scala:46
- InternalOrganizationsDao.validate (cyclomatic 16) api/app/db/InternalOrganizationsDao.scala:39
- TypeValidator.validate (cognitive 80) core/app/TypeValidator.scala:174
- Versions.show (cognitive 47) app/app/controllers/Versions.scala:31
- InternalOrganizationsDao.validate (cognitive 25) api/app/db/InternalOrganizationsDao.scala:39
- JsonUtil.validate (cognitive 20) core/app/builder/JsonUtil.scala:14
- Versions.postByVersion (cognitive 17) api/app/controllers/Versions.scala:102
- Versions.putByApplicationKeyAndVersion (cognitive 17) api/app/controllers/Versions.scala:150
- InternalApplicationsDao.validate (cognitive 17) api/app/db/InternalApplicationsDao.scala:57
- Parser.buildModels (cognitive 17) swagger/src/main/scala/io/apibuilder/swagger/Parser.scala:90
- DatatypeResolver.parse (cognitive 16) lib/src/main/scala/Kind.scala:72
- FileTooLong: api_json/InternalApiJsonForm.scala core/app/builder/api_json/InternalApiJsonForm.scala
- REDACTED
- REDACTED
- Members sharing a duplicated core (22 members, 50+ identical tokens) generated/app/db/ApplicationMovesDao.scala:354
- Members sharing a duplicated core (21 members, 50+ identical tokens) generated/app/db/ApplicationMovesDao.scala:163
- Members sharing a duplicated core (20 members, 50+ identical tokens) generated/app/db/ApplicationMovesDao.scala:426
- Members sharing a duplicated core (4 members, 50+ identical tokens) generated/app/db/GeneratorInvocationsDao.scala:132
- Duplicated block (19–21 lines × 2) api/app/controllers/Versions.scala:128
- Duplicated block (20 lines × 2) api/app/controllers/Versions.scala:105
- Duplicated block (17 lines × 2) api/app/processor/SyncGeneratorServiceProcessor.scala:98
- Duplicated block (14 lines × 21) generated/app/db/ApplicationMovesDao.scala:177
- Duplicated block (14 lines × 4) generated/app/db/GeneratorInvocationsDao.scala:140
- Duplicated block (14 lines × 2) api/app/db/InternalMembershipRequestsDao.scala:135
- Duplicated block (11 lines × 2) generated/app/db/TasksDao.scala:177
- Duplicated block (9 lines × 3) app/app/controllers/Versions.scala:82
- Duplicated block (6 lines × 22) generated/app/db/ApplicationMovesDao.scala:360
- Duplicated block (5 lines × 20) generated/app/db/ApplicationMovesDao.scala:427
- Duplicated block (23 lines × 2) api/app/models/MembershipRequestsModel.scala:19
- Duplicated block (12 lines × 2) api/app/lib/Config.scala:26
- Duplicated block (9 lines × 20) generated/app/db/ApplicationMovesDao.scala:331
- Duplicated block (7 lines × 5) generated/app/db/ApplicationsDao.scala:383
- Duplicated block (9 lines × 5) generated/app/db/AttributesDao.scala:123
- Duplicated block (7 lines × 3) generated/app/db/GeneratorInvocationsDao.scala:320
- End-of-life runtime: Scala 3.7 REDACTED:1
- Sync-over-async blocking app/app/lib/MemberDownload.scala:16
- Weak hash algorithm api/app/util/LockUtil.scala:37
Minor — 112 finding(s)
- Orphaned file api/app/lib/ServiceDiff.scala:1
- Orphaned file app/app/controllers/Versions.scala:1
- Orphaned file core/app/builder/api_json/ApiJsonServiceValidator.scala:1
- Orphaned file api/app/db/InternalVersionsDao.scala:1
- Orphaned file api/app/lib/ExampleJson.scala:1
- Orphaned file core/app/TypeValidator.scala:1
- Orphaned file api/app/db/InternalApplicationsDao.scala:1
- Orphaned file api/app/controllers/Versions.scala:1
- Orphaned file app/app/controllers/Organizations.scala:1
- Orphaned file swagger/src/main/scala/io/apibuilder/swagger/Parser.scala:1
- Orphaned file api/app/db/InternalUsersDao.scala:1
- Orphaned file api/app/controllers/Code.scala:1
- Orphaned file core/app/builder/JsonUtil.scala:1
- Orphaned file api/app/db/InternalOrganizationsDao.scala:1
- Orphaned file app/app/controllers/LoginController.scala:1
- Orphaned file app/app/controllers/Members.scala:1
- Orphaned file app/app/controllers/ApiBuilderController.scala:1
- Orphaned file app/app/controllers/ApplicationSettings.scala:1
- Orphaned file core/app/builder/api_json/InternalDatatype.scala:1
- Orphaned file swagger/src/main/scala/io/apibuilder/swagger/Util.scala:1
- Orphaned file api/app/processor/EmailProcessor.scala:1
- Orphaned file api/app/db/InternalMembershipsDao.scala:1
- Orphaned file api/app/db/InternalMembershipRequestsDao.scala:1
- Orphaned file avro/src/main/scala/io/apibuilder/avro/Parser.scala:1
- Orphaned file api/app/controllers/Users.scala:1
- Most significant orphaned file core/app/builder/ServiceSpecValidator.scala:1
- Most significant orphaned file core/app/builder/api_json/InternalApiJsonForm.scala:1
- Most significant orphaned file core/app/builder/api_json/ServiceBuilder.scala:1
- Blanket warning suppression api/app/controllers/Code.scala:133
- Blanket warning suppression swagger/src/main/scala/io/apibuilder/swagger/Parser.scala:185
- Blanket warning suppression swagger/src/main/scala/io/apibuilder/swagger/translators/Response.scala:12
- REDACTED
- REDACTED
- Fat interface: Client (25 abstract members) generated/app/ApicollectiveApibuilderApiV0Client.scala:3940
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- Placeholder literal left in code api/app/lib/ExampleJson.scala:337
- Thin README
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
- Scala's null is not held to the type system everywhere
Minor — 20 finding(s)
- Outdated: com.datadoghq:dd-java-agent
- Outdated: com.github.tototoshi:scala-csv_3
- Outdated: com.google.inject:guice
- Outdated: com.google.inject.extensions:guice-assistedinject
- Outdated: com.rollbar:rollbar-java
- Outdated: com.typesafe.play:play-json_3
- Outdated: io.circe:circe-core_3
- Outdated: io.circe:circe-generic_3
- Outdated: io.circe:circe-parser_3
- Outdated: io.swagger:swagger-parser
- Outdated: joda-time:joda-time
- Outdated: org.apache.avro:avro
- Outdated: org.apache.avro:avro-compiler
- Outdated: org.atteo:evo-inflector
- Outdated: org.playframework:play-guice_3
- Outdated: org.playframework.anorm:anorm-postgres_3
- Outdated: org.postgresql:postgresql
- Outdated: org.typelevel:cats-core_3
- Outdated: org.webjars:bootstrap
- Outdated: org.webjars:webjars-play_3
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f8ece85798c740b5b140852f17c8940a/history.json --exit-code 0 --source . | 18 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f8ece85798c740b5b140852f17c8940a/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-9bd63c2ece304278b1dcc64209d4335a | 5 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-9bd63c2ece304278b1dcc64209d4335a | 0 | artifacts/raw/osv-scanner.json |