Executive summary
starlane-io/starlane is rated At risk because critical security findings are open. Its score is held back in part because it has packages with a known security hole. It scores 45.0 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Security and Compliance, at 34.1, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4.8 points. Having someone learn and document the 98 files no active contributor knows comes next, worth about 4.7 points. Raising Security and Compliance to 68 would lift the score to about 52.6.
Seven weaknesses in the code could be used by an attacker. Four known security holes in the packages the code depends on can be used by attackers. Fixing the weaknesses the scanner points to and updating the vulnerable packages would close both risks. Pinning each tool to an exact version would fix the four pipeline tools referenced by a changeable name, and switching the validation back on would deal with the security check on connections or logins switched off.
The product code is 56,682 lines, about €50,000 to rebuild.
If Security and Compliance rose from 34.1 to 68, the lowest score rated Strong, the score would rise from 45.0 to about 52.6.
Rebuild cost: about €50,000 · Estimate
| Cost to rebuild | €17,000 to €84,000, for 278 to 881 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 56,682 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 starlane_base.backend | 2 starlane_base.foundation.config | 3 starlane_hyperspace.base.config | 4 starlane_space.types2.package | 5 starlane_base.foundation.implementation.docker_daemon_foundation | 6 starlane_space.hyper | 7 starlane_space.log | 8 starlane_space.types1.property | 9 starlane_space.util | 10 starlane_space.parse.model | 11 starlane_space.wave.core | 12 starlane_space.substance | 13 starlane_space.selector | 14 starlane_space.wave | 15 starlane_space.artifact.asynch | 16 starlane_space.err | 17 starlane_package.create | 18 starlane_space.parse | 19 starlane_base.partial.mount | 20 starlane_space.fail.resource | 21 starlane_space.loc | 22 starlane_space.command.direct.create | 23 starlane_space.wave.exchange.asynch | 24 starlane_hyperspace.hyperlane | 25 starlane_space.particle.traversal | 26 starlane_hyperspace.hyperlane.tcp | 27 starlane_space.kind | 28 starlane_hyperspace.machine | 29 starlane_space.particle | 30 starlane_hyperspace.registry | 31 starlane_hyperspace.star | 32 starlane_space.status | 33 starlane_hyperspace.base.provider | 34 starlane_hyperspace.driver | 35 starlane_hyperspace.layer.field | 36 starlane_platform_for_postgres_registry.registry | 37 starlane_hyperspace.base | 38 starlane_hyperspace.driver.control | 39 starlane_platform_for_postgres.database.concrete | 40 starlane.starlane |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 starlane_base.backend | ||||||||||||||||||||||||||||||||||||||||
| 2 starlane_base.foundation.config | ||||||||||||||||||||||||||||||||||||||||
| 3 starlane_hyperspace.base.config | ||||||||||||||||||||||||||||||||||||||||
| 4 starlane_space.types2.package | ||||||||||||||||||||||||||||||||||||||||
| 5 starlane_base.foundation.implementation.docker_daemon_foundation | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 starlane_space.hyper | 2 | 4 | 4 | 3 | 5 | 4 | ||||||||||||||||||||||||||||||||||
| 7 starlane_space.log | 2 | 2 | 6 | |||||||||||||||||||||||||||||||||||||
| 8 starlane_space.types1.property | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 starlane_space.util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 starlane_space.parse.model | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 starlane_space.wave.core | 1 | 3 | 4 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 12 starlane_space.substance | 3 | 4 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 13 starlane_space.selector | 3 | 4 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 14 starlane_space.wave | 5 | 5 | 12 | 12 | 3 | 20 | ||||||||||||||||||||||||||||||||||
| 15 starlane_space.artifact.asynch | 5 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 starlane_space.err | 2 | 3 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 17 starlane_package.create | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 starlane_space.parse | 5 | 3 | 1 | 1 | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||
| 19 starlane_base.partial.mount | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 starlane_space.fail.resource | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 starlane_space.loc | 4 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 22 starlane_space.command.direct.create | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 starlane_space.wave.exchange.asynch | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 starlane_hyperspace.hyperlane | 24 | 13 | 2 | 7 | 1 | 11 | 6 | |||||||||||||||||||||||||||||||||
| 25 starlane_space.particle.traversal | 1 | 2 | 6 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 starlane_hyperspace.hyperlane.tcp | 1 | 3 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 27 starlane_space.kind | 14 | 6 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 starlane_hyperspace.machine | 2 | 3 | 1 | 3 | 2 | 3 | 1 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||
| 29 starlane_space.particle | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 30 starlane_hyperspace.registry | 1 | 3 | 2 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 31 starlane_hyperspace.star | 1 | 1 | 1 | 1 | 4 | 1 | 1 | 11 | 5 | 2 | 6 | 7 | 2 | 1 | 3 | |||||||||||||||||||||||||
| 32 starlane_space.status | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 starlane_hyperspace.base.provider | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 starlane_hyperspace.driver | 1 | 2 | 2 | 2 | 1 | 3 | 2 | 5 | 2 | 4 | 7 | 2 | 13 | 11 | ||||||||||||||||||||||||||
| 35 starlane_hyperspace.layer.field | 2 | 1 | 1 | 2 | 2 | 2 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||
| 36 starlane_platform_for_postgres_registry.registry | 5 | 2 | 1 | 1 | 2 | 1 | 3 | 3 | 1 | |||||||||||||||||||||||||||||||
| 37 starlane_hyperspace.base | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 38 starlane_hyperspace.driver.control | 1 | 1 | 1 | 2 | 1 | 3 | 1 | 3 | 3 | 18 | ||||||||||||||||||||||||||||||
| 39 starlane_platform_for_postgres.database.concrete | 1 | 1 | 7 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 starlane.starlane | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
5→2 starlane_base.foundation.implementation.docker_daemon_foundation uses starlane_base.foundation.config✕
- Connections
- 2 pairs of types, where a type in starlane_base.foundation.implementation.docker_daemon_foundation uses a type in starlane_base.foundation.config.
- The types involved
starlane_base.foundation.implementation.docker_daemon_foundation.FoundationConfig→starlane_base.foundation.config.FoundationConfigstarlane_base.foundation.implementation.docker_daemon_foundation.ProviderConfig→starlane_base.foundation.config.ProviderConfig
- Direction
- starlane_base.foundation.implementation.docker_daemon_foundation uses starlane_base.foundation.config, so a change to starlane_base.foundation.config can break starlane_base.foundation.implementation.docker_daemon_foundation, while a change to starlane_base.foundation.implementation.docker_daemon_foundation can't break starlane_base.foundation.config.
- Position
- Below the diagonal: starlane_base.foundation.implementation.docker_daemon_foundation uses a module listed above it, which is the healthy direction.
6→11 starlane_space.hyper uses starlane_space.wave.core part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.hyper uses a type in starlane_space.wave.core.
- The types involved
starlane_space.hyper.Assign→starlane_space.wave.core.DirectedCorestarlane_space.hyper.Provision→starlane_space.wave.core.DirectedCore
- Direction
- starlane_space.hyper uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_space.hyper, while a change to starlane_space.hyper can't break starlane_space.wave.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→12 starlane_space.hyper uses starlane_space.substance part of a loop✕
- Connections
- 4 pairs of types, where a type in starlane_space.hyper uses a type in starlane_space.substance.
- The types involved
starlane_space.hyper.Assign→starlane_space.substance.Substancestarlane_space.hyper.HyperSubstanceKind→starlane_space.substance.SubstanceKindstarlane_space.hyper.Knock→starlane_space.substance.Substancestarlane_space.hyper.Provision→starlane_space.substance.Substance
- Direction
- starlane_space.hyper uses starlane_space.substance, so a change to starlane_space.substance can break starlane_space.hyper, while a change to starlane_space.hyper can't break starlane_space.substance.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→14 starlane_space.hyper uses starlane_space.wave part of a loop✕
- Connections
- 4 pairs of types, where a type in starlane_space.hyper uses a type in starlane_space.wave.
- The types involved
starlane_space.hyper.Assign→starlane_space.wave.PingCorestarlane_space.hyper.Greet→starlane_space.wave.Agentstarlane_space.hyper.Knock→starlane_space.wave.WaveVariantDefstarlane_space.hyper.Provision→starlane_space.wave.PingCore
- Direction
- starlane_space.hyper uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.hyper, while a change to starlane_space.hyper can't break starlane_space.wave.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→21 starlane_space.hyper uses starlane_space.loc part of a loop✕
- Connections
- 3 pairs of types, where a type in starlane_space.hyper uses a type in starlane_space.loc.
- The types involved
starlane_space.hyper.Discovery→starlane_space.loc.StarKeystarlane_space.hyper.Greet→starlane_space.loc.Surfacestarlane_space.hyper.Knock→starlane_space.loc.Surface
- Direction
- starlane_space.hyper uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.hyper, while a change to starlane_space.hyper can't break starlane_space.loc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→27 starlane_space.hyper uses starlane_space.kind part of a loop✕
- Connections
- 5 pairs of types, where a type in starlane_space.hyper uses a type in starlane_space.kind.
- The types involved
starlane_space.hyper.Assign→starlane_space.kind.Kindstarlane_space.hyper.Created→starlane_space.kind.KindPartsstarlane_space.hyper.Discovery→starlane_space.kind.StarSubstarlane_space.hyper.HostCmd→starlane_space.kind.Kindstarlane_space.hyper.MountKind→starlane_space.kind.Kind
- Direction
- starlane_space.hyper uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.hyper, while a change to starlane_space.hyper can't break starlane_space.kind.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→29 starlane_space.hyper uses starlane_space.particle part of a loop✕
- Connections
- 4 pairs of types, where a type in starlane_space.hyper uses a type in starlane_space.particle.
- The types involved
starlane_space.hyper.Assign→starlane_space.particle.Detailsstarlane_space.hyper.HostCmd→starlane_space.particle.Detailsstarlane_space.hyper.ParticleRecord→starlane_space.particle.Detailsstarlane_space.hyper.ParticleRecord→starlane_space.particle.Stub
- Direction
- starlane_space.hyper uses starlane_space.particle, so a change to starlane_space.particle can break starlane_space.hyper, while a change to starlane_space.hyper can't break starlane_space.particle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→14 starlane_space.log uses starlane_space.wave part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.log uses a type in starlane_space.wave.
- The types involved
starlane_space.log.Loc→starlane_space.wave.Agentstarlane_space.log.Logger→starlane_space.wave.WaveVariantDef
- Direction
- starlane_space.log uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.log, while a change to starlane_space.log can't break starlane_space.wave.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→18 starlane_space.log uses starlane_space.parse part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.log uses a type in starlane_space.parse.
- The types involved
starlane_space.log.Log→starlane_space.parse.CamelCasestarlane_space.log.LogSpan→starlane_space.parse.CamelCase
- Direction
- starlane_space.log uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.log, while a change to starlane_space.log can't break starlane_space.parse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→21 starlane_space.log uses starlane_space.loc part of a loop✕
- Connections
- 6 pairs of types, where a type in starlane_space.log uses a type in starlane_space.loc.
- The types involved
starlane_space.log.Loc→starlane_space.loc.Surfacestarlane_space.log.Log→starlane_space.loc.Uuidstarlane_space.log.LogSpan→starlane_space.loc.Uuidstarlane_space.log.Logger→starlane_space.loc.Uuidstarlane_space.log.RootLoggerBuilder→starlane_space.loc.Uuidstarlane_space.log.SpanEvent→starlane_space.loc.Uuid
- Direction
- starlane_space.log uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.log, while a change to starlane_space.log can't break starlane_space.loc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→27 starlane_space.types1.property uses starlane_space.kind part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.types1.property uses a type in starlane_space.kind.
- The types involved
starlane_space.types1.property.PropertiesConfig→starlane_space.kind.Kindstarlane_space.types1.property.PropertiesConfigBuilder→starlane_space.kind.Kind
- Direction
- starlane_space.types1.property uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.types1.property, while a change to starlane_space.types1.property can't break starlane_space.kind.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→18 starlane_space.util uses starlane_space.parse part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.util uses a type in starlane_space.parse.
- The types involved
starlane_space.util.ToResolved→starlane_space.parse.Env
- Direction
- starlane_space.util uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.util, while a change to starlane_space.util can't break starlane_space.parse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→21 starlane_space.util uses starlane_space.loc part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.util uses a type in starlane_space.loc.
- The types involved
starlane_space.util.util$module→starlane_space.loc.Uuid
- Direction
- starlane_space.util uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.util, while a change to starlane_space.util can't break starlane_space.loc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→9 starlane_space.parse.model uses starlane_space.util✕
- Connections
- 2 pairs of types, where a type in starlane_space.parse.model uses a type in starlane_space.util.
- The types involved
starlane_space.parse.model.RouteScopeSelector→starlane_space.util.ValueMatcherstarlane_space.parse.model.Subst→starlane_space.util.ToResolved
- Direction
- starlane_space.parse.model uses starlane_space.util, so a change to starlane_space.util can break starlane_space.parse.model, while a change to starlane_space.parse.model can't break starlane_space.util.
- Position
- Below the diagonal: starlane_space.parse.model uses a module listed above it, which is the healthy direction.
10→18 starlane_space.parse.model uses starlane_space.parse part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.parse.model uses a type in starlane_space.parse.
- The types involved
starlane_space.parse.model.Subst→starlane_space.parse.Env
- Direction
- starlane_space.parse.model uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.parse.model, while a change to starlane_space.parse.model can't break starlane_space.parse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→6 starlane_space.wave.core uses starlane_space.hyper✕
- Connections
- 1 pair of types, where a type in starlane_space.wave.core uses a type in starlane_space.hyper.
- The types involved
starlane_space.wave.core.ReflectedCore→starlane_space.hyper.ParticleLocation
- Direction
- starlane_space.wave.core uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_space.wave.core, while a change to starlane_space.wave.core can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_space.wave.core uses a module listed above it, which is the healthy direction.
11→9 starlane_space.wave.core uses starlane_space.util✕
- Connections
- 3 pairs of types, where a type in starlane_space.wave.core uses a type in starlane_space.util.
- The types involved
starlane_space.wave.core.Method→starlane_space.util.ValueMatcherstarlane_space.wave.core.MethodKind→starlane_space.util.ValueMatcherstarlane_space.wave.core.MethodPattern→starlane_space.util.ValueMatcher
- Direction
- starlane_space.wave.core uses starlane_space.util, so a change to starlane_space.util can break starlane_space.wave.core, while a change to starlane_space.wave.core can't break starlane_space.util.
- Position
- Below the diagonal: starlane_space.wave.core uses a module listed above it, which is the healthy direction.
11→12 starlane_space.wave.core uses starlane_space.substance part of a loop✕
- Connections
- 4 pairs of types, where a type in starlane_space.wave.core uses a type in starlane_space.substance.
- The types involved
starlane_space.wave.core.DirectedCore→starlane_space.substance.Substancestarlane_space.wave.core.DirectedCore→starlane_space.substance.ToSubstancestarlane_space.wave.core.ReflectedCore→starlane_space.substance.Substancestarlane_space.wave.core.ReflectedCore→starlane_space.substance.ToSubstance
- Direction
- starlane_space.wave.core uses starlane_space.substance, so a change to starlane_space.substance can break starlane_space.wave.core, while a change to starlane_space.wave.core can't break starlane_space.substance.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→14 starlane_space.wave.core uses starlane_space.wave part of a loop✕
- Connections
- 3 pairs of types, where a type in starlane_space.wave.core uses a type in starlane_space.wave.
- The types involved
starlane_space.wave.core.DirectedCore→starlane_space.wave.PingCorestarlane_space.wave.core.ReflectedCore→starlane_space.wave.PongCorestarlane_space.wave.core.ReflectedCore→starlane_space.wave.WaveId
- Direction
- starlane_space.wave.core uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.wave.core, while a change to starlane_space.wave.core can't break starlane_space.wave.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 starlane_space.wave.core uses starlane_space.err part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.wave.core uses a type in starlane_space.err.
- The types involved
starlane_space.wave.core.ReflectedCore→starlane_space.err.SpaceErr
- Direction
- starlane_space.wave.core uses starlane_space.err, so a change to starlane_space.err can break starlane_space.wave.core, while a change to starlane_space.wave.core can't break starlane_space.err.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→21 starlane_space.wave.core uses starlane_space.loc part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.wave.core uses a type in starlane_space.loc.
- The types involved
starlane_space.wave.core.ReflectedCore→starlane_space.loc.Surface
- Direction
- starlane_space.wave.core uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.wave.core, while a change to starlane_space.wave.core can't break starlane_space.loc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→29 starlane_space.wave.core uses starlane_space.particle part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.wave.core uses a type in starlane_space.particle.
- The types involved
starlane_space.wave.core.ReflectedCore→starlane_space.particle.Status
- Direction
- starlane_space.wave.core uses starlane_space.particle, so a change to starlane_space.particle can break starlane_space.wave.core, while a change to starlane_space.wave.core can't break starlane_space.particle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→9 starlane_space.substance uses starlane_space.util✕
- Connections
- 3 pairs of types, where a type in starlane_space.substance uses a type in starlane_space.util.
- The types involved
starlane_space.substance.MapPatternDef→starlane_space.util.ValuePatternstarlane_space.substance.SubstancePatternDef→starlane_space.util.ValueMatcherstarlane_space.substance.SubstanceTypePatternDef→starlane_space.util.ToResolved
- Direction
- starlane_space.substance uses starlane_space.util, so a change to starlane_space.util can break starlane_space.substance, while a change to starlane_space.substance can't break starlane_space.util.
- Position
- Below the diagonal: starlane_space.substance uses a module listed above it, which is the healthy direction.
12→10 starlane_space.substance uses starlane_space.parse.model✕
- Connections
- 4 pairs of types, where a type in starlane_space.substance uses a type in starlane_space.parse.model.
- The types involved
starlane_space.substance.CmdCall→starlane_space.parse.model.Subststarlane_space.substance.ExtCall→starlane_space.parse.model.Subststarlane_space.substance.HttpCall→starlane_space.parse.model.Subststarlane_space.substance.HypCall→starlane_space.parse.model.Subst
- Direction
- starlane_space.substance uses starlane_space.parse.model, so a change to starlane_space.parse.model can break starlane_space.substance, while a change to starlane_space.substance can't break starlane_space.parse.model.
- Position
- Below the diagonal: starlane_space.substance uses a module listed above it, which is the healthy direction.
12→11 starlane_space.substance uses starlane_space.wave.core✕
- Connections
- 2 pairs of types, where a type in starlane_space.substance uses a type in starlane_space.wave.core.
- The types involved
starlane_space.substance.MultipartForm→starlane_space.wave.core.DirectedCorestarlane_space.substance.ToRequestCore→starlane_space.wave.core.DirectedCore
- Direction
- starlane_space.substance uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_space.substance, while a change to starlane_space.substance can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_space.substance uses a module listed above it, which is the healthy direction.
12→14 starlane_space.substance uses starlane_space.wave part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.substance uses a type in starlane_space.wave.
- The types involved
starlane_space.substance.Substance→starlane_space.wave.PongCorestarlane_space.substance.Token→starlane_space.wave.PongCore
- Direction
- starlane_space.substance uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.substance, while a change to starlane_space.substance can't break starlane_space.wave.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→16 starlane_space.substance uses starlane_space.err part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.substance uses a type in starlane_space.err.
- The types involved
starlane_space.substance.FormErrs→starlane_space.err.SpaceErr
- Direction
- starlane_space.substance uses starlane_space.err, so a change to starlane_space.err can break starlane_space.substance, while a change to starlane_space.substance can't break starlane_space.err.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→18 starlane_space.substance uses starlane_space.parse part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.substance uses a type in starlane_space.parse.
- The types involved
starlane_space.substance.SubstanceTypePatternDef→starlane_space.parse.Env
- Direction
- starlane_space.substance uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.substance, while a change to starlane_space.substance can't break starlane_space.parse.
- 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→9 starlane_space.selector uses starlane_space.util✕
- Connections
- 3 pairs of types, where a type in starlane_space.selector uses a type in starlane_space.util.
- The types involved
starlane_space.selector.KindSelectorDef→starlane_space.util.ValuePatternstarlane_space.selector.MapEntryPatternDef→starlane_space.util.ValuePatternstarlane_space.selector.SubKindSelector→starlane_space.util.ValueMatcher
- Direction
- starlane_space.selector uses starlane_space.util, so a change to starlane_space.util can break starlane_space.selector, while a change to starlane_space.selector can't break starlane_space.util.
- Position
- Below the diagonal: starlane_space.selector uses a module listed above it, which is the healthy direction.
13→12 starlane_space.selector uses starlane_space.substance✕
- Connections
- 4 pairs of types, where a type in starlane_space.selector uses a type in starlane_space.substance.
- The types involved
starlane_space.selector.CreateBlock→starlane_space.substance.Substancestarlane_space.selector.PayloadType2Def→starlane_space.substance.CallWithConfigDefstarlane_space.selector.PayloadType2Def→starlane_space.substance.SubstanceFormatstarlane_space.selector.PayloadType2Def→starlane_space.substance.SubstanceKind
- Direction
- starlane_space.selector uses starlane_space.substance, so a change to starlane_space.substance can break starlane_space.selector, while a change to starlane_space.selector can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_space.selector uses a module listed above it, which is the healthy direction.
13→18 starlane_space.selector uses starlane_space.parse part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.selector uses a type in starlane_space.parse.
- The types involved
starlane_space.selector.SubKindSelector→starlane_space.parse.CamelCase
- Direction
- starlane_space.selector uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.selector, while a change to starlane_space.selector can't break starlane_space.parse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→21 starlane_space.selector uses starlane_space.loc part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.selector uses a type in starlane_space.loc.
- The types involved
starlane_space.selector.PortHierarchy→starlane_space.loc.Layerstarlane_space.selector.PortHierarchy→starlane_space.loc.Topic
- Direction
- starlane_space.selector uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.selector, while a change to starlane_space.selector can't break starlane_space.loc.
- 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→27 starlane_space.selector uses starlane_space.kind part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.selector uses a type in starlane_space.kind.
- The types involved
starlane_space.selector.KindBaseSelector→starlane_space.kind.BaseKindstarlane_space.selector.SubKindSelector→starlane_space.kind.SubKind
- Direction
- starlane_space.selector uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.selector, while a change to starlane_space.selector can't break starlane_space.kind.
- 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→29 starlane_space.selector uses starlane_space.particle part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.selector uses a type in starlane_space.particle.
- The types involved
starlane_space.selector.Pattern→starlane_space.particle.Archetype
- Direction
- starlane_space.selector uses starlane_space.particle, so a change to starlane_space.particle can break starlane_space.selector, while a change to starlane_space.selector can't break starlane_space.particle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→7 starlane_space.wave uses starlane_space.log✕
- Connections
- 5 pairs of types, where a type in starlane_space.wave uses a type in starlane_space.log.
- The types involved
starlane_space.wave.DirectedProto→starlane_space.log.Trackablestarlane_space.wave.DirectedWaveDef→starlane_space.log.Spannerstarlane_space.wave.ReflectedWave→starlane_space.log.Trackablestarlane_space.wave.WaveDef→starlane_space.log.Spannerstarlane_space.wave.WaveVariantDef→starlane_space.log.Trackable
- Direction
- starlane_space.wave uses starlane_space.log, so a change to starlane_space.log can break starlane_space.wave, while a change to starlane_space.wave can't break starlane_space.log.
- Position
- Below the diagonal: starlane_space.wave uses a module listed above it, which is the healthy direction.
14→10 starlane_space.wave uses starlane_space.parse.model✕
- Connections
- 5 pairs of types, where a type in starlane_space.wave uses a type in starlane_space.parse.model.
- The types involved
starlane_space.wave.DirectedProto→starlane_space.parse.model.Scopestarlane_space.wave.DirectedWaveDef→starlane_space.parse.model.Scopestarlane_space.wave.ReflectedProto→starlane_space.parse.model.Scopestarlane_space.wave.Scope→starlane_space.parse.model.Scopestarlane_space.wave.WaveVariantDef→starlane_space.parse.model.Scope
- Direction
- starlane_space.wave uses starlane_space.parse.model, so a change to starlane_space.parse.model can break starlane_space.wave, while a change to starlane_space.wave can't break starlane_space.parse.model.
- Position
- Below the diagonal: starlane_space.wave uses a module listed above it, which is the healthy direction.
14→11 starlane_space.wave uses starlane_space.wave.core✕
- Connections
- 12 pairs of types, where a type in starlane_space.wave uses a type in starlane_space.wave.core.
- The types involved
starlane_space.wave.DirectedProto→starlane_space.wave.core.DirectedCorestarlane_space.wave.DirectedProto→starlane_space.wave.core.Methodstarlane_space.wave.DirectedWaveDef→starlane_space.wave.core.DirectedCorestarlane_space.wave.EchoCore→starlane_space.wave.core.ReflectedCorestarlane_space.wave.PingCore→starlane_space.wave.core.DirectedCorestarlane_space.wave.PongCore→starlane_space.wave.core.ReflectedCorestarlane_space.wave.Reflectable→starlane_space.wave.core.ReflectedCorestarlane_space.wave.ReflectedWave→starlane_space.wave.core.ReflectedCorestarlane_space.wave.Reflection→starlane_space.wave.core.ReflectedCorestarlane_space.wave.RippleCoreDef→starlane_space.wave.core.DirectedCorestarlane_space.wave.SignalCore→starlane_space.wave.core.DirectedCorestarlane_space.wave.WaveVariantDef→starlane_space.wave.core.DirectedCore
- Direction
- starlane_space.wave uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_space.wave, while a change to starlane_space.wave can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_space.wave uses a module listed above it, which is the healthy direction.
14→12 starlane_space.wave uses starlane_space.substance✕
- Connections
- 12 pairs of types, where a type in starlane_space.wave uses a type in starlane_space.substance.
- The types involved
starlane_space.wave.DirectedProto→starlane_space.substance.Substancestarlane_space.wave.DirectedWaveDef→starlane_space.substance.Substancestarlane_space.wave.EchoCore→starlane_space.substance.ToSubstancestarlane_space.wave.PingCore→starlane_space.substance.ToSubstancestarlane_space.wave.PongCore→starlane_space.substance.ToSubstancestarlane_space.wave.Reflectable→starlane_space.substance.Substancestarlane_space.wave.ReflectedProto→starlane_space.substance.Substancestarlane_space.wave.ReflectedWave→starlane_space.substance.ToSubstancestarlane_space.wave.RippleCoreDef→starlane_space.substance.ToSubstancestarlane_space.wave.SignalCore→starlane_space.substance.ToSubstancestarlane_space.wave.WaveDef→starlane_space.substance.Substancestarlane_space.wave.WaveVariantDef→starlane_space.substance.ToSubstance
- Direction
- starlane_space.wave uses starlane_space.substance, so a change to starlane_space.substance can break starlane_space.wave, while a change to starlane_space.wave can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_space.wave uses a module listed above it, which is the healthy direction.
14→16 starlane_space.wave uses starlane_space.err part of a loop✕
- Connections
- 3 pairs of types, where a type in starlane_space.wave uses a type in starlane_space.err.
- The types involved
starlane_space.wave.DirectedWaveDef→starlane_space.err.SpaceErrstarlane_space.wave.Reflectable→starlane_space.err.SpaceErrstarlane_space.wave.WaveVariantDef→starlane_space.err.SpaceErr
- Direction
- starlane_space.wave uses starlane_space.err, so a change to starlane_space.err can break starlane_space.wave, while a change to starlane_space.wave can't break starlane_space.err.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→21 starlane_space.wave uses starlane_space.loc part of a loop✕
- Connections
- 20 pairs of types, where a type in starlane_space.wave uses a type in starlane_space.loc.
- The types involved
starlane_space.wave.Agent→starlane_space.loc.ToPointstarlane_space.wave.Delivery→starlane_space.loc.Surfacestarlane_space.wave.DirectWaveStub→starlane_space.loc.Surfacestarlane_space.wave.DirectedProto→starlane_space.loc.Surfacestarlane_space.wave.DirectedWaveDef→starlane_space.loc.Surfacestarlane_space.wave.EchoCore→starlane_space.loc.Surfacestarlane_space.wave.PingCore→starlane_space.loc.Surfacestarlane_space.wave.PongCore→starlane_space.loc.Surfacestarlane_space.wave.RecipientSelector→starlane_space.loc.Surfacestarlane_space.wave.Recipients→starlane_space.loc.Surfacestarlane_space.wave.Reflectable→starlane_space.loc.Surfacestarlane_space.wave.ReflectedProto→starlane_space.loc.Surfacestarlane_space.wave.ReflectedWave→starlane_space.loc.Surfacestarlane_space.wave.Reflection→starlane_space.loc.Surfacestarlane_space.wave.Session→starlane_space.loc.Uuidstarlane_space.wave.SessionId→starlane_space.loc.Uuidstarlane_space.wave.SignalCore→starlane_space.loc.Surfacestarlane_space.wave.TransportPlanner→starlane_space.loc.Surfacestarlane_space.wave.WaveId→starlane_space.loc.Uuidstarlane_space.wave.WaveVariantDef→starlane_space.loc.Surface
- Direction
- starlane_space.wave uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.wave, while a change to starlane_space.wave can't break starlane_space.loc.
- 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→9 starlane_space.artifact.asynch uses starlane_space.util✕
- Connections
- 5 pairs of types, where a type in starlane_space.artifact.asynch uses a type in starlane_space.util.
- The types involved
starlane_space.artifact.asynch.ArtifactCache→starlane_space.util.ValuePatternstarlane_space.artifact.asynch.ArtifactFetcher→starlane_space.util.ValuePatternstarlane_space.artifact.asynch.MapFetcher→starlane_space.util.ValuePatternstarlane_space.artifact.asynch.NoDiceArtifactFetcher→starlane_space.util.ValuePatternstarlane_space.artifact.asynch.ReadArtifactFetcher→starlane_space.util.ValuePattern
- Direction
- starlane_space.artifact.asynch uses starlane_space.util, so a change to starlane_space.util can break starlane_space.artifact.asynch, while a change to starlane_space.artifact.asynch can't break starlane_space.util.
- Position
- Below the diagonal: starlane_space.artifact.asynch uses a module listed above it, which is the healthy direction.
15→14 starlane_space.artifact.asynch uses starlane_space.wave✕
- Connections
- 2 pairs of types, where a type in starlane_space.artifact.asynch uses a type in starlane_space.wave.
- The types involved
starlane_space.artifact.asynch.ArtifactCache→starlane_space.wave.WaitTimestarlane_space.artifact.asynch.ArtifactsSkel→starlane_space.wave.WaitTime
- Direction
- starlane_space.artifact.asynch uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.artifact.asynch, while a change to starlane_space.artifact.asynch can't break starlane_space.wave.
- Position
- Below the diagonal: starlane_space.artifact.asynch uses a module listed above it, which is the healthy direction.
15→16 starlane_space.artifact.asynch uses starlane_space.err part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.artifact.asynch uses a type in starlane_space.err.
- The types involved
starlane_space.artifact.asynch.ArtErr→starlane_space.err.PrintErr
- Direction
- starlane_space.artifact.asynch uses starlane_space.err, so a change to starlane_space.err can break starlane_space.artifact.asynch, while a change to starlane_space.artifact.asynch can't break starlane_space.err.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→11 starlane_space.err uses starlane_space.wave.core✕
- Connections
- 2 pairs of types, where a type in starlane_space.err uses a type in starlane_space.wave.core.
- The types involved
starlane_space.err.CoreReflector→starlane_space.wave.core.ReflectedCorestarlane_space.err.SpaceErr→starlane_space.wave.core.ReflectedCore
- Direction
- starlane_space.err uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_space.err, while a change to starlane_space.err can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_space.err uses a module listed above it, which is the healthy direction.
16→12 starlane_space.err uses starlane_space.substance✕
- Connections
- 3 pairs of types, where a type in starlane_space.err uses a type in starlane_space.substance.
- The types involved
starlane_space.err.SpaceErr→starlane_space.substance.SubstanceErrstarlane_space.err.SpaceErr→starlane_space.substance.SubstanceKindstarlane_space.err.SpatialError→starlane_space.substance.Substance
- Direction
- starlane_space.err uses starlane_space.substance, so a change to starlane_space.substance can break starlane_space.err, while a change to starlane_space.err can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_space.err uses a module listed above it, which is the healthy direction.
16→15 starlane_space.err uses starlane_space.artifact.asynch✕
- Connections
- 1 pair of types, where a type in starlane_space.err uses a type in starlane_space.artifact.asynch.
- The types involved
starlane_space.err.SpaceErr→starlane_space.artifact.asynch.ArtErr
- Direction
- starlane_space.err uses starlane_space.artifact.asynch, so a change to starlane_space.artifact.asynch can break starlane_space.err, while a change to starlane_space.err can't break starlane_space.artifact.asynch.
- Position
- Below the diagonal: starlane_space.err uses a module listed above it, which is the healthy direction.
16→18 starlane_space.err uses starlane_space.parse part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.err uses a type in starlane_space.parse.
- The types involved
starlane_space.err.ParseErrs0→starlane_space.parse.ResolverErr
- Direction
- starlane_space.err uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.err, while a change to starlane_space.err can't break starlane_space.parse.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→22 starlane_space.err uses starlane_space.command.direct.create part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.err uses a type in starlane_space.command.direct.create.
- The types involved
starlane_space.err.SpaceErr→starlane_space.command.direct.create.KindTemplate
- Direction
- starlane_space.err uses starlane_space.command.direct.create, so a change to starlane_space.command.direct.create can break starlane_space.err, while a change to starlane_space.err can't break starlane_space.command.direct.create.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→27 starlane_space.err uses starlane_space.kind part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.err uses a type in starlane_space.kind.
- The types involved
starlane_space.err.SpaceErr→starlane_space.kind.BaseKind
- Direction
- starlane_space.err uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.err, while a change to starlane_space.err can't break starlane_space.kind.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→29 starlane_space.err uses starlane_space.particle part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.err uses a type in starlane_space.particle.
- The types involved
starlane_space.err.SpaceErr→starlane_space.particle.Statusstarlane_space.err.SpaceErr→starlane_space.particle.StatusDetail
- Direction
- starlane_space.err uses starlane_space.particle, so a change to starlane_space.particle can break starlane_space.err, while a change to starlane_space.err can't break starlane_space.particle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→1 starlane_package.create uses starlane_base.backend✕
- Connections
- 3 pairs of types, where a type in starlane_package.create uses a type in starlane_base.backend.
- The types involved
starlane_package.create.PackageConfig→starlane_base.backend.Resultstarlane_package.create.PackageLayout→starlane_base.backend.Resultstarlane_package.create.create$module→starlane_base.backend.Result
- Direction
- starlane_package.create uses starlane_base.backend, so a change to starlane_base.backend can break starlane_package.create, while a change to starlane_package.create can't break starlane_base.backend.
- Position
- Below the diagonal: starlane_package.create uses a module listed above it, which is the healthy direction.
17→16 starlane_package.create uses starlane_space.err✕
- Connections
- 1 pair of types, where a type in starlane_package.create uses a type in starlane_space.err.
- The types involved
starlane_package.create.PackErr→starlane_space.err.ParseErrs0
- Direction
- starlane_package.create uses starlane_space.err, so a change to starlane_space.err can break starlane_package.create, while a change to starlane_package.create can't break starlane_space.err.
- Position
- Below the diagonal: starlane_package.create uses a module listed above it, which is the healthy direction.
18→10 starlane_space.parse uses starlane_space.parse.model✕
- Connections
- 5 pairs of types, where a type in starlane_space.parse uses a type in starlane_space.parse.model.
- The types involved
starlane_space.parse.LexRouteSelector→starlane_space.parse.model.ScopeFiltersDefstarlane_space.parse.parse$module→starlane_space.parse.model.BlockKindstarlane_space.parse.parse$module→starlane_space.parse.model.DelimitedBlockKindstarlane_space.parse.parse$module→starlane_space.parse.model.NestedBlockKindstarlane_space.parse.parse$module→starlane_space.parse.model.TerminatedBlockKind
- Direction
- starlane_space.parse uses starlane_space.parse.model, so a change to starlane_space.parse.model can break starlane_space.parse, while a change to starlane_space.parse can't break starlane_space.parse.model.
- Position
- Below the diagonal: starlane_space.parse uses a module listed above it, which is the healthy direction.
18→12 starlane_space.parse uses starlane_space.substance✕
- Connections
- 3 pairs of types, where a type in starlane_space.parse uses a type in starlane_space.substance.
- The types involved
starlane_space.parse.CompositeResolver→starlane_space.substance.Substancestarlane_space.parse.Env→starlane_space.substance.Substancestarlane_space.parse.MapResolver→starlane_space.substance.Substance
- Direction
- starlane_space.parse uses starlane_space.substance, so a change to starlane_space.substance can break starlane_space.parse, while a change to starlane_space.parse can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_space.parse uses a module listed above it, which is the healthy direction.
18→13 starlane_space.parse uses starlane_space.selector✕
- Connections
- 1 pair of types, where a type in starlane_space.parse uses a type in starlane_space.selector.
- The types involved
starlane_space.parse.SurfaceSelectorDef→starlane_space.selector.SelectorDef
- Direction
- starlane_space.parse uses starlane_space.selector, so a change to starlane_space.selector can break starlane_space.parse, while a change to starlane_space.parse can't break starlane_space.selector.
- Position
- Below the diagonal: starlane_space.parse uses a module listed above it, which is the healthy direction.
18→16 starlane_space.parse uses starlane_space.err✕
- Connections
- 1 pair of types, where a type in starlane_space.parse uses a type in starlane_space.err.
- The types involved
starlane_space.parse.parse$module→starlane_space.err.ParseErrs0
- Direction
- starlane_space.parse uses starlane_space.err, so a change to starlane_space.err can break starlane_space.parse, while a change to starlane_space.parse can't break starlane_space.err.
- Position
- Below the diagonal: starlane_space.parse uses a module listed above it, which is the healthy direction.
18→21 starlane_space.parse uses starlane_space.loc part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.parse uses a type in starlane_space.loc.
- The types involved
starlane_space.parse.SurfaceSelectorDef→starlane_space.loc.Layerstarlane_space.parse.SurfaceSelectorDef→starlane_space.loc.Topic
- Direction
- starlane_space.parse uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.parse, while a change to starlane_space.parse can't break starlane_space.loc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→27 starlane_space.parse uses starlane_space.kind part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_space.parse uses a type in starlane_space.kind.
- The types involved
starlane_space.parse.KindLex→starlane_space.kind.Specificstarlane_space.parse.parse$module→starlane_space.kind.BaseKind
- Direction
- starlane_space.parse uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.parse, while a change to starlane_space.parse can't break starlane_space.kind.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→29 starlane_space.parse uses starlane_space.particle part of a loop✕
- Connections
- 4 pairs of types, where a type in starlane_space.parse uses a type in starlane_space.particle.
- The types involved
starlane_space.parse.CamelCase→starlane_space.particle.Archetypestarlane_space.parse.Domain→starlane_space.particle.Archetypestarlane_space.parse.SkewerCase→starlane_space.particle.Archetypestarlane_space.parse.SnakeCase→starlane_space.particle.Archetype
- Direction
- starlane_space.parse uses starlane_space.particle, so a change to starlane_space.particle can break starlane_space.parse, while a change to starlane_space.parse can't break starlane_space.particle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→18 starlane_base.partial.mount uses starlane_space.parse✕
- Connections
- 1 pair of types, where a type in starlane_base.partial.mount uses a type in starlane_space.parse.
- The types involved
starlane_base.partial.mount.VolumeConfig→starlane_space.parse.VarCase
- Direction
- starlane_base.partial.mount uses starlane_space.parse, so a change to starlane_space.parse can break starlane_base.partial.mount, while a change to starlane_base.partial.mount can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_base.partial.mount uses a module listed above it, which is the healthy direction.
20→9 starlane_space.fail.resource uses starlane_space.util✕
- Connections
- 1 pair of types, where a type in starlane_space.fail.resource uses a type in starlane_space.util.
- The types involved
starlane_space.fail.resource.Select→starlane_space.util.ToResolved
- Direction
- starlane_space.fail.resource uses starlane_space.util, so a change to starlane_space.util can break starlane_space.fail.resource, while a change to starlane_space.fail.resource can't break starlane_space.util.
- Position
- Below the diagonal: starlane_space.fail.resource uses a module listed above it, which is the healthy direction.
20→11 starlane_space.fail.resource uses starlane_space.wave.core✕
- Connections
- 1 pair of types, where a type in starlane_space.fail.resource uses a type in starlane_space.wave.core.
- The types involved
starlane_space.fail.resource.Create→starlane_space.wave.core.DirectedCore
- Direction
- starlane_space.fail.resource uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_space.fail.resource, while a change to starlane_space.fail.resource can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_space.fail.resource uses a module listed above it, which is the healthy direction.
20→14 starlane_space.fail.resource uses starlane_space.wave✕
- Connections
- 1 pair of types, where a type in starlane_space.fail.resource uses a type in starlane_space.wave.
- The types involved
starlane_space.fail.resource.Create→starlane_space.wave.DirectedProto
- Direction
- starlane_space.fail.resource uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.fail.resource, while a change to starlane_space.fail.resource can't break starlane_space.wave.
- Position
- Below the diagonal: starlane_space.fail.resource uses a module listed above it, which is the healthy direction.
20→18 starlane_space.fail.resource uses starlane_space.parse✕
- Connections
- 1 pair of types, where a type in starlane_space.fail.resource uses a type in starlane_space.parse.
- The types involved
starlane_space.fail.resource.Select→starlane_space.parse.Env
- Direction
- starlane_space.fail.resource uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.fail.resource, while a change to starlane_space.fail.resource can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_space.fail.resource uses a module listed above it, which is the healthy direction.
21→9 starlane_space.loc uses starlane_space.util✕
- Connections
- 4 pairs of types, where a type in starlane_space.loc uses a type in starlane_space.util.
- The types involved
starlane_space.loc.SurfaceSelector→starlane_space.util.ValueMatcherstarlane_space.loc.SurfaceSelector→starlane_space.util.ValuePatternstarlane_space.loc.Topic→starlane_space.util.ValueMatcherstarlane_space.loc.VarVal→starlane_space.util.ToResolved
- Direction
- starlane_space.loc uses starlane_space.util, so a change to starlane_space.util can break starlane_space.loc, while a change to starlane_space.loc can't break starlane_space.util.
- Position
- Below the diagonal: starlane_space.loc uses a module listed above it, which is the healthy direction.
21→11 starlane_space.loc uses starlane_space.wave.core✕
- Connections
- 1 pair of types, where a type in starlane_space.loc uses a type in starlane_space.wave.core.
- The types involved
starlane_space.loc.Surface→starlane_space.wave.core.ReflectedCore
- Direction
- starlane_space.loc uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_space.loc, while a change to starlane_space.loc can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_space.loc uses a module listed above it, which is the healthy direction.
21→14 starlane_space.loc uses starlane_space.wave✕
- Connections
- 2 pairs of types, where a type in starlane_space.loc uses a type in starlane_space.wave.
- The types involved
starlane_space.loc.Surface→starlane_space.wave.Recipientsstarlane_space.loc.Surface→starlane_space.wave.ToRecipients
- Direction
- starlane_space.loc uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.loc, while a change to starlane_space.loc can't break starlane_space.wave.
- Position
- Below the diagonal: starlane_space.loc uses a module listed above it, which is the healthy direction.
21→18 starlane_space.loc uses starlane_space.parse✕
- Connections
- 2 pairs of types, where a type in starlane_space.loc uses a type in starlane_space.parse.
- The types involved
starlane_space.loc.VarVal→starlane_space.parse.Envstarlane_space.loc.Variable→starlane_space.parse.VarCase
- Direction
- starlane_space.loc uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.loc, while a change to starlane_space.loc can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_space.loc uses a module listed above it, which is the healthy direction.
21→27 starlane_space.loc uses starlane_space.kind part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.loc uses a type in starlane_space.kind.
- The types involved
starlane_space.loc.ToBaseKind→starlane_space.kind.BaseKind
- Direction
- starlane_space.loc uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.loc, while a change to starlane_space.loc can't break starlane_space.kind.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→29 starlane_space.loc uses starlane_space.particle part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.loc uses a type in starlane_space.particle.
- The types involved
starlane_space.loc.Version→starlane_space.particle.Archetype
- Direction
- starlane_space.loc uses starlane_space.particle, so a change to starlane_space.particle can break starlane_space.loc, while a change to starlane_space.loc can't break starlane_space.particle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→8 starlane_space.command.direct.create uses starlane_space.types1.property✕
- Connections
- 1 pair of types, where a type in starlane_space.command.direct.create uses a type in starlane_space.types1.property.
- The types involved
starlane_space.command.direct.create.CreateDef→starlane_space.types1.property.SetProperties
- Direction
- starlane_space.command.direct.create uses starlane_space.types1.property, so a change to starlane_space.types1.property can break starlane_space.command.direct.create, while a change to starlane_space.command.direct.create can't break starlane_space.types1.property.
- Position
- Below the diagonal: starlane_space.command.direct.create uses a module listed above it, which is the healthy direction.
22→18 starlane_space.command.direct.create uses starlane_space.parse✕
- Connections
- 1 pair of types, where a type in starlane_space.command.direct.create uses a type in starlane_space.parse.
- The types involved
starlane_space.command.direct.create.KindTemplate→starlane_space.parse.CamelCase
- Direction
- starlane_space.command.direct.create uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.command.direct.create, while a change to starlane_space.command.direct.create can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_space.command.direct.create uses a module listed above it, which is the healthy direction.
22→21 starlane_space.command.direct.create uses starlane_space.loc✕
- Connections
- 1 pair of types, where a type in starlane_space.command.direct.create uses a type in starlane_space.loc.
- The types involved
starlane_space.command.direct.create.PointFactoryU64→starlane_space.loc.PointFactory
- Direction
- starlane_space.command.direct.create uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.command.direct.create, while a change to starlane_space.command.direct.create can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_space.command.direct.create uses a module listed above it, which is the healthy direction.
22→27 starlane_space.command.direct.create uses starlane_space.kind part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.command.direct.create uses a type in starlane_space.kind.
- The types involved
starlane_space.command.direct.create.KindTemplate→starlane_space.kind.BaseKind
- Direction
- starlane_space.command.direct.create uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.command.direct.create, while a change to starlane_space.command.direct.create can't break starlane_space.kind.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→7 starlane_space.wave.exchange.asynch uses starlane_space.log✕
- Connections
- 1 pair of types, where a type in starlane_space.wave.exchange.asynch uses a type in starlane_space.log.
- The types involved
starlane_space.wave.exchange.asynch.Exchanger→starlane_space.log.Logger
- Direction
- starlane_space.wave.exchange.asynch uses starlane_space.log, so a change to starlane_space.log can break starlane_space.wave.exchange.asynch, while a change to starlane_space.wave.exchange.asynch can't break starlane_space.log.
- Position
- Below the diagonal: starlane_space.wave.exchange.asynch uses a module listed above it, which is the healthy direction.
23→14 starlane_space.wave.exchange.asynch uses starlane_space.wave✕
- Connections
- 2 pairs of types, where a type in starlane_space.wave.exchange.asynch uses a type in starlane_space.wave.
- The types involved
starlane_space.wave.exchange.asynch.DirectedHandlerSelector→starlane_space.wave.RecipientSelectorstarlane_space.wave.exchange.asynch.Exchanger→starlane_space.wave.ReflectedWave
- Direction
- starlane_space.wave.exchange.asynch uses starlane_space.wave, so a change to starlane_space.wave can break starlane_space.wave.exchange.asynch, while a change to starlane_space.wave.exchange.asynch can't break starlane_space.wave.
- Position
- Below the diagonal: starlane_space.wave.exchange.asynch uses a module listed above it, which is the healthy direction.
23→21 starlane_space.wave.exchange.asynch uses starlane_space.loc✕
- Connections
- 1 pair of types, where a type in starlane_space.wave.exchange.asynch uses a type in starlane_space.loc.
- The types involved
starlane_space.wave.exchange.asynch.Exchanger→starlane_space.loc.Surface
- Direction
- starlane_space.wave.exchange.asynch uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.wave.exchange.asynch, while a change to starlane_space.wave.exchange.asynch can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_space.wave.exchange.asynch uses a module listed above it, which is the healthy direction.
23→25 starlane_space.wave.exchange.asynch uses starlane_space.particle.traversal part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_space.wave.exchange.asynch uses a type in starlane_space.particle.traversal.
- The types involved
starlane_space.wave.exchange.asynch.TraversalRouter→starlane_space.particle.traversal.Traversal
- Direction
- starlane_space.wave.exchange.asynch uses starlane_space.particle.traversal, so a change to starlane_space.particle.traversal can break starlane_space.wave.exchange.asynch, while a change to starlane_space.wave.exchange.asynch can't break starlane_space.particle.traversal.
- 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.
24→6 starlane_hyperspace.hyperlane uses starlane_space.hyper✕
- Connections
- 24 pairs of types, where a type in starlane_hyperspace.hyperlane uses a type in starlane_space.hyper.
- The types involved
starlane_hyperspace.hyperlane.AnonHyperAuthenticator→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.AnonHyperAuthenticatorAssignEndPoint→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.DefaultHyperwayConfigurator→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.HopRouter→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.HyperApi→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.HyperAuthenticator→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.HyperClient→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.HyperGate→starlane_space.hyper.InterchangeKindstarlane_hyperspace.hyperlane.HyperGate→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.HyperGateSelector→starlane_space.hyper.InterchangeKindstarlane_hyperspace.hyperlane.HyperGateSelector→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.HyperwayConfigurator→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.HyperwayStub→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.InterchangeGate→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.InterchangeGate→starlane_space.hyper.InterchangeKindstarlane_hyperspace.hyperlane.InterchangeGate→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.LocalHyperwayGateJumper→starlane_space.hyper.InterchangeKindstarlane_hyperspace.hyperlane.LocalHyperwayGateUnlocker→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.MountInterchangeGate→starlane_space.hyper.Greetstarlane_hyperspace.hyperlane.MountInterchangeGate→starlane_space.hyper.InterchangeKindstarlane_hyperspace.hyperlane.MountInterchangeGate→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.TokenAuthenticator→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.TokenAuthenticatorWithRemoteWhitelist→starlane_space.hyper.Knockstarlane_hyperspace.hyperlane.TokensFromHeavenHyperAuthenticatorAssignEndPoint→starlane_space.hyper.Knock
- Direction
- starlane_hyperspace.hyperlane uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_hyperspace.hyperlane, while a change to starlane_hyperspace.hyperlane can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane uses a module listed above it, which is the healthy direction.
24→7 starlane_hyperspace.hyperlane uses starlane_space.log✕
- Connections
- 13 pairs of types, where a type in starlane_hyperspace.hyperlane uses a type in starlane_space.log.
- The types involved
starlane_hyperspace.hyperlane.AnonHyperAuthenticatorAssignEndPoint→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.Bridge→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.HyperApi→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.HyperClient→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.HyperClientRunner→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.Hyperway→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.HyperwayEndpoint→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.HyperwayInterchange→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.InterchangeGate→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.MountInterchangeGate→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.OutboundRouter→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.TokenDispensingHyperwayInterchange→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.TokensFromHeavenHyperAuthenticatorAssignEndPoint→starlane_space.log.Logger
- Direction
- starlane_hyperspace.hyperlane uses starlane_space.log, so a change to starlane_space.log can break starlane_hyperspace.hyperlane, while a change to starlane_hyperspace.hyperlane can't break starlane_space.log.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane uses a module listed above it, which is the healthy direction.
24→12 starlane_hyperspace.hyperlane uses starlane_space.substance✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.hyperlane uses a type in starlane_space.substance.
- The types involved
starlane_hyperspace.hyperlane.TokenAuthenticator→starlane_space.substance.Tokenstarlane_hyperspace.hyperlane.TokenAuthenticatorWithRemoteWhitelist→starlane_space.substance.Token
- Direction
- starlane_hyperspace.hyperlane uses starlane_space.substance, so a change to starlane_space.substance can break starlane_hyperspace.hyperlane, while a change to starlane_hyperspace.hyperlane can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane uses a module listed above it, which is the healthy direction.
24→14 starlane_hyperspace.hyperlane uses starlane_space.wave✕
- Connections
- 7 pairs of types, where a type in starlane_hyperspace.hyperlane uses a type in starlane_space.wave.
- The types involved
starlane_hyperspace.hyperlane.AgentTransform→starlane_space.wave.Agentstarlane_hyperspace.hyperlane.HyperRouter→starlane_space.wave.HyperWavestarlane_hyperspace.hyperlane.Hyperway→starlane_space.wave.Agentstarlane_hyperspace.hyperlane.HyperwayStub→starlane_space.wave.Agentstarlane_hyperspace.hyperlane.TokenAuthenticator→starlane_space.wave.Agentstarlane_hyperspace.hyperlane.TokenAuthenticatorWithRemoteWhitelist→starlane_space.wave.Agentstarlane_hyperspace.hyperlane.TokenDispensingHyperwayInterchange→starlane_space.wave.Agent
- Direction
- starlane_hyperspace.hyperlane uses starlane_space.wave, so a change to starlane_space.wave can break starlane_hyperspace.hyperlane, while a change to starlane_hyperspace.hyperlane can't break starlane_space.wave.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane uses a module listed above it, which is the healthy direction.
24→16 starlane_hyperspace.hyperlane uses starlane_space.err✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.hyperlane uses a type in starlane_space.err.
- The types involved
starlane_hyperspace.hyperlane.HyperConnectionErr→starlane_space.err.SpaceErr
- Direction
- starlane_hyperspace.hyperlane uses starlane_space.err, so a change to starlane_space.err can break starlane_hyperspace.hyperlane, while a change to starlane_hyperspace.hyperlane can't break starlane_space.err.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane uses a module listed above it, which is the healthy direction.
24→21 starlane_hyperspace.hyperlane uses starlane_space.loc✕
- Connections
- 11 pairs of types, where a type in starlane_hyperspace.hyperlane uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.hyperlane.FromTransform→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.HopTransform→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.Hyperway→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.HyperwayInterchange→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.HyperwayStub→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.LayerTransform→starlane_space.loc.Layerstarlane_hyperspace.hyperlane.LocalHyperwayGateUnlocker→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.SimpleGreeter→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.ToTransform→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.TransportTransform→starlane_space.loc.Surfacestarlane_hyperspace.hyperlane.VersionGate→starlane_space.loc.Version
- Direction
- starlane_hyperspace.hyperlane uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.hyperlane, while a change to starlane_hyperspace.hyperlane can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane uses a module listed above it, which is the healthy direction.
24→23 starlane_hyperspace.hyperlane uses starlane_space.wave.exchange.asynch✕
- Connections
- 6 pairs of types, where a type in starlane_hyperspace.hyperlane uses a type in starlane_space.wave.exchange.asynch.
- The types involved
starlane_hyperspace.hyperlane.HopRouter→starlane_space.wave.exchange.asynch.Routerstarlane_hyperspace.hyperlane.HyperApi→starlane_space.wave.exchange.asynch.Exchangerstarlane_hyperspace.hyperlane.HyperClient→starlane_space.wave.exchange.asynch.Exchangerstarlane_hyperspace.hyperlane.HyperClient→starlane_space.wave.exchange.asynch.TxRouterstarlane_hyperspace.hyperlane.HyperwayEndpoint→starlane_space.wave.exchange.asynch.TxRouterstarlane_hyperspace.hyperlane.OutboundRouter→starlane_space.wave.exchange.asynch.Router
- Direction
- starlane_hyperspace.hyperlane uses starlane_space.wave.exchange.asynch, so a change to starlane_space.wave.exchange.asynch can break starlane_hyperspace.hyperlane, while a change to starlane_hyperspace.hyperlane can't break starlane_space.wave.exchange.asynch.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane uses a module listed above it, which is the healthy direction.
25→6 starlane_space.particle.traversal uses starlane_space.hyper✕
- Connections
- 1 pair of types, where a type in starlane_space.particle.traversal uses a type in starlane_space.hyper.
- The types involved
starlane_space.particle.traversal.Traversal→starlane_space.hyper.ParticleRecord
- Direction
- starlane_space.particle.traversal uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_space.particle.traversal, while a change to starlane_space.particle.traversal can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_space.particle.traversal uses a module listed above it, which is the healthy direction.
25→7 starlane_space.particle.traversal uses starlane_space.log✕
- Connections
- 2 pairs of types, where a type in starlane_space.particle.traversal uses a type in starlane_space.log.
- The types involved
starlane_space.particle.traversal.Traversal→starlane_space.log.Loggerstarlane_space.particle.traversal.Traversal→starlane_space.log.Trackable
- Direction
- starlane_space.particle.traversal uses starlane_space.log, so a change to starlane_space.log can break starlane_space.particle.traversal, while a change to starlane_space.particle.traversal can't break starlane_space.log.
- Position
- Below the diagonal: starlane_space.particle.traversal uses a module listed above it, which is the healthy direction.
25→21 starlane_space.particle.traversal uses starlane_space.loc✕
- Connections
- 6 pairs of types, where a type in starlane_space.particle.traversal uses a type in starlane_space.loc.
- The types involved
starlane_space.particle.traversal.Traversal→starlane_space.loc.Layerstarlane_space.particle.traversal.Traversal→starlane_space.loc.Surfacestarlane_space.particle.traversal.TraversalDirection→starlane_space.loc.Layerstarlane_space.particle.traversal.TraversalInjection→starlane_space.loc.Surfacestarlane_space.particle.traversal.TraversalLayer→starlane_space.loc.Surfacestarlane_space.particle.traversal.TraversalPlan→starlane_space.loc.Layer
- Direction
- starlane_space.particle.traversal uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.particle.traversal, while a change to starlane_space.particle.traversal can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_space.particle.traversal uses a module listed above it, which is the healthy direction.
25→23 starlane_space.particle.traversal uses starlane_space.wave.exchange.asynch✕
- Connections
- 1 pair of types, where a type in starlane_space.particle.traversal uses a type in starlane_space.wave.exchange.asynch.
- The types involved
starlane_space.particle.traversal.TraversalLayer→starlane_space.wave.exchange.asynch.Exchanger
- Direction
- starlane_space.particle.traversal uses starlane_space.wave.exchange.asynch, so a change to starlane_space.wave.exchange.asynch can break starlane_space.particle.traversal, while a change to starlane_space.particle.traversal can't break starlane_space.wave.exchange.asynch.
- Position
- Below the diagonal: starlane_space.particle.traversal uses a module listed above it, which is the healthy direction.
26→6 starlane_hyperspace.hyperlane.tcp uses starlane_space.hyper✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.hyperlane.tcp uses a type in starlane_space.hyper.
- The types involved
starlane_hyperspace.hyperlane.tcp.HyperlaneTcpClient→starlane_space.hyper.Knock
- Direction
- starlane_hyperspace.hyperlane.tcp uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_hyperspace.hyperlane.tcp, while a change to starlane_hyperspace.hyperlane.tcp can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane.tcp uses a module listed above it, which is the healthy direction.
26→7 starlane_hyperspace.hyperlane.tcp uses starlane_space.log✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.hyperlane.tcp uses a type in starlane_space.log.
- The types involved
starlane_hyperspace.hyperlane.tcp.FrameMuxer→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.tcp.HyperlaneTcpClient→starlane_space.log.Loggerstarlane_hyperspace.hyperlane.tcp.HyperlaneTcpServer→starlane_space.log.Logger
- Direction
- starlane_hyperspace.hyperlane.tcp uses starlane_space.log, so a change to starlane_space.log can break starlane_hyperspace.hyperlane.tcp, while a change to starlane_hyperspace.hyperlane.tcp can't break starlane_space.log.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane.tcp uses a module listed above it, which is the healthy direction.
26→16 starlane_hyperspace.hyperlane.tcp uses starlane_space.err✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.hyperlane.tcp uses a type in starlane_space.err.
- The types involved
starlane_hyperspace.hyperlane.tcp.Error→starlane_space.err.SpaceErr
- Direction
- starlane_hyperspace.hyperlane.tcp uses starlane_space.err, so a change to starlane_space.err can break starlane_hyperspace.hyperlane.tcp, while a change to starlane_hyperspace.hyperlane.tcp can't break starlane_space.err.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane.tcp uses a module listed above it, which is the healthy direction.
26→21 starlane_hyperspace.hyperlane.tcp uses starlane_space.loc✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.hyperlane.tcp uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.hyperlane.tcp.Frame→starlane_space.loc.Versionstarlane_hyperspace.hyperlane.tcp.FrameStream→starlane_space.loc.Version
- Direction
- starlane_hyperspace.hyperlane.tcp uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.hyperlane.tcp, while a change to starlane_hyperspace.hyperlane.tcp can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane.tcp uses a module listed above it, which is the healthy direction.
26→24 starlane_hyperspace.hyperlane.tcp uses starlane_hyperspace.hyperlane✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.hyperlane.tcp uses a type in starlane_hyperspace.hyperlane.
- The types involved
starlane_hyperspace.hyperlane.tcp.FrameMuxer→starlane_hyperspace.hyperlane.HyperwayEndpointstarlane_hyperspace.hyperlane.tcp.HyperlaneTcpClient→starlane_hyperspace.hyperlane.HyperwayEndpointFactorystarlane_hyperspace.hyperlane.tcp.HyperlaneTcpServer→starlane_hyperspace.hyperlane.HyperGateSelector
- Direction
- starlane_hyperspace.hyperlane.tcp uses starlane_hyperspace.hyperlane, so a change to starlane_hyperspace.hyperlane can break starlane_hyperspace.hyperlane.tcp, while a change to starlane_hyperspace.hyperlane.tcp can't break starlane_hyperspace.hyperlane.
- Position
- Below the diagonal: starlane_hyperspace.hyperlane.tcp uses a module listed above it, which is the healthy direction.
27→18 starlane_space.kind uses starlane_space.parse✕
- Connections
- 14 pairs of types, where a type in starlane_space.kind uses a type in starlane_space.parse.
- The types involved
starlane_space.kind.ArtifactSubKind→starlane_space.parse.CamelCasestarlane_space.kind.BaseKind→starlane_space.parse.CamelCasestarlane_space.kind.BaseKind→starlane_space.parse.SkewerCasestarlane_space.kind.DatabaseSubKind→starlane_space.parse.CamelCasestarlane_space.kind.FileSubKind→starlane_space.parse.CamelCasestarlane_space.kind.KindParts→starlane_space.parse.CamelCasestarlane_space.kind.Specific→starlane_space.parse.CamelCasestarlane_space.kind.Specific→starlane_space.parse.Domainstarlane_space.kind.Specific→starlane_space.parse.SkewerCasestarlane_space.kind.StarSub→starlane_space.parse.CamelCasestarlane_space.kind.Sub→starlane_space.parse.CamelCasestarlane_space.kind.Sub→starlane_space.parse.SkewerCasestarlane_space.kind.Tks→starlane_space.parse.CamelCasestarlane_space.kind.UserBaseSubKind→starlane_space.parse.CamelCase
- Direction
- starlane_space.kind uses starlane_space.parse, so a change to starlane_space.parse can break starlane_space.kind, while a change to starlane_space.kind can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_space.kind uses a module listed above it, which is the healthy direction.
27→21 starlane_space.kind uses starlane_space.loc✕
- Connections
- 6 pairs of types, where a type in starlane_space.kind uses a type in starlane_space.loc.
- The types involved
starlane_space.kind.BaseKind→starlane_space.loc.ToBaseKindstarlane_space.kind.Kind→starlane_space.loc.ProvisionAffinitystarlane_space.kind.Kind→starlane_space.loc.ToBaseKindstarlane_space.kind.KindParts→starlane_space.loc.ToBaseKindstarlane_space.kind.Specific→starlane_space.loc.Versionstarlane_space.kind.StarStub→starlane_space.loc.StarKey
- Direction
- starlane_space.kind uses starlane_space.loc, so a change to starlane_space.loc can break starlane_space.kind, while a change to starlane_space.kind can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_space.kind uses a module listed above it, which is the healthy direction.
27→22 starlane_space.kind uses starlane_space.command.direct.create✕
- Connections
- 1 pair of types, where a type in starlane_space.kind uses a type in starlane_space.command.direct.create.
- The types involved
starlane_space.kind.Kind→starlane_space.command.direct.create.KindTemplate
- Direction
- starlane_space.kind uses starlane_space.command.direct.create, so a change to starlane_space.command.direct.create can break starlane_space.kind, while a change to starlane_space.kind can't break starlane_space.command.direct.create.
- Position
- Below the diagonal: starlane_space.kind uses a module listed above it, which is the healthy direction.
27→25 starlane_space.kind uses starlane_space.particle.traversal✕
- Connections
- 1 pair of types, where a type in starlane_space.kind uses a type in starlane_space.particle.traversal.
- The types involved
starlane_space.kind.Kind→starlane_space.particle.traversal.TraversalPlan
- Direction
- starlane_space.kind uses starlane_space.particle.traversal, so a change to starlane_space.particle.traversal can break starlane_space.kind, while a change to starlane_space.kind can't break starlane_space.particle.traversal.
- Position
- Below the diagonal: starlane_space.kind uses a module listed above it, which is the healthy direction.
28→6 starlane_hyperspace.machine uses starlane_space.hyper✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.hyper.
- The types involved
starlane_hyperspace.machine.MachineApi→starlane_space.hyper.InterchangeKindstarlane_hyperspace.machine.MachineApi→starlane_space.hyper.Knock
- Direction
- starlane_hyperspace.machine uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→7 starlane_hyperspace.machine uses starlane_space.log✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.log.
- The types involved
starlane_hyperspace.machine.Machine→starlane_space.log.Loggerstarlane_hyperspace.machine.MachineApiExtFactory→starlane_space.log.Loggerstarlane_hyperspace.machine.MachineSkel→starlane_space.log.Logger
- Direction
- starlane_hyperspace.machine uses starlane_space.log, so a change to starlane_space.log can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.log.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→9 starlane_hyperspace.machine uses starlane_space.util✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.util.
- The types involved
starlane_hyperspace.machine.ClientArtifactFetcher→starlane_space.util.ValuePattern
- Direction
- starlane_hyperspace.machine uses starlane_space.util, so a change to starlane_space.util can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.util.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→15 starlane_hyperspace.machine uses starlane_space.artifact.asynch✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.artifact.asynch.
- The types involved
starlane_hyperspace.machine.ClientArtifactFetcher→starlane_space.artifact.asynch.ArtifactFetcherstarlane_hyperspace.machine.MachineApi→starlane_space.artifact.asynch.Artifactsstarlane_hyperspace.machine.MachineSkel→starlane_space.artifact.asynch.Artifacts
- Direction
- starlane_hyperspace.machine uses starlane_space.artifact.asynch, so a change to starlane_space.artifact.asynch can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.artifact.asynch.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→16 starlane_hyperspace.machine uses starlane_space.err✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.err.
- The types involved
starlane_hyperspace.machine.MachineErr→starlane_space.err.HyperSpatialErrorstarlane_hyperspace.machine.MachineErr→starlane_space.err.SpatialError
- Direction
- starlane_hyperspace.machine uses starlane_space.err, so a change to starlane_space.err can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.err.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→21 starlane_hyperspace.machine uses starlane_space.loc✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.machine.MachineApi→starlane_space.loc.StarKeystarlane_hyperspace.machine.MachineHyperwayEndpointFactory→starlane_space.loc.StarKeystarlane_hyperspace.machine.MachineSkel→starlane_space.loc.Surface
- Direction
- starlane_hyperspace.machine uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→22 starlane_hyperspace.machine uses starlane_space.command.direct.create✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.command.direct.create.
- The types involved
starlane_hyperspace.machine.MachineApi→starlane_space.command.direct.create.KindTemplate
- Direction
- starlane_hyperspace.machine uses starlane_space.command.direct.create, so a change to starlane_space.command.direct.create can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.command.direct.create.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→24 starlane_hyperspace.machine uses starlane_hyperspace.hyperlane✕
- Connections
- 4 pairs of types, where a type in starlane_hyperspace.machine uses a type in starlane_hyperspace.hyperlane.
- The types involved
starlane_hyperspace.machine.ClientArtifactFetcher→starlane_hyperspace.hyperlane.HyperClientstarlane_hyperspace.machine.Machine→starlane_hyperspace.hyperlane.HyperGateSelectorstarlane_hyperspace.machine.MachineApiExtFactory→starlane_hyperspace.hyperlane.HyperwayEndpointFactorystarlane_hyperspace.machine.MachineHyperwayEndpointFactory→starlane_hyperspace.hyperlane.HyperwayEndpointFactory
- Direction
- starlane_hyperspace.machine uses starlane_hyperspace.hyperlane, so a change to starlane_hyperspace.hyperlane can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_hyperspace.hyperlane.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→27 starlane_hyperspace.machine uses starlane_space.kind✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.machine uses a type in starlane_space.kind.
- The types involved
starlane_hyperspace.machine.MachineApi→starlane_space.kind.Kind
- Direction
- starlane_hyperspace.machine uses starlane_space.kind, so a change to starlane_space.kind can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_space.kind.
- Position
- Below the diagonal: starlane_hyperspace.machine uses a module listed above it, which is the healthy direction.
28→31 starlane_hyperspace.machine uses starlane_hyperspace.star part of a loop✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.machine uses a type in starlane_hyperspace.star.
- The types involved
starlane_hyperspace.machine.Machine→starlane_hyperspace.star.HyperStarApistarlane_hyperspace.machine.MachineTemplate→starlane_hyperspace.star.StarTemplate
- Direction
- starlane_hyperspace.machine uses starlane_hyperspace.star, so a change to starlane_hyperspace.star can break starlane_hyperspace.machine, while a change to starlane_hyperspace.machine can't break starlane_hyperspace.star.
- 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.
29→12 starlane_space.particle uses starlane_space.substance✕
- Connections
- 2 pairs of types, where a type in starlane_space.particle uses a type in starlane_space.substance.
- The types involved
starlane_space.particle.Particle→starlane_space.substance.Substancestarlane_space.particle.Particle2→starlane_space.substance.Substance
- Direction
- starlane_space.particle uses starlane_space.substance, so a change to starlane_space.substance can break starlane_space.particle, while a change to starlane_space.particle can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_space.particle uses a module listed above it, which is the healthy direction.
29→27 starlane_space.particle uses starlane_space.kind✕
- Connections
- 4 pairs of types, where a type in starlane_space.particle uses a type in starlane_space.kind.
- The types involved
starlane_space.particle.AddressAndType→starlane_space.kind.BaseKindstarlane_space.particle.Archetype→starlane_space.kind.KindPartsstarlane_space.particle.PointKindDef→starlane_space.kind.Kindstarlane_space.particle.Stub→starlane_space.kind.Kind
- Direction
- starlane_space.particle uses starlane_space.kind, so a change to starlane_space.kind can break starlane_space.particle, while a change to starlane_space.particle can't break starlane_space.kind.
- Position
- Below the diagonal: starlane_space.particle uses a module listed above it, which is the healthy direction.
30→3 starlane_hyperspace.registry uses starlane_hyperspace.base.config✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.registry uses a type in starlane_hyperspace.base.config.
- The types involved
starlane_hyperspace.registry.RegistryConfig→starlane_hyperspace.base.config.BaseSubConfig
- Direction
- starlane_hyperspace.registry uses starlane_hyperspace.base.config, so a change to starlane_hyperspace.base.config can break starlane_hyperspace.registry, while a change to starlane_hyperspace.registry can't break starlane_hyperspace.base.config.
- Position
- Below the diagonal: starlane_hyperspace.registry uses a module listed above it, which is the healthy direction.
30→8 starlane_hyperspace.registry uses starlane_space.types1.property✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.registry uses a type in starlane_space.types1.property.
- The types involved
starlane_hyperspace.registry.Registration→starlane_space.types1.property.SetPropertiesstarlane_hyperspace.registry.RegistryApi→starlane_space.types1.property.SetPropertiesstarlane_hyperspace.registry.RegistryWrapper→starlane_space.types1.property.SetProperties
- Direction
- starlane_hyperspace.registry uses starlane_space.types1.property, so a change to starlane_space.types1.property can break starlane_hyperspace.registry, while a change to starlane_hyperspace.registry can't break starlane_space.types1.property.
- Position
- Below the diagonal: starlane_hyperspace.registry uses a module listed above it, which is the healthy direction.
30→20 starlane_hyperspace.registry uses starlane_space.fail.resource✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.registry uses a type in starlane_space.fail.resource.
- The types involved
starlane_hyperspace.registry.RegistryApi→starlane_space.fail.resource.Selectstarlane_hyperspace.registry.RegistryWrapper→starlane_space.fail.resource.Select
- Direction
- starlane_hyperspace.registry uses starlane_space.fail.resource, so a change to starlane_space.fail.resource can break starlane_hyperspace.registry, while a change to starlane_hyperspace.registry can't break starlane_space.fail.resource.
- Position
- Below the diagonal: starlane_hyperspace.registry uses a module listed above it, which is the healthy direction.
30→22 starlane_hyperspace.registry uses starlane_space.command.direct.create✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.registry uses a type in starlane_space.command.direct.create.
- The types involved
starlane_hyperspace.registry.Registration→starlane_space.command.direct.create.Strategy
- Direction
- starlane_hyperspace.registry uses starlane_space.command.direct.create, so a change to starlane_space.command.direct.create can break starlane_hyperspace.registry, while a change to starlane_hyperspace.registry can't break starlane_space.command.direct.create.
- Position
- Below the diagonal: starlane_hyperspace.registry uses a module listed above it, which is the healthy direction.
30→27 starlane_hyperspace.registry uses starlane_space.kind✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.registry uses a type in starlane_space.kind.
- The types involved
starlane_hyperspace.registry.Registration→starlane_space.kind.Kind
- Direction
- starlane_hyperspace.registry uses starlane_space.kind, so a change to starlane_space.kind can break starlane_hyperspace.registry, while a change to starlane_hyperspace.registry can't break starlane_space.kind.
- Position
- Below the diagonal: starlane_hyperspace.registry uses a module listed above it, which is the healthy direction.
30→29 starlane_hyperspace.registry uses starlane_space.particle✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.registry uses a type in starlane_space.particle.
- The types involved
starlane_hyperspace.registry.Registration→starlane_space.particle.Statusstarlane_hyperspace.registry.RegistryApi→starlane_space.particle.Statusstarlane_hyperspace.registry.RegistryWrapper→starlane_space.particle.Status
- Direction
- starlane_hyperspace.registry uses starlane_space.particle, so a change to starlane_space.particle can break starlane_hyperspace.registry, while a change to starlane_hyperspace.registry can't break starlane_space.particle.
- Position
- Below the diagonal: starlane_hyperspace.registry uses a module listed above it, which is the healthy direction.
31→6 starlane_hyperspace.star uses starlane_space.hyper✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.star uses a type in starlane_space.hyper.
- The types involved
starlane_hyperspace.star.StarMount→starlane_space.hyper.MountKind
- Direction
- starlane_hyperspace.star uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→7 starlane_hyperspace.star uses starlane_space.log✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.star uses a type in starlane_space.log.
- The types involved
starlane_hyperspace.star.HyperStarSkel→starlane_space.log.Logger
- Direction
- starlane_hyperspace.star uses starlane_space.log, so a change to starlane_space.log can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.log.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→11 starlane_hyperspace.star uses starlane_space.wave.core✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.star uses a type in starlane_space.wave.core.
- The types involved
starlane_hyperspace.star.StarErr→starlane_space.wave.core.ReflectedCore
- Direction
- starlane_hyperspace.star uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→12 starlane_hyperspace.star uses starlane_space.substance✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.star uses a type in starlane_space.substance.
- The types involved
starlane_hyperspace.star.TopicHandlerSerde→starlane_space.substance.Substance
- Direction
- starlane_hyperspace.star uses starlane_space.substance, so a change to starlane_space.substance can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→14 starlane_hyperspace.star uses starlane_space.wave✕
- Connections
- 4 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_space.wave.
- The types involved
starlane_hyperspace.star.HyperStar→starlane_space.wave.WaveVariantDefstarlane_hyperspace.star.HyperStarApi→starlane_space.wave.WaveVariantDefstarlane_hyperspace.star.star$module→starlane_space.wave.Recipientsstarlane_hyperspace.star.star$module→starlane_space.wave.WaveVariantDef
- Direction
- starlane_hyperspace.star uses starlane_space.wave, so a change to starlane_space.wave can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.wave.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→16 starlane_hyperspace.star uses starlane_space.err✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.star uses a type in starlane_space.err.
- The types involved
starlane_hyperspace.star.StarErr→starlane_space.err.CoreReflector
- Direction
- starlane_hyperspace.star uses starlane_space.err, so a change to starlane_space.err can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.err.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→20 starlane_hyperspace.star uses starlane_space.fail.resource✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.star uses a type in starlane_space.fail.resource.
- The types involved
starlane_hyperspace.star.HyperStarSkel→starlane_space.fail.resource.Create
- Direction
- starlane_hyperspace.star uses starlane_space.fail.resource, so a change to starlane_space.fail.resource can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.fail.resource.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→21 starlane_hyperspace.star uses starlane_space.loc✕
- Connections
- 11 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.star.HyperStar→starlane_space.loc.StarKeystarlane_hyperspace.star.HyperStar→starlane_space.loc.Surfacestarlane_hyperspace.star.HyperStarApi→starlane_space.loc.StarKeystarlane_hyperspace.star.HyperStarSkel→starlane_space.loc.StarKeystarlane_hyperspace.star.LayerInjectionRouter→starlane_space.loc.Surfacestarlane_hyperspace.star.LayerTraversalEngine→starlane_space.loc.Layerstarlane_hyperspace.star.LayerTraversalEngine→starlane_space.loc.Surfacestarlane_hyperspace.star.ParticleStates→starlane_space.loc.Surfacestarlane_hyperspace.star.StarCon→starlane_space.loc.StarKeystarlane_hyperspace.star.StarTemplate→starlane_space.loc.StarKeystarlane_hyperspace.star.TopicHandler→starlane_space.loc.SurfaceSelector
- Direction
- starlane_hyperspace.star uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→23 starlane_hyperspace.star uses starlane_space.wave.exchange.asynch✕
- Connections
- 5 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_space.wave.exchange.asynch.
- The types involved
starlane_hyperspace.star.HyperStarSkel→starlane_space.wave.exchange.asynch.Exchangerstarlane_hyperspace.star.HyperStarSkel→starlane_space.wave.exchange.asynch.TxRouterstarlane_hyperspace.star.LayerInjectionRouter→starlane_space.wave.exchange.asynch.Routerstarlane_hyperspace.star.TopicHandler→starlane_space.wave.exchange.asynch.DirectedHandlerstarlane_hyperspace.star.TraverseToNextRouter→starlane_space.wave.exchange.asynch.TraversalRouter
- Direction
- starlane_hyperspace.star uses starlane_space.wave.exchange.asynch, so a change to starlane_space.wave.exchange.asynch can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.wave.exchange.asynch.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→24 starlane_hyperspace.star uses starlane_hyperspace.hyperlane✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_hyperspace.hyperlane.
- The types involved
starlane_hyperspace.star.HyperStar→starlane_hyperspace.hyperlane.HyperwayEndpointstarlane_hyperspace.star.HyperStar→starlane_hyperspace.hyperlane.HyperwayInterchange
- Direction
- starlane_hyperspace.star uses starlane_hyperspace.hyperlane, so a change to starlane_hyperspace.hyperlane can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_hyperspace.hyperlane.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→25 starlane_hyperspace.star uses starlane_space.particle.traversal✕
- Connections
- 6 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_space.particle.traversal.
- The types involved
starlane_hyperspace.star.HyperStarApi→starlane_space.particle.traversal.Traversalstarlane_hyperspace.star.HyperStarApi→starlane_space.particle.traversal.TraversalInjectionstarlane_hyperspace.star.LayerInjectionRouter→starlane_space.particle.traversal.TraversalDirectionstarlane_hyperspace.star.LayerTraversalEngine→starlane_space.particle.traversal.Traversalstarlane_hyperspace.star.LayerTraversalEngine→starlane_space.particle.traversal.TraversalInjectionstarlane_hyperspace.star.TraverseToNextRouter→starlane_space.particle.traversal.Traversal
- Direction
- starlane_hyperspace.star uses starlane_space.particle.traversal, so a change to starlane_space.particle.traversal can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.particle.traversal.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→27 starlane_hyperspace.star uses starlane_space.kind✕
- Connections
- 7 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_space.kind.
- The types involved
starlane_hyperspace.star.HyperStarApi→starlane_space.kind.StarSubstarlane_hyperspace.star.HyperStarSkel→starlane_space.kind.StarStubstarlane_hyperspace.star.HyperStarSkel→starlane_space.kind.StarSubstarlane_hyperspace.star.StarCon→starlane_space.kind.StarStubstarlane_hyperspace.star.StarCon→starlane_space.kind.StarSubstarlane_hyperspace.star.StarTemplate→starlane_space.kind.StarStubstarlane_hyperspace.star.StarTemplate→starlane_space.kind.StarSub
- Direction
- starlane_hyperspace.star uses starlane_space.kind, so a change to starlane_space.kind can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.kind.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→28 starlane_hyperspace.star uses starlane_hyperspace.machine✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_hyperspace.machine.
- The types involved
starlane_hyperspace.star.HyperStarSkel→starlane_hyperspace.machine.MachineApistarlane_hyperspace.star.HyperStarSkel→starlane_hyperspace.machine.MachineSkel
- Direction
- starlane_hyperspace.star uses starlane_hyperspace.machine, so a change to starlane_hyperspace.machine can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_hyperspace.machine.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→29 starlane_hyperspace.star uses starlane_space.particle✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.star uses a type in starlane_space.particle.
- The types involved
starlane_hyperspace.star.HyperStarApi→starlane_space.particle.Status
- Direction
- starlane_hyperspace.star uses starlane_space.particle, so a change to starlane_space.particle can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_space.particle.
- Position
- Below the diagonal: starlane_hyperspace.star uses a module listed above it, which is the healthy direction.
31→34 starlane_hyperspace.star uses starlane_hyperspace.driver part of a loop✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.star uses a type in starlane_hyperspace.driver.
- The types involved
starlane_hyperspace.star.HyperStar→starlane_hyperspace.driver.DriversApistarlane_hyperspace.star.HyperStar→starlane_hyperspace.driver.DriversBuilderstarlane_hyperspace.star.HyperStarSkel→starlane_hyperspace.driver.DriversApi
- Direction
- starlane_hyperspace.star uses starlane_hyperspace.driver, so a change to starlane_hyperspace.driver can break starlane_hyperspace.star, while a change to starlane_hyperspace.star can't break starlane_hyperspace.driver.
- 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.
32→29 starlane_space.status uses starlane_space.particle✕
- Connections
- 2 pairs of types, where a type in starlane_space.status uses a type in starlane_space.particle.
- The types involved
starlane_space.status.EntityResult→starlane_space.particle.StatusDetailstarlane_space.status.StatusDetail→starlane_space.particle.Status
- Direction
- starlane_space.status uses starlane_space.particle, so a change to starlane_space.particle can break starlane_space.status, while a change to starlane_space.status can't break starlane_space.particle.
- Position
- Below the diagonal: starlane_space.status uses a module listed above it, which is the healthy direction.
33→32 starlane_hyperspace.base.provider uses starlane_space.status✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base.provider uses a type in starlane_space.status.
- The types involved
starlane_hyperspace.base.provider.Provider→starlane_space.status.StatusProbe
- Direction
- starlane_hyperspace.base.provider uses starlane_space.status, so a change to starlane_space.status can break starlane_hyperspace.base.provider, while a change to starlane_hyperspace.base.provider can't break starlane_space.status.
- Position
- Below the diagonal: starlane_hyperspace.base.provider uses a module listed above it, which is the healthy direction.
33→37 starlane_hyperspace.base.provider uses starlane_hyperspace.base part of a loop✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base.provider uses a type in starlane_hyperspace.base.
- The types involved
starlane_hyperspace.base.provider.Provider→starlane_hyperspace.base.BaseSub
- Direction
- starlane_hyperspace.base.provider uses starlane_hyperspace.base, so a change to starlane_hyperspace.base can break starlane_hyperspace.base.provider, while a change to starlane_hyperspace.base.provider can't break starlane_hyperspace.base.
- 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.
34→6 starlane_hyperspace.driver uses starlane_space.hyper✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.hyper.
- The types involved
starlane_hyperspace.driver.States→starlane_space.hyper.Assign
- Direction
- starlane_hyperspace.driver uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→7 starlane_hyperspace.driver uses starlane_space.log✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.log.
- The types involved
starlane_hyperspace.driver.DriverRunner→starlane_space.log.Loggerstarlane_hyperspace.driver.DriverSkel→starlane_space.log.Logger
- Direction
- starlane_hyperspace.driver uses starlane_space.log, so a change to starlane_space.log can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.log.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→8 starlane_hyperspace.driver uses starlane_space.types1.property✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.types1.property.
- The types involved
starlane_hyperspace.driver.DriverFactory→starlane_space.types1.property.SetPropertiesstarlane_hyperspace.driver.HyperDriverFactory→starlane_space.types1.property.SetProperties
- Direction
- starlane_hyperspace.driver uses starlane_space.types1.property, so a change to starlane_space.types1.property can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.types1.property.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→11 starlane_hyperspace.driver uses starlane_space.wave.core✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.wave.core.
- The types involved
starlane_hyperspace.driver.ParticleDriverErr→starlane_space.wave.core.ReflectedCorestarlane_hyperspace.driver.ParticleStarErr→starlane_space.wave.core.ReflectedCore
- Direction
- starlane_hyperspace.driver uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→15 starlane_hyperspace.driver uses starlane_space.artifact.asynch✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.artifact.asynch.
- The types involved
starlane_hyperspace.driver.DriverSkel→starlane_space.artifact.asynch.Artifacts
- Direction
- starlane_hyperspace.driver uses starlane_space.artifact.asynch, so a change to starlane_space.artifact.asynch can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.artifact.asynch.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→16 starlane_hyperspace.driver uses starlane_space.err✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.err.
- The types involved
starlane_hyperspace.driver.ParticleDriverErr→starlane_space.err.CoreReflectorstarlane_hyperspace.driver.ParticleErr→starlane_space.err.CoreReflectorstarlane_hyperspace.driver.ParticleStarErr→starlane_space.err.CoreReflector
- Direction
- starlane_hyperspace.driver uses starlane_space.err, so a change to starlane_space.err can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.err.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→18 starlane_hyperspace.driver uses starlane_space.parse✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.parse.
- The types involved
starlane_hyperspace.driver.DriverParticle→starlane_space.parse.Ctxstarlane_hyperspace.driver.Particle→starlane_space.parse.Ctx
- Direction
- starlane_hyperspace.driver uses starlane_space.parse, so a change to starlane_space.parse can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→21 starlane_hyperspace.driver uses starlane_space.loc✕
- Connections
- 5 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.driver.Driver→starlane_space.loc.Layerstarlane_hyperspace.driver.DriverRunner→starlane_space.loc.Layerstarlane_hyperspace.driver.DriverSkel→starlane_space.loc.Layerstarlane_hyperspace.driver.Drivers→starlane_space.loc.Surfacestarlane_hyperspace.driver.ParticleOuter→starlane_space.loc.Surface
- Direction
- starlane_hyperspace.driver uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→22 starlane_hyperspace.driver uses starlane_space.command.direct.create✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.command.direct.create.
- The types involved
starlane_hyperspace.driver.DriverSkel→starlane_space.command.direct.create.KindTemplatestarlane_hyperspace.driver.DriverSkel→starlane_space.command.direct.create.PointSegTemplate
- Direction
- starlane_hyperspace.driver uses starlane_space.command.direct.create, so a change to starlane_space.command.direct.create can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.command.direct.create.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→23 starlane_hyperspace.driver uses starlane_space.wave.exchange.asynch✕
- Connections
- 4 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.wave.exchange.asynch.
- The types involved
starlane_hyperspace.driver.DriverHandler→starlane_space.wave.exchange.asynch.DirectedHandlerstarlane_hyperspace.driver.DriverParticle→starlane_space.wave.exchange.asynch.TraversalRouterstarlane_hyperspace.driver.ParticleOuter→starlane_space.wave.exchange.asynch.Exchangerstarlane_hyperspace.driver.ParticleRouter→starlane_space.wave.exchange.asynch.TraversalRouter
- Direction
- starlane_hyperspace.driver uses starlane_space.wave.exchange.asynch, so a change to starlane_space.wave.exchange.asynch can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.wave.exchange.asynch.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→25 starlane_hyperspace.driver uses starlane_space.particle.traversal✕
- Connections
- 7 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.particle.traversal.
- The types involved
starlane_hyperspace.driver.DriverApi→starlane_space.particle.traversal.Traversalstarlane_hyperspace.driver.DriverParticle→starlane_space.particle.traversal.Traversalstarlane_hyperspace.driver.DriverRunner→starlane_space.particle.traversal.Traversalstarlane_hyperspace.driver.Drivers→starlane_space.particle.traversal.Traversalstarlane_hyperspace.driver.DriversApi→starlane_space.particle.traversal.Traversalstarlane_hyperspace.driver.ParticleOuter→starlane_space.particle.traversal.Traversalstarlane_hyperspace.driver.ParticleOuter→starlane_space.particle.traversal.TraversalLayer
- Direction
- starlane_hyperspace.driver uses starlane_space.particle.traversal, so a change to starlane_space.particle.traversal can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.particle.traversal.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→26 starlane_hyperspace.driver uses starlane_hyperspace.hyperlane.tcp✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_hyperspace.hyperlane.tcp.
- The types involved
starlane_hyperspace.driver.ParticleErr→starlane_hyperspace.hyperlane.tcp.Errorstarlane_hyperspace.driver.ParticleStarErr→starlane_hyperspace.hyperlane.tcp.Error
- Direction
- starlane_hyperspace.driver uses starlane_hyperspace.hyperlane.tcp, so a change to starlane_hyperspace.hyperlane.tcp can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_hyperspace.hyperlane.tcp.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→27 starlane_hyperspace.driver uses starlane_space.kind✕
- Connections
- 13 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_space.kind.
- The types involved
starlane_hyperspace.driver.Driver→starlane_space.kind.Kindstarlane_hyperspace.driver.DriverDriver→starlane_space.kind.Kindstarlane_hyperspace.driver.DriverDriverFactory→starlane_space.kind.Kindstarlane_hyperspace.driver.DriverErr→starlane_space.kind.Kindstarlane_hyperspace.driver.DriverFactory→starlane_space.kind.Kindstarlane_hyperspace.driver.DriverFactoryWrapper→starlane_space.kind.Kindstarlane_hyperspace.driver.DriverSkel→starlane_space.kind.Kindstarlane_hyperspace.driver.Drivers→starlane_space.kind.Kindstarlane_hyperspace.driver.DriversApi→starlane_space.kind.Kindstarlane_hyperspace.driver.DriversBuilder→starlane_space.kind.StarSubstarlane_hyperspace.driver.HyperDriverFactory→starlane_space.kind.Kindstarlane_hyperspace.driver.HyperParticleSkel→starlane_space.kind.Kindstarlane_hyperspace.driver.ParticleSkel→starlane_space.kind.Kind
- Direction
- starlane_hyperspace.driver uses starlane_space.kind, so a change to starlane_space.kind can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_space.kind.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
34→31 starlane_hyperspace.driver uses starlane_hyperspace.star✕
- Connections
- 11 pairs of types, where a type in starlane_hyperspace.driver uses a type in starlane_hyperspace.star.
- The types involved
starlane_hyperspace.driver.DriverDriverFactory→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.DriverFactoryWrapper→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.DriverRunner→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.DriverRunner→starlane_hyperspace.star.LayerInjectionRouterstarlane_hyperspace.driver.DriverSkel→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.Drivers→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.DriversBuilder→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.HyperDriverFactory→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.HyperSkel→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.ParticleOuter→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.ParticleStarErr→starlane_hyperspace.star.StarErr
- Direction
- starlane_hyperspace.driver uses starlane_hyperspace.star, so a change to starlane_hyperspace.star can break starlane_hyperspace.driver, while a change to starlane_hyperspace.driver can't break starlane_hyperspace.star.
- Position
- Below the diagonal: starlane_hyperspace.driver uses a module listed above it, which is the healthy direction.
35→7 starlane_hyperspace.layer.field uses starlane_space.log✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.log.
- The types involved
starlane_hyperspace.layer.field.Field→starlane_space.log.Loggerstarlane_hyperspace.layer.field.PipeEx→starlane_space.log.Logger
- Direction
- starlane_hyperspace.layer.field uses starlane_space.log, so a change to starlane_space.log can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.log.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→11 starlane_hyperspace.layer.field uses starlane_space.wave.core✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.wave.core.
- The types involved
starlane_hyperspace.layer.field.PipeEx→starlane_space.wave.core.Method
- Direction
- starlane_hyperspace.layer.field uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→12 starlane_hyperspace.layer.field uses starlane_space.substance✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.substance.
- The types involved
starlane_hyperspace.layer.field.PipeEx→starlane_space.substance.Substance
- Direction
- starlane_hyperspace.layer.field uses starlane_space.substance, so a change to starlane_space.substance can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.substance.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→14 starlane_hyperspace.layer.field uses starlane_space.wave✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.wave.
- The types involved
starlane_hyperspace.layer.field.PipeEx→starlane_space.wave.DirectedKindstarlane_hyperspace.layer.field.PipeEx→starlane_space.wave.DirectedProto
- Direction
- starlane_hyperspace.layer.field uses starlane_space.wave, so a change to starlane_space.wave can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.wave.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→18 starlane_hyperspace.layer.field uses starlane_space.parse✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.parse.
- The types involved
starlane_hyperspace.layer.field.Field→starlane_space.parse.Envstarlane_hyperspace.layer.field.PipeEx→starlane_space.parse.Env
- Direction
- starlane_hyperspace.layer.field uses starlane_space.parse, so a change to starlane_space.parse can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→21 starlane_hyperspace.layer.field uses starlane_space.loc✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.layer.field.Field→starlane_space.loc.Surfacestarlane_hyperspace.layer.field.PipeEx→starlane_space.loc.Surface
- Direction
- starlane_hyperspace.layer.field uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→23 starlane_hyperspace.layer.field uses starlane_space.wave.exchange.asynch✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.wave.exchange.asynch.
- The types involved
starlane_hyperspace.layer.field.Field→starlane_space.wave.exchange.asynch.Exchanger
- Direction
- starlane_hyperspace.layer.field uses starlane_space.wave.exchange.asynch, so a change to starlane_space.wave.exchange.asynch can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.wave.exchange.asynch.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→25 starlane_hyperspace.layer.field uses starlane_space.particle.traversal✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_space.particle.traversal.
- The types involved
starlane_hyperspace.layer.field.Field→starlane_space.particle.traversal.Traversalstarlane_hyperspace.layer.field.Field→starlane_space.particle.traversal.TraversalLayerstarlane_hyperspace.layer.field.PipeEx→starlane_space.particle.traversal.Traversal
- Direction
- starlane_hyperspace.layer.field uses starlane_space.particle.traversal, so a change to starlane_space.particle.traversal can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_space.particle.traversal.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
35→31 starlane_hyperspace.layer.field uses starlane_hyperspace.star✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.layer.field uses a type in starlane_hyperspace.star.
- The types involved
starlane_hyperspace.layer.field.Field→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.layer.field.PipeEx→starlane_hyperspace.star.HyperStarSkel
- Direction
- starlane_hyperspace.layer.field uses starlane_hyperspace.star, so a change to starlane_hyperspace.star can break starlane_hyperspace.layer.field, while a change to starlane_hyperspace.layer.field can't break starlane_hyperspace.star.
- Position
- Below the diagonal: starlane_hyperspace.layer.field uses a module listed above it, which is the healthy direction.
36→1 starlane_platform_for_postgres_registry.registry uses starlane_base.backend✕
- Connections
- 5 pairs of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_base.backend.
- The types involved
starlane_platform_for_postgres_registry.registry.LocalProperty→starlane_base.backend.Resultstarlane_platform_for_postgres_registry.registry.PostgresParticleRecord→starlane_base.backend.Resultstarlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_base.backend.Resultstarlane_platform_for_postgres_registry.registry.RegistryParams→starlane_base.backend.Resultstarlane_platform_for_postgres_registry.registry.WrappedIndexedAccessGrant→starlane_base.backend.Result
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_base.backend, so a change to starlane_base.backend can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_base.backend.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→6 starlane_platform_for_postgres_registry.registry uses starlane_space.hyper✕
- Connections
- 2 pairs of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_space.hyper.
- The types involved
starlane_platform_for_postgres_registry.registry.PostgresParticleRecord→starlane_space.hyper.ParticleLocationstarlane_platform_for_postgres_registry.registry.PostgresParticleRecord→starlane_space.hyper.ParticleRecord
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_space.hyper, so a change to starlane_space.hyper can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_space.hyper.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→7 starlane_platform_for_postgres_registry.registry uses starlane_space.log✕
- Connections
- 1 pair of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_space.log.
- The types involved
starlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_space.log.Logger
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_space.log, so a change to starlane_space.log can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_space.log.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→8 starlane_platform_for_postgres_registry.registry uses starlane_space.types1.property✕
- Connections
- 1 pair of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_space.types1.property.
- The types involved
starlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_space.types1.property.SetProperties
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_space.types1.property, so a change to starlane_space.types1.property can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_space.types1.property.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→18 starlane_platform_for_postgres_registry.registry uses starlane_space.parse✕
- Connections
- 2 pairs of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_space.parse.
- The types involved
starlane_platform_for_postgres_registry.registry.RegistryParams→starlane_space.parse.Domainstarlane_platform_for_postgres_registry.registry.RegistryParams→starlane_space.parse.SkewerCase
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_space.parse, so a change to starlane_space.parse can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→20 starlane_platform_for_postgres_registry.registry uses starlane_space.fail.resource✕
- Connections
- 1 pair of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_space.fail.resource.
- The types involved
starlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_space.fail.resource.Select
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_space.fail.resource, so a change to starlane_space.fail.resource can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_space.fail.resource.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→29 starlane_platform_for_postgres_registry.registry uses starlane_space.particle✕
- Connections
- 3 pairs of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_space.particle.
- The types involved
starlane_platform_for_postgres_registry.registry.LocalProperty→starlane_space.particle.Propertystarlane_platform_for_postgres_registry.registry.PostgresParticleRecord→starlane_space.particle.Detailsstarlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_space.particle.Status
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_space.particle, so a change to starlane_space.particle can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_space.particle.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→30 starlane_platform_for_postgres_registry.registry uses starlane_hyperspace.registry✕
- Connections
- 3 pairs of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_hyperspace.registry.
- The types involved
starlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_hyperspace.registry.Registrationstarlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_hyperspace.registry.RegistryApistarlane_platform_for_postgres_registry.registry.RegistryParams→starlane_hyperspace.registry.Registration
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_hyperspace.registry, so a change to starlane_hyperspace.registry can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_hyperspace.registry.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
36→32 starlane_platform_for_postgres_registry.registry uses starlane_space.status✕
- Connections
- 1 pair of types, where a type in starlane_platform_for_postgres_registry.registry uses a type in starlane_space.status.
- The types involved
starlane_platform_for_postgres_registry.registry.PostgresRegistry→starlane_space.status.Handle
- Direction
- starlane_platform_for_postgres_registry.registry uses starlane_space.status, so a change to starlane_space.status can break starlane_platform_for_postgres_registry.registry, while a change to starlane_platform_for_postgres_registry.registry can't break starlane_space.status.
- Position
- Below the diagonal: starlane_platform_for_postgres_registry.registry uses a module listed above it, which is the healthy direction.
37→3 starlane_hyperspace.base uses starlane_hyperspace.base.config✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.base uses a type in starlane_hyperspace.base.config.
- The types involved
starlane_hyperspace.base.PlatformConfig→starlane_hyperspace.base.config.BaseSubConfigstarlane_hyperspace.base.PlatformConfig→starlane_hyperspace.base.config.RegistryConfig
- Direction
- starlane_hyperspace.base uses starlane_hyperspace.base.config, so a change to starlane_hyperspace.base.config can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_hyperspace.base.config.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→7 starlane_hyperspace.base uses starlane_space.log✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_space.log.
- The types involved
starlane_hyperspace.base.Platform→starlane_space.log.Logger
- Direction
- starlane_hyperspace.base uses starlane_space.log, so a change to starlane_space.log can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.log.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→8 starlane_hyperspace.base uses starlane_space.types1.property✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_space.types1.property.
- The types involved
starlane_hyperspace.base.Platform→starlane_space.types1.property.PropertiesConfig
- Direction
- starlane_hyperspace.base uses starlane_space.types1.property, so a change to starlane_space.types1.property can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.types1.property.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→15 starlane_hyperspace.base uses starlane_space.artifact.asynch✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_space.artifact.asynch.
- The types involved
starlane_hyperspace.base.Platform→starlane_space.artifact.asynch.Artifacts
- Direction
- starlane_hyperspace.base uses starlane_space.artifact.asynch, so a change to starlane_space.artifact.asynch can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.artifact.asynch.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→21 starlane_hyperspace.base uses starlane_space.loc✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.base.Platform→starlane_space.loc.StarKey
- Direction
- starlane_hyperspace.base uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→22 starlane_hyperspace.base uses starlane_space.command.direct.create✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_space.command.direct.create.
- The types involved
starlane_hyperspace.base.Platform→starlane_space.command.direct.create.KindTemplate
- Direction
- starlane_hyperspace.base uses starlane_space.command.direct.create, so a change to starlane_space.command.direct.create can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.command.direct.create.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→24 starlane_hyperspace.base uses starlane_hyperspace.hyperlane✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_hyperspace.hyperlane.
- The types involved
starlane_hyperspace.base.Platform→starlane_hyperspace.hyperlane.HyperGateSelector
- Direction
- starlane_hyperspace.base uses starlane_hyperspace.hyperlane, so a change to starlane_hyperspace.hyperlane can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_hyperspace.hyperlane.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→27 starlane_hyperspace.base uses starlane_space.kind✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.base uses a type in starlane_space.kind.
- The types involved
starlane_hyperspace.base.Platform→starlane_space.kind.Kindstarlane_hyperspace.base.Platform→starlane_space.kind.StarSub
- Direction
- starlane_hyperspace.base uses starlane_space.kind, so a change to starlane_space.kind can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.kind.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→28 starlane_hyperspace.base uses starlane_hyperspace.machine✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_hyperspace.machine.
- The types involved
starlane_hyperspace.base.Platform→starlane_hyperspace.machine.MachineTemplate
- Direction
- starlane_hyperspace.base uses starlane_hyperspace.machine, so a change to starlane_hyperspace.machine can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_hyperspace.machine.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→29 starlane_hyperspace.base uses starlane_space.particle✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.base uses a type in starlane_space.particle.
- The types involved
starlane_hyperspace.base.Foundation→starlane_space.particle.Progressstarlane_hyperspace.base.Foundation→starlane_space.particle.StatusDetail
- Direction
- starlane_hyperspace.base uses starlane_space.particle, so a change to starlane_space.particle can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.particle.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→32 starlane_hyperspace.base uses starlane_space.status✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_space.status.
- The types involved
starlane_hyperspace.base.Foundation→starlane_space.status.StatusResult
- Direction
- starlane_hyperspace.base uses starlane_space.status, so a change to starlane_space.status can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_space.status.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→33 starlane_hyperspace.base uses starlane_hyperspace.base.provider✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_hyperspace.base.provider.
- The types involved
starlane_hyperspace.base.Foundation→starlane_hyperspace.base.provider.ProviderKind
- Direction
- starlane_hyperspace.base uses starlane_hyperspace.base.provider, so a change to starlane_hyperspace.base.provider can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_hyperspace.base.provider.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
37→34 starlane_hyperspace.base uses starlane_hyperspace.driver✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.base uses a type in starlane_hyperspace.driver.
- The types involved
starlane_hyperspace.base.Platform→starlane_hyperspace.driver.DriversBuilder
- Direction
- starlane_hyperspace.base uses starlane_hyperspace.driver, so a change to starlane_hyperspace.driver can break starlane_hyperspace.base, while a change to starlane_hyperspace.base can't break starlane_hyperspace.driver.
- Position
- Below the diagonal: starlane_hyperspace.base uses a module listed above it, which is the healthy direction.
38→11 starlane_hyperspace.driver.control uses starlane_space.wave.core✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_space.wave.core.
- The types involved
starlane_hyperspace.driver.control.ControlErr→starlane_space.wave.core.ReflectedCore
- Direction
- starlane_hyperspace.driver.control uses starlane_space.wave.core, so a change to starlane_space.wave.core can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_space.wave.core.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→16 starlane_hyperspace.driver.control uses starlane_space.err✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_space.err.
- The types involved
starlane_hyperspace.driver.control.ControlErr→starlane_space.err.CoreReflector
- Direction
- starlane_hyperspace.driver.control uses starlane_space.err, so a change to starlane_space.err can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_space.err.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→18 starlane_hyperspace.driver.control uses starlane_space.parse✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_space.parse.
- The types involved
starlane_hyperspace.driver.control.Control→starlane_space.parse.Ctx
- Direction
- starlane_hyperspace.driver.control uses starlane_space.parse, so a change to starlane_space.parse can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_space.parse.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→21 starlane_hyperspace.driver.control uses starlane_space.loc✕
- Connections
- 2 pairs of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_space.loc.
- The types involved
starlane_hyperspace.driver.control.ControlCreator→starlane_space.loc.PointFactorystarlane_hyperspace.driver.control.ControlDriver→starlane_space.loc.Layer
- Direction
- starlane_hyperspace.driver.control uses starlane_space.loc, so a change to starlane_space.loc can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_space.loc.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→23 starlane_hyperspace.driver.control uses starlane_space.wave.exchange.asynch✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_space.wave.exchange.asynch.
- The types involved
starlane_hyperspace.driver.control.Control→starlane_space.wave.exchange.asynch.TraversalRouter
- Direction
- starlane_hyperspace.driver.control uses starlane_space.wave.exchange.asynch, so a change to starlane_space.wave.exchange.asynch can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_space.wave.exchange.asynch.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→24 starlane_hyperspace.driver.control uses starlane_hyperspace.hyperlane✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_hyperspace.hyperlane.
- The types involved
starlane_hyperspace.driver.control.ControlClient→starlane_hyperspace.hyperlane.HyperClientstarlane_hyperspace.driver.control.ControlGreeter→starlane_hyperspace.hyperlane.HyperGreeterstarlane_hyperspace.driver.control.ControlGreeter→starlane_hyperspace.hyperlane.HyperwayStub
- Direction
- starlane_hyperspace.driver.control uses starlane_hyperspace.hyperlane, so a change to starlane_hyperspace.hyperlane can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_hyperspace.hyperlane.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→25 starlane_hyperspace.driver.control uses starlane_space.particle.traversal✕
- Connections
- 1 pair of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_space.particle.traversal.
- The types involved
starlane_hyperspace.driver.control.Control→starlane_space.particle.traversal.Traversal
- Direction
- starlane_hyperspace.driver.control uses starlane_space.particle.traversal, so a change to starlane_space.particle.traversal can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_space.particle.traversal.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→27 starlane_hyperspace.driver.control uses starlane_space.kind✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_space.kind.
- The types involved
starlane_hyperspace.driver.control.ControlDriver→starlane_space.kind.Kindstarlane_hyperspace.driver.control.ControlDriverFactory→starlane_space.kind.Kindstarlane_hyperspace.driver.control.ControlFactory→starlane_space.kind.Kind
- Direction
- starlane_hyperspace.driver.control uses starlane_space.kind, so a change to starlane_space.kind can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_space.kind.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→31 starlane_hyperspace.driver.control uses starlane_hyperspace.star✕
- Connections
- 3 pairs of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_hyperspace.star.
- The types involved
starlane_hyperspace.driver.control.ControlDriverFactory→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.control.ControlFactory→starlane_hyperspace.star.HyperStarSkelstarlane_hyperspace.driver.control.ControlSkel→starlane_hyperspace.star.HyperStarSkel
- Direction
- starlane_hyperspace.driver.control uses starlane_hyperspace.star, so a change to starlane_hyperspace.star can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_hyperspace.star.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
38→34 starlane_hyperspace.driver.control uses starlane_hyperspace.driver✕
- Connections
- 18 pairs of types, where a type in starlane_hyperspace.driver.control uses a type in starlane_hyperspace.driver.
- The types involved
starlane_hyperspace.driver.control.Control→starlane_hyperspace.driver.HyperSkelstarlane_hyperspace.driver.control.Control→starlane_hyperspace.driver.Particlestarlane_hyperspace.driver.control.ControlCreator→starlane_hyperspace.driver.DriverCtxstarlane_hyperspace.driver.control.ControlCreator→starlane_hyperspace.driver.HyperSkelstarlane_hyperspace.driver.control.ControlDriver→starlane_hyperspace.driver.Driverstarlane_hyperspace.driver.control.ControlDriver→starlane_hyperspace.driver.DriverCtxstarlane_hyperspace.driver.control.ControlDriver→starlane_hyperspace.driver.DriverSkelstarlane_hyperspace.driver.control.ControlDriver→starlane_hyperspace.driver.HyperSkelstarlane_hyperspace.driver.control.ControlDriverFactory→starlane_hyperspace.driver.DriverAvailstarlane_hyperspace.driver.control.ControlDriverFactory→starlane_hyperspace.driver.DriverCtxstarlane_hyperspace.driver.control.ControlDriverFactory→starlane_hyperspace.driver.DriverSkelstarlane_hyperspace.driver.control.ControlDriverFactory→starlane_hyperspace.driver.HyperDriverFactorystarlane_hyperspace.driver.control.ControlErr→starlane_hyperspace.driver.ParticleErrstarlane_hyperspace.driver.control.ControlFactory→starlane_hyperspace.driver.DriverCtxstarlane_hyperspace.driver.control.ControlFactory→starlane_hyperspace.driver.DriverSkelstarlane_hyperspace.driver.control.ControlFactory→starlane_hyperspace.driver.HyperDriverFactorystarlane_hyperspace.driver.control.ControlGreeter→starlane_hyperspace.driver.HyperSkelstarlane_hyperspace.driver.control.ControlSkel→starlane_hyperspace.driver.DriverSkel
- Direction
- starlane_hyperspace.driver.control uses starlane_hyperspace.driver, so a change to starlane_hyperspace.driver can break starlane_hyperspace.driver.control, while a change to starlane_hyperspace.driver.control can't break starlane_hyperspace.driver.
- Position
- Below the diagonal: starlane_hyperspace.driver.control uses a module listed above it, which is the healthy direction.
39→1 starlane_platform_for_postgres.database.concrete uses starlane_base.backend✕
- Connections
- 1 pair of types, where a type in starlane_platform_for_postgres.database.concrete uses a type in starlane_base.backend.
- The types involved
starlane_platform_for_postgres.database.concrete.PostgresDatabase→starlane_base.backend.Result
- Direction
- starlane_platform_for_postgres.database.concrete uses starlane_base.backend, so a change to starlane_base.backend can break starlane_platform_for_postgres.database.concrete, while a change to starlane_platform_for_postgres.database.concrete can't break starlane_base.backend.
- Position
- Below the diagonal: starlane_platform_for_postgres.database.concrete uses a module listed above it, which is the healthy direction.
39→3 starlane_platform_for_postgres.database.concrete uses starlane_hyperspace.base.config✕
- Connections
- 1 pair of types, where a type in starlane_platform_for_postgres.database.concrete uses a type in starlane_hyperspace.base.config.
- The types involved
starlane_platform_for_postgres.database.concrete.Config→starlane_hyperspace.base.config.BaseSubConfig
- Direction
- starlane_platform_for_postgres.database.concrete uses starlane_hyperspace.base.config, so a change to starlane_hyperspace.base.config can break starlane_platform_for_postgres.database.concrete, while a change to starlane_platform_for_postgres.database.concrete can't break starlane_hyperspace.base.config.
- Position
- Below the diagonal: starlane_platform_for_postgres.database.concrete uses a module listed above it, which is the healthy direction.
39→32 starlane_platform_for_postgres.database.concrete uses starlane_space.status✕
- Connections
- 7 pairs of types, where a type in starlane_platform_for_postgres.database.concrete uses a type in starlane_space.status.
- The types involved
starlane_platform_for_postgres.database.concrete.PostgresDatabase→starlane_space.status.Entitystarlane_platform_for_postgres.database.concrete.PostgresDatabase→starlane_space.status.StatusProbestarlane_platform_for_postgres.database.concrete.PostgresDatabase→starlane_space.status.StatusResultstarlane_platform_for_postgres.database.concrete.PostgresDatabaseProvider→starlane_space.status.EntityReadierstarlane_platform_for_postgres.database.concrete.PostgresDatabaseProvider→starlane_space.status.EntityResultstarlane_platform_for_postgres.database.concrete.PostgresDatabaseProvider→starlane_space.status.StatusProbestarlane_platform_for_postgres.database.concrete.PostgresDatabaseProvider→starlane_space.status.StatusResult
- Direction
- starlane_platform_for_postgres.database.concrete uses starlane_space.status, so a change to starlane_space.status can break starlane_platform_for_postgres.database.concrete, while a change to starlane_platform_for_postgres.database.concrete can't break starlane_space.status.
- Position
- Below the diagonal: starlane_platform_for_postgres.database.concrete uses a module listed above it, which is the healthy direction.
39→37 starlane_platform_for_postgres.database.concrete uses starlane_hyperspace.base✕
- Connections
- 1 pair of types, where a type in starlane_platform_for_postgres.database.concrete uses a type in starlane_hyperspace.base.
- The types involved
starlane_platform_for_postgres.database.concrete.PostgresDatabaseProvider→starlane_hyperspace.base.BaseSub
- Direction
- starlane_platform_for_postgres.database.concrete uses starlane_hyperspace.base, so a change to starlane_hyperspace.base can break starlane_platform_for_postgres.database.concrete, while a change to starlane_platform_for_postgres.database.concrete can't break starlane_hyperspace.base.
- Position
- Below the diagonal: starlane_platform_for_postgres.database.concrete uses a module listed above it, which is the healthy direction.
40→1 starlane.starlane uses starlane_base.backend✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_base.backend.
- The types involved
starlane.starlane.Starlane→starlane_base.backend.Result
- Direction
- starlane.starlane uses starlane_base.backend, so a change to starlane_base.backend can break starlane.starlane, while a change to starlane.starlane can't break starlane_base.backend.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→15 starlane.starlane uses starlane_space.artifact.asynch✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_space.artifact.asynch.
- The types involved
starlane.starlane.Starlane→starlane_space.artifact.asynch.Artifacts
- Direction
- starlane.starlane uses starlane_space.artifact.asynch, so a change to starlane_space.artifact.asynch can break starlane.starlane, while a change to starlane.starlane can't break starlane_space.artifact.asynch.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→21 starlane.starlane uses starlane_space.loc✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_space.loc.
- The types involved
starlane.starlane.Starlane→starlane_space.loc.StarKey
- Direction
- starlane.starlane uses starlane_space.loc, so a change to starlane_space.loc can break starlane.starlane, while a change to starlane.starlane can't break starlane_space.loc.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→24 starlane.starlane uses starlane_hyperspace.hyperlane✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_hyperspace.hyperlane.
- The types involved
starlane.starlane.Starlane→starlane_hyperspace.hyperlane.HyperGateSelector
- Direction
- starlane.starlane uses starlane_hyperspace.hyperlane, so a change to starlane_hyperspace.hyperlane can break starlane.starlane, while a change to starlane.starlane can't break starlane_hyperspace.hyperlane.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→27 starlane.starlane uses starlane_space.kind✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_space.kind.
- The types involved
starlane.starlane.Starlane→starlane_space.kind.StarSub
- Direction
- starlane.starlane uses starlane_space.kind, so a change to starlane_space.kind can break starlane.starlane, while a change to starlane.starlane can't break starlane_space.kind.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→28 starlane.starlane uses starlane_hyperspace.machine✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_hyperspace.machine.
- The types involved
starlane.starlane.Starlane→starlane_hyperspace.machine.MachineTemplate
- Direction
- starlane.starlane uses starlane_hyperspace.machine, so a change to starlane_hyperspace.machine can break starlane.starlane, while a change to starlane.starlane can't break starlane_hyperspace.machine.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→34 starlane.starlane uses starlane_hyperspace.driver✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_hyperspace.driver.
- The types involved
starlane.starlane.Starlane→starlane_hyperspace.driver.DriversBuilder
- Direction
- starlane.starlane uses starlane_hyperspace.driver, so a change to starlane_hyperspace.driver can break starlane.starlane, while a change to starlane.starlane can't break starlane_hyperspace.driver.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→37 starlane.starlane uses starlane_hyperspace.base✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_hyperspace.base.
- The types involved
starlane.starlane.Starlane→starlane_hyperspace.base.BaseSub
- Direction
- starlane.starlane uses starlane_hyperspace.base, so a change to starlane_hyperspace.base can break starlane.starlane, while a change to starlane.starlane can't break starlane_hyperspace.base.
- Position
- Below the diagonal: starlane.starlane uses a module listed above it, which is the healthy direction.
40→39 starlane.starlane uses starlane_platform_for_postgres.database.concrete✕
- Connections
- 1 pair of types, where a type in starlane.starlane uses a type in starlane_platform_for_postgres.database.concrete.
- The types involved
starlane.starlane.Starlane→starlane_platform_for_postgres.database.concrete.Config
- Direction
- starlane.starlane uses starlane_platform_for_postgres.database.concrete, so a change to starlane_platform_for_postgres.database.concrete can break starlane.starlane, while a change to starlane.starlane can't break starlane_platform_for_postgres.database.concrete.
- Position
- Below the diagonal: starlane.starlane 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 — Event-Driven
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 51 | High / Critical |
| A05:2025 — Injection | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off; Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +4.8 pts | Low | ADR Quality |
| Resolve the 98 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (7), lib.rs (4), err.rs (4). | +4.7 pts | Medium | Knowledge Freshness |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). | +4.3 pts | Low | Static Analysis (SAST) |
| Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off. | +6.3 pts | Medium | Web-Security Posture |
| Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable. | +5.7 pts | Medium | Access Controls |
| 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. | +3.9 pts | Medium | Architecture documentation |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 20 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (20). | +2.9 pts | Medium | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.3 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| hyperspace/src/star.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| hyperspace/src/hyperlane/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| hyperspace/src/base/provider.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| space/src/parse/mod.rs | 7.0 | Near-clean | Cyclomatic Complexity: starlane_space::parse::resolve_kind (cyclomatic 31) |
| macros/src/lib.rs | 7.0 | Near-clean | Cognitive Complexity: starlane_macros::to_substance (cognitive 27) |
| space/src/types1/property.rs | 7.0 | Near-clean | Code Duplication: Edited copy of a member (42 corresponding lines) |
| space/src/wave.rs | 7.0 | Near-clean | God Classes: FileTooLong: src/wave.rs |
| hyperspace/src/machine.rs | 7.0 | Near-clean | Cyclomatic Complexity: Machine::init (cyclomatic 19) |
| hyperspace/src/driver/mod.rs | 7.1 | Near-clean | Cyclomatic Complexity: Drivers::start (cyclomatic 19) |
| hyperspace/src/driver/star.rs | 7.2 | Near-clean | Cognitive Complexity: Star::handle_search_request (cognitive 18) |
| space/src/point.rs | 7.2 | Near-clean | God Classes: FileTooLong: src/point.rs |
| hyperspace/src/layer/field.rs | 7.2 | Near-clean | Code Duplication: Edited copy of a member (35 corresponding lines) |
| space/src/wave/exchange/asynch.rs | 7.4 | Near-clean | Cognitive Complexity: Exchanger::exchange (cognitive 33) |
| space/src/selector.rs | 7.4 | Near-clean | God Classes: FileTooLong: src/selector.rs |
| main/src/install.rs | 7.4 | Near-clean | God Classes: TooManyMethods: Console |
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 58 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 — 58 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, 582 of 632 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- 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 (.rs) and this repository declares a Cargo test suite (repository root, 46 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 1751 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- GD1 Unfinished & placeholder code — 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. 64 further occurrence(s) are not listed individually; the score already reflects all 104.
- IC1 Incompleteness & stubs — 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. 108 further occurrence(s) are not listed individually; the score already reflects all 148.
- X19 Unrestored process-global state — 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, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic was found in this repository, 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.
- X24 Document value interpolated into markup unescaped — 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, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, 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.
- X5 Nullable reference types — 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. 310 further occurrence(s) are not listed individually; the score already reflects all 350.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain 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.
- 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
12 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was starlane_space::parse::resolve_kind at 31. A further 4 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Platform::select_kind at 29 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: hyperspace/src/base.rs (Platform::select_kind at 29), space/src/substance.rs (Substance::kind at 29), space/src/kind.rs (Kind::try_from at 28). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 12 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with starlane_space::parse::resolve_kind (cyclomatic 31), LayerTraversalEngine::start_layer_traversal (cyclomatic 27), PostgresRegistry::sub_select (cyclomatic 23). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 12 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
30 function(s) exceeded the cognitive complexity threshold of 15; the worst was LayerTraversalEngine::start_layer_traversal at 59.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with LayerTraversalEngine::start_layer_traversal (cognitive 59), PostgresRegistry::access (cognitive 50), PostgresRegistry::sub_select (cognitive 40). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
24 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 17 FileTooLong finding(s) in God Classes — start with mod.rs (3), star.rs (2), wave.rs. — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with mod.rs (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with install.rs, wave.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
81 duplicated block group(s) detected. 5.8 % of the production lines (3,294 of 56,682) are in a reported copy. A further 58 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 11 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with property.rs (2), quic.rs, machine.rs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with property.rs (4), mod.rs (3), star.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (3), err.rs, point.rs. — One of this dimension's main actionable groups (7 warning-level).
D5 · Coupling
12 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 8 of the 12 (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 Unstable project starlane-platform-for-postgres-registry finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 178 classes have LCOM4 above 3.
D12 · Dependency Hygiene
36 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 514 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: main/src/main.rs (8×20=160)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
7 deducted task-comment markers across 56682 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with provider.rs (4), status.rs, star.rs. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 7 document(s) read across 13 unit(s).
What to do
- Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 12 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml (2). — One of this dimension's main actionable groups (2 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 11 high, 0 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
- No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
44 finding(s): 1 critical, 3 high, 40 medium, 0 low.
What to do
- Resolve the 20 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (20). — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 1 high, 4 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
101 of 101 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is space/src/parse/mod.rs. Counted over 101 of the 181 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 98 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (7), lib.rs (4), err.rs (4). — One of this dimension's main actionable groups (98 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), wave.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: runner.rs↔postgres.rs 79%; runner.rs↔util.rs 60%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with runner.rs (2). — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- 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).
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 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C2 · Access Controls
- Authorization rules exist but no route guard, auth middleware or handler that refuses a caller was found.
What to do
- Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
DM4 · Rich vs anemic domain model
DM5 · Encapsulated state
ED1 · Handler temporal coupling
- `env.enviro` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:18
- `env.set_enviro` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — base/src/env.rs:26, base/src/env.rs:31
- `env.set_enviro` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:27
- `env.config_exists` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::exists`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:176
- `env.config` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::exists`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:182
- `env.config` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:184
- `env.config_save_new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:205
- `env.config_save_new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:206
- `env.global_settings_exists` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::exists`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:225
- `env.load_global_settings` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:236
- `env.save_global_settings` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:261
- `env.save_global_settings` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — base/src/env.rs:262
- `HyperlaneTcpClient.create` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `File::open`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — hyperspace/src/hyperlane/tcp.rs:65
- `HyperlaneTcpServer.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `File::open`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — hyperspace/src/hyperlane/tcp.rs:404, hyperspace/src/hyperlane/tcp.rs:409
- `Session.command` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — main/src/cli.rs:198
- `Session.command` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — main/src/cli.rs:220
- `src.main` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — main/src/main.rs:184
- `src.nuke` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — main/src/main.rs:681, main/src/main.rs:695
- `Starlane.start_services` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — main/src/starlane.rs:279
- `PackageLayout.read_toml` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — package/src/create.rs:50
- `zip.unzip_from_binary_to_temp` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — package/src/zip.rs:291, package/src/zip.rs:295
- `zip.unzip_from_binary_to_temp` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `File::create`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — package/src/zip.rs:300
- `zip.unzip_from_binary_to_temp` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::set_permissions`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — package/src/zip.rs:310
What to do
- Use the awaited twin of each blocking call, or move the work off the loop with `tokio::task::spawn_blocking` — a synchronous handler cannot simply `.await` in place.
ES2 · Immutable events
GD1 · Unfinished & placeholder code
- `status_detail` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×4) — base/src/backend/relay.rs:49, base/src/safety.rs:52, base/src/skel/foundation.rs:137, …
- `status_watcher` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×4) — base/src/backend/relay.rs:53, base/src/foundation/proxy.rs:59, base/src/skel/foundation.rs:141, …
- `probe` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×5) — base/src/backend/relay.rs:57, base/src/backend/runner.rs:60, base/src/skel/foundation.rs:145, …
- `ready` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — base/src/backend/relay.rs:61, base/src/skel/foundation.rs:149, base/src/skel/foundation.rs:235
- `provider` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — base/src/backend/relay.rs:65, base/src/skel/foundation.rs:153
- `dependency` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — base/src/foundation/implementation/docker_daemon_foundation.rs:122, base/src/foundation/proxy.rs:71
- `registry` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — base/src/foundation/implementation/docker_daemon_foundation.rs:129, base/src/foundation/proxy.rs:75
- `dependency_kinds` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/foundation/implementation/docker_daemon_foundation.rs:157
- `config` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — base/src/foundation/proxy.rs:51, base/src/skel/foundation.rs:129, base/src/skel/foundation.rs:227
- `status` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — base/src/foundation/proxy.rs:55, base/src/skel/foundation.rs:133, base/src/skel/foundation.rs:201
- `synchronize` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/foundation/proxy.rs:63
- `install` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/foundation/proxy.rs:67
- `serialize_as` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/foundation/util.rs:71
- `proxy` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/safety.rs:24
- `kind` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — base/src/skel/foundation.rs:125, base/src/skel/foundation.rs:191
- `mounts` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/skel/foundation.rs:183
- `provider_kind` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/skel/foundation.rs:223
- `volumes` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/skel/foundation.rs:295
- `name` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/skel/foundation.rs:318
- `path` is a shipped function whose whole body is still `todo!()`/`unimplemented!()` — generated scaffolding that was never completed. Implement it or remove the dead surface. — base/src/skel/foundation.rs:322
What to do
- Finish or delete the functions that are still `todo!()`/`unimplemented!()` or panic "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `status_detail` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×4) — base/src/backend/relay.rs:49, base/src/safety.rs:52, base/src/skel/foundation.rs:137, …
- `status_watcher` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×4) — base/src/backend/relay.rs:53, base/src/foundation/proxy.rs:59, base/src/skel/foundation.rs:141, …
- `probe` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×5) — base/src/backend/relay.rs:57, base/src/backend/runner.rs:60, base/src/skel/foundation.rs:145, …
- `ready` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×3) — base/src/backend/relay.rs:61, base/src/skel/foundation.rs:149, base/src/skel/foundation.rs:235
- `provider` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×2) — base/src/backend/relay.rs:65, base/src/skel/foundation.rs:153
- `start` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — base/src/backend/runner.rs:141
- `synchronize` does real work, but one of its branches is `todo!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — base/src/foundation/implementation/docker_daemon_foundation.rs:115
- `install` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — base/src/foundation/implementation/docker_daemon_foundation.rs:118
- `dependency` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×2) — base/src/foundation/implementation/docker_daemon_foundation.rs:122, base/src/foundation/proxy.rs:71
- `registry` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×2) — base/src/foundation/implementation/docker_daemon_foundation.rs:129, base/src/foundation/proxy.rs:75
- `dependency_kinds` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — base/src/foundation/implementation/docker_daemon_foundation.rs:157
- `config` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×3) — base/src/foundation/proxy.rs:51, base/src/skel/foundation.rs:129, base/src/skel/foundation.rs:227
- `status` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×3) — base/src/foundation/proxy.rs:55, base/src/skel/foundation.rs:133, base/src/skel/foundation.rs:201
- `synchronize` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — base/src/foundation/proxy.rs:63
- `install` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — base/src/foundation/proxy.rs:67
- `serialize_as` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — base/src/foundation/util.rs:71
- `proxy` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — base/src/safety.rs:24
- `kind` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. (×2) — base/src/skel/foundation.rs:125, base/src/skel/foundation.rs:191
- `mounts` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — base/src/skel/foundation.rs:183
- `provider_kind` is a shipped function whose whole body is `todo!()`/`unimplemented!()` — scaffolding that was never completed, and a panic on the first call. Implement it or remove the dead surface. — base/src/skel/foundation.rs:223
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
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.
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
P10 · Library API & versioning
P2 · Observability
- Only 5/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `ext/service/starlane-cli-filestore-s3-service`, `ext/service/starlane-cli-local-filestore-service`, `package`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Cargo.toml:21
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
- Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
P7 · Outbound HTTP resilience
- `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — package/src/remote.rs:58, package/src/remote.rs:80, package/src/remote.rs:90, …
What to do
- Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- a rustls `ServerCertVerifier` that accepts every certificate (`SkipServerVerification`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the TLS stack verifies the peer — reqwest, native-tls, rustls and openssl's `SslConnector` all check the chain and hostname when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: `reqwest::ClientBuilder::add_root_certificate(Certificate::from_pem(…))`, a rustls `RootCertStore` holding its CA, or `SslConnectorBuilder::set_ca_file`, which keeps the chain and hostname checks on. — hyperspace/src/hyperlane/quic.rs:16
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — space/src/point.rs:1439
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum::serve(` (package/src/server.rs:91).
What to do
- Stop accepting every TLS certificate: delete `danger_accept_invalid_certs(true)` / `SslVerifyMode::NONE` / the rustls verifier that returns `ServerCertVerified::assertion()` unconditionally, and trust a self-signed or private server by adding its CA as a root (`add_root_certificate`, a rustls `RootCertStore`) — never by switching verification off.
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X12 · Unreachable branch
- `else if self.id < other.id` can only be reached when `self.id < other.id` on line 535 was false — but every value satisfying this condition satisfies that one, so this arm never runs. Test the narrower condition first, or make the arms mutually exclusive. — space/src/security.rs:537
- `else if self.id < other.id` can only be reached when `self.id < other.id` on line 561 was false — but every value satisfying this condition satisfies that one, so this arm never runs. Test the narrower condition first, or make the arms mutually exclusive. — space/src/security.rs:563
- `Ok(())` follows `loop { tokio::time::sleep(Duration::from_secs(60)).await; }` (line 338) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — main/src/main.rs:342
- `let attributes = call.attrs.clone();` follows `todo !();` (line 1040) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — macros/src/lib.rs:1042
- The arm `BaseKind::User` can only be tried when the arm `BaseKind::User` on line 181 did not match — but every value this arm matches, that one matches first, so it never runs (rustc: `unreachable_patterns`). Move the more specific arm above the more general one, or remove it. — hyperspace/src/properties.rs:182
- `Ok(())` follows `loop { tokio::select ! { wave = self.rx.recv() => { match wave { None => { re…` (line 298) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — hyperspace/src/hyperlane/tcp.rs:328
- The arm `_` can only be tried when the arm `e` on line 1940 did not match — but every value this arm matches, that one matches first, so it never runs (rustc: `unreachable_patterns`). Move the more specific arm above the more general one, or remove it. — hyperspace/src/driver/mod.rs:1941
- `Ok(Default::default())` follows `todo !();` (line 115) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — base/src/foundation/implementation/docker_daemon_foundation.rs:116
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X13 · Undrained process stream
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `to_bin` is public and takes a `StateSrc` as its receiver from its caller, and it calls itself at line 68 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `to_bin` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/command.rs:68
- `to_string` is public and takes a `VersionReq` as its receiver from its caller, and it calls itself at line 557 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `to_string` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/selector.rs:557
- `kind` is public and takes a `Substance` as its receiver from its caller, and it calls itself at line 278 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `kind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/substance.rs:278
- `is_match` is public and takes a `SubstancePatternDef` as its receiver from its caller, and it calls itself at line 685 with a piece of the document (and at line 1004, line 1015) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_match` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/substance.rs:685
- `to_substance` is public and takes a `ReflectedCore` as its receiver from its caller, and it calls itself at line 45 with a piece of the document (and at line 403) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `to_substance` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/wave/core.rs:45
- `to_substance_ref` is public and takes a `ReflectedCore` as its receiver from its caller, and it calls itself at line 49 with a piece of the document (and at line 407) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `to_substance_ref` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/wave/core.rs:49
- `kind` is public and takes a `DirectedCore` as its receiver from its caller, and it calls itself at line 459 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `kind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/wave/core.rs:459
- `val` is public and takes a `Env` as its receiver from its caller, and it calls itself at line 2446 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `val` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — space/src/parse/mod.rs:2446
- `is_member` is public and takes a `SliceLayout` as its receiver from its caller, and it calls itself at line 108 with a piece of the document (and at line 294) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `is_member` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — package/src/lib.rs:108
- `verify_children` is public and takes a `SliceLayout` as its receiver from its caller, and it calls itself at line 217 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `verify_children` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — package/src/lib.rs:217
- `diagnose_indent` is public and takes a `SliceLayout` as its receiver from its caller, and it calls itself at line 235 with a piece of the document (and at line 237, line 325) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `diagnose_indent` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — package/src/lib.rs:235
- `gather_slice_paths` is public and takes a `SliceLayout` as its receiver from its caller, and it calls itself at line 244 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `gather_slice_paths` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — package/src/lib.rs:244
- `display` is public and takes a `Value` as its receiver from its caller, and it calls itself at line 152 with a piece of the document (and at line 162, line 163) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `display` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — base/src/foundation/util.rs:152
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
- `server` (line 303) is a `HyperlaneTcpServer` this function owns and never releases: no `run()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `HyperlaneTcpServer` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends. — main/src/starlane.rs:303
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X25 · Inert configuration knob
- `StarlaneConfig.context` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — base/src/foundation/mod.rs:77
- `StarlaneConfig.control_port` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — base/src/foundation/mod.rs:81
- `Registry.seed` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — base/src/foundation/util.rs:322
- `Cli.logs` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — main/src/cli.rs:31
- `PostgresClusterConfig.database_dir` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — platform/registry/postgres/src/postgres_embedded_deprecated.rs:161
- `PostgresClusterConfig.timeout` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — platform/registry/postgres/src/postgres_embedded_deprecated.rs:163
- `PortalConfig.max_payload_size` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/config.rs:40
- `PortalConfig.init_timeout` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/config.rs:41
- `PortalConfig.frame_timeout` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/config.rs:42
- `PortalConfig.response_timeout` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/config.rs:43
- `Report.note` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/err.rs:866
- `Report.help` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/err.rs:867
- `LogMark.file` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/log.rs:1267
- `LogMark.object` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/log.rs:1272
- `LogMark.function` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/log.rs:1274
- `Handling.priority` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/wave.rs:3176
- `Handling.retries` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/wave.rs:3177
- `DirectedCore.headers` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/wave/core.rs:392
- `ExtDirected.headers` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — space/src/wave/core/ext.rs:93
What to do
- Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- `shadow_rs::ShadowBuilder::builder().build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/build.rs:2
- `self.point.clone().to_bundle()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `bundle` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/artifact.rs:57
- `substance.to_bin()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_bin` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/command.rs:68
- `ExtMethod::new("Command")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `into` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/command.rs:525
- `StatusCode::from_u16(500)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `into` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — space/src/err.rs:229, space/src/err.rs:234
- `StatusCode::from_u16(self.status())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `as_reflected_core` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/err.rs:254
- `Self::result_utf8(Err(err))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `from` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/err.rs:694
- `proto.build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `into` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/hyper.rs:473
- `(match self{BaseKind::Star=>PointHierarchy::from_str("GLOBAL::repo<Repo>:builtin<BundleSeries>:1.0.0<Bundle>:/<FileStore>star.bind<File<File>>"),BaseKind::Driver=>PointHierarchy::from_str("GLOBAL::repo<Repo>:builtin<BundleSeries>:1.0.0<Bundle>:/<FileStore>driver.bind<File<File>>"),BaseKind::Global=>PointHierarchy::from_str("GLOBAL::repo<Repo>:builtin<BundleSeries>:1.0.0<Bundle>:/<FileStore>global.bind<File<File>>"),_=>Ok(Self::nothing_bind_point_hierarchy())}).map_err(|errs|{errs.print();errs})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `bind_point_hierarchy` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/kind.rs:157
- `PointHierarchy::from_str("GLOBAL::repo<Repo>:builtin<BundleSeries>:1.0.0<Bundle>:/<FileStore>nothing.bind<File<File>>")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `nothing_bind_point_hierarchy` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/kind.rs:169
- `SkewerCase::from_str(self.to_string().to_case(Case::Kebab).as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_skewer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — space/src/kind.rs:175, space/src/kind.rs:245
- `CamelCase::from_str(d.to_string().as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_camel_case` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/kind.rs:226
- `CamelCase::from_str(x.to_string().as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_camel_case` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×4) — space/src/kind.rs:227, space/src/kind.rs:228, space/src/kind.rs:229, …
- `CamelCase::from_str(self.to_string().as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_camel_case` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/kind.rs:560
- `CamelCase::from_str(self.to_string().as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `into` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×5) — space/src/kind.rs:593, space/src/kind.rs:640, space/src/kind.rs:675, …
- `SpecificSelector::from_str(self.to_string().as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_selector` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/kind.rs:837
- `var` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_resolved` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/loc.rs:273
- `val` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_resolved` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/loc.rs:282
- `Point::from_str(format!("<<{}>>::star",self.to_string()).as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_point` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/loc.rs:610
- `self.loggers.last()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `get` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/log.rs:67
- `message` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `commit` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/log.rs:441
- `builder.build()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `raw` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/log.rs:512
- `self.transmitter.signal(directed)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `span_event` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/log.rs:685
- `self.transmitter.signal(directed)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `pointless` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/log.rs:693
- `self.0.try_send(log)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `log` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/log.rs:1178
- `Self::from_str(skewer.as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `from` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/point.rs:70
- `result(all_consuming(point_selector)(new_span(string.as_str())))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `into` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/point.rs:711
- `env.point_or()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `to_resolved` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/point.rs:924
- `point.segments.get(i).as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `is_parent_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — space/src/point.rs:1072
- `self.segments.get(i)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `relative_segs` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — space/src/point.rs:1112, space/src/point.rs:1123
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70.2 | Adequate — gated by IC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95.3 | Exemplary | Solid. |
| Maturity | 43.4 | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43.6 | Adequate — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 34.1 | Weak — gated by D29, D36, C2, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100.0 | Exemplary | Strongest area. |
| Event-Driven | 73.9 | Strong | Solid. |
| Event Sourcing | 100.0 | Exemplary | Solid. |
| Performance | 100.0 | Exemplary | Solid. |
Unscored — 2 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.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — REDACTED:8 -------------------- 6 | RUN mkdir /rust 7 | 8 | >>> COPY rust /rust 9 | 10 | WORKDIR /rust -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 155cbfcd-7bbf-4d48-b41b-253b82876693::k3k8hqzgyqz1a3iyordp3jxit: "/rust": not found; likely cause (the repository): a file the REDACTED copies (`rust`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore); runtime evidence skipped The cause is in the repository, not in our sandbox: a file the REDACTED copies (`rust`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore). Nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~14 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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 — Rust suite
- DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
- M4 Documentation accuracy — Not applicable: the 7 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); 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'.
- P8 Schema migrations — sqlx is declared, but this repository defines no table or model of its own, so there is no database schema here for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 44 finding(s)
- Blocking call on the event loop: env.enviro calls `std::fs::read_to_string` base/src/env.rs:18
- Blocking call on the event loop: env.set_enviro calls `std::fs::create_dir_all` base/src/env.rs:26
- Blocking call on the event loop: env.set_enviro calls `std::fs::write` base/src/env.rs:27
- Blocking call on the event loop: env.set_enviro calls `std::fs::create_dir_all` base/src/env.rs:31
- Blocking call on the event loop: env.config_exists calls `std::fs::exists` base/src/env.rs:176
- Blocking call on the event loop: env.config calls `std::fs::exists` base/src/env.rs:182
- Blocking call on the event loop: env.config calls `std::fs::read_to_string` base/src/env.rs:184
- Blocking call on the event loop: env.config_save_new calls `std::fs::create_dir_all` base/src/env.rs:205
- Blocking call on the event loop: env.config_save_new calls `std::fs::write` base/src/env.rs:206
- Blocking call on the event loop: env.global_settings_exists calls `std::fs::exists` base/src/env.rs:225
- Blocking call on the event loop: env.load_global_settings calls `std::fs::read_to_string` base/src/env.rs:236
- Blocking call on the event loop: env.save_global_settings calls `std::fs::create_dir_all` base/src/env.rs:261
- Blocking call on the event loop: env.save_global_settings calls `std::fs::write` base/src/env.rs:262
- Blocking call on the event loop: HyperlaneTcpClient.create calls `File::open` hyperspace/src/hyperlane/tcp.rs:65
- Blocking call on the event loop: HyperlaneTcpServer.new calls `File::open` hyperspace/src/hyperlane/tcp.rs:404
- Blocking call on the event loop: HyperlaneTcpServer.new calls `File::open` hyperspace/src/hyperlane/tcp.rs:409
- Blocking call on the event loop: Session.command calls `std::fs::metadata` main/src/cli.rs:198
- Blocking call on the event loop: Session.command calls `std::fs::read` main/src/cli.rs:220
- Blocking call on the event loop: src.main calls `std::fs::read_dir` main/src/main.rs:184
- Blocking call on the event loop: src.nuke calls `std::fs::remove_dir_all` main/src/main.rs:681
- Blocking call on the event loop: src.nuke calls `std::fs::remove_dir_all` main/src/main.rs:695
- Blocking call on the event loop: Starlane.start_services calls `std::fs::create_dir_all` main/src/starlane.rs:279
- Blocking call on the event loop: PackageLayout.read_toml calls `std::fs::read_to_string` package/src/create.rs:50
- Blocking call on the event loop: zip.unzip_from_binary_to_temp calls `std::fs::create_dir_all` package/src/zip.rs:291
- Blocking call on the event loop: zip.unzip_from_binary_to_temp calls `std::fs::create_dir_all` package/src/zip.rs:295
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled hyperspace/src/hyperlane/quic.rs:16
Serious — 430 finding(s)
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:49
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:53
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:57
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:61
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:65
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/runner.rs:60
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/implementation/docker_daemon_foundation.rs:122
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/implementation/docker_daemon_foundation.rs:129
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/implementation/docker_daemon_foundation.rs:157
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:51
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:55
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:59
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:63
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:67
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:71
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:75
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/util.rs:71
- Unfinished stub — body is todo!() / unimplemented!() base/src/safety.rs:24
- Unfinished stub — body is todo!() / unimplemented!() base/src/safety.rs:52
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:125
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:129
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:133
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:137
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:141
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:145
- Symbol treated as nullable, then dereferenced unguarded space/build.rs:2
- Symbol treated as nullable, then dereferenced unguarded space/src/artifact.rs:57
- Symbol treated as nullable, then dereferenced unguarded space/src/command.rs:68
- Symbol treated as nullable, then dereferenced unguarded space/src/command.rs:525
- Symbol treated as nullable, then dereferenced unguarded space/src/err.rs:229
- Symbol treated as nullable, then dereferenced unguarded space/src/err.rs:234
- Symbol treated as nullable, then dereferenced unguarded space/src/err.rs:254
- Symbol treated as nullable, then dereferenced unguarded space/src/err.rs:694
- Symbol treated as nullable, then dereferenced unguarded space/src/hyper.rs:473
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:157
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:169
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:175
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:226
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:227
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:228
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:229
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:230
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:245
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:560
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:593
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:640
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:675
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:713
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:745
- Symbol treated as nullable, then dereferenced unguarded space/src/kind.rs:837
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:49
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:53
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:57
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:61
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/relay.rs:65
- Unfinished stub — body is todo!() / unimplemented!() base/src/backend/runner.rs:60
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/implementation/docker_daemon_foundation.rs:122
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/implementation/docker_daemon_foundation.rs:129
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/implementation/docker_daemon_foundation.rs:157
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:51
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:55
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:59
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:63
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:67
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:71
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/proxy.rs:75
- Unfinished stub — body is todo!() / unimplemented!() base/src/foundation/util.rs:71
- Unfinished stub — body is todo!() / unimplemented!() base/src/safety.rs:24
- Unfinished stub — body is todo!() / unimplemented!() base/src/safety.rs:52
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:125
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:129
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:133
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:137
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:141
- Unfinished stub — body is todo!() / unimplemented!() base/src/skel/foundation.rs:145
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Configuration option is read nowhere base/src/foundation/mod.rs:77
- Configuration option is read nowhere base/src/foundation/mod.rs:81
- Configuration option is read nowhere base/src/foundation/util.rs:322
- Configuration option is read nowhere main/src/cli.rs:31
- Configuration option is read nowhere platform/registry/postgres/src/postgres_embedded_deprecated.rs:161
- Configuration option is read nowhere platform/registry/postgres/src/postgres_embedded_deprecated.rs:163
- Configuration option is read nowhere space/src/config.rs:40
- Configuration option is read nowhere space/src/config.rs:41
- Configuration option is read nowhere space/src/config.rs:42
- Configuration option is read nowhere space/src/config.rs:43
- Configuration option is read nowhere space/src/err.rs:866
- Configuration option is read nowhere space/src/err.rs:867
- Configuration option is read nowhere space/src/log.rs:1267
- Configuration option is read nowhere space/src/log.rs:1272
- Configuration option is read nowhere space/src/log.rs:1274
- Configuration option is read nowhere space/src/wave.rs:3176
- Configuration option is read nowhere space/src/wave.rs:3177
- Configuration option is read nowhere space/src/wave/core.rs:392
- Configuration option is read nowhere space/src/wave/core/ext.rs:93
- FileTooLong: parse/mod.rs space/src/parse/mod.rs
- FileTooLong: src/wave.rs space/src/wave.rs
- FileTooLong: hyperlane/mod.rs hyperspace/src/hyperlane/mod.rs
- FileTooLong: driver/mod.rs hyperspace/src/driver/mod.rs
- FileTooLong: src/star.rs hyperspace/src/star.rs
- FileTooLong: src/point.rs space/src/point.rs
- FileTooLong: REDACTED REDACTED
- FileTooLong: src/selector.rs space/src/selector.rs
- FileTooLong: src/log.rs space/src/log.rs
- FileTooLong: src/command.rs space/src/command.rs
- FileTooLong: parse/util.rs space/src/parse/util.rs
- FileTooLong: src/substance.rs space/src/substance.rs
- FileTooLong: src/err.rs space/src/err.rs
- FileTooLong: src/machine.rs hyperspace/src/machine.rs
- FileTooLong: src/lib.rs macros/src/lib.rs
- FileTooLong: src/kind.rs space/src/kind.rs
- FileTooLong: driver/star.rs hyperspace/src/driver/star.rs
- Recursive walk over a caller-supplied document has no depth cap space/src/command.rs:68
- Recursive walk over a caller-supplied document has no depth cap space/src/selector.rs:557
- Recursive walk over a caller-supplied document has no depth cap space/src/substance.rs:278
- Recursive walk over a caller-supplied document has no depth cap space/src/substance.rs:685
- Recursive walk over a caller-supplied document has no depth cap space/src/wave/core.rs:45
- Recursive walk over a caller-supplied document has no depth cap space/src/wave/core.rs:49
- Recursive walk over a caller-supplied document has no depth cap space/src/wave/core.rs:459
- Recursive walk over a caller-supplied document has no depth cap space/src/parse/mod.rs:2446
- Recursive walk over a caller-supplied document has no depth cap package/src/lib.rs:108
- Recursive walk over a caller-supplied document has no depth cap package/src/lib.rs:217
- Recursive walk over a caller-supplied document has no depth cap package/src/lib.rs:235
- Recursive walk over a caller-supplied document has no depth cap package/src/lib.rs:244
- Recursive walk over a caller-supplied document has no depth cap base/src/foundation/util.rs:152
- Duplicated block (9 lines × 2) hyperspace/src/hyperlane/quic.rs:73
- Duplicated block (9 lines × 2) hyperspace/src/machine.rs:305
- Duplicated block (9 lines × 2) main/src/install.rs:423
- Duplicated block (9 lines × 2) package/src/zip.rs:25
- Duplicated block (9 lines × 2) space/src/kind.rs:251
- Duplicated block (9 lines × 2) space/src/parse/mod.rs:6144
- Duplicated block (9 lines × 2) space/src/wave/exchange.rs:146
- Duplicated block (9 lines × 2) space/src/types1/property.rs:161
- Duplicated block (9 lines × 2) space/src/types1/property.rs:171
- Duplicated block (9 lines × 2) space/src/loc.rs:183
- Duplicated block (9 lines × 2) space/src/wave/exchange/asynch.rs:356
- Duplicated block (7 lines × 2) hyperspace/src/driver/star.rs:270
- Duplicated block (7 lines × 2) hyperspace/src/hyperlane/mod.rs:1517
- Duplicated block (7 lines × 2) space/src/parse/mod.rs:6680
- Duplicated block (7 lines × 2) space/src/types1/property.rs:197
- Duplicated block (7 lines × 2) space/src/types1/property.rs:79
- Duplicated block (7 lines × 2) space/src/types1/property.rs:92
- Duplicated block (7 lines × 2) space/src/types1/property.rs:115
- Duplicated block (7 lines × 2) space/src/wave/core/ext.rs:126
- Duplicated block (7 lines × 2) space/src/parse/mod.rs:2127
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment space/src/status.rs:603
- TodoComment hyperspace/src/star.rs:1851
- TodoComment hyperspace/src/hyperlane/mod.rs:2339
- TodoComment hyperspace/src/base/provider.rs:158
- TodoComment hyperspace/src/base/provider.rs:162
- TodoComment hyperspace/src/base/provider.rs:166
- TodoComment hyperspace/src/base/provider.rs:170
- Duplicated block (10 lines × 2) space/src/err.rs:752
- Duplicated block (10 lines × 2) space/src/parse/mod.rs:6084
- Duplicated block (10 lines × 2) space/src/parse/mod.rs:6122
- Duplicated block (10 lines × 2) space/src/parse/mod.rs:6133
- Duplicated block (10 lines × 2) space/src/point.rs:359
- Duplicated block (10 lines × 2) space/src/wave.rs:1211
- Duplicated block (10 lines × 2) space/src/types1/property.rs:423
- Duplicated block (8 lines × 2) space/src/parse/mod.rs:133
- Duplicated block (8 lines × 2) space/src/parse/mod.rs:3297
- Duplicated block (8 lines × 2) space/src/parse/mod.rs:4143
- Duplicated block (8 lines × 2) space/src/wave/exchange/asynch.rs:413
- Duplicated block (8 lines × 2) ext/service/starlane-cli-filestore-s3-service/src/main.rs:97
- Duplicated block (8 lines × 2) space/src/wave/core/ext.rs:134
- Duplicated block (8 lines × 2) hyperspace/src/hyperlane/mod.rs:204
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) hyperspace/src/hyperlane/quic.rs:226
- Duplicated block (6 lines × 2) space/src/parse/mod.rs:5911
- Duplicated block (6 lines × 2) space/src/selector.rs:179
- Duplicated block (6 lines × 2) space/src/types1/property.rs:382
- Duplicated block (6 lines × 2) space/src/types1/property.rs:389
- Duplicated block (6 lines × 2) hyperspace/src/star.rs:800
- Duplicated block (11 lines × 2) hyperspace/src/base.rs:171
- Duplicated block (11 lines × 2) hyperspace/src/hyperlane/mod.rs:2163
- Duplicated block (11 lines × 2) space/src/parse/mod.rs:6110
- Duplicated block (11 lines × 2) hyperspace/src/layer/field.rs:333
- Duplicated block (11 lines × 2) hyperspace/src/properties.rs:80
- starlane_macros::to_substance (cognitive 27) macros/src/lib.rs:581
- starlane_macros::autobox (cognitive 26) macros/src/lib.rs:492
- starlane_macros::_handler (cognitive 18) macros/src/lib.rs:72
- starlane_macros::rtn_type (cognitive 18) macros/src/lib.rs:339
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (12 corresponding lines) main/src/install.rs:420
- Edited copy of a member (12 corresponding lines) space/src/parse/mod.rs:1235
- Edited copy of a member (12 corresponding lines) space/src/wave/core/ext.rs:147
- Edited copy of a member (12 corresponding lines) space/src/types1/property.rs:357
- Edited copy of a member (5 corresponding lines) hyperspace/src/machine.rs:129
- Edited copy of a member (5 corresponding lines) space/src/wave.rs:1521
- Edited copy of a member (5 corresponding lines) space/src/wave.rs:1527
- Edited copy of a member (5 corresponding lines) space/src/wave.rs:1533
- Outbound HTTP without resilience package/src/remote.rs:58
- Outbound HTTP without resilience package/src/remote.rs:80
- Outbound HTTP without resilience package/src/remote.rs:90
- Outbound HTTP without resilience package/src/remote.rs:110
- Statement is unreachable — control never gets past the statement before it main/src/main.rs:342
- Statement is unreachable — control never gets past the statement before it macros/src/lib.rs:1042
- Statement is unreachable — control never gets past the statement before it hyperspace/src/hyperlane/tcp.rs:328
- Statement is unreachable — control never gets past the statement before it base/src/foundation/implementation/docker_daemon_foundation.rs:116
- HyperStar::new (cognitive 28) hyperspace/src/star.rs:625
- HyperStar::shard::shard (cognitive 23) hyperspace/src/star.rs:1036
- HyperStar::start (cognitive 17) hyperspace/src/star.rs:845
- MethodTooLong: HyperClient.new_with_exchanger hyperspace/src/hyperlane/mod.rs:1295
- MethodTooLong: Drivers.create hyperspace/src/driver/mod.rs:608
- MethodTooLong: PostgresRegistry.sub_select REDACTED:529
- Edited copy of a member (18 corresponding lines) space/src/parse/mod.rs:3095
- Edited copy of a member (18 corresponding lines) space/src/command.rs:373
- Edited copy of a member (18 corresponding lines) space/src/parse/mod.rs:369
- Edited copy of a member (13 corresponding lines) space/src/parse/mod.rs:6677
- Edited copy of a member (13 corresponding lines) space/src/point.rs:358
- Edited copy of a member (13 corresponding lines) space/src/parse/mod.rs:623
- Edited copy of a member (11 corresponding lines) hyperspace/src/hyperlane/mod.rs:1513
- Edited copy of a member (11 corresponding lines) space/src/particle/traversal.rs:374
- Edited copy of a member (11 corresponding lines) space/src/types2/specific.rs:415
- Edited copy of a member (14 corresponding lines) space/src/parse/mod.rs:5832
- Edited copy of a member (14 corresponding lines) space/src/parse/mod.rs:2126
- Edited copy of a member (14 corresponding lines) space/src/wave.rs:2724
- Edited copy of a member (16 corresponding lines) space/src/loc.rs:415
- Edited copy of a member (16 corresponding lines) space/src/hyper.rs:103
- Edited copy of a member (16 corresponding lines) space/src/types1/property.rs:33
- Edited copy of a member (9 corresponding lines) space/src/types2/class.rs:158
- Edited copy of a member (9 corresponding lines) space/src/kind2.rs:437
- Edited copy of a member (9 corresponding lines) space/src/parse/mod.rs:4142
- Duplicated block (17 lines × 2) space/src/parse/mod.rs:6332
- Duplicated block (17 lines × 2) space/src/types1/property.rs:259
- Duplicated block (17 lines × 2) space/src/wave/exchange.rs:361
- Duplicated block (13 lines × 2) space/src/parse/mod.rs:1412
- Duplicated block (13 lines × 2) space/src/parse/mod.rs:2850
- Duplicated block (13 lines × 2) space/src/parse/mod.rs:7376
- Duplicated block (10 lines × 3) space/src/parse/mod.rs:6312
- Duplicated block (10 lines × 3) space/src/types2/mod.rs:244
- Duplicated block (10 lines × 3) space/src/wave.rs:1306
- PostgresRegistry::sub_select (cyclomatic 23) REDACTED:529
- PostgresRegistry::access (cyclomatic 22) REDACTED:728
- Drivers::start (cyclomatic 19) hyperspace/src/driver/mod.rs:372
- Drivers::status_listen (cyclomatic 16) hyperspace/src/driver/mod.rs:529
- Machine::init (cyclomatic 19) hyperspace/src/machine.rs:218
- Machine::start (cyclomatic 18) hyperspace/src/machine.rs:454
- HyperStar::start (cyclomatic 19) hyperspace/src/star.rs:845
- HyperStar::new (cyclomatic 18) hyperspace/src/star.rs:625
- PostgresRegistry::access (cognitive 50) REDACTED:728
- PostgresRegistry::sub_select (cognitive 40) REDACTED:529
- Machine::init (cognitive 18) hyperspace/src/machine.rs:218
- Machine::start (cognitive 17) hyperspace/src/machine.rs:454
- TooManyMethods: Console main/src/install.rs:357
- TooManyMethods: DirectedProto space/src/wave.rs:1239
- Change coupling: runner.rs ↔ postgres.rs base/src/backend/runner.rs:1
- Change coupling: runner.rs ↔ util.rs base/src/backend/runner.rs:1
- REDACTED
- REDACTED
- Edited copy of a member (43 corresponding lines) macros/src/proxy.rs:435
- Edited copy of a member (43 corresponding lines) hyperspace/src/host/wasm/mod.rs:85
- Edited copy of a member (25 corresponding lines) space/src/point.rs:479
- Edited copy of a member (25 corresponding lines) space/src/parse/mod.rs:5859
- Edited copy of a member (15 corresponding lines) space/src/parse/mod.rs:2848
- Edited copy of a member (15 corresponding lines) space/src/parse/mod.rs:2244
- Edited copies of one member (3 members, 17+ corresponding lines) space/src/parse/mod.rs:3285
- Edited copies of one member (3 members, 17+ corresponding lines) space/src/types2/mod.rs:243
- Edited copy of a member (20 corresponding lines) macros/src/lib.rs:842
- Edited copy of a member (20 corresponding lines) space/src/parse/mod.rs:6628
- Edited copy of a member (8 corresponding lines) space/src/parse/mod.rs:5823
- Edited copy of a member (8 corresponding lines) space/src/parse/mod.rs:2185
- Duplicated block (29 lines × 2) macros/src/lib.rs:751
- Duplicated block (29 lines × 2) space/src/types1/property.rs:228
- Duplicated block (19 lines × 2) hyperspace/src/hyperlane/mod.rs:2094
- Duplicated block (19 lines × 2) space/src/parse/mod.rs:7246
- Duplicated block (12 lines × 2) macros/src/proxy.rs:510
- Duplicated block (12 lines × 2) space/src/security.rs:126
- Duplicated block (8 lines × 3) space/src/parse/mod.rs:5713
- Duplicated block (8 lines × 3) space/src/parse/mod.rs:7297
- Duplicated block (5 lines × 2) hyperspace/src/hyperlane/quic.rs:90
- Duplicated block (5 lines × 2) REDACTED:438
- Unfinished branch — a todo!() / unimplemented!() arm in a real function base/src/backend/runner.rs:141
- Unfinished branch — a todo!() / unimplemented!() arm in a real function base/src/foundation/implementation/docker_daemon_foundation.rs:115
- Branch is unreachable — an earlier arm already matches it space/src/security.rs:537
- Branch is unreachable — an earlier arm already matches it space/src/security.rs:563
- Match arm is unreachable — an earlier arm already matches it hyperspace/src/properties.rs:182
- Match arm is unreachable — an earlier arm already matches it hyperspace/src/driver/mod.rs:1941
- starlane_space::parse::resolve_kind (cyclomatic 31) space/src/parse/mod.rs:6024
- LayerTraversalEngine::start_layer_traversal (cyclomatic 27) hyperspace/src/star.rs:1335
- starlane::main (cyclomatic 20) main/src/main.rs:103
- HyperClient::new_with_exchanger (cyclomatic 19) hyperspace/src/hyperlane/mod.rs:1295
- Hotspot: main/src/main.rs main/src/main.rs:103
- LayerTraversalEngine::start_layer_traversal (cognitive 59) hyperspace/src/star.rs:1335
- Exchanger::exchange (cognitive 33) space/src/wave/exchange/asynch.rs:377
- PostgresParticleRecord::from_row::wrap (cognitive 30) REDACTED:1065
- Drivers::status_listen (cognitive 26) hyperspace/src/driver/mod.rs:529
- starlane::main (cognitive 26) main/src/main.rs:103
- starlane_space::parse::resolve_kind (cognitive 26) space/src/parse/mod.rs:6024
- Hyperlane::new (cognitive 24) hyperspace/src/hyperlane/mod.rs:421
- HyperClientRunner::start (cognitive 24) hyperspace/src/hyperlane/mod.rs:1679
- HyperClient::new_with_exchanger::relay (cognitive 22) hyperspace/src/hyperlane/mod.rs:1356
- BindConfig::select (cognitive 21) space/src/config/bind.rs:44
- SliceLayout::create (cognitive 20) package/src/lib.rs:119
- Directory::is_member (cognitive 19) package/src/lib.rs:274
- Star::handle_search_request (cognitive 18) hyperspace/src/driver/star.rs:459
- Wrangler::wrangle (cognitive 18) hyperspace/src/driver/star.rs:709
- ControlDriver::init (cognitive 17) hyperspace/src/driver/control.rs:147
- DriverRunner::start (cognitive 17) hyperspace/src/driver/mod.rs:1176
- RootLoggerBuilder::commit (cognitive 17) space/src/log.rs:410
- HyperwayInterchange::new (cognitive 16) hyperspace/src/hyperlane/mod.rs:540
- TraversalLayer::visit (cognitive 16) space/src/particle/traversal.rs:33
- ClassTooLong: PostgresRegistry REDACTED:53
- FunctionTooLong: starlane_space::parse::resolve_kind space/src/parse/mod.rs:6024
- REDACTED
- Near-duplicate member pair (73 shared lines) hyperspace/src/hyperlane/mod.rs:2093
- Near-duplicate member pair (50 shared lines) space/src/parse/mod.rs:6024
- Members sharing a duplicated core (5 members, 50+ identical tokens) space/src/parse/mod.rs:1159
- Edited copy of a member (67 corresponding lines) package/src/zip.rs:24
- Edited copy of a member (35 corresponding lines) hyperspace/src/layer/field.rs:331
- Edited copy of a member (42 corresponding lines) space/src/types1/property.rs:181
- Edited copy of a member (44 corresponding lines) hyperspace/src/properties.rs:78
- Edited copy of a member (36 corresponding lines) space/src/parse/mod.rs:118
- Edited copy of a member (33 corresponding lines) space/src/types1/property.rs:224
- Edited copy of a member (26 corresponding lines) space/src/parse/mod.rs:7363
- Edited copy of a member (27 corresponding lines) space/src/wave/exchange.rs:74
- Edited copy of a member (21 corresponding lines) REDACTED:289
- Edited copies of one member (3 members, 30+ corresponding lines) space/src/parse/mod.rs:2090
- Edited copy of a member (24 corresponding lines) hyperspace/src/properties.rs:28
- Edited copy of a member (7 corresponding lines) space/src/parse/util.rs:448
- Edited copies of one member (4 members, 9+ corresponding lines) space/src/parse/mod.rs:1599
- Edited copies of one member (4 members, 14+ corresponding lines) space/src/parse/mod.rs:6310
- Edited copies of one member (8 members, 10+ corresponding lines) space/src/parse/mod.rs:5328
- Edited copies of one member (3 members, 9+ corresponding lines) space/src/selector.rs:166
- Edited copy of a member (6 corresponding lines) space/src/artifact/asynch.rs:96
- Duplicated block (43 lines × 2) hyperspace/src/hyperlane/mod.rs:2114
- Duplicated block (37–38 lines × 2) hyperspace/src/host/wasm/mod.rs:96
- Duplicated block (30 lines × 2) macros/src/lib.rs:493
- Duplicated block (34 lines × 2) macros/src/proxy.rs:444
- Duplicated block (21–24 lines × 2) package/src/zip.rs:53
- Duplicated block (20–21 lines × 2) space/src/parse/mod.rs:5919
- Duplicated block (21 lines × 2) space/src/types1/property.rs:278
- Duplicated block (20 lines × 2) hyperspace/src/layer/field.rs:348
- Duplicated block (15–16 lines × 2) macros/src/lib.rs:865
- Duplicated block (15 lines × 2) REDACTED:295
- Duplicated block (12 lines × 3) space/src/parse/mod.rs:352
- Duplicated block (10 lines × 5) space/src/parse/mod.rs:1160
- Duplicated block (9 lines × 3) space/src/parse/mod.rs:370
- Duplicated block (8–9 lines × 2) hyperspace/src/star.rs:1070
- Duplicated block (7 lines × 4) hyperspace/src/layer/field.rs:335
- Duplicated block (7 lines × 3) macros/src/lib.rs:849
- Duplicated block (14 lines × 2) hyperspace/src/hyperlane/mod.rs:1385
- Unstable project starlane-platform-for-postgres-registry
- Off the main sequence: starlane-space
- Hollow method — returns a constant without doing the work base/src/foundation/implementation/docker_daemon_foundation.rs:118
- Weak hash algorithm space/src/point.rs:1439
- Explicit release owed and not made on every path main/src/starlane.rs:303
Minor — 122 finding(s)
- Orphaned file hyperspace/src/star.rs:1
- Orphaned file REDACTED:1
- Orphaned file hyperspace/src/driver/mod.rs:1
- Orphaned file space/src/point.rs:1
- Orphaned file space/src/selector.rs:1
- Orphaned file macros/src/lib.rs:1
- Orphaned file space/src/command.rs:1
- Orphaned file space/src/parse/test.rs:1
- Orphaned file space/src/log.rs:1
- Orphaned file space/src/substance.rs:1
- Orphaned file main/src/install.rs:1
- Orphaned file space/src/err.rs:1
- Orphaned file hyperspace/src/machine.rs:1
- Orphaned file space/src/kind.rs:1
- Orphaned file space/src/kind2.rs:1
- Orphaned file hyperspace/src/driver/star.rs:1
- Orphaned file space/src/parse/util.rs:1
- Orphaned file main/src/main.rs:1
- Orphaned file hyperspace/src/hyperlane/tcp.rs:1
- Orphaned file space/src/status.rs:1
- Orphaned file hyperspace/src/driver/artifact.rs:1
- Orphaned file space/src/loc.rs:1
- Orphaned file space/src/types2/mod.rs:1
- Orphaned file package/src/lib.rs:1
- Orphaned file space/src/wave/core.rs:1
- Most significant orphaned file space/src/parse/mod.rs:1
- Most significant orphaned file space/src/wave.rs:1
- Most significant orphaned file hyperspace/src/hyperlane/mod.rs:1
- Documentation: no build, run or usage example README.md:1
- Documentation: no build, run or usage example macros/README.md:1
- Projects may be oversized for their cohesion space/Cargo.toml:1
- Projects may be oversized for their cohesion hyperspace/Cargo.toml:1
- Silent fallback default on Err space/src/log.rs:74
- Silent fallback default on Err space/src/parse/util.rs:907
- Thin authorization enforcement
- No ADRs found main/Cargo.toml:92
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:6
- No dependency-update automation Cargo.toml:21
- Changelog looks stale/thin
- No security response headers detected
- Duplicated predicate space/src/types1/property.rs:201
Minor — 36 finding(s)
- Outdated: anyhow
- Outdated: async-recursion
- Outdated: async-trait
- Outdated: axum
- Outdated: axum-core
- Outdated: chrono
- Outdated: clap
- Outdated: ctrlc
- Outdated: dashmap
- Outdated: enum-ordinalize
- Outdated: eyre
- Outdated: futures
- Outdated: getset
- Outdated: indexmap
- Outdated: lazy_static
- Outdated: once_cell
- Outdated: proc-macro2
- Outdated: quote
- Outdated: regex
- Outdated: rustls
- Outdated: semver
- Outdated: serde
- Outdated: serde_derive
- Outdated: serde_json
- Outdated: serde_with
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-1be0d723f61247ae951d77df32720cbd/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-1be0d723f61247ae951d77df32720cbd/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=751" --report-format json --report-path /tmp/watchdog-gitleaks-1be0d723f61247ae951d77df32720cbd/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.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-1be0d723f61247ae951d77df32720cbd/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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 44 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |