Executive summary
rahulsom/grooves falls short of our standard for a preview release, in part because we found no recorded design decisions and no architecture document or diagram. It scores 58 out of 100 and is rated Adequate, and eight of its nine critical findings are security problems in the build pipeline.
Maturity, at 54, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Adding build and run instructions to the README is another step, worth about 3 points. Raising Maturity to 62 would lift the score to about 61.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk. The test that checks nothing needs to check the result it produces.
The product code is 6,567 lines, about €11,000 to rebuild.
If Maturity rose from 54 to 62, the lowest score rated Strong, the score would rise from 58 to about 61.
New since the last survey: 5 findings
- Test Quality · No assertions (empty test): contextLoads grooves-example-javaee/src/test/java/grooves/example/javaee/PatientTest.java
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Deployment & Rollback · No deployment automation
Fixed since the last survey: 3 findings
- Test Quality · No assertions: contextLoads grooves-example-javaee/src/test/java/grooves/example/javaee/PatientTest.java
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · Medium: watchdog-checkout-credential-persisted-in-privileged-job REDACTED
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,600 to €18,000, for 60 to 190 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,567 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 com.github.rahulsom.grooves.api | 2 com.github.rahulsom.grooves.api.events | 3 com.github.rahulsom.grooves.api.snapshots.internal | 4 com.github.rahulsom.grooves.asciidoctor | 5 com.github.rahulsom.grooves.logging | 6 grooves-site.src.main | 7 grooves.boot.kotlin.BeansHolder | 8 scripts | 9 com.github.rahulsom.grooves.api.EventApplyOutcome | 10 com.github.rahulsom.grooves.api.snapshots | 11 com.github.rahulsom.grooves.asciidoctor.EventType | 12 com.github.rahulsom.grooves.functions | 13 com.github.rahulsom.grooves.queries.internal | 14 grooves.boot.kotlin.repositories | 15 com.github.rahulsom.grooves | 16 com.github.rahulsom.grooves.groovy.transformations | 17 com.github.rahulsom.grooves.java | 18 com.github.rahulsom.grooves.queries | 19 grooves.boot.kotlin.domain | 20 com.github.rahulsom.grooves.groovy.transformations.internal | 21 com.github.rahulsom.grooves.impl | 22 grooves.boot.kotlin.domain.PatientEvent | 23 grooves.boot.kotlin.domain.PatientEvent.Applicable | 24 grooves.boot.kotlin.queries | 25 grooves.boot.kotlin | 26 grooves.boot.kotlin.controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.github.rahulsom.grooves.api | ||||||||||||||||||||||||||
| 2 com.github.rahulsom.grooves.api.events | ||||||||||||||||||||||||||
| 3 com.github.rahulsom.grooves.api.snapshots.internal | ||||||||||||||||||||||||||
| 4 com.github.rahulsom.grooves.asciidoctor | ||||||||||||||||||||||||||
| 5 com.github.rahulsom.grooves.logging | ||||||||||||||||||||||||||
| 6 grooves-site.src.main | ||||||||||||||||||||||||||
| 7 grooves.boot.kotlin.BeansHolder | ||||||||||||||||||||||||||
| 8 scripts | ||||||||||||||||||||||||||
| 9 com.github.rahulsom.grooves.api.EventApplyOutcome | 2 | |||||||||||||||||||||||||
| 10 com.github.rahulsom.grooves.api.snapshots | 4 | |||||||||||||||||||||||||
| 11 com.github.rahulsom.grooves.asciidoctor.EventType | 6 | |||||||||||||||||||||||||
| 12 com.github.rahulsom.grooves.functions | 4 | |||||||||||||||||||||||||
| 13 com.github.rahulsom.grooves.queries.internal | 4 | 5 | 1 | |||||||||||||||||||||||
| 14 grooves.boot.kotlin.repositories | 5 | |||||||||||||||||||||||||
| 15 com.github.rahulsom.grooves | 13 | |||||||||||||||||||||||||
| 16 com.github.rahulsom.grooves.groovy.transformations | 1 | |||||||||||||||||||||||||
| 17 com.github.rahulsom.grooves.java | 1 | |||||||||||||||||||||||||
| 18 com.github.rahulsom.grooves.queries | 2 | 14 | ||||||||||||||||||||||||
| 19 grooves.boot.kotlin.domain | 2 | 2 | 2 | |||||||||||||||||||||||
| 20 com.github.rahulsom.grooves.groovy.transformations.internal | 3 | |||||||||||||||||||||||||
| 21 com.github.rahulsom.grooves.impl | 13 | 4 | ||||||||||||||||||||||||
| 22 grooves.boot.kotlin.domain.PatientEvent | 3 | 6 | ||||||||||||||||||||||||
| 23 grooves.boot.kotlin.domain.PatientEvent.Applicable | 3 | |||||||||||||||||||||||||
| 24 grooves.boot.kotlin.queries | 2 | 4 | 2 | 6 | 2 | |||||||||||||||||||||
| 25 grooves.boot.kotlin | 1 | 4 | 2 | 1 | 2 | |||||||||||||||||||||
| 26 grooves.boot.kotlin.controllers | 2 | 2 | 2 |
9→1 com.github.rahulsom.grooves.api.EventApplyOutcome uses com.github.rahulsom.grooves.api✕
- Connections
- 2 pairs of types, where a type in com.github.rahulsom.grooves.api.EventApplyOutcome uses a type in com.github.rahulsom.grooves.api.
- The types involved
com.github.rahulsom.grooves.api.EventApplyOutcome.CONTINUE→com.github.rahulsom.grooves.api.EventApplyOutcomecom.github.rahulsom.grooves.api.EventApplyOutcome.RETURN→com.github.rahulsom.grooves.api.EventApplyOutcome
- Direction
- com.github.rahulsom.grooves.api.EventApplyOutcome uses com.github.rahulsom.grooves.api, so a change to com.github.rahulsom.grooves.api can break com.github.rahulsom.grooves.api.EventApplyOutcome, while a change to com.github.rahulsom.grooves.api.EventApplyOutcome can't break com.github.rahulsom.grooves.api.
- Position
- Below the diagonal: com.github.rahulsom.grooves.api.EventApplyOutcome uses a module listed above it, which is the healthy direction.
10→3 com.github.rahulsom.grooves.api.snapshots uses com.github.rahulsom.grooves.api.snapshots.internal✕
- Connections
- 4 pairs of types, where a type in com.github.rahulsom.grooves.api.snapshots uses a type in com.github.rahulsom.grooves.api.snapshots.internal.
- The types involved
com.github.rahulsom.grooves.api.snapshots.TemporalJoin→com.github.rahulsom.grooves.api.snapshots.internal.BaseJoincom.github.rahulsom.grooves.api.snapshots.TemporalSnapshot→com.github.rahulsom.grooves.api.snapshots.internal.BaseSnapshotcom.github.rahulsom.grooves.api.snapshots.VersionedJoin→com.github.rahulsom.grooves.api.snapshots.internal.BaseJoincom.github.rahulsom.grooves.api.snapshots.VersionedSnapshot→com.github.rahulsom.grooves.api.snapshots.internal.BaseSnapshot
- Direction
- com.github.rahulsom.grooves.api.snapshots uses com.github.rahulsom.grooves.api.snapshots.internal, so a change to com.github.rahulsom.grooves.api.snapshots.internal can break com.github.rahulsom.grooves.api.snapshots, while a change to com.github.rahulsom.grooves.api.snapshots can't break com.github.rahulsom.grooves.api.snapshots.internal.
- Position
- Below the diagonal: com.github.rahulsom.grooves.api.snapshots uses a module listed above it, which is the healthy direction.
11→4 com.github.rahulsom.grooves.asciidoctor.EventType uses com.github.rahulsom.grooves.asciidoctor✕
- Connections
- 6 pairs of types, where a type in com.github.rahulsom.grooves.asciidoctor.EventType uses a type in com.github.rahulsom.grooves.asciidoctor.
- The types involved
com.github.rahulsom.grooves.asciidoctor.EventType.DeprecatedBy→com.github.rahulsom.grooves.asciidoctor.EventTypecom.github.rahulsom.grooves.asciidoctor.EventType.Deprecates→com.github.rahulsom.grooves.asciidoctor.EventTypecom.github.rahulsom.grooves.asciidoctor.EventType.Disjoin→com.github.rahulsom.grooves.asciidoctor.EventTypecom.github.rahulsom.grooves.asciidoctor.EventType.Join→com.github.rahulsom.grooves.asciidoctor.EventTypecom.github.rahulsom.grooves.asciidoctor.EventType.Normal→com.github.rahulsom.grooves.asciidoctor.EventTypecom.github.rahulsom.grooves.asciidoctor.EventType.Revert→com.github.rahulsom.grooves.asciidoctor.EventType
- Direction
- com.github.rahulsom.grooves.asciidoctor.EventType uses com.github.rahulsom.grooves.asciidoctor, so a change to com.github.rahulsom.grooves.asciidoctor can break com.github.rahulsom.grooves.asciidoctor.EventType, while a change to com.github.rahulsom.grooves.asciidoctor.EventType can't break com.github.rahulsom.grooves.asciidoctor.
- Position
- Below the diagonal: com.github.rahulsom.grooves.asciidoctor.EventType uses a module listed above it, which is the healthy direction.
12→15 com.github.rahulsom.grooves.functions uses com.github.rahulsom.grooves part of a loop✕
- Connections
- 4 pairs of types, where a type in com.github.rahulsom.grooves.functions uses a type in com.github.rahulsom.grooves.
- The types involved
com.github.rahulsom.grooves.functions.DeprecatedByProvider→com.github.rahulsom.grooves.DeprecatedByResultcom.github.rahulsom.grooves.functions.EventClassifier→com.github.rahulsom.grooves.EventTypecom.github.rahulsom.grooves.functions.EventHandler→com.github.rahulsom.grooves.EventApplyOutcomecom.github.rahulsom.grooves.functions.ExceptionHandler→com.github.rahulsom.grooves.EventApplyOutcome
- Direction
- com.github.rahulsom.grooves.functions uses com.github.rahulsom.grooves, so a change to com.github.rahulsom.grooves can break com.github.rahulsom.grooves.functions, while a change to com.github.rahulsom.grooves.functions can't break com.github.rahulsom.grooves.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 com.github.rahulsom.grooves.queries.internal uses com.github.rahulsom.grooves.api✕
- Connections
- 4 pairs of types, where a type in com.github.rahulsom.grooves.queries.internal uses a type in com.github.rahulsom.grooves.api.
- The types involved
com.github.rahulsom.grooves.queries.internal.BaseQuery→com.github.rahulsom.grooves.api.EventApplyOutcomecom.github.rahulsom.grooves.queries.internal.QueryExecutor→com.github.rahulsom.grooves.api.EventApplyOutcomecom.github.rahulsom.grooves.queries.internal.SimpleExecutor→com.github.rahulsom.grooves.api.EventApplyOutcomecom.github.rahulsom.grooves.queries.internal.SimpleQuery→com.github.rahulsom.grooves.api.EventApplyOutcome
- Direction
- com.github.rahulsom.grooves.queries.internal uses com.github.rahulsom.grooves.api, so a change to com.github.rahulsom.grooves.api can break com.github.rahulsom.grooves.queries.internal, while a change to com.github.rahulsom.grooves.queries.internal can't break com.github.rahulsom.grooves.api.
- Position
- Below the diagonal: com.github.rahulsom.grooves.queries.internal uses a module listed above it, which is the healthy direction.
13→2 com.github.rahulsom.grooves.queries.internal uses com.github.rahulsom.grooves.api.events✕
- Connections
- 5 pairs of types, where a type in com.github.rahulsom.grooves.queries.internal uses a type in com.github.rahulsom.grooves.api.events.
- The types involved
com.github.rahulsom.grooves.queries.internal.Executor→com.github.rahulsom.grooves.api.events.Deprecatescom.github.rahulsom.grooves.queries.internal.JoinExecutor→com.github.rahulsom.grooves.api.events.Deprecatescom.github.rahulsom.grooves.queries.internal.QueryExecutor→com.github.rahulsom.grooves.api.events.DeprecatedBycom.github.rahulsom.grooves.queries.internal.QueryExecutor→com.github.rahulsom.grooves.api.events.Deprecatescom.github.rahulsom.grooves.queries.internal.Utils→com.github.rahulsom.grooves.api.events.BaseEvent
- Direction
- com.github.rahulsom.grooves.queries.internal uses com.github.rahulsom.grooves.api.events, so a change to com.github.rahulsom.grooves.api.events can break com.github.rahulsom.grooves.queries.internal, while a change to com.github.rahulsom.grooves.queries.internal can't break com.github.rahulsom.grooves.api.events.
- Position
- Below the diagonal: com.github.rahulsom.grooves.queries.internal uses a module listed above it, which is the healthy direction.
13→3 com.github.rahulsom.grooves.queries.internal uses com.github.rahulsom.grooves.api.snapshots.internal✕
- Connections
- 1 pair of types, where a type in com.github.rahulsom.grooves.queries.internal uses a type in com.github.rahulsom.grooves.api.snapshots.internal.
- The types involved
com.github.rahulsom.grooves.queries.internal.Utils→com.github.rahulsom.grooves.api.snapshots.internal.BaseSnapshot
- Direction
- com.github.rahulsom.grooves.queries.internal uses com.github.rahulsom.grooves.api.snapshots.internal, so a change to com.github.rahulsom.grooves.api.snapshots.internal can break com.github.rahulsom.grooves.queries.internal, while a change to com.github.rahulsom.grooves.queries.internal can't break com.github.rahulsom.grooves.api.snapshots.internal.
- Position
- Below the diagonal: com.github.rahulsom.grooves.queries.internal uses a module listed above it, which is the healthy direction.
14→19 grooves.boot.kotlin.repositories uses grooves.boot.kotlin.domain part of a loop✕
- Connections
- 5 pairs of types, where a type in grooves.boot.kotlin.repositories uses a type in grooves.boot.kotlin.domain.
- The types involved
grooves.boot.kotlin.repositories.PatientAccountRepository→grooves.boot.kotlin.domain.PatientAccountgrooves.boot.kotlin.repositories.PatientEventBlockingRepository→grooves.boot.kotlin.domain.PatientEventgrooves.boot.kotlin.repositories.PatientEventRepository→grooves.boot.kotlin.domain.PatientEventgrooves.boot.kotlin.repositories.PatientHealthRepository→grooves.boot.kotlin.domain.PatientHealthgrooves.boot.kotlin.repositories.PatientRepository→grooves.boot.kotlin.domain.Patient
- Direction
- grooves.boot.kotlin.repositories uses grooves.boot.kotlin.domain, so a change to grooves.boot.kotlin.domain can break grooves.boot.kotlin.repositories, while a change to grooves.boot.kotlin.repositories can't break grooves.boot.kotlin.domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→12 com.github.rahulsom.grooves uses com.github.rahulsom.grooves.functions✕
- Connections
- 13 pairs of types, where a type in com.github.rahulsom.grooves uses a type in com.github.rahulsom.grooves.functions.
- The types involved
com.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.ApplyMoreEventsPredicatecom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.DeprecatedByProvidercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.Deprecatorcom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.EmptySnapshotProvidercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.EventClassifiercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.EventHandlercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.EventIdProvidercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.EventVersionercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.EventsProvidercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.ExceptionHandlercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.RevertedEventProvidercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.SnapshotProvidercom.github.rahulsom.grooves.GroovesQueryBuilder→com.github.rahulsom.grooves.functions.SnapshotVersioner
- Direction
- com.github.rahulsom.grooves uses com.github.rahulsom.grooves.functions, so a change to com.github.rahulsom.grooves.functions can break com.github.rahulsom.grooves, while a change to com.github.rahulsom.grooves can't break com.github.rahulsom.grooves.functions.
- Position
- Below the diagonal: com.github.rahulsom.grooves uses a module listed above it, which is the healthy direction.
16→10 com.github.rahulsom.grooves.groovy.transformations uses com.github.rahulsom.grooves.api.snapshots✕
- Connections
- 1 pair of types, where a type in com.github.rahulsom.grooves.groovy.transformations uses a type in com.github.rahulsom.grooves.api.snapshots.
- The types involved
com.github.rahulsom.grooves.groovy.transformations.Query→com.github.rahulsom.grooves.api.snapshots.Snapshot
- Direction
- com.github.rahulsom.grooves.groovy.transformations uses com.github.rahulsom.grooves.api.snapshots, so a change to com.github.rahulsom.grooves.api.snapshots can break com.github.rahulsom.grooves.groovy.transformations, while a change to com.github.rahulsom.grooves.groovy.transformations can't break com.github.rahulsom.grooves.api.snapshots.
- Position
- Below the diagonal: com.github.rahulsom.grooves.groovy.transformations uses a module listed above it, which is the healthy direction.
17→10 com.github.rahulsom.grooves.java uses com.github.rahulsom.grooves.api.snapshots✕
- Connections
- 1 pair of types, where a type in com.github.rahulsom.grooves.java uses a type in com.github.rahulsom.grooves.api.snapshots.
- The types involved
com.github.rahulsom.grooves.java.Query→com.github.rahulsom.grooves.api.snapshots.Snapshot
- Direction
- com.github.rahulsom.grooves.java uses com.github.rahulsom.grooves.api.snapshots, so a change to com.github.rahulsom.grooves.api.snapshots can break com.github.rahulsom.grooves.java, while a change to com.github.rahulsom.grooves.java can't break com.github.rahulsom.grooves.api.snapshots.
- Position
- Below the diagonal: com.github.rahulsom.grooves.java uses a module listed above it, which is the healthy direction.
18→1 com.github.rahulsom.grooves.queries uses com.github.rahulsom.grooves.api✕
- Connections
- 2 pairs of types, where a type in com.github.rahulsom.grooves.queries uses a type in com.github.rahulsom.grooves.api.
- The types involved
com.github.rahulsom.grooves.queries.FunctionalTemporalQuery→com.github.rahulsom.grooves.api.EventApplyOutcomecom.github.rahulsom.grooves.queries.FunctionalVersionedQuery→com.github.rahulsom.grooves.api.EventApplyOutcome
- Direction
- com.github.rahulsom.grooves.queries uses com.github.rahulsom.grooves.api, so a change to com.github.rahulsom.grooves.api can break com.github.rahulsom.grooves.queries, while a change to com.github.rahulsom.grooves.queries can't break com.github.rahulsom.grooves.api.
- Position
- Below the diagonal: com.github.rahulsom.grooves.queries uses a module listed above it, which is the healthy direction.
18→13 com.github.rahulsom.grooves.queries uses com.github.rahulsom.grooves.queries.internal✕
- Connections
- 14 pairs of types, where a type in com.github.rahulsom.grooves.queries uses a type in com.github.rahulsom.grooves.queries.internal.
- The types involved
com.github.rahulsom.grooves.queries.FunctionalTemporalQuery→com.github.rahulsom.grooves.queries.internal.SimpleExecutorcom.github.rahulsom.grooves.queries.FunctionalTemporalQuery→com.github.rahulsom.grooves.queries.internal.SimpleQuerycom.github.rahulsom.grooves.queries.FunctionalVersionedQuery→com.github.rahulsom.grooves.queries.internal.SimpleExecutorcom.github.rahulsom.grooves.queries.FunctionalVersionedQuery→com.github.rahulsom.grooves.queries.internal.SimpleQuerycom.github.rahulsom.grooves.queries.JoinSupport→com.github.rahulsom.grooves.queries.internal.JoinExecutorcom.github.rahulsom.grooves.queries.QuerySupport→com.github.rahulsom.grooves.queries.internal.QueryExecutorcom.github.rahulsom.grooves.queries.TemporalJoinSupport→com.github.rahulsom.grooves.queries.internal.JoinExecutorcom.github.rahulsom.grooves.queries.TemporalQuerySupport→com.github.rahulsom.grooves.queries.internal.BaseQuerycom.github.rahulsom.grooves.queries.TemporalQuerySupport→com.github.rahulsom.grooves.queries.internal.Paircom.github.rahulsom.grooves.queries.TemporalQuerySupport→com.github.rahulsom.grooves.queries.internal.QueryExecutorcom.github.rahulsom.grooves.queries.VersionedJoinSupport→com.github.rahulsom.grooves.queries.internal.JoinExecutorcom.github.rahulsom.grooves.queries.VersionedQuerySupport→com.github.rahulsom.grooves.queries.internal.BaseQuerycom.github.rahulsom.grooves.queries.VersionedQuerySupport→com.github.rahulsom.grooves.queries.internal.Paircom.github.rahulsom.grooves.queries.VersionedQuerySupport→com.github.rahulsom.grooves.queries.internal.QueryExecutor
- Direction
- com.github.rahulsom.grooves.queries uses com.github.rahulsom.grooves.queries.internal, so a change to com.github.rahulsom.grooves.queries.internal can break com.github.rahulsom.grooves.queries, while a change to com.github.rahulsom.grooves.queries can't break com.github.rahulsom.grooves.queries.internal.
- Position
- Below the diagonal: com.github.rahulsom.grooves.queries uses a module listed above it, which is the healthy direction.
19→2 grooves.boot.kotlin.domain uses com.github.rahulsom.grooves.api.events✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.domain uses a type in com.github.rahulsom.grooves.api.events.
- The types involved
grooves.boot.kotlin.domain.PatientEvent→com.github.rahulsom.grooves.api.events.BaseEventgrooves.boot.kotlin.domain.PatientEvent→com.github.rahulsom.grooves.api.events.RevertEvent
- Direction
- grooves.boot.kotlin.domain uses com.github.rahulsom.grooves.api.events, so a change to com.github.rahulsom.grooves.api.events can break grooves.boot.kotlin.domain, while a change to grooves.boot.kotlin.domain can't break com.github.rahulsom.grooves.api.events.
- Position
- Below the diagonal: grooves.boot.kotlin.domain uses a module listed above it, which is the healthy direction.
19→10 grooves.boot.kotlin.domain uses com.github.rahulsom.grooves.api.snapshots✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.domain uses a type in com.github.rahulsom.grooves.api.snapshots.
- The types involved
grooves.boot.kotlin.domain.PatientAccount→com.github.rahulsom.grooves.api.snapshots.Snapshotgrooves.boot.kotlin.domain.PatientHealth→com.github.rahulsom.grooves.api.snapshots.Snapshot
- Direction
- grooves.boot.kotlin.domain uses com.github.rahulsom.grooves.api.snapshots, so a change to com.github.rahulsom.grooves.api.snapshots can break grooves.boot.kotlin.domain, while a change to grooves.boot.kotlin.domain can't break com.github.rahulsom.grooves.api.snapshots.
- Position
- Below the diagonal: grooves.boot.kotlin.domain uses a module listed above it, which is the healthy direction.
19→14 grooves.boot.kotlin.domain uses grooves.boot.kotlin.repositories✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.domain uses a type in grooves.boot.kotlin.repositories.
- The types involved
grooves.boot.kotlin.domain.PatientAccount→grooves.boot.kotlin.repositories.PatientRepositorygrooves.boot.kotlin.domain.PatientHealth→grooves.boot.kotlin.repositories.PatientRepository
- Direction
- grooves.boot.kotlin.domain uses grooves.boot.kotlin.repositories, so a change to grooves.boot.kotlin.repositories can break grooves.boot.kotlin.domain, while a change to grooves.boot.kotlin.domain can't break grooves.boot.kotlin.repositories.
- Position
- Below the diagonal: grooves.boot.kotlin.domain uses a module listed above it, which is the healthy direction.
20→16 com.github.rahulsom.grooves.groovy.transformations.internal uses com.github.rahulsom.grooves.groovy.transformations✕
- Connections
- 3 pairs of types, where a type in com.github.rahulsom.grooves.groovy.transformations.internal uses a type in com.github.rahulsom.grooves.groovy.transformations.
- The types involved
com.github.rahulsom.grooves.groovy.transformations.internal.AggregateASTTransformation→com.github.rahulsom.grooves.groovy.transformations.Aggregatecom.github.rahulsom.grooves.groovy.transformations.internal.EventASTTransformation→com.github.rahulsom.grooves.groovy.transformations.Eventcom.github.rahulsom.grooves.groovy.transformations.internal.QueryASTTransformation→com.github.rahulsom.grooves.groovy.transformations.Query
- Direction
- com.github.rahulsom.grooves.groovy.transformations.internal uses com.github.rahulsom.grooves.groovy.transformations, so a change to com.github.rahulsom.grooves.groovy.transformations can break com.github.rahulsom.grooves.groovy.transformations.internal, while a change to com.github.rahulsom.grooves.groovy.transformations.internal can't break com.github.rahulsom.grooves.groovy.transformations.
- Position
- Below the diagonal: com.github.rahulsom.grooves.groovy.transformations.internal uses a module listed above it, which is the healthy direction.
21→12 com.github.rahulsom.grooves.impl uses com.github.rahulsom.grooves.functions✕
- Connections
- 13 pairs of types, where a type in com.github.rahulsom.grooves.impl uses a type in com.github.rahulsom.grooves.functions.
- The types involved
com.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.ApplyMoreEventsPredicatecom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.DeprecatedByProvidercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.Deprecatorcom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.EmptySnapshotProvidercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.EventClassifiercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.EventHandlercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.EventIdProvidercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.EventVersionercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.EventsProvidercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.ExceptionHandlercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.RevertedEventProvidercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.SnapshotProvidercom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.functions.SnapshotVersioner
- Direction
- com.github.rahulsom.grooves.impl uses com.github.rahulsom.grooves.functions, so a change to com.github.rahulsom.grooves.functions can break com.github.rahulsom.grooves.impl, while a change to com.github.rahulsom.grooves.impl can't break com.github.rahulsom.grooves.functions.
- Position
- Below the diagonal: com.github.rahulsom.grooves.impl uses a module listed above it, which is the healthy direction.
21→15 com.github.rahulsom.grooves.impl uses com.github.rahulsom.grooves✕
- Connections
- 4 pairs of types, where a type in com.github.rahulsom.grooves.impl uses a type in com.github.rahulsom.grooves.
- The types involved
com.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.DeprecatedByResultcom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.EventApplyOutcomecom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.GroovesQuerycom.github.rahulsom.grooves.impl.GroovesQueryImpl→com.github.rahulsom.grooves.GroovesResult
- Direction
- com.github.rahulsom.grooves.impl uses com.github.rahulsom.grooves, so a change to com.github.rahulsom.grooves can break com.github.rahulsom.grooves.impl, while a change to com.github.rahulsom.grooves.impl can't break com.github.rahulsom.grooves.
- Position
- Below the diagonal: com.github.rahulsom.grooves.impl uses a module listed above it, which is the healthy direction.
22→2 grooves.boot.kotlin.domain.PatientEvent uses com.github.rahulsom.grooves.api.events✕
- Connections
- 3 pairs of types, where a type in grooves.boot.kotlin.domain.PatientEvent uses a type in com.github.rahulsom.grooves.api.events.
- The types involved
grooves.boot.kotlin.domain.PatientEvent.PatientDeprecatedBy→com.github.rahulsom.grooves.api.events.DeprecatedBygrooves.boot.kotlin.domain.PatientEvent.PatientDeprecates→com.github.rahulsom.grooves.api.events.Deprecatesgrooves.boot.kotlin.domain.PatientEvent.Reverted→com.github.rahulsom.grooves.api.events.RevertEvent
- Direction
- grooves.boot.kotlin.domain.PatientEvent uses com.github.rahulsom.grooves.api.events, so a change to com.github.rahulsom.grooves.api.events can break grooves.boot.kotlin.domain.PatientEvent, while a change to grooves.boot.kotlin.domain.PatientEvent can't break com.github.rahulsom.grooves.api.events.
- Position
- Below the diagonal: grooves.boot.kotlin.domain.PatientEvent uses a module listed above it, which is the healthy direction.
22→19 grooves.boot.kotlin.domain.PatientEvent uses grooves.boot.kotlin.domain✕
- Connections
- 6 pairs of types, where a type in grooves.boot.kotlin.domain.PatientEvent uses a type in grooves.boot.kotlin.domain.
- The types involved
grooves.boot.kotlin.domain.PatientEvent.Applicable→grooves.boot.kotlin.domain.PatientEventgrooves.boot.kotlin.domain.PatientEvent.PatientDeprecatedBy→grooves.boot.kotlin.domain.Patientgrooves.boot.kotlin.domain.PatientEvent.PatientDeprecatedBy→grooves.boot.kotlin.domain.PatientEventgrooves.boot.kotlin.domain.PatientEvent.PatientDeprecates→grooves.boot.kotlin.domain.Patientgrooves.boot.kotlin.domain.PatientEvent.PatientDeprecates→grooves.boot.kotlin.domain.PatientEventgrooves.boot.kotlin.domain.PatientEvent.Reverted→grooves.boot.kotlin.domain.PatientEvent
- Direction
- grooves.boot.kotlin.domain.PatientEvent uses grooves.boot.kotlin.domain, so a change to grooves.boot.kotlin.domain can break grooves.boot.kotlin.domain.PatientEvent, while a change to grooves.boot.kotlin.domain.PatientEvent can't break grooves.boot.kotlin.domain.
- Position
- Below the diagonal: grooves.boot.kotlin.domain.PatientEvent uses a module listed above it, which is the healthy direction.
23→22 grooves.boot.kotlin.domain.PatientEvent.Applicable uses grooves.boot.kotlin.domain.PatientEvent✕
- Connections
- 3 pairs of types, where a type in grooves.boot.kotlin.domain.PatientEvent.Applicable uses a type in grooves.boot.kotlin.domain.PatientEvent.
- The types involved
grooves.boot.kotlin.domain.PatientEvent.Applicable.Created→grooves.boot.kotlin.domain.PatientEvent.Applicablegrooves.boot.kotlin.domain.PatientEvent.Applicable.PaymentMade→grooves.boot.kotlin.domain.PatientEvent.Applicablegrooves.boot.kotlin.domain.PatientEvent.Applicable.ProcedurePerformed→grooves.boot.kotlin.domain.PatientEvent.Applicable
- Direction
- grooves.boot.kotlin.domain.PatientEvent.Applicable uses grooves.boot.kotlin.domain.PatientEvent, so a change to grooves.boot.kotlin.domain.PatientEvent can break grooves.boot.kotlin.domain.PatientEvent.Applicable, while a change to grooves.boot.kotlin.domain.PatientEvent.Applicable can't break grooves.boot.kotlin.domain.PatientEvent.
- Position
- Below the diagonal: grooves.boot.kotlin.domain.PatientEvent.Applicable uses a module listed above it, which is the healthy direction.
24→13 grooves.boot.kotlin.queries uses com.github.rahulsom.grooves.queries.internal✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.queries uses a type in com.github.rahulsom.grooves.queries.internal.
- The types involved
grooves.boot.kotlin.queries.PatientAccountQuery→com.github.rahulsom.grooves.queries.internal.SimpleQuerygrooves.boot.kotlin.queries.PatientHealthQuery→com.github.rahulsom.grooves.queries.internal.SimpleQuery
- Direction
- grooves.boot.kotlin.queries uses com.github.rahulsom.grooves.queries.internal, so a change to com.github.rahulsom.grooves.queries.internal can break grooves.boot.kotlin.queries, while a change to grooves.boot.kotlin.queries can't break com.github.rahulsom.grooves.queries.internal.
- Position
- Below the diagonal: grooves.boot.kotlin.queries uses a module listed above it, which is the healthy direction.
24→14 grooves.boot.kotlin.queries uses grooves.boot.kotlin.repositories✕
- Connections
- 4 pairs of types, where a type in grooves.boot.kotlin.queries uses a type in grooves.boot.kotlin.repositories.
- The types involved
grooves.boot.kotlin.queries.PatientAccountQuery→grooves.boot.kotlin.repositories.PatientAccountRepositorygrooves.boot.kotlin.queries.PatientAccountQuery→grooves.boot.kotlin.repositories.PatientEventRepositorygrooves.boot.kotlin.queries.PatientHealthQuery→grooves.boot.kotlin.repositories.PatientEventRepositorygrooves.boot.kotlin.queries.PatientHealthQuery→grooves.boot.kotlin.repositories.PatientHealthRepository
- Direction
- grooves.boot.kotlin.queries uses grooves.boot.kotlin.repositories, so a change to grooves.boot.kotlin.repositories can break grooves.boot.kotlin.queries, while a change to grooves.boot.kotlin.queries can't break grooves.boot.kotlin.repositories.
- Position
- Below the diagonal: grooves.boot.kotlin.queries uses a module listed above it, which is the healthy direction.
24→18 grooves.boot.kotlin.queries uses com.github.rahulsom.grooves.queries✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.queries uses a type in com.github.rahulsom.grooves.queries.
- The types involved
grooves.boot.kotlin.queries.PatientAccountQuery→com.github.rahulsom.grooves.queries.QuerySupportgrooves.boot.kotlin.queries.PatientHealthQuery→com.github.rahulsom.grooves.queries.QuerySupport
- Direction
- grooves.boot.kotlin.queries uses com.github.rahulsom.grooves.queries, so a change to com.github.rahulsom.grooves.queries can break grooves.boot.kotlin.queries, while a change to grooves.boot.kotlin.queries can't break com.github.rahulsom.grooves.queries.
- Position
- Below the diagonal: grooves.boot.kotlin.queries uses a module listed above it, which is the healthy direction.
24→19 grooves.boot.kotlin.queries uses grooves.boot.kotlin.domain✕
- Connections
- 6 pairs of types, where a type in grooves.boot.kotlin.queries uses a type in grooves.boot.kotlin.domain.
- The types involved
grooves.boot.kotlin.queries.PatientAccountQuery→grooves.boot.kotlin.domain.Patientgrooves.boot.kotlin.queries.PatientAccountQuery→grooves.boot.kotlin.domain.PatientAccountgrooves.boot.kotlin.queries.PatientAccountQuery→grooves.boot.kotlin.domain.PatientEventgrooves.boot.kotlin.queries.PatientHealthQuery→grooves.boot.kotlin.domain.Patientgrooves.boot.kotlin.queries.PatientHealthQuery→grooves.boot.kotlin.domain.PatientEventgrooves.boot.kotlin.queries.PatientHealthQuery→grooves.boot.kotlin.domain.PatientHealth
- Direction
- grooves.boot.kotlin.queries uses grooves.boot.kotlin.domain, so a change to grooves.boot.kotlin.domain can break grooves.boot.kotlin.queries, while a change to grooves.boot.kotlin.queries can't break grooves.boot.kotlin.domain.
- Position
- Below the diagonal: grooves.boot.kotlin.queries uses a module listed above it, which is the healthy direction.
24→22 grooves.boot.kotlin.queries uses grooves.boot.kotlin.domain.PatientEvent✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.queries uses a type in grooves.boot.kotlin.domain.PatientEvent.
- The types involved
grooves.boot.kotlin.queries.PatientAccountQuery→grooves.boot.kotlin.domain.PatientEvent.Applicablegrooves.boot.kotlin.queries.PatientHealthQuery→grooves.boot.kotlin.domain.PatientEvent.Applicable
- Direction
- grooves.boot.kotlin.queries uses grooves.boot.kotlin.domain.PatientEvent, so a change to grooves.boot.kotlin.domain.PatientEvent can break grooves.boot.kotlin.queries, while a change to grooves.boot.kotlin.queries can't break grooves.boot.kotlin.domain.PatientEvent.
- Position
- Below the diagonal: grooves.boot.kotlin.queries uses a module listed above it, which is the healthy direction.
25→10 grooves.boot.kotlin uses com.github.rahulsom.grooves.api.snapshots✕
- Connections
- 1 pair of types, where a type in grooves.boot.kotlin uses a type in com.github.rahulsom.grooves.api.snapshots.
- The types involved
grooves.boot.kotlin.BootStrap→com.github.rahulsom.grooves.api.snapshots.Snapshot
- Direction
- grooves.boot.kotlin uses com.github.rahulsom.grooves.api.snapshots, so a change to com.github.rahulsom.grooves.api.snapshots can break grooves.boot.kotlin, while a change to grooves.boot.kotlin can't break com.github.rahulsom.grooves.api.snapshots.
- Position
- Below the diagonal: grooves.boot.kotlin uses a module listed above it, which is the healthy direction.
25→14 grooves.boot.kotlin uses grooves.boot.kotlin.repositories✕
- Connections
- 4 pairs of types, where a type in grooves.boot.kotlin uses a type in grooves.boot.kotlin.repositories.
- The types involved
grooves.boot.kotlin.BootStrap→grooves.boot.kotlin.repositories.PatientAccountRepositorygrooves.boot.kotlin.BootStrap→grooves.boot.kotlin.repositories.PatientBlockingRepositorygrooves.boot.kotlin.BootStrap→grooves.boot.kotlin.repositories.PatientEventBlockingRepositorygrooves.boot.kotlin.BootStrap→grooves.boot.kotlin.repositories.PatientHealthRepository
- Direction
- grooves.boot.kotlin uses grooves.boot.kotlin.repositories, so a change to grooves.boot.kotlin.repositories can break grooves.boot.kotlin, while a change to grooves.boot.kotlin can't break grooves.boot.kotlin.repositories.
- Position
- Below the diagonal: grooves.boot.kotlin uses a module listed above it, which is the healthy direction.
25→19 grooves.boot.kotlin uses grooves.boot.kotlin.domain✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin uses a type in grooves.boot.kotlin.domain.
- The types involved
grooves.boot.kotlin.BootStrap→grooves.boot.kotlin.domain.Patientgrooves.boot.kotlin.BootStrap→grooves.boot.kotlin.domain.PatientEvent
- Direction
- grooves.boot.kotlin uses grooves.boot.kotlin.domain, so a change to grooves.boot.kotlin.domain can break grooves.boot.kotlin, while a change to grooves.boot.kotlin can't break grooves.boot.kotlin.domain.
- Position
- Below the diagonal: grooves.boot.kotlin uses a module listed above it, which is the healthy direction.
25→22 grooves.boot.kotlin uses grooves.boot.kotlin.domain.PatientEvent✕
- Connections
- 1 pair of types, where a type in grooves.boot.kotlin uses a type in grooves.boot.kotlin.domain.PatientEvent.
- The types involved
grooves.boot.kotlin.BootStrap→grooves.boot.kotlin.domain.PatientEvent.PatientDeprecatedBy
- Direction
- grooves.boot.kotlin uses grooves.boot.kotlin.domain.PatientEvent, so a change to grooves.boot.kotlin.domain.PatientEvent can break grooves.boot.kotlin, while a change to grooves.boot.kotlin can't break grooves.boot.kotlin.domain.PatientEvent.
- Position
- Below the diagonal: grooves.boot.kotlin uses a module listed above it, which is the healthy direction.
25→24 grooves.boot.kotlin uses grooves.boot.kotlin.queries✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin uses a type in grooves.boot.kotlin.queries.
- The types involved
grooves.boot.kotlin.BootStrap→grooves.boot.kotlin.queries.PatientAccountQuerygrooves.boot.kotlin.BootStrap→grooves.boot.kotlin.queries.PatientHealthQuery
- Direction
- grooves.boot.kotlin uses grooves.boot.kotlin.queries, so a change to grooves.boot.kotlin.queries can break grooves.boot.kotlin, while a change to grooves.boot.kotlin can't break grooves.boot.kotlin.queries.
- Position
- Below the diagonal: grooves.boot.kotlin uses a module listed above it, which is the healthy direction.
26→14 grooves.boot.kotlin.controllers uses grooves.boot.kotlin.repositories✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.controllers uses a type in grooves.boot.kotlin.repositories.
- The types involved
grooves.boot.kotlin.controllers.PatientController→grooves.boot.kotlin.repositories.PatientEventRepositorygrooves.boot.kotlin.controllers.PatientController→grooves.boot.kotlin.repositories.PatientRepository
- Direction
- grooves.boot.kotlin.controllers uses grooves.boot.kotlin.repositories, so a change to grooves.boot.kotlin.repositories can break grooves.boot.kotlin.controllers, while a change to grooves.boot.kotlin.controllers can't break grooves.boot.kotlin.repositories.
- Position
- Below the diagonal: grooves.boot.kotlin.controllers uses a module listed above it, which is the healthy direction.
26→19 grooves.boot.kotlin.controllers uses grooves.boot.kotlin.domain✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.controllers uses a type in grooves.boot.kotlin.domain.
- The types involved
grooves.boot.kotlin.controllers.PatientController→grooves.boot.kotlin.domain.Patientgrooves.boot.kotlin.controllers.PatientController→grooves.boot.kotlin.domain.PatientEvent
- Direction
- grooves.boot.kotlin.controllers uses grooves.boot.kotlin.domain, so a change to grooves.boot.kotlin.domain can break grooves.boot.kotlin.controllers, while a change to grooves.boot.kotlin.controllers can't break grooves.boot.kotlin.domain.
- Position
- Below the diagonal: grooves.boot.kotlin.controllers uses a module listed above it, which is the healthy direction.
26→24 grooves.boot.kotlin.controllers uses grooves.boot.kotlin.queries✕
- Connections
- 2 pairs of types, where a type in grooves.boot.kotlin.controllers uses a type in grooves.boot.kotlin.queries.
- The types involved
grooves.boot.kotlin.controllers.PatientController→grooves.boot.kotlin.queries.PatientAccountQuerygrooves.boot.kotlin.controllers.PatientController→grooves.boot.kotlin.queries.PatientHealthQuery
- Direction
- grooves.boot.kotlin.controllers uses grooves.boot.kotlin.queries, so a change to grooves.boot.kotlin.queries can break grooves.boot.kotlin.controllers, while a change to grooves.boot.kotlin.controllers can't break grooves.boot.kotlin.queries.
- Position
- Below the diagonal: grooves.boot.kotlin.controllers 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 — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.2 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.2 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.8 pts | Medium | Documentation (README) |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with PatientTest.java. | +1.2 pts | Low | Test Quality |
| Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI. | +1.5 pts | Medium | A11y enforcement |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +1.5 pts | Medium | Deployment & Rollback |
| Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with PatientTest.java. | +0.7 pts | Low | Test Quality |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.4 pts | Medium | Page structure |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| grooves-example-javaee/src/test/java/grooves/example/javaee/PatientTest.java | 6.5 | Mixed | Test Quality: No assertions (empty test): contextLoads |
| grooves-api/src/main/java/com/github/rahulsom/grooves/queries/TemporalQuerySupport.java | 7.4 | Near-clean | Code Duplication: Duplicated block (15–16 lines × 2) |
| grooves-example-javaee/src/main/java/grooves/example/javaee/BootStrap.java | 7.4 | Near-clean | Code Duplication: Edited copy of a member (26 corresponding lines) |
| grooves-api/src/main/java/com/github/rahulsom/grooves/queries/internal/JoinExecutor.java | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| grooves-groovy/src/main/java/com/github/rahulsom/grooves/groovy/transformations/internal/EventASTTransformation.java | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| grooves-api/src/main/java/com/github/rahulsom/grooves/queries/FunctionalTemporalQuery.java | 8.5 | Near-clean | Code Duplication: Duplicated block (90 lines × 2) |
| grooves-example-javaee/src/main/java/grooves/example/javaee/domain/PatientAccount.java | 8.5 | Near-clean | Code Duplication: Duplicated block (69 lines × 2) |
| grooves-example-javaee/src/main/java/grooves/example/javaee/queries/PatientAccountQuery.java | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| grooves-example-springboot-kotlin/src/main/kotlin/grooves/boot/kotlin/queries/PatientAccountQuery.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| grooves-example-springboot-kotlin/src/main/kotlin/grooves/boot/kotlin/BootStrap.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
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 88 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 88 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, 31 of 44 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D4 Code Duplication — 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 12 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .groovy (1,441 lines, 18% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- 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 JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — grooves-site/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- 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 14 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 4 test source file(s) (.ts) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language 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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.ts, .java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. Not scored — a Gradle build resolved 369 artifact(s) across its subprojects (155 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — 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 repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 2312 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 4 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (grooves-types/build.gradle.kts), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — 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 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.
- D26 Project Cohesion — 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. Project size and spread are measured over build units whose source a code model reads. This repository's .groovy source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 381 sampled here came from .java files. This repository's .kt, .groovy source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- AX1 Captive dependencies — 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 repository also uses Enterprise JavaBeans and Guice, whose singleton and shorter-lived bindings can capture one another the same way, but this check does not read them yet. That is a gap in this analyzer's language reach — not a finding that those bindings are free of it.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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 frontend declares that it computes whether a construction is produced or passed, yet 99 of 267 constructions arrived without the answer. Arm two skipped them; it did not clear them.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin, Python, groovy is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
12 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 7 of the 13 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .groovy (18% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with EventASTTransformation.java, PatientAccountQuery.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with TemporalQuerySupport.java, BootStrap.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (15–16 lines × 2) finding(s) in Code Duplication — start with TemporalQuerySupport.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
11 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 8 of the 11 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 13 classes have LCOM4 above 3.
D9 · Test Distribution
53 test methods: 53 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 32 `it`/`test` case(s) across 4 test file(s) declaring at least one beside 14 .NET test method(s); its tier split is read from package names and paths only. The Python suite contributes 7 test function(s) across 1 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 14 tests. Measured on the .java suite only — at least 4 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with PatientTest.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with PatientTest.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 46 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 16 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 12 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 2 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 6567 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 10 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 69 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D26 · Project Cohesion
0 of 8 build units (Gradle) flagged as possibly oversized/incoherent. This repository's .groovy source was read by no build unit, so this covers part of the tree, not all of it.
D27 · Navigability
35 % of calls cross a namespace and 21 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .java source only — this repository's .kt, .groovy was not sampled for call sites, so this score covers part of the tree, not all of it.
What to do
- Improve Navigability — currently 9.0/10. — 35 % of calls cross a namespace and 21 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .java source only — this repository's .kt, .groovy was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 8 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 2 file(s) — `gradlew` (line 74, line 178), `grooves-example-springboot-kotlin/src/main/kotlin/grooves/boot/kotlin/BootStrap.kt` (line 172, line 229) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- No action in Static Analysis (SAST) — all 7 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 (7 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 1 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 (1 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 39 of the 139 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 platform declaration(s) and 48 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
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — grooves-site/index.html:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — grooves-site/index.html:49
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — grooves-site/styles/foundation.css:128
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — grooves-site/package.json:15
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `PatientEvent.aggregateId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — grooves-example-springboot-kotlin/src/main/kotlin/grooves/boot/kotlin/domain/PatientEvent.kt:28
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `Patient` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — grooves-example-javaee/src/main/java/grooves/example/javaee/domain/Patient.java:10
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 11 of 14 project(s) that lack one — worth up to 1.6 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- Only 5/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `grooves-example-springboot-kotlin`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
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.
P8 · Schema migrations
R1 · Type Safety
R10 · Code Duplication
- grooves-site/src/main.ts:24 · grooves-site/src/main.ts:29 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — grooves-site/src/main.ts:24
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 0/9 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| 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 |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 78% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 66% | Adequate — gated by DM2, DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 58% | Adequate | Acceptable, with room to improve. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 369 artifact(s) across its subprojects (155 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Kotlin, Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (grooves-example-javaee), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 10 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 3); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Java, Python and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): contextLoads grooves-example-javaee/src/test/java/grooves/example/javaee/PatientTest.java:61
- REDACTED
Serious — 24 finding(s)
- Duplicated block (6 lines × 2) grooves-groovy/src/main/java/com/github/rahulsom/grooves/groovy/transformations/internal/EventASTTransformation.java:31
- Duplicated block (6 lines × 2) grooves-example-javaee/src/main/java/grooves/example/javaee/queries/PatientAccountQuery.java:55
- Duplicated block (8 lines × 2) grooves-api/src/main/java/com/github/rahulsom/grooves/queries/TemporalQuerySupport.java:98
- Duplicated block (8 lines × 2) grooves-example-springboot-kotlin/src/main/kotlin/grooves/boot/kotlin/BootStrap.kt:112
- Page without a main landmark grooves-site/index.html:2
- Heading level jumps from h1 to h3 grooves-site/index.html:49
- Focus outline removed in CSS without a :focus replacement grooves-site/styles/foundation.css:128
- Accessibility enforcement below the top rung grooves-site/package.json:15
- Test project verifies nothing: grooves-example-javaee grooves-example-javaee/src/test/java/grooves/example/javaee/PatientTest.java:61
- REDACTED
- Duplicated block (15–16 lines × 2) grooves-api/src/main/java/com/github/rahulsom/grooves/queries/TemporalQuerySupport.java:141
- Duplicated block (12 lines × 2) grooves-api/src/main/java/com/github/rahulsom/grooves/queries/TemporalQuerySupport.java:181
- Duplicated block (11 lines × 2) grooves-api/src/main/java/com/github/rahulsom/grooves/queries/internal/JoinExecutor.java:70
- Duplicated block (90 lines × 2) grooves-api/src/main/java/com/github/rahulsom/grooves/queries/FunctionalTemporalQuery.java:1
- Edited copy of a member (26 corresponding lines) grooves-example-javaee/src/main/java/grooves/example/javaee/BootStrap.java:170
- Duplicated block (25 lines × 2) grooves-example-javaee/src/main/java/grooves/example/javaee/BootStrap.java:171
- Duplicated block (7 lines × 2) grooves-example-javaee/src/main/java/grooves/example/javaee/BootStrap.java:246
- Duplicated block (69 lines × 2) grooves-example-javaee/src/main/java/grooves/example/javaee/domain/PatientAccount.java:1
- Duplicated block (10 lines × 2) grooves-example-springboot-kotlin/src/main/kotlin/grooves/boot/kotlin/queries/PatientAccountQuery.kt:97
- Off the main sequence: :grooves-java
- Anemic entity: Patient grooves-example-javaee/src/main/java/grooves/example/javaee/domain/Patient.java:10
- No deployment automation
- Duplicated block (5 lines × 2 locations) grooves-site/src/main.ts:24
- No lint script
Minor — 11 finding(s)
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- Primitive id on a domain type: PatientEvent.aggregateId grooves-example-springboot-kotlin/src/main/kotlin/grooves/boot/kotlin/domain/PatientEvent.kt:28
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No changelog
- Duplicated predicate grooves-example-javaee/build.gradle.kts:38
- Java packages are not null-marked everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-552c23ef670b4f9da7d670a79d251cba/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-552c23ef670b4f9da7d670a79d251cba/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 . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |