Executive summary
ScottArbeit/Grace meets our standard for a preview release. It scores 65 out of 100 and is rated Strong, and 13 of its 26 critical findings are security problems.
Performance, at 60, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 4 points. Removing the blocking calls would lift Performance itself, also worth about 4. Raising Performance to 65 would lift the score to about 66.
Six passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and five sets of files in separate parts keep changing together, which points to hidden dependencies. Replacing each exposed password or key, pinning each tool to an exact version and making the hidden dependencies explicit would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. The three sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 157,285 lines, about €480,000 to rebuild.
If Performance rose from 60 to 65, the lowest score rated Strong, the score would rise from 65 to about 66.
Fixed since the last survey: 3 findings
- REDACTED Scanning · Leaked secret: signing-key src/Grace.Shared/Constants.Shared.fs
- Secrets (history) · High secret: REDACTED src/docker-compose.yml
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €480,000 · Estimate
| Cost to rebuild | €160,000 to €800,000, for 2,647 to 8,417 hours of work, about 3.3 person-years for 1 to 7 engineers |
|---|---|
| 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.9 at a score of 65. 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 | Large: 157,285 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Grace.Actors.Interfaces | 2 Grace.CLI.Command.WorkingDirectoryUpdateContracts | 3 Grace.CLI.Services | 4 Grace.Shared.Parameters.Common | 5 Grace.Shared.Validation.Common.Guid | 6 Grace.Types.Common | 7 Grace.Types.Usage | 8 grace_generated_openapi_probe.apis.configuration | 9 grace_generated_openapi_probe.models.file_content_reference | 10 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.approvals_api | 11 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.branches_api | 12 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.default_api | 13 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.directories_api | 14 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.libraries_api | 15 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.owners_api | 16 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.repositories_api | 17 sdk.generated.matrix.openapi-generator.typescript-fetch.src.models | 18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime | 19 Grace.Types.ContentBlockMetadata | 20 Grace.Types.Library | 21 Grace.Types.Reference | 22 Grace.Types.Repository | 23 Grace.Types.Webhooks | 24 grace_generated_openapi_probe.apis.branches_api | 25 grace_generated_openapi_probe.apis.default_api | 26 grace_generated_openapi_probe.apis.libraries_api | 27 grace_generated_openapi_probe.apis.repositories_api | 28 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi | 29 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi | 30 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi | 31 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi | 32 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi | 33 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi | 34 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi | 35 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi | 36 Grace.Types.Events | 37 Grace.Types.Reminder | 38 Grace.Actors.DirectoryVersion | 39 Grace.Actors.Services | 40 Grace.Server.Branch |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Grace.Actors.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 2 Grace.CLI.Command.WorkingDirectoryUpdateContracts | ||||||||||||||||||||||||||||||||||||||||
| 3 Grace.CLI.Services | ||||||||||||||||||||||||||||||||||||||||
| 4 Grace.Shared.Parameters.Common | ||||||||||||||||||||||||||||||||||||||||
| 5 Grace.Shared.Validation.Common.Guid | ||||||||||||||||||||||||||||||||||||||||
| 6 Grace.Types.Common | ||||||||||||||||||||||||||||||||||||||||
| 7 Grace.Types.Usage | ||||||||||||||||||||||||||||||||||||||||
| 8 grace_generated_openapi_probe.apis.configuration | ||||||||||||||||||||||||||||||||||||||||
| 9 grace_generated_openapi_probe.models.file_content_reference | ||||||||||||||||||||||||||||||||||||||||
| 10 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.approvals_api | ||||||||||||||||||||||||||||||||||||||||
| 11 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.branches_api | ||||||||||||||||||||||||||||||||||||||||
| 12 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.default_api | ||||||||||||||||||||||||||||||||||||||||
| 13 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.directories_api | ||||||||||||||||||||||||||||||||||||||||
| 14 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.libraries_api | ||||||||||||||||||||||||||||||||||||||||
| 15 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.owners_api | ||||||||||||||||||||||||||||||||||||||||
| 16 sdk.generated.matrix.openapi-generator.python.grace_generated_openapi_probe.api.repositories_api | ||||||||||||||||||||||||||||||||||||||||
| 17 sdk.generated.matrix.openapi-generator.typescript-fetch.src.models | ||||||||||||||||||||||||||||||||||||||||
| 18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime | ||||||||||||||||||||||||||||||||||||||||
| 19 Grace.Types.ContentBlockMetadata | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Grace.Types.Library | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Grace.Types.Reference | 7 | |||||||||||||||||||||||||||||||||||||||
| 22 Grace.Types.Repository | 14 | |||||||||||||||||||||||||||||||||||||||
| 23 Grace.Types.Webhooks | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 grace_generated_openapi_probe.apis.branches_api | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 grace_generated_openapi_probe.apis.default_api | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 grace_generated_openapi_probe.apis.libraries_api | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 grace_generated_openapi_probe.apis.repositories_api | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 Grace.Types.Events | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 Grace.Types.Reminder | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Grace.Actors.DirectoryVersion | 3 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Grace.Actors.Services | 4 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||
| 40 Grace.Server.Branch | 1 | 2 | 1 | 3 | 1 | 1 |
19→6 Grace.Types.ContentBlockMetadata uses Grace.Types.Common✕
- Connections
- 1 pair of types, where a type in Grace.Types.ContentBlockMetadata uses a type in Grace.Types.Common.
- The types involved
Grace.Types.ContentBlockMetadata.ContentBlockMetadataEvent→Grace.Types.Common.EventMetadata
- Direction
- Grace.Types.ContentBlockMetadata uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Types.ContentBlockMetadata, while a change to Grace.Types.ContentBlockMetadata can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Types.ContentBlockMetadata uses a module listed above it, which is the healthy direction.
20→5 Grace.Types.Library uses Grace.Shared.Validation.Common.Guid✕
- Connections
- 3 pairs of types, where a type in Grace.Types.Library uses a type in Grace.Shared.Validation.Common.Guid.
- The types involved
Grace.Types.Library.LibraryBaselineManifestDocument→Grace.Shared.Validation.Common.Guid.GuidGrace.Types.Library.LibraryControlDocument→Grace.Shared.Validation.Common.Guid.GuidGrace.Types.Library.LibraryCursorEpoch→Grace.Shared.Validation.Common.Guid.Guid
- Direction
- Grace.Types.Library uses Grace.Shared.Validation.Common.Guid, so a change to Grace.Shared.Validation.Common.Guid can break Grace.Types.Library, while a change to Grace.Types.Library can't break Grace.Shared.Validation.Common.Guid.
- Position
- Below the diagonal: Grace.Types.Library uses a module listed above it, which is the healthy direction.
20→6 Grace.Types.Library uses Grace.Types.Common✕
- Connections
- 1 pair of types, where a type in Grace.Types.Library uses a type in Grace.Types.Common.
- The types involved
Grace.Types.Library.LibraryContentLocationDocument→Grace.Types.Common.FileManifest
- Direction
- Grace.Types.Library uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Types.Library, while a change to Grace.Types.Library can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Types.Library uses a module listed above it, which is the healthy direction.
21→6 Grace.Types.Reference uses Grace.Types.Common✕
- Connections
- 7 pairs of types, where a type in Grace.Types.Reference uses a type in Grace.Types.Common.
- The types involved
Grace.Types.Reference.CurrentBranchReferenceNotification→Grace.Types.Common.ReferenceTypeGrace.Types.Reference.ReferenceCommand→Grace.Types.Common.ReferenceLinkTypeGrace.Types.Reference.ReferenceCommand→Grace.Types.Common.ReferenceTypeGrace.Types.Reference.ReferenceDto→Grace.Types.Common.ReferenceTypeGrace.Types.Reference.ReferenceEvent→Grace.Types.Common.EventMetadataGrace.Types.Reference.ReferenceEventType→Grace.Types.Common.ReferenceLinkTypeGrace.Types.Reference.ReferenceEventType→Grace.Types.Common.ReferenceType
- Direction
- Grace.Types.Reference uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Types.Reference, while a change to Grace.Types.Reference can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Types.Reference uses a module listed above it, which is the healthy direction.
22→6 Grace.Types.Repository uses Grace.Types.Common✕
- Connections
- 14 pairs of types, where a type in Grace.Types.Repository uses a type in Grace.Types.Common.
- The types involved
Grace.Types.Repository.RepositoryCommand→Grace.Types.Common.ConflictResolutionPolicyGrace.Types.Repository.RepositoryCommand→Grace.Types.Common.ObjectStorageProviderGrace.Types.Repository.RepositoryCommand→Grace.Types.Common.RepositoryStatusGrace.Types.Repository.RepositoryCommand→Grace.Types.Common.RepositoryTypeGrace.Types.Repository.RepositoryDto→Grace.Types.Common.ConflictResolutionPolicyGrace.Types.Repository.RepositoryDto→Grace.Types.Common.ManifestEligibilityPolicyGrace.Types.Repository.RepositoryDto→Grace.Types.Common.ObjectStorageProviderGrace.Types.Repository.RepositoryDto→Grace.Types.Common.RepositoryStatusGrace.Types.Repository.RepositoryDto→Grace.Types.Common.RepositoryTypeGrace.Types.Repository.RepositoryEvent→Grace.Types.Common.EventMetadataGrace.Types.Repository.RepositoryEventType→Grace.Types.Common.ConflictResolutionPolicyGrace.Types.Repository.RepositoryEventType→Grace.Types.Common.ObjectStorageProviderGrace.Types.Repository.RepositoryEventType→Grace.Types.Common.RepositoryStatusGrace.Types.Repository.RepositoryEventType→Grace.Types.Common.RepositoryType
- Direction
- Grace.Types.Repository uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Types.Repository, while a change to Grace.Types.Repository can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Types.Repository uses a module listed above it, which is the healthy direction.
23→6 Grace.Types.Webhooks uses Grace.Types.Common✕
- Connections
- 2 pairs of types, where a type in Grace.Types.Webhooks uses a type in Grace.Types.Common.
- The types involved
Grace.Types.Webhooks.ApprovalRequestEvent→Grace.Types.Common.EventMetadataGrace.Types.Webhooks.ApprovalRequestIndexEvent→Grace.Types.Common.EventMetadata
- Direction
- Grace.Types.Webhooks uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Types.Webhooks, while a change to Grace.Types.Webhooks can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Types.Webhooks uses a module listed above it, which is the healthy direction.
24→8 grace_generated_openapi_probe.apis.branches_api uses grace_generated_openapi_probe.apis.configuration✕
- Connections
- 1 pair of types, where a type in grace_generated_openapi_probe.apis.branches_api uses a type in grace_generated_openapi_probe.apis.configuration.
- The types involved
grace_generated_openapi_probe.apis.branches_api.branches_api$module→grace_generated_openapi_probe.apis.configuration.Configuration
- Direction
- grace_generated_openapi_probe.apis.branches_api uses grace_generated_openapi_probe.apis.configuration, so a change to grace_generated_openapi_probe.apis.configuration can break grace_generated_openapi_probe.apis.branches_api, while a change to grace_generated_openapi_probe.apis.branches_api can't break grace_generated_openapi_probe.apis.configuration.
- Position
- Below the diagonal: grace_generated_openapi_probe.apis.branches_api uses a module listed above it, which is the healthy direction.
25→8 grace_generated_openapi_probe.apis.default_api uses grace_generated_openapi_probe.apis.configuration✕
- Connections
- 1 pair of types, where a type in grace_generated_openapi_probe.apis.default_api uses a type in grace_generated_openapi_probe.apis.configuration.
- The types involved
grace_generated_openapi_probe.apis.default_api.default_api$module→grace_generated_openapi_probe.apis.configuration.Configuration
- Direction
- grace_generated_openapi_probe.apis.default_api uses grace_generated_openapi_probe.apis.configuration, so a change to grace_generated_openapi_probe.apis.configuration can break grace_generated_openapi_probe.apis.default_api, while a change to grace_generated_openapi_probe.apis.default_api can't break grace_generated_openapi_probe.apis.configuration.
- Position
- Below the diagonal: grace_generated_openapi_probe.apis.default_api uses a module listed above it, which is the healthy direction.
26→8 grace_generated_openapi_probe.apis.libraries_api uses grace_generated_openapi_probe.apis.configuration✕
- Connections
- 1 pair of types, where a type in grace_generated_openapi_probe.apis.libraries_api uses a type in grace_generated_openapi_probe.apis.configuration.
- The types involved
grace_generated_openapi_probe.apis.libraries_api.libraries_api$module→grace_generated_openapi_probe.apis.configuration.Configuration
- Direction
- grace_generated_openapi_probe.apis.libraries_api uses grace_generated_openapi_probe.apis.configuration, so a change to grace_generated_openapi_probe.apis.configuration can break grace_generated_openapi_probe.apis.libraries_api, while a change to grace_generated_openapi_probe.apis.libraries_api can't break grace_generated_openapi_probe.apis.configuration.
- Position
- Below the diagonal: grace_generated_openapi_probe.apis.libraries_api uses a module listed above it, which is the healthy direction.
27→8 grace_generated_openapi_probe.apis.repositories_api uses grace_generated_openapi_probe.apis.configuration✕
- Connections
- 1 pair of types, where a type in grace_generated_openapi_probe.apis.repositories_api uses a type in grace_generated_openapi_probe.apis.configuration.
- The types involved
grace_generated_openapi_probe.apis.repositories_api.repositories_api$module→grace_generated_openapi_probe.apis.configuration.Configuration
- Direction
- grace_generated_openapi_probe.apis.repositories_api uses grace_generated_openapi_probe.apis.configuration, so a change to grace_generated_openapi_probe.apis.configuration can break grace_generated_openapi_probe.apis.repositories_api, while a change to grace_generated_openapi_probe.apis.repositories_api can't break grace_generated_openapi_probe.apis.configuration.
- Position
- Below the diagonal: grace_generated_openapi_probe.apis.repositories_api uses a module listed above it, which is the healthy direction.
28→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi.ApprovalsApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi.ApprovalsApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.ApprovalsApi uses a module listed above it, which is the healthy direction.
29→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi.BranchesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi.BranchesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.BranchesApi uses a module listed above it, which is the healthy direction.
30→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi.DefaultApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi.DefaultApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DefaultApi uses a module listed above it, which is the healthy direction.
31→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi.DirectoriesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi.DirectoriesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.DirectoriesApi uses a module listed above it, which is the healthy direction.
32→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi.LibrariesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi.LibrariesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.LibrariesApi uses a module listed above it, which is the healthy direction.
33→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi.OrganizationsApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi.OrganizationsApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OrganizationsApi uses a module listed above it, which is the healthy direction.
34→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi.OwnersApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi.OwnersApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.OwnersApi uses a module listed above it, which is the healthy direction.
35→18 sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime✕
- Connections
- 2 pairs of types, where a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi uses a type in sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- The types involved
sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi.RepositoriesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.ApiResponsesdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi.RepositoriesApi→sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.RequestOpts
- Direction
- sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi uses sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime, so a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime can break sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi, while a change to sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi can't break sdk.generated.matrix.openapi-generator.typescript-fetch.src.runtime.
- Position
- Below the diagonal: sdk.generated.matrix.openapi-generator.typescript-fetch.src.apis.RepositoriesApi uses a module listed above it, which is the healthy direction.
36→20 Grace.Types.Events uses Grace.Types.Library✕
- Connections
- 1 pair of types, where a type in Grace.Types.Events uses a type in Grace.Types.Library.
- The types involved
Grace.Types.Events.GraceEvent→Grace.Types.Library.LibraryContentAvailable
- Direction
- Grace.Types.Events uses Grace.Types.Library, so a change to Grace.Types.Library can break Grace.Types.Events, while a change to Grace.Types.Events can't break Grace.Types.Library.
- Position
- Below the diagonal: Grace.Types.Events uses a module listed above it, which is the healthy direction.
36→21 Grace.Types.Events uses Grace.Types.Reference✕
- Connections
- 1 pair of types, where a type in Grace.Types.Events uses a type in Grace.Types.Reference.
- The types involved
Grace.Types.Events.GraceEvent→Grace.Types.Reference.ReferenceEvent
- Direction
- Grace.Types.Events uses Grace.Types.Reference, so a change to Grace.Types.Reference can break Grace.Types.Events, while a change to Grace.Types.Events can't break Grace.Types.Reference.
- Position
- Below the diagonal: Grace.Types.Events uses a module listed above it, which is the healthy direction.
36→22 Grace.Types.Events uses Grace.Types.Repository✕
- Connections
- 1 pair of types, where a type in Grace.Types.Events uses a type in Grace.Types.Repository.
- The types involved
Grace.Types.Events.GraceEvent→Grace.Types.Repository.RepositoryEvent
- Direction
- Grace.Types.Events uses Grace.Types.Repository, so a change to Grace.Types.Repository can break Grace.Types.Events, while a change to Grace.Types.Events can't break Grace.Types.Repository.
- Position
- Below the diagonal: Grace.Types.Events uses a module listed above it, which is the healthy direction.
36→23 Grace.Types.Events uses Grace.Types.Webhooks✕
- Connections
- 1 pair of types, where a type in Grace.Types.Events uses a type in Grace.Types.Webhooks.
- The types involved
Grace.Types.Events.GraceEvent→Grace.Types.Webhooks.ApprovalRequestEvent
- Direction
- Grace.Types.Events uses Grace.Types.Webhooks, so a change to Grace.Types.Webhooks can break Grace.Types.Events, while a change to Grace.Types.Events can't break Grace.Types.Webhooks.
- Position
- Below the diagonal: Grace.Types.Events uses a module listed above it, which is the healthy direction.
37→6 Grace.Types.Reminder uses Grace.Types.Common✕
- Connections
- 1 pair of types, where a type in Grace.Types.Reminder uses a type in Grace.Types.Common.
- The types involved
Grace.Types.Reminder.ReminderDto→Grace.Types.Common.ReminderTypes
- Direction
- Grace.Types.Reminder uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Types.Reminder, while a change to Grace.Types.Reminder can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Types.Reminder uses a module listed above it, which is the healthy direction.
37→21 Grace.Types.Reminder uses Grace.Types.Reference✕
- Connections
- 1 pair of types, where a type in Grace.Types.Reminder uses a type in Grace.Types.Reference.
- The types involved
Grace.Types.Reminder.ReminderState→Grace.Types.Reference.PhysicalDeletionReminderState
- Direction
- Grace.Types.Reminder uses Grace.Types.Reference, so a change to Grace.Types.Reference can break Grace.Types.Reminder, while a change to Grace.Types.Reminder can't break Grace.Types.Reference.
- Position
- Below the diagonal: Grace.Types.Reminder uses a module listed above it, which is the healthy direction.
37→22 Grace.Types.Reminder uses Grace.Types.Repository✕
- Connections
- 1 pair of types, where a type in Grace.Types.Reminder uses a type in Grace.Types.Repository.
- The types involved
Grace.Types.Reminder.ReminderState→Grace.Types.Repository.PhysicalDeletionReminderState
- Direction
- Grace.Types.Reminder uses Grace.Types.Repository, so a change to Grace.Types.Repository can break Grace.Types.Reminder, while a change to Grace.Types.Reminder can't break Grace.Types.Repository.
- Position
- Below the diagonal: Grace.Types.Reminder uses a module listed above it, which is the healthy direction.
38→1 Grace.Actors.DirectoryVersion uses Grace.Actors.Interfaces✕
- Connections
- 3 pairs of types, where a type in Grace.Actors.DirectoryVersion uses a type in Grace.Actors.Interfaces.
- The types involved
Grace.Actors.DirectoryVersion.DirectoryVersionActor→Grace.Actors.Interfaces.IDirectoryVersionActorGrace.Actors.DirectoryVersion.DirectoryVersionActor→Grace.Actors.Interfaces.IGraceReminderWithGuidKeyGrace.Actors.DirectoryVersion.DirectoryVersionActor→Grace.Actors.Interfaces.IHasRepositoryId
- Direction
- Grace.Actors.DirectoryVersion uses Grace.Actors.Interfaces, so a change to Grace.Actors.Interfaces can break Grace.Actors.DirectoryVersion, while a change to Grace.Actors.DirectoryVersion can't break Grace.Actors.Interfaces.
- Position
- Below the diagonal: Grace.Actors.DirectoryVersion uses a module listed above it, which is the healthy direction.
38→6 Grace.Actors.DirectoryVersion uses Grace.Types.Common✕
- Connections
- 5 pairs of types, where a type in Grace.Actors.DirectoryVersion uses a type in Grace.Types.Common.
- The types involved
Grace.Actors.DirectoryVersion.DirectoryVersion→Grace.Types.Common.EventMetadataGrace.Actors.DirectoryVersion.DirectoryVersion→Grace.Types.Common.FileManifestGrace.Actors.DirectoryVersion.DirectoryVersion→Grace.Types.Common.FileVersionGrace.Actors.DirectoryVersion.FileValidationResult→Grace.Types.Common.FileVersionGrace.Actors.DirectoryVersion.ManifestReferenceForSaveBoundary→Grace.Types.Common.FileManifest
- Direction
- Grace.Actors.DirectoryVersion uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Actors.DirectoryVersion, while a change to Grace.Actors.DirectoryVersion can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Actors.DirectoryVersion uses a module listed above it, which is the healthy direction.
38→22 Grace.Actors.DirectoryVersion uses Grace.Types.Repository✕
- Connections
- 1 pair of types, where a type in Grace.Actors.DirectoryVersion uses a type in Grace.Types.Repository.
- The types involved
Grace.Actors.DirectoryVersion.DirectoryVersion→Grace.Types.Repository.RepositoryDto
- Direction
- Grace.Actors.DirectoryVersion uses Grace.Types.Repository, so a change to Grace.Types.Repository can break Grace.Actors.DirectoryVersion, while a change to Grace.Actors.DirectoryVersion can't break Grace.Types.Repository.
- Position
- Below the diagonal: Grace.Actors.DirectoryVersion uses a module listed above it, which is the healthy direction.
38→37 Grace.Actors.DirectoryVersion uses Grace.Types.Reminder✕
- Connections
- 1 pair of types, where a type in Grace.Actors.DirectoryVersion uses a type in Grace.Types.Reminder.
- The types involved
Grace.Actors.DirectoryVersion.DirectoryVersionActor→Grace.Types.Reminder.ReminderDto
- Direction
- Grace.Actors.DirectoryVersion uses Grace.Types.Reminder, so a change to Grace.Types.Reminder can break Grace.Actors.DirectoryVersion, while a change to Grace.Actors.DirectoryVersion can't break Grace.Types.Reminder.
- Position
- Below the diagonal: Grace.Actors.DirectoryVersion uses a module listed above it, which is the healthy direction.
39→6 Grace.Actors.Services uses Grace.Types.Common✕
- Connections
- 4 pairs of types, where a type in Grace.Actors.Services uses a type in Grace.Types.Common.
- The types involved
Grace.Actors.Services.Services→Grace.Types.Common.EventMetadataGrace.Actors.Services.Services→Grace.Types.Common.FileVersionGrace.Actors.Services.Services→Grace.Types.Common.GraceIdsGrace.Actors.Services.Services→Grace.Types.Common.ReferenceType
- Direction
- Grace.Actors.Services uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→7 Grace.Actors.Services uses Grace.Types.Usage✕
- Connections
- 1 pair of types, where a type in Grace.Actors.Services uses a type in Grace.Types.Usage.
- The types involved
Grace.Actors.Services.Services→Grace.Types.Usage.UsageFactScope
- Direction
- Grace.Actors.Services uses Grace.Types.Usage, so a change to Grace.Types.Usage can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.Usage.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→19 Grace.Actors.Services uses Grace.Types.ContentBlockMetadata✕
- Connections
- 1 pair of types, where a type in Grace.Actors.Services uses a type in Grace.Types.ContentBlockMetadata.
- The types involved
Grace.Actors.Services.Services→Grace.Types.ContentBlockMetadata.ContentBlockStoragePlacement
- Direction
- Grace.Actors.Services uses Grace.Types.ContentBlockMetadata, so a change to Grace.Types.ContentBlockMetadata can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.ContentBlockMetadata.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→20 Grace.Actors.Services uses Grace.Types.Library✕
- Connections
- 1 pair of types, where a type in Grace.Actors.Services uses a type in Grace.Types.Library.
- The types involved
Grace.Actors.Services.Services→Grace.Types.Library.FailedGraceEventEnvelope
- Direction
- Grace.Actors.Services uses Grace.Types.Library, so a change to Grace.Types.Library can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.Library.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→21 Grace.Actors.Services uses Grace.Types.Reference✕
- Connections
- 1 pair of types, where a type in Grace.Actors.Services uses a type in Grace.Types.Reference.
- The types involved
Grace.Actors.Services.Services→Grace.Types.Reference.ReferenceDto
- Direction
- Grace.Actors.Services uses Grace.Types.Reference, so a change to Grace.Types.Reference can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.Reference.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→22 Grace.Actors.Services uses Grace.Types.Repository✕
- Connections
- 1 pair of types, where a type in Grace.Actors.Services uses a type in Grace.Types.Repository.
- The types involved
Grace.Actors.Services.Services→Grace.Types.Repository.RepositoryDto
- Direction
- Grace.Actors.Services uses Grace.Types.Repository, so a change to Grace.Types.Repository can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.Repository.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→36 Grace.Actors.Services uses Grace.Types.Events✕
- Connections
- 1 pair of types, where a type in Grace.Actors.Services uses a type in Grace.Types.Events.
- The types involved
Grace.Actors.Services.Services→Grace.Types.Events.GraceEvent
- Direction
- Grace.Actors.Services uses Grace.Types.Events, so a change to Grace.Types.Events can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.Events.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→37 Grace.Actors.Services uses Grace.Types.Reminder✕
- Connections
- 2 pairs of types, where a type in Grace.Actors.Services uses a type in Grace.Types.Reminder.
- The types involved
Grace.Actors.Services.ReminderValue→Grace.Types.Reminder.ReminderDtoGrace.Actors.Services.Services→Grace.Types.Reminder.ReminderDto
- Direction
- Grace.Actors.Services uses Grace.Types.Reminder, so a change to Grace.Types.Reminder can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Types.Reminder.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
39→38 Grace.Actors.Services uses Grace.Actors.DirectoryVersion✕
- Connections
- 1 pair of types, where a type in Grace.Actors.Services uses a type in Grace.Actors.DirectoryVersion.
- The types involved
Grace.Actors.Services.Services→Grace.Actors.DirectoryVersion.DirectoryVersion
- Direction
- Grace.Actors.Services uses Grace.Actors.DirectoryVersion, so a change to Grace.Actors.DirectoryVersion can break Grace.Actors.Services, while a change to Grace.Actors.Services can't break Grace.Actors.DirectoryVersion.
- Position
- Below the diagonal: Grace.Actors.Services uses a module listed above it, which is the healthy direction.
40→1 Grace.Server.Branch uses Grace.Actors.Interfaces✕
- Connections
- 1 pair of types, where a type in Grace.Server.Branch uses a type in Grace.Actors.Interfaces.
- The types involved
Grace.Server.Branch.Branch→Grace.Actors.Interfaces.IBranchActor
- Direction
- Grace.Server.Branch uses Grace.Actors.Interfaces, so a change to Grace.Actors.Interfaces can break Grace.Server.Branch, while a change to Grace.Server.Branch can't break Grace.Actors.Interfaces.
- Position
- Below the diagonal: Grace.Server.Branch uses a module listed above it, which is the healthy direction.
40→5 Grace.Server.Branch uses Grace.Shared.Validation.Common.Guid✕
- Connections
- 2 pairs of types, where a type in Grace.Server.Branch uses a type in Grace.Shared.Validation.Common.Guid.
- The types involved
Grace.Server.Branch.Branch→Grace.Shared.Validation.Common.Guid.GuidGrace.Server.Branch.WatchSourceSubscriptionKey→Grace.Shared.Validation.Common.Guid.Guid
- Direction
- Grace.Server.Branch uses Grace.Shared.Validation.Common.Guid, so a change to Grace.Shared.Validation.Common.Guid can break Grace.Server.Branch, while a change to Grace.Server.Branch can't break Grace.Shared.Validation.Common.Guid.
- Position
- Below the diagonal: Grace.Server.Branch uses a module listed above it, which is the healthy direction.
40→6 Grace.Server.Branch uses Grace.Types.Common✕
- Connections
- 1 pair of types, where a type in Grace.Server.Branch uses a type in Grace.Types.Common.
- The types involved
Grace.Server.Branch.Branch→Grace.Types.Common.GraceIds
- Direction
- Grace.Server.Branch uses Grace.Types.Common, so a change to Grace.Types.Common can break Grace.Server.Branch, while a change to Grace.Server.Branch can't break Grace.Types.Common.
- Position
- Below the diagonal: Grace.Server.Branch uses a module listed above it, which is the healthy direction.
40→21 Grace.Server.Branch uses Grace.Types.Reference✕
- Connections
- 3 pairs of types, where a type in Grace.Server.Branch uses a type in Grace.Types.Reference.
- The types involved
Grace.Server.Branch.Branch→Grace.Types.Reference.ReferenceDtoGrace.Server.Branch.Branch→Grace.Types.Reference.ReferenceMaterializationBoundaryDtoGrace.Server.Branch.ReferenceMaterializationBoundaryCandidate→Grace.Types.Reference.ReferenceDto
- Direction
- Grace.Server.Branch uses Grace.Types.Reference, so a change to Grace.Types.Reference can break Grace.Server.Branch, while a change to Grace.Server.Branch can't break Grace.Types.Reference.
- Position
- Below the diagonal: Grace.Server.Branch uses a module listed above it, which is the healthy direction.
40→22 Grace.Server.Branch uses Grace.Types.Repository✕
- Connections
- 1 pair of types, where a type in Grace.Server.Branch uses a type in Grace.Types.Repository.
- The types involved
Grace.Server.Branch.Branch→Grace.Types.Repository.RepositoryDto
- Direction
- Grace.Server.Branch uses Grace.Types.Repository, so a change to Grace.Types.Repository can break Grace.Server.Branch, while a change to Grace.Server.Branch can't break Grace.Types.Repository.
- Position
- Below the diagonal: Grace.Server.Branch uses a module listed above it, which is the healthy direction.
40→38 Grace.Server.Branch uses Grace.Actors.DirectoryVersion✕
- Connections
- 1 pair of types, where a type in Grace.Server.Branch uses a type in Grace.Actors.DirectoryVersion.
- The types involved
Grace.Server.Branch.Branch→Grace.Actors.DirectoryVersion.DirectoryVersion
- Direction
- Grace.Server.Branch uses Grace.Actors.DirectoryVersion, so a change to Grace.Actors.DirectoryVersion can break Grace.Server.Branch, while a change to Grace.Server.Branch can't break Grace.Actors.DirectoryVersion.
- Position
- Below the diagonal: Grace.Server.Branch 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 9 | High / Critical |
| A05:2025 — Injection | 7 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
Roadmap
Top priorities: F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow; Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). | +3.9 pts | Low | REDACTED Scanning |
| F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow. | +4.2 pts | Medium | Async & latency hygiene |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +1.4 pts | Medium | Text alternatives |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.4 pts | Medium | Release Hygiene |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +0.7 pts | Low | Vulnerability-disclosure Policy |
| Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (2). | +0.7 pts | Low | Explicit Debt |
| Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Grace.Aspire.AppHost.csproj, Grace.Orleans.CodeGen.csproj, Directory.Build.props. | +0.7 pts | Low | Explicit Debt |
| Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2). | +0.4 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Grace.Actors/Constants.Actor.fs | 6.3 | Mixed | God Classes: TooManyFunctions: ActorName |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/Grace.Actors/Services.Actor.fs | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: Services.Actor.fs ↔ Dto.Shared.fs |
| src/Grace.Server/Branch.Server.fs | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: Branch.Server.fs ↔ Dto.Shared.fs |
| src/Grace.CLI/Command/Repository.CLI.fs | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: Repository.CLI.fs ↔ Dto.Shared.fs |
| src/Grace.Actors/Branch.Actor.fs | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: Branch.Actor.fs ↔ Dto.Shared.fs |
| src/Grace.Aspire.AppHost/Grace.Aspire.AppHost.csproj | 7.1 | Near-clean | Explicit Debt: NoWarnInCsproj |
| src/Grace.Orleans.CodeGen/Grace.Orleans.CodeGen.csproj | 7.6 | Near-clean | Explicit Debt: NoWarnInCsproj |
| src/Directory.Build.props | 7.6 | Near-clean | Explicit Debt: NoWarnInCsproj |
| src/Grace.Actors/PromotionSet.Actor.fs | 7.8 | Near-clean | God Classes: FileTooLong: Grace.Actors/PromotionSet.Actor.fs |
| src/Grace.Server/Startup.Server.fs | 7.8 | Near-clean | God Classes: FileTooLong: Grace.Server/Startup.Server.fs |
| src/Grace.Actors/RepositoryLibrary.Actor.fs | 7.8 | Near-clean | God Classes: FileTooLong: Grace.Actors/RepositoryLibrary.Actor.fs |
| src/Grace.Shared/Constants.Shared.fs | 7.8 | Near-clean | God Classes: TooManyFunctions: Constants |
| src/Grace.CLI/Command/Branch.CLI.fs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: Branch.CLI.fs ↔ Dto.Shared.fs |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 48 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 48 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 136 of 143 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D4 Code Duplication — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Code Duplication couldn't be assessed within its 13-minute budget on a solution this large — not included in this run.
- D6 Cohesion (LCOM4) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 74 of 108 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the .NET half could not be measured — the test projects could not be restored — nuget.pkg.github.com could not be reached (Unable to load the service index for source https://nuget.pkg.github.com/ScottArbeit/index.json. [src/Grace.Authorization.Tests/Grace.Authorization.Tests.fsproj]) — so no test was built or run; the JavaScript/TypeScript half measured 92.4% (node:test via `npm ci --ignore-scripts` in sdk/typescript/grace/). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 10 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 543 test source file(s) (.fs, .py, .mjs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D15 Churn × Complexity Hotspots — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (337854 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, 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-contributor repository — bus factor is not applicable (1 contributor(s) across 1925 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Grace.Actors/Grace.Actors.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 6 deducted marker(s) and the 1.8/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (128,754 lines, 60% of production source), .py (60,842 lines, 29% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 1 task marker(s) (TODO/FIXME/HACK/XXX) across 1 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D20 ADR Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. ADR Quality couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (157,098 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Nuget.pkg.github.com could not be reached (NU1900: Warning As Error: Error occurred while getting package vulnerability data: Unable to load the service index for source https://nuget.pkg.github.com/ScottArbeit/index.json.). 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via AspireAppHost (src/Grace.Aspire.AppHost/Grace.Aspire.AppHost.csproj). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/Grace.Aspire.AppHost/Grace.Aspire.AppHost.csproj, src/Grace.Authorization.Tests/Grace.Authorization.Tests.fsproj, src/Grace.Operations.Tests/Grace.Operations.Tests.fsproj, src/Grace.Server.Tests/Grace.Server.Tests.fsproj, src/Grace.Server.Unit.Tests/Grace.Server.Unit.Tests.fsproj and 1 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D3 · God Classes
68 god class(es) detected.
What to do
- Resolve the 55 FileTooLong finding(s) in God Classes — start with Watch.CLI.fs, Services.Actor.fs, Services.CLI.fs. — One of this dimension's main actionable groups (55 warning-level).
- Resolve the 6 TooManyFunctions finding(s) in God Classes — start with Constants.Shared.fs (2), Constants.Actor.fs (2), Utilities.Shared.fs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with RepositoryLibrary.Actor.fs, MemoryCache.Extensions.Actor.fs, PromotionSet.Actor.fs. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D7 · Architectural Integrity
All 11 mechanizable ADR(s) are enforced: 11 by analyzers, 0 by tests. Cycles found: 0.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 10 tests. Measured on the C# suite only — at least 543 test source file(s) (.fs, .py, .mjs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in sdk/typescript/grace/ (19 tests)): measured (0 flaky).
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 374 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 103 direct `PackageReference`(s), and 147 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D17 · Explicit Debt
6 deducted debt markers + unmeasured dead symbols across 1066 LoC in the .NET projects (1.8/KLoC) → score 6.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs, .py (89% of production source) was not read, and carries at least 1 uncounted task marker(s) in 1 file(s).
What to do
- Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Grace.Aspire.AppHost.csproj, Grace.Orleans.CodeGen.csproj, Directory.Build.props. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 BarePragmaDisable finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F4 map. 72 document(s) read across 5 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
2 naming inconsistencies among 1311 declarations measured against a convention their peers follow.
D26 · Project Cohesion
1 of 5 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Grace.Aspire.AppHost.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
93 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
6 finding(s): 0 critical, 6 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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)
7 finding(s): 0 critical, 4 high, 3 medium, 0 low. 4 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 4 file(s) — `docs/Design concepts/ContentBlock and global dedupe design.html` (lines 1175–1187, lines 1386–1387), `src/Grace.Cache.Tests/CacheArtifactGrantValidatorTests.cs` (line 59), `src/Grace.Cache.Tests/CacheFillCoordinatorTests.cs` (line 138, line 154), `src/Grace.Cache.Tests/DirectoryVersionZipEndpointTests.cs` (lines 16–315, line 316, line 370) — 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. In 2 of those file(s) — `src/Grace.Cache.Tests/CacheArtifactGrantValidatorTests.cs`, `src/Grace.Cache.Tests/CacheFillCoordinatorTests.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `src/Grace.Cache.Tests/CacheFillCoordinatorTests.cs`, `src/Grace.Cache.Tests/DirectoryVersionZipEndpointTests.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,osv). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: nuget.pkg.github.com could not be reached (NU1900: Warning As Error: Error occurred while getting package vulnerability data: Unable to load the service index for source https://nuget.pkg.github.com/ScottArbeit/index.json.)), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
6 finding(s): 0 critical, 1 high, 4 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
4 of 261 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Grace.CLI/Command/Admin.CLI.fs. Counted over 261 of the 325 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 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with Admin.CLI.fs, Reminder.Server.fs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with Reminder.Parameters.fs, Admin.SDK.fs. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: EndpointAuthorizationManifest.Server.fs↔Startup.Server.fs 100%; Constants.Actor.fs↔Interfaces.Actor.fs 80%; Branch.Actor.fs↔Dto.Shared.fs 79%
What to do
- Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with Branch.Actor.fs, Branch.CLI.fs, Repository.CLI.fs. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with EndpointAuthorizationManifest.Server.fs, Constants.Actor.fs, Owner.Actor.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with RepositoryName.Actor.fs, OrganizationName.Actor.fs, BranchName.Actor.fs. — One of this dimension's main actionable groups (3 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but only routes reports to a public channel (no private reporting contact).
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 27 platform declaration(s) and 4 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby. — Brain2DevelopmentProcess.html:0
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
AC3 · Page structure
AC5 · ARIA correctness
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
AX9 · CQS / query purity
ED5 · Idempotency
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 6/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs/design/Libraries.Object-Experiment`, `docs/design/Libraries.Pause-Experiment`, `src/Grace.CLI.LocalStateDb.Worker`, `src/Grace.Cache`, `src/Grace.Load`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `src/Grace.Actors/Grace.Actors.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Grace.Actors/Grace.Actors.fsproj:84
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
PF3 · Async & latency hygiene
- `diffToReferenceType` is async and calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — src/Grace.CLI/Command/Diff.CLI.fs:420
- `InvokeAsync` is async and calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — src/Grace.CLI/Command/Diff.CLI.fs:757
- `processChangedFilesWithClients` is async and calls .GetAwaiter().GetResult() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — src/Grace.CLI/Command/Watch.CLI.fs:8889
What to do
- F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
X5 · Nullable reference types
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 |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Checked 3 of 9 | Solid. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 93% | Exemplary | Solid. |
| Readiness | 61% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Strong | Solid. |
| Accessibility | 70% | Adequate — gated by AC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Largest drag on the score — prioritise here. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 66 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — AX6 reached only 1% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D12 Dependency Hygiene — Dependency hygiene not measured
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, .py, .rs, .ts, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- D20 ADR Quality — ADR Quality not included (time budget)
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 1 exposed C# types.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs, .py, .rs source were not judged.
- D25 ADR Conformance — None of 11 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- 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.
- D4 Code Duplication — Code Duplication not included (time budget)
- 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.
- D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
- D8 Code Coverage — Coverage not measured — .NET suite
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 715 value object(s); 79 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — X13 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — X23 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — X28 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — X4 reached only 0% of this repository's production lines — fsharp (132,828 lines), python (61,511 lines), rust (20,735 lines), typescript (1,642 lines), javascript (187 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — 26 finding(s)
- Boundary-crossing change coupling: Branch.Actor.fs ↔ Dto.Shared.fs src/Grace.Actors/Branch.Actor.fs:1
- Boundary-crossing change coupling: Branch.CLI.fs ↔ Dto.Shared.fs src/Grace.CLI/Command/Branch.CLI.fs:1
- Boundary-crossing change coupling: Repository.CLI.fs ↔ Dto.Shared.fs src/Grace.CLI/Command/Repository.CLI.fs:1
- Boundary-crossing change coupling: Services.Actor.fs ↔ Dto.Shared.fs src/Grace.Actors/Services.Actor.fs:1
- Boundary-crossing change coupling: Branch.Server.fs ↔ Dto.Shared.fs src/Grace.Server/Branch.Server.fs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj src/Grace.Aspire.AppHost/Grace.Aspire.AppHost.csproj:8
- NoWarnInCsproj src/Grace.Orleans.CodeGen/Grace.Orleans.CodeGen.csproj:12
- NoWarnInCsproj src/Directory.Build.props:33
- REDACTED
- REDACTED
- EmptyCatchBlock REDACTED:887
- EmptyCatchBlock REDACTED:893
- REDACTED
- REDACTED
- Orphaned knowledge src/Grace.CLI/Command/Admin.CLI.fs:1
- Orphaned knowledge src/Grace.Server/Reminder.Server.fs:1
- <svg role="img"> without an accessible name Brain2DevelopmentProcess.html
- REDACTED
Serious — 93 finding(s)
- FileTooLong: Command/Watch.CLI.fs src/Grace.CLI/Command/Watch.CLI.fs
- FileTooLong: Grace.Actors/Services.Actor.fs src/Grace.Actors/Services.Actor.fs
- FileTooLong: Command/Services.CLI.fs src/Grace.CLI/Command/Services.CLI.fs
- FileTooLong: Grace.Server/Branch.Server.fs src/Grace.Server/Branch.Server.fs
- FileTooLong: Command/WorkingDirectoryUpdate.CLI.fs src/Grace.CLI/Command/WorkingDirectoryUpdate.CLI.fs
- FileTooLong: Grace.Server/WorkItem.Server.fs src/Grace.Server/WorkItem.Server.fs
- FileTooLong: Grace.Server/Storage.Server.fs src/Grace.Server/Storage.Server.fs
- FileTooLong: Grace.Actors/PromotionSet.Actor.fs src/Grace.Actors/PromotionSet.Actor.fs
- FileTooLong: Grace.Server/Startup.Server.fs src/Grace.Server/Startup.Server.fs
- FileTooLong: Command/Repository.CLI.fs src/Grace.CLI/Command/Repository.CLI.fs
- FileTooLong: Grace.Actors/RepositoryLibrary.Actor.fs src/Grace.Actors/RepositoryLibrary.Actor.fs
- FileTooLong: Grace.Actors/UploadSession.Actor.fs src/Grace.Actors/UploadSession.Actor.fs
- FileTooLong: Grace.Actors/DirectoryVersion.Actor.fs src/Grace.Actors/DirectoryVersion.Actor.fs
- FileTooLong: Command/Doctor.CLI.fs src/Grace.CLI/Command/Doctor.CLI.fs
- FileTooLong: Command/Auth.CLI.fs src/Grace.CLI/Command/Auth.CLI.fs
- FileTooLong: Grace.Server/Notification.Server.fs src/Grace.Server/Notification.Server.fs
- FileTooLong: Grace.CLI/CommandOutputContract.CLI.fs src/Grace.CLI/CommandOutputContract.CLI.fs
- FileTooLong: Grace.Server/Review.Server.fs src/Grace.Server/Review.Server.fs
- FileTooLong: Command/WorkItem.CLI.fs src/Grace.CLI/Command/WorkItem.CLI.fs
- FileTooLong: Grace.CLI/Program.CLI.fs src/Grace.CLI/Program.CLI.fs
- FileTooLong: Library/LibrarySynchronization.CLI.fs src/Grace.CLI/Library/LibrarySynchronization.CLI.fs
- FileTooLong: Command/Reference.CLI.fs src/Grace.CLI/Command/Reference.CLI.fs
- FileTooLong: Grace.Actors/Branch.Actor.fs src/Grace.Actors/Branch.Actor.fs
- FileTooLong: Command/Access.CLI.fs src/Grace.CLI/Command/Access.CLI.fs
- FileTooLong: Command/Agent.CLI.fs src/Grace.CLI/Command/Agent.CLI.fs
- TooManyFunctions: Constants src/Grace.Shared/Constants.Shared.fs:23
- TooManyFunctions: EnvironmentVariables src/Grace.Shared/Constants.Shared.fs:302
- TooManyFunctions: Utilities src/Grace.Shared/Utilities.Shared.fs:46
- TooManyFunctions: ActorName src/Grace.Actors/Constants.Actor.fs:16
- TooManyFunctions: CacheArtifactStoreModule src/Grace.Cache.Storage/CacheArtifactStore.fs:59
- TooManyFunctions: StateName src/Grace.Actors/Constants.Actor.fs:135
- TooManyMethods: RepositoryLibraryActor src/Grace.Actors/RepositoryLibrary.Actor.fs:22
- TooManyMethods: IMemoryCache src/Grace.Actors/Extensions/MemoryCache.Extensions.Actor.fs:44
- TooManyMethods: PromotionSetActor src/Grace.Actors/PromotionSet.Actor.fs:316
- TooManyMethods: Branch src/Grace.SDK/Branch.SDK.fs:17
- TooManyMethods: Startup src/Grace.Server/Startup.Server.fs:206
- Change coupling: EndpointAuthorizationManifest.Server.fs ↔ Startup.Server.fs src/Grace.Server/Security/EndpointAuthorizationManifest.Server.fs:1
- Change coupling: Constants.Actor.fs ↔ Interfaces.Actor.fs src/Grace.Actors/Constants.Actor.fs:1
- Change coupling: Owner.Actor.fs ↔ Repository.Actor.fs src/Grace.Actors/Owner.Actor.fs:1
- Change coupling: Diff.Actor.fs ↔ Organization.Actor.fs src/Grace.Actors/Diff.Actor.fs:1
- Change coupling: Organization.Actor.fs ↔ Reference.Actor.fs src/Grace.Actors/Organization.Actor.fs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change-coupling hub: RepositoryName.Actor.fs → Branch.Actor.fs, BranchName.Actor.fs, OrganizationName.Actor.fs, Owner.Actor.fs, OwnerName.Actor.fs src/Grace.Actors/RepositoryName.Actor.fs
- Change-coupling hub: OrganizationName.Actor.fs → Branch.Actor.fs, OwnerName.Actor.fs, Repository.Actor.fs src/Grace.Actors/OrganizationName.Actor.fs
- Change-coupling hub: BranchName.Actor.fs → Organization.Actor.fs, Owner.Actor.fs, OwnerName.Actor.fs src/Grace.Actors/BranchName.Actor.fs
- REDACTED
- REDACTED
- REDACTED
- Sync-over-async blocking src/Grace.CLI/Command/Diff.CLI.fs:420
- Sync-over-async blocking src/Grace.CLI/Command/Diff.CLI.fs:757
- Sync-over-async blocking src/Grace.CLI/Command/Watch.CLI.fs:8889
- REDACTED
- REDACTED
- BarePragmaDisable REDACTED:283
- REDACTED
- MethodTooLong: Program.Main REDACTED:52
- ClassTooLong: Program REDACTED
- Coverage collected but not gated
- NuGet dependencies are not locked
- JavaScript dependencies are not locked sdk/generated/matrix/openapi-generator/typescript-fetch/package.json:18
Minor — 24 finding(s)
- Duplicated predicate src/Grace.Cache.Storage/CacheArtifactStore.fs:108
- Duplicated predicate src/Grace.CLI/Command/Watch.CLI.fs:6113
- Duplicated predicate src/Grace.CLI/Library/LibraryBaseline.CLI.fs:59
- Duplicated predicate src/Grace.CLI/Command/Services.CLI.fs:242
- Duplicated predicate src/Grace.Operations.Worker/OperationsWorker.fs:415
- Duplicated predicate src/Grace.Server/Artifact.Server.fs:303
- Duplicated predicate src/Grace.Server/DirectoryVersion.Server.fs:671
- Duplicated predicate src/Grace.CLI/Command/Services.CLI.fs:577
- Duplicated predicate src/Grace.Server/Auth.Server.fs:32
- Duplicated predicate sdk/typescript/grace/src/protocol/content-address.ts:168
- Orphaned file src/Grace.Shared/Parameters/Reminder.Parameters.fs:1
- Orphaned file src/Grace.SDK/Admin.SDK.fs:1
- Documentation: no map of the repository's parts README.md:1
- `BaseAPI` spells `API` where 89 names in the project spell it `Api` sdk/generated/matrix/openapi-generator/typescript-fetch/src/runtime.ts:91
- `isJsonMime` spells `Json` where 1220 names in the project spell it `JSON` sdk/generated/matrix/openapi-generator/typescript-fetch/src/runtime.ts:126
- Projects may be oversized for their cohesion src/Grace.Aspire.AppHost/Grace.Aspire.AppHost.csproj:1
- REDACTED
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- Logging is not universal
- No dependency-update automation src/Grace.Actors/Grace.Actors.fsproj:84
- No changelog
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-36d74dffa5cd474982220c226e644bcb/history.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-36d74dffa5cd474982220c226e644bcb/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude sdk/typescript/grace/dist --exclude sdk/dotnet/Grace.Sdk.Harness/Internal --exclude sdk/generated/matrix/openapi-generator/python/grace_generated_openapi_probe/api --exclude sdk/generated/matrix/openapi-generator/python/grace_generated_openapi_probe/models --exclude sdk/generated/matrix/openapi-generator/python/test --exclude sdk/generated/matrix/openapi-generator/typescript-fetch/src/apis --exclude sdk/generated/matrix/openapi-generator/typescript-fetch/src/models --exclude sdk/python/grace-sdk/src/grace_sdk/_generated --exclude sdk/typescript . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Grace.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | 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 | — |
| 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |