Executive summary
neon-bindings/neon is rated At risk because critical security findings are open. Its score is held back in part because we found no logging, tracing or health checks in the code. It scores 56 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 47, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 7 points. Adding tests for the code no test reaches comes next, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 64.
Sixteen known security holes in the packages the code depends on can be used by attackers. Fourteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two passwords or keys are open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed, and the two places where the code runs text as code or as a command need a direct call instead. The loop of files that import each other needs breaking.
The product code is 16,914 lines, about €21,000 to rebuild.
If Production Readiness rose from 47 to 70, the lowest score rated Strong, the score would rise from 56 to about 64.
New since the last survey: 16 findings
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge crates/neon-macros/src/class/mod.rs
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Async & latency hygiene · Sync-over-async blocking pkgs/create-neon/src/fs.ts
- Async & latency hygiene · Sync-over-async blocking pkgs/create-neon/src/fs.ts
Fixed since the last survey: 9 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
- Async & latency hygiene · Sync-over-async blocking pkgs/create-neon/src/fs.ts
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €7,100 to €36,000, for 118 to 375 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 16,914 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 neon.event.channel.oneshot | 2 neon.handle.internal | 3 neon.sys.bindings.types | 4 neon.types_impl.buffer.lock | 5 neon.types_impl.buffer.private | 6 neon_macros.class.meta | 7 pkgs.create-neon.src.expand.context | 8 neon.context.internal | 9 neon.types_impl.extract.either | 10 neon.types_impl.function | 11 pkgs.create-neon.src.create.creator | 12 neon.sys.async_work | 13 neon.sys.typedarray | 14 neon.types_impl.private | 15 neon.types_impl | 16 neon.sys.tsfn | 17 neon.types_impl.boxed | 18 neon.types_impl.buffer | 19 neon.lifecycle | 20 neon.handle.root | 21 neon.object | 22 neon.handle | 23 neon.types_impl.extract | 24 neon.result | 25 neon.event.channel | 26 neon.types_impl.promise | 27 neon.event.task | 28 neon.sys.promise | 29 neon.context | 30 neon.object.class | 31 neon.object.wrap | 32 neon.types_impl.buffer.types | 33 neon.types_impl.date | 34 neon.types_impl.error | 35 neon.types_impl.extract.array | 36 neon.types_impl.extract.boxed | 37 neon.types_impl.extract.buffer | 38 neon.types_impl.extract.error | 39 neon.types_impl.extract.json | 40 neon.types_impl.extract.with |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 neon.event.channel.oneshot | ||||||||||||||||||||||||||||||||||||||||
| 2 neon.handle.internal | ||||||||||||||||||||||||||||||||||||||||
| 3 neon.sys.bindings.types | ||||||||||||||||||||||||||||||||||||||||
| 4 neon.types_impl.buffer.lock | ||||||||||||||||||||||||||||||||||||||||
| 5 neon.types_impl.buffer.private | ||||||||||||||||||||||||||||||||||||||||
| 6 neon_macros.class.meta | ||||||||||||||||||||||||||||||||||||||||
| 7 pkgs.create-neon.src.expand.context | ||||||||||||||||||||||||||||||||||||||||
| 8 neon.context.internal | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 neon.types_impl.extract.either | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 neon.types_impl.function | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 pkgs.create-neon.src.create.creator | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 neon.sys.async_work | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 neon.sys.typedarray | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 neon.types_impl.private | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 neon.types_impl | 12 | 11 | 3 | 11 | 3 | 11 | 10 | |||||||||||||||||||||||||||||||||
| 16 neon.sys.tsfn | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 neon.types_impl.boxed | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 18 neon.types_impl.buffer | 3 | 2 | 1 | 1 | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 19 neon.lifecycle | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 neon.handle.root | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 21 neon.object | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 22 neon.handle | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 23 neon.types_impl.extract | 1 | 4 | 5 | |||||||||||||||||||||||||||||||||||||
| 24 neon.result | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 neon.event.channel | 1 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 neon.types_impl.promise | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||
| 27 neon.event.task | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 neon.sys.promise | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 neon.context | 1 | 10 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 neon.object.class | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 31 neon.object.wrap | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 32 neon.types_impl.buffer.types | 3 | 3 | 5 | 2 | 1 | 2 | 2 | 5 | 2 | 3 | 2 | |||||||||||||||||||||||||||||
| 33 neon.types_impl.date | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 neon.types_impl.error | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 neon.types_impl.extract.array | 2 | 1 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 36 neon.types_impl.extract.boxed | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 neon.types_impl.extract.buffer | 12 | 12 | 24 | 12 | ||||||||||||||||||||||||||||||||||||
| 38 neon.types_impl.extract.error | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 neon.types_impl.extract.json | 2 | 1 | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||
| 40 neon.types_impl.extract.with | 1 | 1 | 1 |
8→29 neon.context.internal uses neon.context part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.context.internal uses a type in neon.context.
- The types involved
neon.context.internal.ContextInternal→neon.context.Cxneon.context.internal.internal$module→neon.context.ModuleContext
- Direction
- neon.context.internal uses neon.context, so a change to neon.context can break neon.context.internal, while a change to neon.context.internal can't break neon.context.
- 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→5 neon.types_impl.extract.either uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.either uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.either.Error→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract.either uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract.either, while a change to neon.types_impl.extract.either can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract.either uses a module listed above it, which is the healthy direction.
9→23 neon.types_impl.extract.either uses neon.types_impl.extract part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.either uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.extract.either.Error→neon.types_impl.extract.TryIntoJs
- Direction
- neon.types_impl.extract.either uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.extract.either, while a change to neon.types_impl.extract.either can't break neon.types_impl.extract.
- 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→29 neon.types_impl.extract.either uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.either uses a type in neon.context.
- The types involved
neon.types_impl.extract.either.Error→neon.context.Cx
- Direction
- neon.types_impl.extract.either uses neon.context, so a change to neon.context can break neon.types_impl.extract.either, while a change to neon.types_impl.extract.either can't break neon.context.
- 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→22 neon.types_impl.function uses neon.handle part of a loop✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.function uses a type in neon.handle.
- The types involved
neon.types_impl.function.BindOptions→neon.handle.Handleneon.types_impl.function.CallOptions→neon.handle.Handleneon.types_impl.function.ConstructOptions→neon.handle.Handle
- Direction
- neon.types_impl.function uses neon.handle, so a change to neon.handle can break neon.types_impl.function, while a change to neon.types_impl.function can't break neon.handle.
- 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→29 neon.types_impl.function uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.function uses a type in neon.context.
- The types involved
neon.types_impl.function.BindOptions→neon.context.Cx
- Direction
- neon.types_impl.function uses neon.context, so a change to neon.context can break neon.types_impl.function, while a change to neon.types_impl.function can't break neon.context.
- 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→7 pkgs.create-neon.src.create.creator uses pkgs.create-neon.src.expand.context✕
- Connections
- 1 pair of types, where a type in pkgs.create-neon.src.create.creator uses a type in pkgs.create-neon.src.expand.context.
- The types involved
pkgs.create-neon.src.create.creator.Creator→pkgs.create-neon.src.expand.context.Context
- Direction
- pkgs.create-neon.src.create.creator uses pkgs.create-neon.src.expand.context, so a change to pkgs.create-neon.src.expand.context can break pkgs.create-neon.src.create.creator, while a change to pkgs.create-neon.src.create.creator can't break pkgs.create-neon.src.expand.context.
- Position
- Below the diagonal: pkgs.create-neon.src.create.creator uses a module listed above it, which is the healthy direction.
12→3 neon.sys.async_work uses neon.sys.bindings.types✕
- Connections
- 1 pair of types, where a type in neon.sys.async_work uses a type in neon.sys.bindings.types.
- The types involved
neon.sys.async_work.async_work$module→neon.sys.bindings.types.Status
- Direction
- neon.sys.async_work uses neon.sys.bindings.types, so a change to neon.sys.bindings.types can break neon.sys.async_work, while a change to neon.sys.async_work can't break neon.sys.bindings.types.
- Position
- Below the diagonal: neon.sys.async_work uses a module listed above it, which is the healthy direction.
12→8 neon.sys.async_work uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.sys.async_work uses a type in neon.context.internal.
- The types involved
neon.sys.async_work.async_work$module→neon.context.internal.Env
- Direction
- neon.sys.async_work uses neon.context.internal, so a change to neon.context.internal can break neon.sys.async_work, while a change to neon.sys.async_work can't break neon.context.internal.
- Position
- Below the diagonal: neon.sys.async_work uses a module listed above it, which is the healthy direction.
13→3 neon.sys.typedarray uses neon.sys.bindings.types✕
- Connections
- 2 pairs of types, where a type in neon.sys.typedarray uses a type in neon.sys.bindings.types.
- The types involved
neon.sys.typedarray.TypedArrayInfo→neon.sys.bindings.types.TypedArrayTypeneon.sys.typedarray.typedarray$module→neon.sys.bindings.types.TypedArrayType
- Direction
- neon.sys.typedarray uses neon.sys.bindings.types, so a change to neon.sys.bindings.types can break neon.sys.typedarray, while a change to neon.sys.typedarray can't break neon.sys.bindings.types.
- Position
- Below the diagonal: neon.sys.typedarray uses a module listed above it, which is the healthy direction.
13→8 neon.sys.typedarray uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.sys.typedarray uses a type in neon.context.internal.
- The types involved
neon.sys.typedarray.typedarray$module→neon.context.internal.Env
- Direction
- neon.sys.typedarray uses neon.context.internal, so a change to neon.context.internal can break neon.sys.typedarray, while a change to neon.sys.typedarray can't break neon.context.internal.
- Position
- Below the diagonal: neon.sys.typedarray uses a module listed above it, which is the healthy direction.
14→2 neon.types_impl.private uses neon.handle.internal✕
- Connections
- 1 pair of types, where a type in neon.types_impl.private uses a type in neon.handle.internal.
- The types involved
neon.types_impl.private.ValueInternal→neon.handle.internal.TransparentNoCopyWrapper
- Direction
- neon.types_impl.private uses neon.handle.internal, so a change to neon.handle.internal can break neon.types_impl.private, while a change to neon.types_impl.private can't break neon.handle.internal.
- Position
- Below the diagonal: neon.types_impl.private uses a module listed above it, which is the healthy direction.
14→8 neon.types_impl.private uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.types_impl.private uses a type in neon.context.internal.
- The types involved
neon.types_impl.private.ValueInternal→neon.context.internal.Env
- Direction
- neon.types_impl.private uses neon.context.internal, so a change to neon.context.internal can break neon.types_impl.private, while a change to neon.types_impl.private can't break neon.context.internal.
- Position
- Below the diagonal: neon.types_impl.private uses a module listed above it, which is the healthy direction.
14→22 neon.types_impl.private uses neon.handle part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.private uses a type in neon.handle.
- The types involved
neon.types_impl.private.ValueInternal→neon.handle.Handle
- Direction
- neon.types_impl.private uses neon.handle, so a change to neon.handle can break neon.types_impl.private, while a change to neon.types_impl.private can't break neon.handle.
- 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→29 neon.types_impl.private uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.private uses a type in neon.context.
- The types involved
neon.types_impl.private.ValueInternal→neon.context.Cx
- Direction
- neon.types_impl.private uses neon.context, so a change to neon.context can break neon.types_impl.private, while a change to neon.types_impl.private can't break neon.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 neon.types_impl uses neon.handle.internal✕
- Connections
- 12 pairs of types, where a type in neon.types_impl uses a type in neon.handle.internal.
- The types involved
neon.types_impl.JsArray→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsBigInt→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsBoolean→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsFunction→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsNull→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsNumber→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsObject→neon.handle.internal.SuperTypeneon.types_impl.JsObject→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsString→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsUndefined→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.JsValue→neon.handle.internal.SuperTypeneon.types_impl.JsValue→neon.handle.internal.TransparentNoCopyWrapper
- Direction
- neon.types_impl uses neon.handle.internal, so a change to neon.handle.internal can break neon.types_impl, while a change to neon.types_impl can't break neon.handle.internal.
- Position
- Below the diagonal: neon.types_impl uses a module listed above it, which is the healthy direction.
15→8 neon.types_impl uses neon.context.internal✕
- Connections
- 11 pairs of types, where a type in neon.types_impl uses a type in neon.context.internal.
- The types involved
neon.types_impl.JsArray→neon.context.internal.Envneon.types_impl.JsBigInt→neon.context.internal.Envneon.types_impl.JsBoolean→neon.context.internal.Envneon.types_impl.JsFunction→neon.context.internal.Envneon.types_impl.JsNull→neon.context.internal.Envneon.types_impl.JsNumber→neon.context.internal.Envneon.types_impl.JsObject→neon.context.internal.Envneon.types_impl.JsString→neon.context.internal.Envneon.types_impl.JsUndefined→neon.context.internal.Envneon.types_impl.JsValue→neon.context.internal.Envneon.types_impl.types_impl$module→neon.context.internal.Env
- Direction
- neon.types_impl uses neon.context.internal, so a change to neon.context.internal can break neon.types_impl, while a change to neon.types_impl can't break neon.context.internal.
- Position
- Below the diagonal: neon.types_impl uses a module listed above it, which is the healthy direction.
15→10 neon.types_impl uses neon.types_impl.function✕
- Connections
- 3 pairs of types, where a type in neon.types_impl uses a type in neon.types_impl.function.
- The types involved
neon.types_impl.JsFunction→neon.types_impl.function.BindOptionsneon.types_impl.JsFunction→neon.types_impl.function.CallOptionsneon.types_impl.JsFunction→neon.types_impl.function.ConstructOptions
- Direction
- neon.types_impl uses neon.types_impl.function, so a change to neon.types_impl.function can break neon.types_impl, while a change to neon.types_impl can't break neon.types_impl.function.
- Position
- Below the diagonal: neon.types_impl uses a module listed above it, which is the healthy direction.
15→14 neon.types_impl uses neon.types_impl.private✕
- Connections
- 11 pairs of types, where a type in neon.types_impl uses a type in neon.types_impl.private.
- The types involved
neon.types_impl.JsArray→neon.types_impl.private.ValueInternalneon.types_impl.JsBigInt→neon.types_impl.private.ValueInternalneon.types_impl.JsBoolean→neon.types_impl.private.ValueInternalneon.types_impl.JsFunction→neon.types_impl.private.ValueInternalneon.types_impl.JsNull→neon.types_impl.private.ValueInternalneon.types_impl.JsNumber→neon.types_impl.private.ValueInternalneon.types_impl.JsObject→neon.types_impl.private.ValueInternalneon.types_impl.JsString→neon.types_impl.private.ValueInternalneon.types_impl.JsUndefined→neon.types_impl.private.ValueInternalneon.types_impl.JsValue→neon.types_impl.private.ValueInternalneon.types_impl.Value→neon.types_impl.private.ValueInternal
- Direction
- neon.types_impl uses neon.types_impl.private, so a change to neon.types_impl.private can break neon.types_impl, while a change to neon.types_impl can't break neon.types_impl.private.
- Position
- Below the diagonal: neon.types_impl uses a module listed above it, which is the healthy direction.
15→21 neon.types_impl uses neon.object part of a loop✕
- Connections
- 3 pairs of types, where a type in neon.types_impl uses a type in neon.object.
- The types involved
neon.types_impl.JsArray→neon.object.Objectneon.types_impl.JsFunction→neon.object.Objectneon.types_impl.JsObject→neon.object.Object
- Direction
- neon.types_impl uses neon.object, so a change to neon.object can break neon.types_impl, while a change to neon.types_impl can't break neon.object.
- 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→22 neon.types_impl uses neon.handle part of a loop✕
- Connections
- 11 pairs of types, where a type in neon.types_impl uses a type in neon.handle.
- The types involved
neon.types_impl.JsArray→neon.handle.Handleneon.types_impl.JsBigInt→neon.handle.Handleneon.types_impl.JsBoolean→neon.handle.Handleneon.types_impl.JsFunction→neon.handle.Handleneon.types_impl.JsNull→neon.handle.Handleneon.types_impl.JsNumber→neon.handle.Handleneon.types_impl.JsObject→neon.handle.Handleneon.types_impl.JsString→neon.handle.Handleneon.types_impl.JsUndefined→neon.handle.Handleneon.types_impl.JsValue→neon.handle.Handleneon.types_impl.Value→neon.handle.Handle
- Direction
- neon.types_impl uses neon.handle, so a change to neon.handle can break neon.types_impl, while a change to neon.types_impl can't break neon.handle.
- 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→29 neon.types_impl uses neon.context part of a loop✕
- Connections
- 10 pairs of types, where a type in neon.types_impl uses a type in neon.context.
- The types involved
neon.types_impl.JsArray→neon.context.Cxneon.types_impl.JsBigInt→neon.context.Cxneon.types_impl.JsBoolean→neon.context.Cxneon.types_impl.JsFunction→neon.context.Cxneon.types_impl.JsNull→neon.context.Cxneon.types_impl.JsNumber→neon.context.Cxneon.types_impl.JsObject→neon.context.Cxneon.types_impl.JsString→neon.context.Cxneon.types_impl.JsUndefined→neon.context.Cxneon.types_impl.JsValue→neon.context.Cx
- Direction
- neon.types_impl uses neon.context, so a change to neon.context can break neon.types_impl, while a change to neon.types_impl can't break neon.context.
- 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→3 neon.sys.tsfn uses neon.sys.bindings.types✕
- Connections
- 1 pair of types, where a type in neon.sys.tsfn uses a type in neon.sys.bindings.types.
- The types involved
neon.sys.tsfn.ThreadsafeFunction→neon.sys.bindings.types.ThreadsafeFunctionCallMode
- Direction
- neon.sys.tsfn uses neon.sys.bindings.types, so a change to neon.sys.bindings.types can break neon.sys.tsfn, while a change to neon.sys.tsfn can't break neon.sys.bindings.types.
- Position
- Below the diagonal: neon.sys.tsfn uses a module listed above it, which is the healthy direction.
16→8 neon.sys.tsfn uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.sys.tsfn uses a type in neon.context.internal.
- The types involved
neon.sys.tsfn.ThreadsafeFunction→neon.context.internal.Env
- Direction
- neon.sys.tsfn uses neon.context.internal, so a change to neon.context.internal can break neon.sys.tsfn, while a change to neon.sys.tsfn can't break neon.context.internal.
- Position
- Below the diagonal: neon.sys.tsfn uses a module listed above it, which is the healthy direction.
16→15 neon.sys.tsfn uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.sys.tsfn uses a type in neon.types_impl.
- The types involved
neon.sys.tsfn.ThreadsafeFunction→neon.types_impl.Value
- Direction
- neon.sys.tsfn uses neon.types_impl, so a change to neon.types_impl can break neon.sys.tsfn, while a change to neon.sys.tsfn can't break neon.types_impl.
- Position
- Below the diagonal: neon.sys.tsfn uses a module listed above it, which is the healthy direction.
17→2 neon.types_impl.boxed uses neon.handle.internal✕
- Connections
- 1 pair of types, where a type in neon.types_impl.boxed uses a type in neon.handle.internal.
- The types involved
neon.types_impl.boxed.JsBox→neon.handle.internal.TransparentNoCopyWrapper
- Direction
- neon.types_impl.boxed uses neon.handle.internal, so a change to neon.handle.internal can break neon.types_impl.boxed, while a change to neon.types_impl.boxed can't break neon.handle.internal.
- Position
- Below the diagonal: neon.types_impl.boxed uses a module listed above it, which is the healthy direction.
17→8 neon.types_impl.boxed uses neon.context.internal✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.boxed uses a type in neon.context.internal.
- The types involved
neon.types_impl.boxed.JsBox→neon.context.internal.Envneon.types_impl.boxed.boxed$module→neon.context.internal.Env
- Direction
- neon.types_impl.boxed uses neon.context.internal, so a change to neon.context.internal can break neon.types_impl.boxed, while a change to neon.types_impl.boxed can't break neon.context.internal.
- Position
- Below the diagonal: neon.types_impl.boxed uses a module listed above it, which is the healthy direction.
17→14 neon.types_impl.boxed uses neon.types_impl.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.boxed uses a type in neon.types_impl.private.
- The types involved
neon.types_impl.boxed.JsBox→neon.types_impl.private.ValueInternal
- Direction
- neon.types_impl.boxed uses neon.types_impl.private, so a change to neon.types_impl.private can break neon.types_impl.boxed, while a change to neon.types_impl.boxed can't break neon.types_impl.private.
- Position
- Below the diagonal: neon.types_impl.boxed uses a module listed above it, which is the healthy direction.
17→15 neon.types_impl.boxed uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.types_impl.boxed uses a type in neon.types_impl.
- The types involved
neon.types_impl.boxed.JsBox→neon.types_impl.Value
- Direction
- neon.types_impl.boxed uses neon.types_impl, so a change to neon.types_impl can break neon.types_impl.boxed, while a change to neon.types_impl.boxed can't break neon.types_impl.
- Position
- Below the diagonal: neon.types_impl.boxed uses a module listed above it, which is the healthy direction.
17→21 neon.types_impl.boxed uses neon.object part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.boxed uses a type in neon.object.
- The types involved
neon.types_impl.boxed.JsBox→neon.object.Object
- Direction
- neon.types_impl.boxed uses neon.object, so a change to neon.object can break neon.types_impl.boxed, while a change to neon.types_impl.boxed can't break neon.object.
- 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→22 neon.types_impl.boxed uses neon.handle part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.boxed uses a type in neon.handle.
- The types involved
neon.types_impl.boxed.JsBox→neon.handle.Handle
- Direction
- neon.types_impl.boxed uses neon.handle, so a change to neon.handle can break neon.types_impl.boxed, while a change to neon.types_impl.boxed can't break neon.handle.
- 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→29 neon.types_impl.boxed uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.types_impl.boxed uses a type in neon.context.
- The types involved
neon.types_impl.boxed.JsBox→neon.context.Cx
- Direction
- neon.types_impl.boxed uses neon.context, so a change to neon.context can break neon.types_impl.boxed, while a change to neon.types_impl.boxed can't break neon.context.
- 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→4 neon.types_impl.buffer uses neon.types_impl.buffer.lock✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.buffer uses a type in neon.types_impl.buffer.lock.
- The types involved
neon.types_impl.buffer.Ref→neon.types_impl.buffer.lock.Ledgerneon.types_impl.buffer.RefMut→neon.types_impl.buffer.lock.Ledgerneon.types_impl.buffer.TypedArray→neon.types_impl.buffer.lock.Lock
- Direction
- neon.types_impl.buffer uses neon.types_impl.buffer.lock, so a change to neon.types_impl.buffer.lock can break neon.types_impl.buffer, while a change to neon.types_impl.buffer can't break neon.types_impl.buffer.lock.
- Position
- Below the diagonal: neon.types_impl.buffer uses a module listed above it, which is the healthy direction.
18→5 neon.types_impl.buffer uses neon.types_impl.buffer.private✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.buffer.Ref→neon.types_impl.buffer.private.Sealedneon.types_impl.buffer.RefMut→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.buffer uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.buffer, while a change to neon.types_impl.buffer can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.buffer uses a module listed above it, which is the healthy direction.
18→9 neon.types_impl.buffer uses neon.types_impl.extract.either✕
- Connections
- 1 pair of types, where a type in neon.types_impl.buffer uses a type in neon.types_impl.extract.either.
- The types involved
neon.types_impl.buffer.BorrowError→neon.types_impl.extract.either.Error
- Direction
- neon.types_impl.buffer uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.types_impl.buffer, while a change to neon.types_impl.buffer can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.types_impl.buffer uses a module listed above it, which is the healthy direction.
18→15 neon.types_impl.buffer uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.types_impl.buffer uses a type in neon.types_impl.
- The types involved
neon.types_impl.buffer.TypedArray→neon.types_impl.Value
- Direction
- neon.types_impl.buffer uses neon.types_impl, so a change to neon.types_impl can break neon.types_impl.buffer, while a change to neon.types_impl.buffer can't break neon.types_impl.
- Position
- Below the diagonal: neon.types_impl.buffer uses a module listed above it, which is the healthy direction.
18→22 neon.types_impl.buffer uses neon.handle part of a loop✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.buffer uses a type in neon.handle.
- The types involved
neon.types_impl.buffer.Ref→neon.handle.Handleneon.types_impl.buffer.RefMut→neon.handle.Handleneon.types_impl.buffer.Region→neon.handle.Handle
- Direction
- neon.types_impl.buffer uses neon.handle, so a change to neon.handle can break neon.types_impl.buffer, while a change to neon.types_impl.buffer can't break neon.handle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→23 neon.types_impl.buffer uses neon.types_impl.extract part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.buffer.Ref→neon.types_impl.extract.TryFromJsneon.types_impl.buffer.RefMut→neon.types_impl.extract.TryFromJs
- Direction
- neon.types_impl.buffer uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.buffer, while a change to neon.types_impl.buffer can't break neon.types_impl.extract.
- 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 neon.types_impl.buffer uses neon.context part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer uses a type in neon.context.
- The types involved
neon.types_impl.buffer.Ref→neon.context.Cxneon.types_impl.buffer.RefMut→neon.context.Cx
- Direction
- neon.types_impl.buffer uses neon.context, so a change to neon.context can break neon.types_impl.buffer, while a change to neon.types_impl.buffer can't break neon.context.
- 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→8 neon.lifecycle uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.lifecycle uses a type in neon.context.internal.
- The types involved
neon.lifecycle.DropData→neon.context.internal.Env
- Direction
- neon.lifecycle uses neon.context.internal, so a change to neon.context.internal can break neon.lifecycle, while a change to neon.lifecycle can't break neon.context.internal.
- Position
- Below the diagonal: neon.lifecycle uses a module listed above it, which is the healthy direction.
19→16 neon.lifecycle uses neon.sys.tsfn✕
- Connections
- 1 pair of types, where a type in neon.lifecycle uses a type in neon.sys.tsfn.
- The types involved
neon.lifecycle.InstanceData→neon.sys.tsfn.ThreadsafeFunction
- Direction
- neon.lifecycle uses neon.sys.tsfn, so a change to neon.sys.tsfn can break neon.lifecycle, while a change to neon.lifecycle can't break neon.sys.tsfn.
- Position
- Below the diagonal: neon.lifecycle uses a module listed above it, which is the healthy direction.
19→25 neon.lifecycle uses neon.event.channel part of a loop✕
- Connections
- 1 pair of types, where a type in neon.lifecycle uses a type in neon.event.channel.
- The types involved
neon.lifecycle.InstanceData→neon.event.channel.Channel
- Direction
- neon.lifecycle uses neon.event.channel, so a change to neon.event.channel can break neon.lifecycle, while a change to neon.lifecycle can't break neon.event.channel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→5 neon.handle.root uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.handle.root uses a type in neon.types_impl.buffer.private.
- The types involved
neon.handle.root.Root→neon.types_impl.buffer.private.Sealed
- Direction
- neon.handle.root uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.handle.root, while a change to neon.handle.root can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.handle.root uses a module listed above it, which is the healthy direction.
20→8 neon.handle.root uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.handle.root uses a type in neon.context.internal.
- The types involved
neon.handle.root.NapiRef→neon.context.internal.Env
- Direction
- neon.handle.root uses neon.context.internal, so a change to neon.context.internal can break neon.handle.root, while a change to neon.handle.root can't break neon.context.internal.
- Position
- Below the diagonal: neon.handle.root uses a module listed above it, which is the healthy direction.
20→16 neon.handle.root uses neon.sys.tsfn✕
- Connections
- 1 pair of types, where a type in neon.handle.root uses a type in neon.sys.tsfn.
- The types involved
neon.handle.root.Root→neon.sys.tsfn.ThreadsafeFunction
- Direction
- neon.handle.root uses neon.sys.tsfn, so a change to neon.sys.tsfn can break neon.handle.root, while a change to neon.handle.root can't break neon.sys.tsfn.
- Position
- Below the diagonal: neon.handle.root uses a module listed above it, which is the healthy direction.
20→17 neon.handle.root uses neon.types_impl.boxed✕
- Connections
- 1 pair of types, where a type in neon.handle.root uses a type in neon.types_impl.boxed.
- The types involved
neon.handle.root.Root→neon.types_impl.boxed.Finalize
- Direction
- neon.handle.root uses neon.types_impl.boxed, so a change to neon.types_impl.boxed can break neon.handle.root, while a change to neon.handle.root can't break neon.types_impl.boxed.
- Position
- Below the diagonal: neon.handle.root uses a module listed above it, which is the healthy direction.
20→19 neon.handle.root uses neon.lifecycle✕
- Connections
- 2 pairs of types, where a type in neon.handle.root uses a type in neon.lifecycle.
- The types involved
neon.handle.root.Root→neon.lifecycle.InstanceIdneon.handle.root.root$module→neon.lifecycle.InstanceId
- Direction
- neon.handle.root uses neon.lifecycle, so a change to neon.lifecycle can break neon.handle.root, while a change to neon.handle.root can't break neon.lifecycle.
- Position
- Below the diagonal: neon.handle.root uses a module listed above it, which is the healthy direction.
20→22 neon.handle.root uses neon.handle part of a loop✕
- Connections
- 1 pair of types, where a type in neon.handle.root uses a type in neon.handle.
- The types involved
neon.handle.root.Root→neon.handle.Handle
- Direction
- neon.handle.root uses neon.handle, so a change to neon.handle can break neon.handle.root, while a change to neon.handle.root can't break neon.handle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→23 neon.handle.root uses neon.types_impl.extract part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.handle.root uses a type in neon.types_impl.extract.
- The types involved
neon.handle.root.Root→neon.types_impl.extract.TryFromJsneon.handle.root.Root→neon.types_impl.extract.TryIntoJs
- Direction
- neon.handle.root uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.handle.root, while a change to neon.handle.root can't break neon.types_impl.extract.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→29 neon.handle.root uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.handle.root uses a type in neon.context.
- The types involved
neon.handle.root.Root→neon.context.Cx
- Direction
- neon.handle.root uses neon.context, so a change to neon.context can break neon.handle.root, while a change to neon.handle.root can't break neon.context.
- 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→15 neon.object uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.object uses a type in neon.types_impl.
- The types involved
neon.object.Object→neon.types_impl.Value
- Direction
- neon.object uses neon.types_impl, so a change to neon.types_impl can break neon.object, while a change to neon.object can't break neon.types_impl.
- Position
- Below the diagonal: neon.object uses a module listed above it, which is the healthy direction.
21→20 neon.object uses neon.handle.root✕
- Connections
- 1 pair of types, where a type in neon.object uses a type in neon.handle.root.
- The types involved
neon.object.Object→neon.handle.root.Root
- Direction
- neon.object uses neon.handle.root, so a change to neon.handle.root can break neon.object, while a change to neon.object can't break neon.handle.root.
- Position
- Below the diagonal: neon.object uses a module listed above it, which is the healthy direction.
21→22 neon.object uses neon.handle part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.object uses a type in neon.handle.
- The types involved
neon.object.Object→neon.handle.Handleneon.object.PropOptions→neon.handle.Handle
- Direction
- neon.object uses neon.handle, so a change to neon.handle can break neon.object, while a change to neon.object can't break neon.handle.
- 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 neon.object uses neon.context part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.object uses a type in neon.context.
- The types involved
neon.object.Object→neon.context.Cxneon.object.PropOptions→neon.context.Cx
- Direction
- neon.object uses neon.context, so a change to neon.context can break neon.object, while a change to neon.object can't break neon.context.
- 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→5 neon.handle uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.handle uses a type in neon.types_impl.buffer.private.
- The types involved
neon.handle.Handle→neon.types_impl.buffer.private.Sealed
- Direction
- neon.handle uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.handle, while a change to neon.handle can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.handle uses a module listed above it, which is the healthy direction.
22→9 neon.handle uses neon.types_impl.extract.either✕
- Connections
- 1 pair of types, where a type in neon.handle uses a type in neon.types_impl.extract.either.
- The types involved
neon.handle.DowncastError→neon.types_impl.extract.either.Error
- Direction
- neon.handle uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.handle, while a change to neon.handle can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.handle uses a module listed above it, which is the healthy direction.
22→18 neon.handle uses neon.types_impl.buffer✕
- Connections
- 1 pair of types, where a type in neon.handle uses a type in neon.types_impl.buffer.
- The types involved
neon.handle.Handle→neon.types_impl.buffer.Region
- Direction
- neon.handle uses neon.types_impl.buffer, so a change to neon.types_impl.buffer can break neon.handle, while a change to neon.handle can't break neon.types_impl.buffer.
- Position
- Below the diagonal: neon.handle uses a module listed above it, which is the healthy direction.
22→21 neon.handle uses neon.object✕
- Connections
- 1 pair of types, where a type in neon.handle uses a type in neon.object.
- The types involved
neon.handle.Handle→neon.object.PropertyKey
- Direction
- neon.handle uses neon.object, so a change to neon.object can break neon.handle, while a change to neon.handle can't break neon.object.
- Position
- Below the diagonal: neon.handle uses a module listed above it, which is the healthy direction.
22→23 neon.handle uses neon.types_impl.extract part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.handle uses a type in neon.types_impl.extract.
- The types involved
neon.handle.Handle→neon.types_impl.extract.TryFromJsneon.handle.Handle→neon.types_impl.extract.TryIntoJs
- Direction
- neon.handle uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.handle, while a change to neon.handle can't break neon.types_impl.extract.
- 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→29 neon.handle uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.handle uses a type in neon.context.
- The types involved
neon.handle.Handle→neon.context.Cx
- Direction
- neon.handle uses neon.context, so a change to neon.context can break neon.handle, while a change to neon.handle can't break neon.context.
- 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→5 neon.types_impl.extract uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.Date→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract, while a change to neon.types_impl.extract can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract uses a module listed above it, which is the healthy direction.
23→22 neon.types_impl.extract uses neon.handle✕
- Connections
- 4 pairs of types, where a type in neon.types_impl.extract uses a type in neon.handle.
- The types involved
neon.types_impl.extract.Date→neon.handle.Handleneon.types_impl.extract.TryFromJs→neon.handle.Handleneon.types_impl.extract.TryFromJsRef→neon.handle.Handleneon.types_impl.extract.TryFromJsRefMut→neon.handle.Handle
- Direction
- neon.types_impl.extract uses neon.handle, so a change to neon.handle can break neon.types_impl.extract, while a change to neon.types_impl.extract can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.extract uses a module listed above it, which is the healthy direction.
23→29 neon.types_impl.extract uses neon.context part of a loop✕
- Connections
- 5 pairs of types, where a type in neon.types_impl.extract uses a type in neon.context.
- The types involved
neon.types_impl.extract.Date→neon.context.Cxneon.types_impl.extract.TryFromJs→neon.context.Cxneon.types_impl.extract.TryFromJsRef→neon.context.Cxneon.types_impl.extract.TryFromJsRefMut→neon.context.Cxneon.types_impl.extract.TryIntoJs→neon.context.Cx
- Direction
- neon.types_impl.extract uses neon.context, so a change to neon.context can break neon.types_impl.extract, while a change to neon.types_impl.extract can't break neon.context.
- 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→5 neon.result uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.result uses a type in neon.types_impl.buffer.private.
- The types involved
neon.result.Throw→neon.types_impl.buffer.private.Sealed
- Direction
- neon.result uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.result, while a change to neon.result can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.result uses a module listed above it, which is the healthy direction.
24→23 neon.result uses neon.types_impl.extract✕
- Connections
- 1 pair of types, where a type in neon.result uses a type in neon.types_impl.extract.
- The types involved
neon.result.Throw→neon.types_impl.extract.TryIntoJs
- Direction
- neon.result uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.result, while a change to neon.result can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.result uses a module listed above it, which is the healthy direction.
24→29 neon.result uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.result uses a type in neon.context.
- The types involved
neon.result.Throw→neon.context.Cx
- Direction
- neon.result uses neon.context, so a change to neon.context can break neon.result, while a change to neon.result can't break neon.context.
- 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.
25→1 neon.event.channel uses neon.event.channel.oneshot✕
- Connections
- 1 pair of types, where a type in neon.event.channel uses a type in neon.event.channel.oneshot.
- The types involved
neon.event.channel.JoinHandle→neon.event.channel.oneshot.Receiver
- Direction
- neon.event.channel uses neon.event.channel.oneshot, so a change to neon.event.channel.oneshot can break neon.event.channel, while a change to neon.event.channel can't break neon.event.channel.oneshot.
- Position
- Below the diagonal: neon.event.channel uses a module listed above it, which is the healthy direction.
25→8 neon.event.channel uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.event.channel uses a type in neon.context.internal.
- The types involved
neon.event.channel.ChannelState→neon.context.internal.Env
- Direction
- neon.event.channel uses neon.context.internal, so a change to neon.context.internal can break neon.event.channel, while a change to neon.event.channel can't break neon.context.internal.
- Position
- Below the diagonal: neon.event.channel uses a module listed above it, which is the healthy direction.
25→9 neon.event.channel uses neon.types_impl.extract.either✕
- Connections
- 2 pairs of types, where a type in neon.event.channel uses a type in neon.types_impl.extract.either.
- The types involved
neon.event.channel.JoinError→neon.types_impl.extract.either.Errorneon.event.channel.SendError→neon.types_impl.extract.either.Error
- Direction
- neon.event.channel uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.event.channel, while a change to neon.event.channel can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.event.channel uses a module listed above it, which is the healthy direction.
25→16 neon.event.channel uses neon.sys.tsfn✕
- Connections
- 2 pairs of types, where a type in neon.event.channel uses a type in neon.sys.tsfn.
- The types involved
neon.event.channel.ChannelState→neon.sys.tsfn.Callbackneon.event.channel.ChannelState→neon.sys.tsfn.ThreadsafeFunction
- Direction
- neon.event.channel uses neon.sys.tsfn, so a change to neon.sys.tsfn can break neon.event.channel, while a change to neon.event.channel can't break neon.sys.tsfn.
- Position
- Below the diagonal: neon.event.channel uses a module listed above it, which is the healthy direction.
25→24 neon.event.channel uses neon.result✕
- Connections
- 1 pair of types, where a type in neon.event.channel uses a type in neon.result.
- The types involved
neon.event.channel.SendThrow→neon.result.Throw
- Direction
- neon.event.channel uses neon.result, so a change to neon.result can break neon.event.channel, while a change to neon.event.channel can't break neon.result.
- Position
- Below the diagonal: neon.event.channel uses a module listed above it, which is the healthy direction.
25→29 neon.event.channel uses neon.context part of a loop✕
- Connections
- 1 pair of types, where a type in neon.event.channel uses a type in neon.context.
- The types involved
neon.event.channel.JoinHandle→neon.context.Context
- Direction
- neon.event.channel uses neon.context, so a change to neon.context can break neon.event.channel, while a change to neon.event.channel can't break neon.context.
- 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.
26→1 neon.types_impl.promise uses neon.event.channel.oneshot✕
- Connections
- 1 pair of types, where a type in neon.types_impl.promise uses a type in neon.event.channel.oneshot.
- The types involved
neon.types_impl.promise.JsFuture→neon.event.channel.oneshot.Receiver
- Direction
- neon.types_impl.promise uses neon.event.channel.oneshot, so a change to neon.event.channel.oneshot can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.event.channel.oneshot.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→2 neon.types_impl.promise uses neon.handle.internal✕
- Connections
- 1 pair of types, where a type in neon.types_impl.promise uses a type in neon.handle.internal.
- The types involved
neon.types_impl.promise.JsPromise→neon.handle.internal.TransparentNoCopyWrapper
- Direction
- neon.types_impl.promise uses neon.handle.internal, so a change to neon.handle.internal can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.handle.internal.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→8 neon.types_impl.promise uses neon.context.internal✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.promise uses a type in neon.context.internal.
- The types involved
neon.types_impl.promise.JsPromise→neon.context.internal.Envneon.types_impl.promise.NodeApiDeferred→neon.context.internal.Env
- Direction
- neon.types_impl.promise uses neon.context.internal, so a change to neon.context.internal can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.context.internal.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→14 neon.types_impl.promise uses neon.types_impl.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.promise uses a type in neon.types_impl.private.
- The types involved
neon.types_impl.promise.JsPromise→neon.types_impl.private.ValueInternal
- Direction
- neon.types_impl.promise uses neon.types_impl.private, so a change to neon.types_impl.private can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.types_impl.private.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→15 neon.types_impl.promise uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.types_impl.promise uses a type in neon.types_impl.
- The types involved
neon.types_impl.promise.JsPromise→neon.types_impl.Value
- Direction
- neon.types_impl.promise uses neon.types_impl, so a change to neon.types_impl can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.types_impl.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→16 neon.types_impl.promise uses neon.sys.tsfn✕
- Connections
- 1 pair of types, where a type in neon.types_impl.promise uses a type in neon.sys.tsfn.
- The types involved
neon.types_impl.promise.Deferred→neon.sys.tsfn.ThreadsafeFunction
- Direction
- neon.types_impl.promise uses neon.sys.tsfn, so a change to neon.sys.tsfn can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.sys.tsfn.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→21 neon.types_impl.promise uses neon.object✕
- Connections
- 1 pair of types, where a type in neon.types_impl.promise uses a type in neon.object.
- The types involved
neon.types_impl.promise.JsPromise→neon.object.Object
- Direction
- neon.types_impl.promise uses neon.object, so a change to neon.object can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.object.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→22 neon.types_impl.promise uses neon.handle✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.promise uses a type in neon.handle.
- The types involved
neon.types_impl.promise.Deferred→neon.handle.Handleneon.types_impl.promise.JsPromise→neon.handle.Handle
- Direction
- neon.types_impl.promise uses neon.handle, so a change to neon.handle can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→25 neon.types_impl.promise uses neon.event.channel✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.promise uses a type in neon.event.channel.
- The types involved
neon.types_impl.promise.Deferred→neon.event.channel.Channelneon.types_impl.promise.Deferred→neon.event.channel.JoinHandle
- Direction
- neon.types_impl.promise uses neon.event.channel, so a change to neon.event.channel can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.event.channel.
- Position
- Below the diagonal: neon.types_impl.promise uses a module listed above it, which is the healthy direction.
26→29 neon.types_impl.promise uses neon.context part of a loop✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.promise uses a type in neon.context.
- The types involved
neon.types_impl.promise.JsFuture→neon.context.Contextneon.types_impl.promise.JsPromise→neon.context.Cx
- Direction
- neon.types_impl.promise uses neon.context, so a change to neon.context can break neon.types_impl.promise, while a change to neon.types_impl.promise can't break neon.context.
- 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.
27→8 neon.event.task uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.event.task uses a type in neon.context.internal.
- The types involved
neon.event.task.task$module→neon.context.internal.Env
- Direction
- neon.event.task uses neon.context.internal, so a change to neon.context.internal can break neon.event.task, while a change to neon.event.task can't break neon.context.internal.
- Position
- Below the diagonal: neon.event.task uses a module listed above it, which is the healthy direction.
27→22 neon.event.task uses neon.handle✕
- Connections
- 1 pair of types, where a type in neon.event.task uses a type in neon.handle.
- The types involved
neon.event.task.TaskBuilder→neon.handle.Handle
- Direction
- neon.event.task uses neon.handle, so a change to neon.handle can break neon.event.task, while a change to neon.event.task can't break neon.handle.
- Position
- Below the diagonal: neon.event.task uses a module listed above it, which is the healthy direction.
27→26 neon.event.task uses neon.types_impl.promise✕
- Connections
- 1 pair of types, where a type in neon.event.task uses a type in neon.types_impl.promise.
- The types involved
neon.event.task.task$module→neon.types_impl.promise.Deferred
- Direction
- neon.event.task uses neon.types_impl.promise, so a change to neon.types_impl.promise can break neon.event.task, while a change to neon.event.task can't break neon.types_impl.promise.
- Position
- Below the diagonal: neon.event.task uses a module listed above it, which is the healthy direction.
28→8 neon.sys.promise uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.sys.promise uses a type in neon.context.internal.
- The types involved
neon.sys.promise.promise$module→neon.context.internal.Env
- Direction
- neon.sys.promise uses neon.context.internal, so a change to neon.context.internal can break neon.sys.promise, while a change to neon.sys.promise can't break neon.context.internal.
- Position
- Below the diagonal: neon.sys.promise uses a module listed above it, which is the healthy direction.
28→15 neon.sys.promise uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.sys.promise uses a type in neon.types_impl.
- The types involved
neon.sys.promise.promise$module→neon.types_impl.Value
- Direction
- neon.sys.promise uses neon.types_impl, so a change to neon.types_impl can break neon.sys.promise, while a change to neon.sys.promise can't break neon.types_impl.
- Position
- Below the diagonal: neon.sys.promise uses a module listed above it, which is the healthy direction.
28→26 neon.sys.promise uses neon.types_impl.promise✕
- Connections
- 1 pair of types, where a type in neon.sys.promise uses a type in neon.types_impl.promise.
- The types involved
neon.sys.promise.promise$module→neon.types_impl.promise.Deferred
- Direction
- neon.sys.promise uses neon.types_impl.promise, so a change to neon.types_impl.promise can break neon.sys.promise, while a change to neon.sys.promise can't break neon.types_impl.promise.
- Position
- Below the diagonal: neon.sys.promise uses a module listed above it, which is the healthy direction.
29→4 neon.context uses neon.types_impl.buffer.lock✕
- Connections
- 1 pair of types, where a type in neon.context uses a type in neon.types_impl.buffer.lock.
- The types involved
neon.context.Context→neon.types_impl.buffer.lock.Lock
- Direction
- neon.context uses neon.types_impl.buffer.lock, so a change to neon.types_impl.buffer.lock can break neon.context, while a change to neon.context can't break neon.types_impl.buffer.lock.
- Position
- Below the diagonal: neon.context uses a module listed above it, which is the healthy direction.
29→8 neon.context uses neon.context.internal✕
- Connections
- 10 pairs of types, where a type in neon.context uses a type in neon.context.internal.
- The types involved
neon.context.Context→neon.context.internal.ContextInternalneon.context.Context→neon.context.internal.Envneon.context.Cx→neon.context.internal.ContextInternalneon.context.Cx→neon.context.internal.Envneon.context.FunctionContext→neon.context.internal.ContextInternalneon.context.FunctionContext→neon.context.internal.Envneon.context.ModuleContext→neon.context.internal.ContextInternalneon.context.ModuleContext→neon.context.internal.Envneon.context.ScopedCx→neon.context.internal.ContextInternalneon.context.ScopedCx→neon.context.internal.Env
- Direction
- neon.context uses neon.context.internal, so a change to neon.context.internal can break neon.context, while a change to neon.context can't break neon.context.internal.
- Position
- Below the diagonal: neon.context uses a module listed above it, which is the healthy direction.
29→22 neon.context uses neon.handle✕
- Connections
- 3 pairs of types, where a type in neon.context uses a type in neon.handle.
- The types involved
neon.context.Context→neon.handle.Handleneon.context.FunctionContext→neon.handle.Handleneon.context.ModuleContext→neon.handle.Handle
- Direction
- neon.context uses neon.handle, so a change to neon.handle can break neon.context, while a change to neon.context can't break neon.handle.
- Position
- Below the diagonal: neon.context uses a module listed above it, which is the healthy direction.
29→25 neon.context uses neon.event.channel✕
- Connections
- 1 pair of types, where a type in neon.context uses a type in neon.event.channel.
- The types involved
neon.context.Context→neon.event.channel.Channel
- Direction
- neon.context uses neon.event.channel, so a change to neon.event.channel can break neon.context, while a change to neon.context can't break neon.event.channel.
- Position
- Below the diagonal: neon.context uses a module listed above it, which is the healthy direction.
29→27 neon.context uses neon.event.task✕
- Connections
- 1 pair of types, where a type in neon.context uses a type in neon.event.task.
- The types involved
neon.context.Context→neon.event.task.TaskBuilder
- Direction
- neon.context uses neon.event.task, so a change to neon.event.task can break neon.context, while a change to neon.context can't break neon.event.task.
- Position
- Below the diagonal: neon.context uses a module listed above it, which is the healthy direction.
30→20 neon.object.class uses neon.handle.root✕
- Connections
- 1 pair of types, where a type in neon.object.class uses a type in neon.handle.root.
- The types involved
neon.object.class.RootClassMetadata→neon.handle.root.Root
- Direction
- neon.object.class uses neon.handle.root, so a change to neon.handle.root can break neon.object.class, while a change to neon.object.class can't break neon.handle.root.
- Position
- Below the diagonal: neon.object.class uses a module listed above it, which is the healthy direction.
30→22 neon.object.class uses neon.handle✕
- Connections
- 2 pairs of types, where a type in neon.object.class uses a type in neon.handle.
- The types involved
neon.object.class.ClassMetadata→neon.handle.Handleneon.object.class.class$module→neon.handle.Handle
- Direction
- neon.object.class uses neon.handle, so a change to neon.handle can break neon.object.class, while a change to neon.object.class can't break neon.handle.
- Position
- Below the diagonal: neon.object.class uses a module listed above it, which is the healthy direction.
30→29 neon.object.class uses neon.context✕
- Connections
- 4 pairs of types, where a type in neon.object.class uses a type in neon.context.
- The types involved
neon.object.class.Class→neon.context.Cxneon.object.class.ClassInternal→neon.context.Cxneon.object.class.ClassMetadata→neon.context.Cxneon.object.class.RootClassMetadata→neon.context.Cx
- Direction
- neon.object.class uses neon.context, so a change to neon.context can break neon.object.class, while a change to neon.object.class can't break neon.context.
- Position
- Below the diagonal: neon.object.class uses a module listed above it, which is the healthy direction.
31→5 neon.object.wrap uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.object.wrap uses a type in neon.types_impl.buffer.private.
- The types involved
neon.object.wrap.WrapError→neon.types_impl.buffer.private.Sealed
- Direction
- neon.object.wrap uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.object.wrap, while a change to neon.object.wrap can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.object.wrap uses a module listed above it, which is the healthy direction.
31→9 neon.object.wrap uses neon.types_impl.extract.either✕
- Connections
- 1 pair of types, where a type in neon.object.wrap uses a type in neon.types_impl.extract.either.
- The types involved
neon.object.wrap.WrapError→neon.types_impl.extract.either.Error
- Direction
- neon.object.wrap uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.object.wrap, while a change to neon.object.wrap can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.object.wrap uses a module listed above it, which is the healthy direction.
31→22 neon.object.wrap uses neon.handle✕
- Connections
- 1 pair of types, where a type in neon.object.wrap uses a type in neon.handle.
- The types involved
neon.object.wrap.wrap$module→neon.handle.Handle
- Direction
- neon.object.wrap uses neon.handle, so a change to neon.handle can break neon.object.wrap, while a change to neon.object.wrap can't break neon.handle.
- Position
- Below the diagonal: neon.object.wrap uses a module listed above it, which is the healthy direction.
31→23 neon.object.wrap uses neon.types_impl.extract✕
- Connections
- 1 pair of types, where a type in neon.object.wrap uses a type in neon.types_impl.extract.
- The types involved
neon.object.wrap.WrapError→neon.types_impl.extract.TryIntoJs
- Direction
- neon.object.wrap uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.object.wrap, while a change to neon.object.wrap can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.object.wrap uses a module listed above it, which is the healthy direction.
31→29 neon.object.wrap uses neon.context✕
- Connections
- 2 pairs of types, where a type in neon.object.wrap uses a type in neon.context.
- The types involved
neon.object.wrap.WrapError→neon.context.Cxneon.object.wrap.wrap$module→neon.context.Cx
- Direction
- neon.object.wrap uses neon.context, so a change to neon.context can break neon.object.wrap, while a change to neon.object.wrap can't break neon.context.
- Position
- Below the diagonal: neon.object.wrap uses a module listed above it, which is the healthy direction.
32→2 neon.types_impl.buffer.types uses neon.handle.internal✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.handle.internal.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.buffer.types.JsBuffer→neon.handle.internal.TransparentNoCopyWrapperneon.types_impl.buffer.types.JsTypedArray→neon.handle.internal.TransparentNoCopyWrapper
- Direction
- neon.types_impl.buffer.types uses neon.handle.internal, so a change to neon.handle.internal can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.handle.internal.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→4 neon.types_impl.buffer.types uses neon.types_impl.buffer.lock✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.types_impl.buffer.lock.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.types_impl.buffer.lock.Lockneon.types_impl.buffer.types.JsBuffer→neon.types_impl.buffer.lock.Lockneon.types_impl.buffer.types.JsTypedArray→neon.types_impl.buffer.lock.Lock
- Direction
- neon.types_impl.buffer.types uses neon.types_impl.buffer.lock, so a change to neon.types_impl.buffer.lock can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.types_impl.buffer.lock.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→5 neon.types_impl.buffer.types uses neon.types_impl.buffer.private✕
- Connections
- 5 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.buffer.types.Binary→neon.types_impl.buffer.private.Sealedneon.types_impl.buffer.types.JsArrayBuffer→neon.types_impl.buffer.private.Sealedneon.types_impl.buffer.types.JsBuffer→neon.types_impl.buffer.private.Sealedneon.types_impl.buffer.types.JsTypedArray→neon.types_impl.buffer.private.JsTypedArrayInnerneon.types_impl.buffer.types.JsTypedArray→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.buffer.types uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→8 neon.types_impl.buffer.types uses neon.context.internal✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.context.internal.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.context.internal.Envneon.types_impl.buffer.types.JsBuffer→neon.context.internal.Env
- Direction
- neon.types_impl.buffer.types uses neon.context.internal, so a change to neon.context.internal can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.context.internal.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→13 neon.types_impl.buffer.types uses neon.sys.typedarray✕
- Connections
- 1 pair of types, where a type in neon.types_impl.buffer.types uses a type in neon.sys.typedarray.
- The types involved
neon.types_impl.buffer.types.types$module→neon.sys.typedarray.TypedArrayInfo
- Direction
- neon.types_impl.buffer.types uses neon.sys.typedarray, so a change to neon.sys.typedarray can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.sys.typedarray.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→14 neon.types_impl.buffer.types uses neon.types_impl.private✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.types_impl.private.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.types_impl.private.ValueInternalneon.types_impl.buffer.types.JsBuffer→neon.types_impl.private.ValueInternal
- Direction
- neon.types_impl.buffer.types uses neon.types_impl.private, so a change to neon.types_impl.private can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.types_impl.private.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→15 neon.types_impl.buffer.types uses neon.types_impl✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.types_impl.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.types_impl.Valueneon.types_impl.buffer.types.JsBuffer→neon.types_impl.Value
- Direction
- neon.types_impl.buffer.types uses neon.types_impl, so a change to neon.types_impl can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.types_impl.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→18 neon.types_impl.buffer.types uses neon.types_impl.buffer✕
- Connections
- 5 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.types_impl.buffer.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.types_impl.buffer.Regionneon.types_impl.buffer.types.JsArrayBuffer→neon.types_impl.buffer.TypedArrayneon.types_impl.buffer.types.JsBuffer→neon.types_impl.buffer.TypedArrayneon.types_impl.buffer.types.JsTypedArray→neon.types_impl.buffer.Regionneon.types_impl.buffer.types.JsTypedArray→neon.types_impl.buffer.TypedArray
- Direction
- neon.types_impl.buffer.types uses neon.types_impl.buffer, so a change to neon.types_impl.buffer can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.types_impl.buffer.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→21 neon.types_impl.buffer.types uses neon.object✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.object.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.object.Objectneon.types_impl.buffer.types.JsBuffer→neon.object.Object
- Direction
- neon.types_impl.buffer.types uses neon.object, so a change to neon.object can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.object.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→22 neon.types_impl.buffer.types uses neon.handle✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.handle.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.handle.Handleneon.types_impl.buffer.types.JsBuffer→neon.handle.Handleneon.types_impl.buffer.types.JsTypedArray→neon.handle.Handle
- Direction
- neon.types_impl.buffer.types uses neon.handle, so a change to neon.handle can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
32→29 neon.types_impl.buffer.types uses neon.context✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.buffer.types uses a type in neon.context.
- The types involved
neon.types_impl.buffer.types.JsArrayBuffer→neon.context.Cxneon.types_impl.buffer.types.JsBuffer→neon.context.Cx
- Direction
- neon.types_impl.buffer.types uses neon.context, so a change to neon.context can break neon.types_impl.buffer.types, while a change to neon.types_impl.buffer.types can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.buffer.types uses a module listed above it, which is the healthy direction.
33→2 neon.types_impl.date uses neon.handle.internal✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.handle.internal.
- The types involved
neon.types_impl.date.JsDate→neon.handle.internal.TransparentNoCopyWrapper
- Direction
- neon.types_impl.date uses neon.handle.internal, so a change to neon.handle.internal can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.handle.internal.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
33→8 neon.types_impl.date uses neon.context.internal✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.context.internal.
- The types involved
neon.types_impl.date.JsDate→neon.context.internal.Env
- Direction
- neon.types_impl.date uses neon.context.internal, so a change to neon.context.internal can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.context.internal.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
33→9 neon.types_impl.date uses neon.types_impl.extract.either✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.types_impl.extract.either.
- The types involved
neon.types_impl.date.DateError→neon.types_impl.extract.either.Error
- Direction
- neon.types_impl.date uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
33→14 neon.types_impl.date uses neon.types_impl.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.types_impl.private.
- The types involved
neon.types_impl.date.JsDate→neon.types_impl.private.ValueInternal
- Direction
- neon.types_impl.date uses neon.types_impl.private, so a change to neon.types_impl.private can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.types_impl.private.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
33→15 neon.types_impl.date uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.types_impl.
- The types involved
neon.types_impl.date.JsDate→neon.types_impl.Value
- Direction
- neon.types_impl.date uses neon.types_impl, so a change to neon.types_impl can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.types_impl.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
33→21 neon.types_impl.date uses neon.object✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.object.
- The types involved
neon.types_impl.date.JsDate→neon.object.Object
- Direction
- neon.types_impl.date uses neon.object, so a change to neon.object can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.object.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
33→22 neon.types_impl.date uses neon.handle✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.handle.
- The types involved
neon.types_impl.date.JsDate→neon.handle.Handle
- Direction
- neon.types_impl.date uses neon.handle, so a change to neon.handle can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
33→29 neon.types_impl.date uses neon.context✕
- Connections
- 1 pair of types, where a type in neon.types_impl.date uses a type in neon.context.
- The types involved
neon.types_impl.date.JsDate→neon.context.Cx
- Direction
- neon.types_impl.date uses neon.context, so a change to neon.context can break neon.types_impl.date, while a change to neon.types_impl.date can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.date uses a module listed above it, which is the healthy direction.
34→2 neon.types_impl.error uses neon.handle.internal✕
- Connections
- 1 pair of types, where a type in neon.types_impl.error uses a type in neon.handle.internal.
- The types involved
neon.types_impl.error.JsError→neon.handle.internal.TransparentNoCopyWrapper
- Direction
- neon.types_impl.error uses neon.handle.internal, so a change to neon.handle.internal can break neon.types_impl.error, while a change to neon.types_impl.error can't break neon.handle.internal.
- Position
- Below the diagonal: neon.types_impl.error uses a module listed above it, which is the healthy direction.
34→8 neon.types_impl.error uses neon.context.internal✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.error uses a type in neon.context.internal.
- The types involved
neon.types_impl.error.JsError→neon.context.internal.Envneon.types_impl.error.error$module→neon.context.internal.Env
- Direction
- neon.types_impl.error uses neon.context.internal, so a change to neon.context.internal can break neon.types_impl.error, while a change to neon.types_impl.error can't break neon.context.internal.
- Position
- Below the diagonal: neon.types_impl.error uses a module listed above it, which is the healthy direction.
34→14 neon.types_impl.error uses neon.types_impl.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.error uses a type in neon.types_impl.private.
- The types involved
neon.types_impl.error.JsError→neon.types_impl.private.ValueInternal
- Direction
- neon.types_impl.error uses neon.types_impl.private, so a change to neon.types_impl.private can break neon.types_impl.error, while a change to neon.types_impl.error can't break neon.types_impl.private.
- Position
- Below the diagonal: neon.types_impl.error uses a module listed above it, which is the healthy direction.
34→15 neon.types_impl.error uses neon.types_impl✕
- Connections
- 1 pair of types, where a type in neon.types_impl.error uses a type in neon.types_impl.
- The types involved
neon.types_impl.error.JsError→neon.types_impl.Value
- Direction
- neon.types_impl.error uses neon.types_impl, so a change to neon.types_impl can break neon.types_impl.error, while a change to neon.types_impl.error can't break neon.types_impl.
- Position
- Below the diagonal: neon.types_impl.error uses a module listed above it, which is the healthy direction.
34→21 neon.types_impl.error uses neon.object✕
- Connections
- 1 pair of types, where a type in neon.types_impl.error uses a type in neon.object.
- The types involved
neon.types_impl.error.JsError→neon.object.Object
- Direction
- neon.types_impl.error uses neon.object, so a change to neon.object can break neon.types_impl.error, while a change to neon.types_impl.error can't break neon.object.
- Position
- Below the diagonal: neon.types_impl.error uses a module listed above it, which is the healthy direction.
34→29 neon.types_impl.error uses neon.context✕
- Connections
- 1 pair of types, where a type in neon.types_impl.error uses a type in neon.context.
- The types involved
neon.types_impl.error.JsError→neon.context.Cx
- Direction
- neon.types_impl.error uses neon.context, so a change to neon.context can break neon.types_impl.error, while a change to neon.types_impl.error can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.error uses a module listed above it, which is the healthy direction.
35→5 neon.types_impl.extract.array uses neon.types_impl.buffer.private✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.extract.array uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.array.Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.array.ArrayError→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract.array uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract.array, while a change to neon.types_impl.extract.array can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract.array uses a module listed above it, which is the healthy direction.
35→9 neon.types_impl.extract.array uses neon.types_impl.extract.either✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.array uses a type in neon.types_impl.extract.either.
- The types involved
neon.types_impl.extract.array.ArrayError→neon.types_impl.extract.either.Error
- Direction
- neon.types_impl.extract.array uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.types_impl.extract.array, while a change to neon.types_impl.extract.array can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.types_impl.extract.array uses a module listed above it, which is the healthy direction.
35→22 neon.types_impl.extract.array uses neon.handle✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.array uses a type in neon.handle.
- The types involved
neon.types_impl.extract.array.Array→neon.handle.Handle
- Direction
- neon.types_impl.extract.array uses neon.handle, so a change to neon.handle can break neon.types_impl.extract.array, while a change to neon.types_impl.extract.array can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.extract.array uses a module listed above it, which is the healthy direction.
35→23 neon.types_impl.extract.array uses neon.types_impl.extract✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.extract.array uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.extract.array.Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.array.Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.array.ArrayError→neon.types_impl.extract.TryIntoJs
- Direction
- neon.types_impl.extract.array uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.extract.array, while a change to neon.types_impl.extract.array can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.types_impl.extract.array uses a module listed above it, which is the healthy direction.
35→29 neon.types_impl.extract.array uses neon.context✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.extract.array uses a type in neon.context.
- The types involved
neon.types_impl.extract.array.Array→neon.context.Cxneon.types_impl.extract.array.ArrayError→neon.context.Cx
- Direction
- neon.types_impl.extract.array uses neon.context, so a change to neon.context can break neon.types_impl.extract.array, while a change to neon.types_impl.extract.array can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.extract.array uses a module listed above it, which is the healthy direction.
36→5 neon.types_impl.extract.boxed uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.boxed uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.boxed.Boxed→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract.boxed uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract.boxed, while a change to neon.types_impl.extract.boxed can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract.boxed uses a module listed above it, which is the healthy direction.
36→22 neon.types_impl.extract.boxed uses neon.handle✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.boxed uses a type in neon.handle.
- The types involved
neon.types_impl.extract.boxed.Boxed→neon.handle.Handle
- Direction
- neon.types_impl.extract.boxed uses neon.handle, so a change to neon.handle can break neon.types_impl.extract.boxed, while a change to neon.types_impl.extract.boxed can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.extract.boxed uses a module listed above it, which is the healthy direction.
36→23 neon.types_impl.extract.boxed uses neon.types_impl.extract✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.extract.boxed uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.extract.boxed.Boxed→neon.types_impl.extract.TryFromJsneon.types_impl.extract.boxed.Boxed→neon.types_impl.extract.TryIntoJs
- Direction
- neon.types_impl.extract.boxed uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.extract.boxed, while a change to neon.types_impl.extract.boxed can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.types_impl.extract.boxed uses a module listed above it, which is the healthy direction.
36→29 neon.types_impl.extract.boxed uses neon.context✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.boxed uses a type in neon.context.
- The types involved
neon.types_impl.extract.boxed.Boxed→neon.context.Cx
- Direction
- neon.types_impl.extract.boxed uses neon.context, so a change to neon.context can break neon.types_impl.extract.boxed, while a change to neon.types_impl.extract.boxed can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.extract.boxed uses a module listed above it, which is the healthy direction.
37→5 neon.types_impl.extract.buffer uses neon.types_impl.buffer.private✕
- Connections
- 12 pairs of types, where a type in neon.types_impl.extract.buffer uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.buffer.ArrayBuffer→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.BigInt64Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.BigUint64Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Buffer→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Float32Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Float64Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Int16Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Int32Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Int8Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Uint16Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Uint32Array→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.buffer.Uint8Array→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract.buffer uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract.buffer, while a change to neon.types_impl.extract.buffer can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract.buffer uses a module listed above it, which is the healthy direction.
37→22 neon.types_impl.extract.buffer uses neon.handle✕
- Connections
- 12 pairs of types, where a type in neon.types_impl.extract.buffer uses a type in neon.handle.
- The types involved
neon.types_impl.extract.buffer.ArrayBuffer→neon.handle.Handleneon.types_impl.extract.buffer.BigInt64Array→neon.handle.Handleneon.types_impl.extract.buffer.BigUint64Array→neon.handle.Handleneon.types_impl.extract.buffer.Buffer→neon.handle.Handleneon.types_impl.extract.buffer.Float32Array→neon.handle.Handleneon.types_impl.extract.buffer.Float64Array→neon.handle.Handleneon.types_impl.extract.buffer.Int16Array→neon.handle.Handleneon.types_impl.extract.buffer.Int32Array→neon.handle.Handleneon.types_impl.extract.buffer.Int8Array→neon.handle.Handleneon.types_impl.extract.buffer.Uint16Array→neon.handle.Handleneon.types_impl.extract.buffer.Uint32Array→neon.handle.Handleneon.types_impl.extract.buffer.Uint8Array→neon.handle.Handle
- Direction
- neon.types_impl.extract.buffer uses neon.handle, so a change to neon.handle can break neon.types_impl.extract.buffer, while a change to neon.types_impl.extract.buffer can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.extract.buffer uses a module listed above it, which is the healthy direction.
37→23 neon.types_impl.extract.buffer uses neon.types_impl.extract✕
- Connections
- 24 pairs of types, where a type in neon.types_impl.extract.buffer uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.extract.buffer.ArrayBuffer→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.ArrayBuffer→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.BigInt64Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.BigInt64Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.BigUint64Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.BigUint64Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Buffer→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Buffer→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Float32Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Float32Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Float64Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Float64Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Int16Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Int16Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Int32Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Int32Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Int8Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Int8Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Uint16Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Uint16Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Uint32Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Uint32Array→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.buffer.Uint8Array→neon.types_impl.extract.TryFromJsneon.types_impl.extract.buffer.Uint8Array→neon.types_impl.extract.TryIntoJs
- Direction
- neon.types_impl.extract.buffer uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.extract.buffer, while a change to neon.types_impl.extract.buffer can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.types_impl.extract.buffer uses a module listed above it, which is the healthy direction.
37→29 neon.types_impl.extract.buffer uses neon.context✕
- Connections
- 12 pairs of types, where a type in neon.types_impl.extract.buffer uses a type in neon.context.
- The types involved
neon.types_impl.extract.buffer.ArrayBuffer→neon.context.Cxneon.types_impl.extract.buffer.BigInt64Array→neon.context.Cxneon.types_impl.extract.buffer.BigUint64Array→neon.context.Cxneon.types_impl.extract.buffer.Buffer→neon.context.Cxneon.types_impl.extract.buffer.Float32Array→neon.context.Cxneon.types_impl.extract.buffer.Float64Array→neon.context.Cxneon.types_impl.extract.buffer.Int16Array→neon.context.Cxneon.types_impl.extract.buffer.Int32Array→neon.context.Cxneon.types_impl.extract.buffer.Int8Array→neon.context.Cxneon.types_impl.extract.buffer.Uint16Array→neon.context.Cxneon.types_impl.extract.buffer.Uint32Array→neon.context.Cxneon.types_impl.extract.buffer.Uint8Array→neon.context.Cx
- Direction
- neon.types_impl.extract.buffer uses neon.context, so a change to neon.context can break neon.types_impl.extract.buffer, while a change to neon.types_impl.extract.buffer can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.extract.buffer uses a module listed above it, which is the healthy direction.
38→5 neon.types_impl.extract.error uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.error uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.error.TypeExpected→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract.error uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract.error, while a change to neon.types_impl.extract.error can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract.error uses a module listed above it, which is the healthy direction.
38→9 neon.types_impl.extract.error uses neon.types_impl.extract.either✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.error uses a type in neon.types_impl.extract.either.
- The types involved
neon.types_impl.extract.error.TypeExpected→neon.types_impl.extract.either.Error
- Direction
- neon.types_impl.extract.error uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.types_impl.extract.error, while a change to neon.types_impl.extract.error can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.types_impl.extract.error uses a module listed above it, which is the healthy direction.
38→23 neon.types_impl.extract.error uses neon.types_impl.extract✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.extract.error uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.extract.error.Error→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.error.TypeExpected→neon.types_impl.extract.TryIntoJs
- Direction
- neon.types_impl.extract.error uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.extract.error, while a change to neon.types_impl.extract.error can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.types_impl.extract.error uses a module listed above it, which is the healthy direction.
38→29 neon.types_impl.extract.error uses neon.context✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.extract.error uses a type in neon.context.
- The types involved
neon.types_impl.extract.error.Error→neon.context.Cxneon.types_impl.extract.error.TypeExpected→neon.context.Cx
- Direction
- neon.types_impl.extract.error uses neon.context, so a change to neon.context can break neon.types_impl.extract.error, while a change to neon.types_impl.extract.error can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.extract.error uses a module listed above it, which is the healthy direction.
39→5 neon.types_impl.extract.json uses neon.types_impl.buffer.private✕
- Connections
- 2 pairs of types, where a type in neon.types_impl.extract.json uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.json.Error→neon.types_impl.buffer.private.Sealedneon.types_impl.extract.json.Json→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract.json uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract.json, while a change to neon.types_impl.extract.json can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract.json uses a module listed above it, which is the healthy direction.
39→9 neon.types_impl.extract.json uses neon.types_impl.extract.either✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.json uses a type in neon.types_impl.extract.either.
- The types involved
neon.types_impl.extract.json.Error→neon.types_impl.extract.either.Error
- Direction
- neon.types_impl.extract.json uses neon.types_impl.extract.either, so a change to neon.types_impl.extract.either can break neon.types_impl.extract.json, while a change to neon.types_impl.extract.json can't break neon.types_impl.extract.either.
- Position
- Below the diagonal: neon.types_impl.extract.json uses a module listed above it, which is the healthy direction.
39→22 neon.types_impl.extract.json uses neon.handle✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.json uses a type in neon.handle.
- The types involved
neon.types_impl.extract.json.Json→neon.handle.Handle
- Direction
- neon.types_impl.extract.json uses neon.handle, so a change to neon.handle can break neon.types_impl.extract.json, while a change to neon.types_impl.extract.json can't break neon.handle.
- Position
- Below the diagonal: neon.types_impl.extract.json uses a module listed above it, which is the healthy direction.
39→23 neon.types_impl.extract.json uses neon.types_impl.extract✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.extract.json uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.extract.json.Error→neon.types_impl.extract.TryIntoJsneon.types_impl.extract.json.Json→neon.types_impl.extract.TryFromJsneon.types_impl.extract.json.Json→neon.types_impl.extract.TryIntoJs
- Direction
- neon.types_impl.extract.json uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.extract.json, while a change to neon.types_impl.extract.json can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.types_impl.extract.json uses a module listed above it, which is the healthy direction.
39→29 neon.types_impl.extract.json uses neon.context✕
- Connections
- 3 pairs of types, where a type in neon.types_impl.extract.json uses a type in neon.context.
- The types involved
neon.types_impl.extract.json.Error→neon.context.Cxneon.types_impl.extract.json.Json→neon.context.Cxneon.types_impl.extract.json.json$module→neon.context.Cx
- Direction
- neon.types_impl.extract.json uses neon.context, so a change to neon.context can break neon.types_impl.extract.json, while a change to neon.types_impl.extract.json can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.extract.json uses a module listed above it, which is the healthy direction.
40→5 neon.types_impl.extract.with uses neon.types_impl.buffer.private✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.with uses a type in neon.types_impl.buffer.private.
- The types involved
neon.types_impl.extract.with.With→neon.types_impl.buffer.private.Sealed
- Direction
- neon.types_impl.extract.with uses neon.types_impl.buffer.private, so a change to neon.types_impl.buffer.private can break neon.types_impl.extract.with, while a change to neon.types_impl.extract.with can't break neon.types_impl.buffer.private.
- Position
- Below the diagonal: neon.types_impl.extract.with uses a module listed above it, which is the healthy direction.
40→23 neon.types_impl.extract.with uses neon.types_impl.extract✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.with uses a type in neon.types_impl.extract.
- The types involved
neon.types_impl.extract.with.With→neon.types_impl.extract.TryIntoJs
- Direction
- neon.types_impl.extract.with uses neon.types_impl.extract, so a change to neon.types_impl.extract can break neon.types_impl.extract.with, while a change to neon.types_impl.extract.with can't break neon.types_impl.extract.
- Position
- Below the diagonal: neon.types_impl.extract.with uses a module listed above it, which is the healthy direction.
40→29 neon.types_impl.extract.with uses neon.context✕
- Connections
- 1 pair of types, where a type in neon.types_impl.extract.with uses a type in neon.context.
- The types involved
neon.types_impl.extract.with.With→neon.context.Cx
- Direction
- neon.types_impl.extract.with uses neon.context, so a change to neon.context can break neon.types_impl.extract.with, while a change to neon.types_impl.extract.with can't break neon.context.
- Position
- Below the diagonal: neon.types_impl.extract.with uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 28 | High / Critical |
| A05:2025 — Injection | 18 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
First, establish observability by adding diagnostic logging to error paths so users can provide reproducible bug reports. Second, improve test coverage by adding tests for currently unreached production modules to ensure code reliability. Third, enable automated dependency management and security scanning to catch vulnerabilities and outdated packages early. Fourth, resolve the existing high-severity dependency vulnerabilities to secure the application. Finally, document significant architectural decisions to preserve institutional knowledge and guide future development.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +6.8 pts | Medium | Observability |
| Add tests that import the unreached modules (directly or through their public entry). | +5.6 pts | Medium | Test Coverage |
| Enable Dependabot/Renovate or a dependency-review gate. | +3.6 pts | Medium | Security & performance tooling |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.4 pts | Low | Static Analysis (SAST) |
| Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). | +1.3 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). | +1.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secrets (history): High secret: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.1 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| crates/neon/src/types_impl/bigint.rs | 6.7 | Mixed | Explicit Debt: XxxComment |
| crates/neon-macros/src/class/mod.rs | 7.0 | Mixed | Cyclomatic Complexity: neon_macros::class::class_with_name (cyclomatic 40) |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| crates/neon-macros/src/export/class/meta.rs | 7.4 | Mixed | Cognitive Complexity: Meta::parse (cognitive 17) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| crates/neon/src/sys/call.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| crates/neon/src/sys/no_panic.rs | 8.2 | Near-clean | Explicit Debt: HackComment |
| crates/neon-macros/src/export/class.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (4–6 lines × 3) |
| crates/neon-macros/src/export/mod.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| crates/neon/src/event/channel.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| crates/neon/src/sys/array.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| crates/neon/src/sys/arraybuffer.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| crates/neon/src/handle/root.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| crates/neon/src/types_impl/buffer/types.rs | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: JsTypedArray (LCOM4 8) |
| crates/neon/src/handle/mod.rs | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Handle (LCOM4 5) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 67 of 67 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 67 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, 129 of 155 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 60 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .rs, and the rust executor ran against the .rs half and never executed — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (mocha via `npm ci --ignore-scripts` in pkgs/cargo-cp-artifact/ (10 tests); mocha via `npm ci --ignore-scripts` in pkgs/create-neon/ (0 tests); mocha via `npm ci --ignore-scripts` in test/napi/): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- 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.
- 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.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was neon_macros::class::class_with_name at 40.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with neon_macros::class::class_with_name (cyclomatic 40), neon_macros::class::generate_method_wrapper (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was neon_macros::class::class_with_name at 89.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with neon_macros::class::class_with_name (cognitive 89), neon_macros::class::validate_method_attributes (cognitive 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.8 to about 9.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with mod.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
24 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), meta.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), bigint.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), arraybuffer.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
7 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 7 (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).
D6 · Cohesion (LCOM4)
3 of 59 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with types.rs, mod.rs, meta.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
7 test methods: 7 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 1 `it`/`test` case(s) across 1 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 6 `#[test]` function(s) across 4 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests. Measured on the JavaScript/TypeScript suite only — at least 60 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
12 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 76 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/neon/src/macros.rs. Counted over 60 of the 105 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
3 deducted task-comment markers across 16914 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with bigint.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with call.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with no_panic.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 8 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 4 build units (Cargo, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
18 finding(s): 0 critical, 17 high, 1 medium, 0 low. 14 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 14 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 (14 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
28 finding(s): 2 critical, 14 high, 10 medium, 2 low.
What to do
- Resolve the 13 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
16 of 60 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/neon-macros/src/class/mod.rs. Counted over 60 of the 105 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 15 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), meta.rs (2), wrap.rs. — One of this dimension's main actionable groups (15 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: async_work.rs↔tsfn.rs 55%; prelude.rs↔mod.rs 53%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with async_work.rs, prelude.rs. — One of this dimension's main actionable groups (2 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 2 of 5 project(s) that lack one — worth up to 0.8 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `existsSync` in `cleanupTmp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — pkgs/create-neon/src/fs.ts:17
- `rmSync` in `cleanupTmp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — pkgs/create-neon/src/fs.ts:18
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
- 17 typed · 27 plain JS — the untyped files are pkgs/cargo-cp-artifact/src/args.js, REDACTED, pkgs/cargo-cp-artifact/test/args.js, test/electron/main.js, test/electron/main.test.js, test/electron/preload.js (+21 more).
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- pkgs/create-neon/src/create/creator.ts:69 · pkgs/create-neon/src/create/creator.ts:127 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pkgs/create-neon/src/create/creator.ts:69
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×14) — REDACTED:1, pkgs/create-neon/src/create/creator.ts:1, pkgs/create-neon/src/index.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- 20 file(s) (~3679 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — test/napi
- Unreachable from the 5 application, 1 tooling and 26 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (5 application, 1 tooling, 26 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — pkgs/create-neon/src/print.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
- pkgs/create-neon/src/create/app.ts → pkgs/create-neon/src/create/creator.ts → pkgs/create-neon/src/create/app.ts (one verified cycle inside a mutually-dependent group of 3 files) — pkgs/create-neon/src/create/app.ts:1
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — REDACTED:127, REDACTED:157
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~9.2 `!` null assertions per 1k TypeScript source lines — 11 assertion(s) across the 1195 source line(s) of the 16 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: pkgs/create-neon/dev/expect.ts (3), pkgs/create-neon/src/create/lib.ts (3), pkgs/create-neon/src/index.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 66% | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Exemplary | Strongest area. |
| Maturity | 64% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Weak — gated by R4, P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D30 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 70% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; 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; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in 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.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named 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.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, 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+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, .ts, 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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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: the JavaScript/TypeScript half could not be measured — pkgs/cargo-cp-artifact/ runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (68 value object(s))
- 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 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — 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
- M4 Documentation accuracy — Not applicable: the 8 current-state document(s) make no claim of a kind M4 checks. 12 claim(s) of kinds M4 does not check were not checked (path 2, command argument 9, environment variable 1); M4 checks only links and versions.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[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 applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb. TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — No web surface: 88 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's 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.
- 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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 39 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite declares a test script but contains no test files: pkgs/create-neon/
- Test suite aborts before any test executes: test/napi/
- REDACTED
- REDACTED
- Orphaned knowledge crates/neon-macros/src/class/mod.rs:1
- Import cycle (2 files) pkgs/create-neon/src/create/app.ts:1
Serious — 78 finding(s)
- No test reaches this file REDACTED:1
- No test reaches this file pkgs/create-neon/src/create/creator.ts:1
- No test reaches this file pkgs/create-neon/src/index.ts:1
- No test reaches this file pkgs/create-neon/src/create/lib.ts:1
- No test reaches this file pkgs/create-neon/src/print.ts:1
- No test reaches this file pkgs/create-neon/src/expand/versions.ts:1
- No test reaches this file pkgs/create-neon/src/ci/github.ts:1
- No test reaches this file pkgs/create-neon/src/expand/context.ts:1
- No test reaches this file pkgs/create-neon/src/fs.ts:1
- No test reaches this file pkgs/create-neon/src/expand/index.ts:1
- No test reaches this file pkgs/create-neon/src/create/app.ts:1
- No test reaches this file pkgs/create-neon/src/die.ts:1
- No test reaches this file pkgs/create-neon/src/cache/npm.ts:1
- No test reaches this file pkgs/cargo-cp-artifact/bin/cargo-cp-artifact.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- neon_macros::class::class_with_name (cognitive 89) crates/neon-macros/src/class/mod.rs:828
- neon_macros::class::validate_method_attributes (cognitive 34) crates/neon-macros/src/class/mod.rs:529
- neon_macros::class::generate_method_wrapper (cognitive 21) crates/neon-macros/src/class/mod.rs:64
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) crates/neon-macros/src/class/mod.rs:371
- Duplicated block (7 lines × 2) crates/neon-macros/src/class/mod.rs:870
- Duplicated block (7 lines × 2) crates/neon-macros/src/export/class/meta.rs:31
- Duplicated block (6 lines × 2) crates/neon-macros/src/export/mod.rs:25
- Duplicated block (6 lines × 2) crates/neon/src/types_impl/bigint.rs:270
- Duplicated block (6 lines × 2) crates/neon-macros/src/class/mod.rs:1330
- Duplicated block (8 lines × 2) crates/neon-macros/src/class/mod.rs:500
- Duplicated block (8 lines × 2) crates/neon-macros/src/class/mod.rs:519
- Duplicated block (8 lines × 2) crates/neon/src/sys/arraybuffer.rs:69
- Low cohesion: JsTypedArray (LCOM4 8) crates/neon/src/types_impl/buffer/types.rs:527
- Low cohesion: Handle (LCOM4 5) crates/neon/src/handle/mod.rs:70
- Low cohesion: Meta (LCOM4 5) crates/neon-macros/src/export/function/meta.rs:2
- neon_macros::class::class_with_name (cyclomatic 40) crates/neon-macros/src/class/mod.rs:828
- neon_macros::class::generate_method_wrapper (cyclomatic 16) crates/neon-macros/src/class/mod.rs:64
- FunctionTooLong: neon_macros::class::class_with_name crates/neon-macros/src/class/mod.rs:828
- FunctionTooLong: neon_macros::class::generate_method_wrapper crates/neon-macros/src/class/mod.rs:64
- Change coupling: async_work.rs ↔ tsfn.rs crates/neon/src/sys/async_work.rs:1
- Change coupling: prelude.rs ↔ mod.rs crates/neon/src/prelude.rs:1
- REDACTED
- REDACTED
- Duplicated block (16 lines × 3) crates/neon-macros/src/class/mod.rs:211
- Duplicated block (16 lines × 3) crates/neon-macros/src/class/mod.rs:416
- Duplicated block (5 lines × 2) crates/neon-macros/src/class/mod.rs:234
- Duplicated block (5 lines × 2) crates/neon/src/sys/array.rs:17
- Duplicated block (14 lines × 2) crates/neon/src/event/channel.rs:275
- Duplicated block (14 lines × 2) crates/neon-macros/src/export/class/meta.rs:40
- Sync-over-async blocking pkgs/create-neon/src/fs.ts:17
- Sync-over-async blocking pkgs/create-neon/src/fs.ts:18
- Swallowed exception (empty catch) REDACTED:127
- Swallowed exception (empty catch) REDACTED:157
- XxxComment crates/neon/src/types_impl/bigint.rs:187
- TodoComment crates/neon/src/sys/call.rs:52
- HackComment crates/neon/src/sys/no_panic.rs:126
- Meta::parse (cognitive 17) crates/neon-macros/src/export/class/meta.rs:13
- REDACTED
- FileTooLong: class/mod.rs crates/neon-macros/src/class/mod.rs
- REDACTED
- Duplicated block (33 lines × 2) crates/neon-macros/src/class/mod.rs:436
- Duplicated block (21 lines × 2) crates/neon-macros/src/class/mod.rs:383
- Duplicated block (17 lines × 2) crates/neon-macros/src/class/mod.rs:194
- Duplicated block (16 lines × 2) crates/neon-macros/src/class/mod.rs:629
- Duplicated block (11–13 lines × 2) crates/neon-macros/src/class/mod.rs:180
- Duplicated block (12 lines × 4) crates/neon-macros/src/class/mod.rs:206
- Duplicated block (4–6 lines × 3) crates/neon-macros/src/export/class.rs:54
- Duplicated block (15 lines × 2) crates/neon-macros/src/class/mod.rs:477
- Duplicated block (13 lines × 2) crates/neon/src/handle/root.rs:212
- Coverage not measured — JavaScript/TypeScript suite
- Coverage collected but not gated
- No structured logging
- Type Safety
- Duplicated block (8 lines × 2 locations) pkgs/create-neon/src/create/creator.ts:69
- Dead file (~107 LoC) pkgs/create-neon/src/print.ts
Minor — 26 finding(s)
- Orphaned file crates/neon/src/types_impl/function/mod.rs:1
- Orphaned file crates/neon/src/thread/mod.rs:1
- Orphaned file crates/neon/src/object/wrap.rs:1
- Orphaned file crates/neon/src/types_docs.rs:1
- Orphaned file REDACTED:1
- Orphaned file pkgs/create-neon/dev/expect.ts:1
- Orphaned file pkgs/create-neon/src/create/creator.ts:1
- Orphaned file crates/neon-macros/src/name.rs:1
- Orphaned file pkgs/create-neon/src/index.ts:1
- Orphaned file pkgs/create-neon/src/create/lib.ts:1
- Orphaned file crates/neon/src/types_impl/extract/container.rs:1
- Orphaned file crates/neon-macros/src/export/class.rs:1
- Orphaned file crates/neon-macros/src/class/meta.rs:1
- Orphaned file crates/neon-macros/src/export/class/meta.rs:1
- Orphaned file pkgs/create-neon/src/print.ts:1
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- No ADRs
- Duplicated predicate crates/neon-macros/src/class/mod.rs:506
- Null assertions (`!`) reduce the strict null checking score
Minor — 12 finding(s)
- Outdated: doc-comment
- Outdated: either
- Outdated: linkme
- Outdated: once_cell
- Outdated: proc-macro2
- Outdated: quote
- Outdated: rustversion
- Outdated: semver
- Outdated: serde
- Outdated: serde_json
- Outdated: smallvec
- Outdated: tokio
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4842c8fcb9e8418996a2338199d5d014/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4842c8fcb9e8418996a2338199d5d014/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 18 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 28 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |