Executive summary
hyoo-ru/mam_mol falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 33.0 out of 100 and is rated Weak, and 88 of its 98 critical findings are security problems in the build pipeline.
Production Readiness, at 22.6, is the weakest lens and counts most in the score. The best first steps are adopting a logging library and adding automated security scanning, each worth about 4.3 points. Raising Production Readiness to 70 would lift the score to about 41.3.
Sixty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-six secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks. The four pages or frames without a title need a descriptive title.
The product code is 54,228 lines, about €56,000 to rebuild.
If Production Readiness rose from 22.6 to 70, the lowest score rated Strong, the score would rise from 33.0 to about 41.3.
Rebuild cost: about €56,000 · Estimate
| Cost to rebuild | €18,000 to €93,000, for 307 to 975 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 33. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 54,228 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: which parts of the code depend on which
| uses → | 1 buffer.buffer | 2 jsx.jsx | 3 mem.force.force | 4 object2.object2 | 5 schema.any.any | 6 time.moment.moment | 7 wire.dom.dom | 8 after.timeout.timeout | 9 crypto.sacred.sacred | 10 crypto2.key.key | 11 dom.point.point | 12 object.object | 13 store.store | 14 wrapper.wrapper | 15 app.supplies.domain.domain | 16 audio.node.node | 17 crypto2.auditor.auditor | 18 dom.range.range | 19 file.base.base | 20 http.http | 21 layout.layout | 22 model.model | 23 rest.port.port | 24 rpc.rpc | 25 view.view.view | 26 wire.fiber.fiber | 27 audio.instrument.instrument | 28 github.entity.entity | 29 layout.tree.tree | 30 plugin.plugin | 31 rest.message.message_node | 32 rest.port.ws.ws | 33 github.user.user | 34 layout.flex.flex | 35 layout.stack.stack | 36 rest.resource.resource_node | 37 github.comment.comment | 38 rest.server.server_node | 39 github.issue.issue | 40 github.repository.repository |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 buffer.buffer | ||||||||||||||||||||||||||||||||||||||||
| 2 jsx.jsx | ||||||||||||||||||||||||||||||||||||||||
| 3 mem.force.force | ||||||||||||||||||||||||||||||||||||||||
| 4 object2.object2 | ||||||||||||||||||||||||||||||||||||||||
| 5 schema.any.any | ||||||||||||||||||||||||||||||||||||||||
| 6 time.moment.moment | ||||||||||||||||||||||||||||||||||||||||
| 7 wire.dom.dom | ||||||||||||||||||||||||||||||||||||||||
| 8 after.timeout.timeout | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 crypto.sacred.sacred | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 crypto2.key.key | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 dom.point.point | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 object.object | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 store.store | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 wrapper.wrapper | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 app.supplies.domain.domain | 1 | 14 | ||||||||||||||||||||||||||||||||||||||
| 16 audio.node.node | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 crypto2.auditor.auditor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 dom.range.range | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 file.base.base | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 http.http | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 layout.layout | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 model.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 rest.port.port | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 rpc.rpc | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 view.view.view | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 wire.fiber.fiber | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 audio.instrument.instrument | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 github.entity.entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 layout.tree.tree | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 plugin.plugin | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 rest.message.message_node | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 rest.port.ws.ws | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 github.user.user | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 layout.flex.flex | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 layout.stack.stack | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 rest.resource.resource_node | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 github.comment.comment | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 rest.server.server_node | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 github.issue.issue | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 github.repository.repository | 1 | 1 | 1 | 1 | 1 |
8→4 after.timeout.timeout uses object2.object2✕
- Connections
- 1 pair of types, where a type in after.timeout.timeout uses a type in object2.object2.
- The types involved
after.timeout.timeout.$mol_after_timeout→object2.object2.$mol_object2
- Direction
- after.timeout.timeout uses object2.object2, so a change to object2.object2 can break after.timeout.timeout, while a change to after.timeout.timeout can't break object2.object2.
- Position
- Below the diagonal: after.timeout.timeout uses a module listed above it, which is the healthy direction.
9→1 crypto.sacred.sacred uses buffer.buffer✕
- Connections
- 1 pair of types, where a type in crypto.sacred.sacred uses a type in buffer.buffer.
- The types involved
crypto.sacred.sacred.$mol_crypto_sacred→buffer.buffer.$mol_buffer
- Direction
- crypto.sacred.sacred uses buffer.buffer, so a change to buffer.buffer can break crypto.sacred.sacred, while a change to crypto.sacred.sacred can't break buffer.buffer.
- Position
- Below the diagonal: crypto.sacred.sacred uses a module listed above it, which is the healthy direction.
10→1 crypto2.key.key uses buffer.buffer✕
- Connections
- 1 pair of types, where a type in crypto2.key.key uses a type in buffer.buffer.
- The types involved
crypto2.key.key.$mol_crypto2_key→buffer.buffer.$mol_buffer
- Direction
- crypto2.key.key uses buffer.buffer, so a change to buffer.buffer can break crypto2.key.key, while a change to crypto2.key.key can't break buffer.buffer.
- Position
- Below the diagonal: crypto2.key.key uses a module listed above it, which is the healthy direction.
11→2 dom.point.point uses jsx.jsx✕
- Connections
- 1 pair of types, where a type in dom.point.point uses a type in jsx.jsx.
- The types involved
dom.point.point.$mol_dom_point→jsx.jsx.Element
- Direction
- dom.point.point uses jsx.jsx, so a change to jsx.jsx can break dom.point.point, while a change to dom.point.point can't break jsx.jsx.
- Position
- Below the diagonal: dom.point.point uses a module listed above it, which is the healthy direction.
11→7 dom.point.point uses wire.dom.dom✕
- Connections
- 1 pair of types, where a type in dom.point.point uses a type in wire.dom.dom.
- The types involved
dom.point.point.$mol_dom_point→wire.dom.dom.Node
- Direction
- dom.point.point uses wire.dom.dom, so a change to wire.dom.dom can break dom.point.point, while a change to dom.point.point can't break wire.dom.dom.
- Position
- Below the diagonal: dom.point.point uses a module listed above it, which is the healthy direction.
12→4 object.object uses object2.object2✕
- Connections
- 1 pair of types, where a type in object.object uses a type in object2.object2.
- The types involved
object.object.$mol_object→object2.object2.$mol_object2
- Direction
- object.object uses object2.object2, so a change to object2.object2 can break object.object, while a change to object.object can't break object2.object2.
- Position
- Below the diagonal: object.object uses a module listed above it, which is the healthy direction.
13→4 store.store uses object2.object2✕
- Connections
- 1 pair of types, where a type in store.store uses a type in object2.object2.
- The types involved
store.store.$mol_store→object2.object2.$mol_object2
- Direction
- store.store uses object2.object2, so a change to object2.object2 can break store.store, while a change to store.store can't break object2.object2.
- Position
- Below the diagonal: store.store uses a module listed above it, which is the healthy direction.
14→4 wrapper.wrapper uses object2.object2✕
- Connections
- 1 pair of types, where a type in wrapper.wrapper uses a type in object2.object2.
- The types involved
wrapper.wrapper.$mol_wrapper→object2.object2.$mol_object2
- Direction
- wrapper.wrapper uses object2.object2, so a change to object2.object2 can break wrapper.wrapper, while a change to wrapper.wrapper can't break object2.object2.
- Position
- Below the diagonal: wrapper.wrapper uses a module listed above it, which is the healthy direction.
15→6 app.supplies.domain.domain uses time.moment.moment✕
- Connections
- 1 pair of types, where a type in app.supplies.domain.domain uses a type in time.moment.moment.
- The types involved
app.supplies.domain.domain.$mol_app_supplies_domain_supply_position→time.moment.moment.$mol_time_moment
- Direction
- app.supplies.domain.domain uses time.moment.moment, so a change to time.moment.moment can break app.supplies.domain.domain, while a change to app.supplies.domain.domain can't break time.moment.moment.
- Position
- Below the diagonal: app.supplies.domain.domain uses a module listed above it, which is the healthy direction.
15→12 app.supplies.domain.domain uses object.object✕
- Connections
- 14 pairs of types, where a type in app.supplies.domain.domain uses a type in object.object.
- The types involved
app.supplies.domain.domain.$mol_app_supplies_domain_attachment→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_ballance_unit→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_consumer→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_contract→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_debitor→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_mock→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_pay_method→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_person→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_provider→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_store→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_supply→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_supply_division→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_supply_group→object.object.$mol_objectapp.supplies.domain.domain.$mol_app_supplies_domain_supply_position→object.object.$mol_object
- Direction
- app.supplies.domain.domain uses object.object, so a change to object.object can break app.supplies.domain.domain, while a change to app.supplies.domain.domain can't break object.object.
- Position
- Below the diagonal: app.supplies.domain.domain uses a module listed above it, which is the healthy direction.
16→12 audio.node.node uses object.object✕
- Connections
- 1 pair of types, where a type in audio.node.node uses a type in object.object.
- The types involved
audio.node.node.$mol_audio_node→object.object.$mol_object
- Direction
- audio.node.node uses object.object, so a change to object.object can break audio.node.node, while a change to audio.node.node can't break object.object.
- Position
- Below the diagonal: audio.node.node uses a module listed above it, which is the healthy direction.
17→9 crypto2.auditor.auditor uses crypto.sacred.sacred✕
- Connections
- 1 pair of types, where a type in crypto2.auditor.auditor uses a type in crypto.sacred.sacred.
- The types involved
crypto2.auditor.auditor.$mol_crypto2_auditor→crypto.sacred.sacred.BufferSource
- Direction
- crypto2.auditor.auditor uses crypto.sacred.sacred, so a change to crypto.sacred.sacred can break crypto2.auditor.auditor, while a change to crypto2.auditor.auditor can't break crypto.sacred.sacred.
- Position
- Below the diagonal: crypto2.auditor.auditor uses a module listed above it, which is the healthy direction.
17→10 crypto2.auditor.auditor uses crypto2.key.key✕
- Connections
- 1 pair of types, where a type in crypto2.auditor.auditor uses a type in crypto2.key.key.
- The types involved
crypto2.auditor.auditor.$mol_crypto2_auditor→crypto2.key.key.$mol_crypto2_key
- Direction
- crypto2.auditor.auditor uses crypto2.key.key, so a change to crypto2.key.key can break crypto2.auditor.auditor, while a change to crypto2.auditor.auditor can't break crypto2.key.key.
- Position
- Below the diagonal: crypto2.auditor.auditor uses a module listed above it, which is the healthy direction.
18→2 dom.range.range uses jsx.jsx✕
- Connections
- 1 pair of types, where a type in dom.range.range uses a type in jsx.jsx.
- The types involved
dom.range.range.$mol_dom_range→jsx.jsx.Element
- Direction
- dom.range.range uses jsx.jsx, so a change to jsx.jsx can break dom.range.range, while a change to dom.range.range can't break jsx.jsx.
- Position
- Below the diagonal: dom.range.range uses a module listed above it, which is the healthy direction.
18→7 dom.range.range uses wire.dom.dom✕
- Connections
- 1 pair of types, where a type in dom.range.range uses a type in wire.dom.dom.
- The types involved
dom.range.range.$mol_dom_range→wire.dom.dom.Node
- Direction
- dom.range.range uses wire.dom.dom, so a change to wire.dom.dom can break dom.range.range, while a change to dom.range.range can't break wire.dom.dom.
- Position
- Below the diagonal: dom.range.range uses a module listed above it, which is the healthy direction.
18→11 dom.range.range uses dom.point.point✕
- Connections
- 1 pair of types, where a type in dom.range.range uses a type in dom.point.point.
- The types involved
dom.range.range.$mol_dom_range→dom.point.point.$mol_dom_point
- Direction
- dom.range.range uses dom.point.point, so a change to dom.point.point can break dom.range.range, while a change to dom.range.range can't break dom.point.point.
- Position
- Below the diagonal: dom.range.range uses a module listed above it, which is the healthy direction.
19→12 file.base.base uses object.object✕
- Connections
- 1 pair of types, where a type in file.base.base uses a type in object.object.
- The types involved
file.base.base.$mol_file_base→object.object.$mol_object
- Direction
- file.base.base uses object.object, so a change to object.object can break file.base.base, while a change to file.base.base can't break object.object.
- Position
- Below the diagonal: file.base.base uses a module listed above it, which is the healthy direction.
20→3 http.http uses mem.force.force✕
- Connections
- 1 pair of types, where a type in http.http uses a type in mem.force.force.
- The types involved
http.http.$mol_http→mem.force.force.$mol_mem_force
- Direction
- http.http uses mem.force.force, so a change to mem.force.force can break http.http, while a change to http.http can't break mem.force.force.
- Position
- Below the diagonal: http.http uses a module listed above it, which is the healthy direction.
20→12 http.http uses object.object✕
- Connections
- 1 pair of types, where a type in http.http uses a type in object.object.
- The types involved
http.http.$mol_http→object.object.$mol_object
- Direction
- http.http uses object.object, so a change to object.object can break http.http, while a change to http.http can't break object.object.
- Position
- Below the diagonal: http.http uses a module listed above it, which is the healthy direction.
21→12 layout.layout uses object.object✕
- Connections
- 1 pair of types, where a type in layout.layout uses a type in object.object.
- The types involved
layout.layout.$mol_layout→object.object.$mol_object
- Direction
- layout.layout uses object.object, so a change to object.object can break layout.layout, while a change to layout.layout can't break object.object.
- Position
- Below the diagonal: layout.layout uses a module listed above it, which is the healthy direction.
22→12 model.model uses object.object✕
- Connections
- 1 pair of types, where a type in model.model uses a type in object.object.
- The types involved
model.model.$mol_model→object.object.$mol_object
- Direction
- model.model uses object.object, so a change to object.object can break model.model, while a change to model.model can't break object.object.
- Position
- Below the diagonal: model.model uses a module listed above it, which is the healthy direction.
23→2 rest.port.port uses jsx.jsx✕
- Connections
- 1 pair of types, where a type in rest.port.port uses a type in jsx.jsx.
- The types involved
rest.port.port.$mol_rest_port→jsx.jsx.Element
- Direction
- rest.port.port uses jsx.jsx, so a change to jsx.jsx can break rest.port.port, while a change to rest.port.port can't break jsx.jsx.
- Position
- Below the diagonal: rest.port.port uses a module listed above it, which is the healthy direction.
23→12 rest.port.port uses object.object✕
- Connections
- 1 pair of types, where a type in rest.port.port uses a type in object.object.
- The types involved
rest.port.port.$mol_rest_port→object.object.$mol_object
- Direction
- rest.port.port uses object.object, so a change to object.object can break rest.port.port, while a change to rest.port.port can't break object.object.
- Position
- Below the diagonal: rest.port.port uses a module listed above it, which is the healthy direction.
24→12 rpc.rpc uses object.object✕
- Connections
- 1 pair of types, where a type in rpc.rpc uses a type in object.object.
- The types involved
rpc.rpc.$mol_rpc→object.object.$mol_object
- Direction
- rpc.rpc uses object.object, so a change to object.object can break rpc.rpc, while a change to rpc.rpc can't break object.object.
- Position
- Below the diagonal: rpc.rpc uses a module listed above it, which is the healthy direction.
25→2 view.view.view uses jsx.jsx✕
- Connections
- 1 pair of types, where a type in view.view.view uses a type in jsx.jsx.
- The types involved
view.view.view.$mol_view→jsx.jsx.Element
- Direction
- view.view.view uses jsx.jsx, so a change to jsx.jsx can break view.view.view, while a change to view.view.view can't break jsx.jsx.
- Position
- Below the diagonal: view.view.view uses a module listed above it, which is the healthy direction.
25→12 view.view.view uses object.object✕
- Connections
- 1 pair of types, where a type in view.view.view uses a type in object.object.
- The types involved
view.view.view.$mol_view→object.object.$mol_object
- Direction
- view.view.view uses object.object, so a change to object.object can break view.view.view, while a change to view.view.view can't break object.object.
- Position
- Below the diagonal: view.view.view uses a module listed above it, which is the healthy direction.
26→14 wire.fiber.fiber uses wrapper.wrapper✕
- Connections
- 1 pair of types, where a type in wire.fiber.fiber uses a type in wrapper.wrapper.
- The types involved
wire.fiber.fiber.$mol_wire_fiber→wrapper.wrapper.Args
- Direction
- wire.fiber.fiber uses wrapper.wrapper, so a change to wrapper.wrapper can break wire.fiber.fiber, while a change to wire.fiber.fiber can't break wrapper.wrapper.
- Position
- Below the diagonal: wire.fiber.fiber uses a module listed above it, which is the healthy direction.
27→16 audio.instrument.instrument uses audio.node.node✕
- Connections
- 1 pair of types, where a type in audio.instrument.instrument uses a type in audio.node.node.
- The types involved
audio.instrument.instrument.$mol_audio_instrument→audio.node.node.$mol_audio_node
- Direction
- audio.instrument.instrument uses audio.node.node, so a change to audio.node.node can break audio.instrument.instrument, while a change to audio.instrument.instrument can't break audio.node.node.
- Position
- Below the diagonal: audio.instrument.instrument uses a module listed above it, which is the healthy direction.
28→22 github.entity.entity uses model.model✕
- Connections
- 1 pair of types, where a type in github.entity.entity uses a type in model.model.
- The types involved
github.entity.entity.$mol_github_entity→model.model.$mol_model
- Direction
- github.entity.entity uses model.model, so a change to model.model can break github.entity.entity, while a change to github.entity.entity can't break model.model.
- Position
- Below the diagonal: github.entity.entity uses a module listed above it, which is the healthy direction.
29→21 layout.tree.tree uses layout.layout✕
- Connections
- 1 pair of types, where a type in layout.tree.tree uses a type in layout.layout.
- The types involved
layout.tree.tree.$mol_layout_tree→layout.layout.$mol_layout
- Direction
- layout.tree.tree uses layout.layout, so a change to layout.layout can break layout.tree.tree, while a change to layout.tree.tree can't break layout.layout.
- Position
- Below the diagonal: layout.tree.tree uses a module listed above it, which is the healthy direction.
30→2 plugin.plugin uses jsx.jsx✕
- Connections
- 1 pair of types, where a type in plugin.plugin uses a type in jsx.jsx.
- The types involved
plugin.plugin.$mol_plugin→jsx.jsx.Element
- Direction
- plugin.plugin uses jsx.jsx, so a change to jsx.jsx can break plugin.plugin, while a change to plugin.plugin can't break jsx.jsx.
- Position
- Below the diagonal: plugin.plugin uses a module listed above it, which is the healthy direction.
30→25 plugin.plugin uses view.view.view✕
- Connections
- 1 pair of types, where a type in plugin.plugin uses a type in view.view.view.
- The types involved
plugin.plugin.$mol_plugin→view.view.view.$mol_view
- Direction
- plugin.plugin uses view.view.view, so a change to view.view.view can break plugin.plugin, while a change to plugin.plugin can't break view.view.view.
- Position
- Below the diagonal: plugin.plugin uses a module listed above it, which is the healthy direction.
31→12 rest.message.message_node uses object.object✕
- Connections
- 1 pair of types, where a type in rest.message.message_node uses a type in object.object.
- The types involved
rest.message.message_node.$mol_rest_message→object.object.$mol_object
- Direction
- rest.message.message_node uses object.object, so a change to object.object can break rest.message.message_node, while a change to rest.message.message_node can't break object.object.
- Position
- Below the diagonal: rest.message.message_node uses a module listed above it, which is the healthy direction.
31→23 rest.message.message_node uses rest.port.port✕
- Connections
- 1 pair of types, where a type in rest.message.message_node uses a type in rest.port.port.
- The types involved
rest.message.message_node.$mol_rest_message→rest.port.port.$mol_rest_port
- Direction
- rest.message.message_node uses rest.port.port, so a change to rest.port.port can break rest.message.message_node, while a change to rest.message.message_node can't break rest.port.port.
- Position
- Below the diagonal: rest.message.message_node uses a module listed above it, which is the healthy direction.
32→23 rest.port.ws.ws uses rest.port.port✕
- Connections
- 1 pair of types, where a type in rest.port.ws.ws uses a type in rest.port.port.
- The types involved
rest.port.ws.ws.$mol_rest_port_ws→rest.port.port.$mol_rest_port
- Direction
- rest.port.ws.ws uses rest.port.port, so a change to rest.port.port can break rest.port.ws.ws, while a change to rest.port.ws.ws can't break rest.port.port.
- Position
- Below the diagonal: rest.port.ws.ws uses a module listed above it, which is the healthy direction.
33→28 github.user.user uses github.entity.entity✕
- Connections
- 1 pair of types, where a type in github.user.user uses a type in github.entity.entity.
- The types involved
github.user.user.$mol_github_user→github.entity.entity.$mol_github_entity
- Direction
- github.user.user uses github.entity.entity, so a change to github.entity.entity can break github.user.user, while a change to github.user.user can't break github.entity.entity.
- Position
- Below the diagonal: github.user.user uses a module listed above it, which is the healthy direction.
34→29 layout.flex.flex uses layout.tree.tree✕
- Connections
- 1 pair of types, where a type in layout.flex.flex uses a type in layout.tree.tree.
- The types involved
layout.flex.flex.$mol_layout_flex→layout.tree.tree.$mol_layout_tree
- Direction
- layout.flex.flex uses layout.tree.tree, so a change to layout.tree.tree can break layout.flex.flex, while a change to layout.flex.flex can't break layout.tree.tree.
- Position
- Below the diagonal: layout.flex.flex uses a module listed above it, which is the healthy direction.
35→29 layout.stack.stack uses layout.tree.tree✕
- Connections
- 1 pair of types, where a type in layout.stack.stack uses a type in layout.tree.tree.
- The types involved
layout.stack.stack.$mol_layout_stack→layout.tree.tree.$mol_layout_tree
- Direction
- layout.stack.stack uses layout.tree.tree, so a change to layout.tree.tree can break layout.stack.stack, while a change to layout.stack.stack can't break layout.tree.tree.
- Position
- Below the diagonal: layout.stack.stack uses a module listed above it, which is the healthy direction.
36→12 rest.resource.resource_node uses object.object✕
- Connections
- 1 pair of types, where a type in rest.resource.resource_node uses a type in object.object.
- The types involved
rest.resource.resource_node.$mol_rest_resource→object.object.$mol_object
- Direction
- rest.resource.resource_node uses object.object, so a change to object.object can break rest.resource.resource_node, while a change to rest.resource.resource_node can't break object.object.
- Position
- Below the diagonal: rest.resource.resource_node uses a module listed above it, which is the healthy direction.
36→31 rest.resource.resource_node uses rest.message.message_node✕
- Connections
- 1 pair of types, where a type in rest.resource.resource_node uses a type in rest.message.message_node.
- The types involved
rest.resource.resource_node.$mol_rest_resource→rest.message.message_node.$mol_rest_message
- Direction
- rest.resource.resource_node uses rest.message.message_node, so a change to rest.message.message_node can break rest.resource.resource_node, while a change to rest.resource.resource_node can't break rest.message.message_node.
- Position
- Below the diagonal: rest.resource.resource_node uses a module listed above it, which is the healthy direction.
37→28 github.comment.comment uses github.entity.entity✕
- Connections
- 1 pair of types, where a type in github.comment.comment uses a type in github.entity.entity.
- The types involved
github.comment.comment.$mol_github_comment→github.entity.entity.$mol_github_entity
- Direction
- github.comment.comment uses github.entity.entity, so a change to github.entity.entity can break github.comment.comment, while a change to github.comment.comment can't break github.entity.entity.
- Position
- Below the diagonal: github.comment.comment uses a module listed above it, which is the healthy direction.
37→33 github.comment.comment uses github.user.user✕
- Connections
- 1 pair of types, where a type in github.comment.comment uses a type in github.user.user.
- The types involved
github.comment.comment.$mol_github_comment_json→github.user.user.$mol_github_user_json
- Direction
- github.comment.comment uses github.user.user, so a change to github.user.user can break github.comment.comment, while a change to github.comment.comment can't break github.user.user.
- Position
- Below the diagonal: github.comment.comment uses a module listed above it, which is the healthy direction.
38→12 rest.server.server_node uses object.object✕
- Connections
- 1 pair of types, where a type in rest.server.server_node uses a type in object.object.
- The types involved
rest.server.server_node.$mol_rest_server→object.object.$mol_object
- Direction
- rest.server.server_node uses object.object, so a change to object.object can break rest.server.server_node, while a change to rest.server.server_node can't break object.object.
- Position
- Below the diagonal: rest.server.server_node uses a module listed above it, which is the healthy direction.
38→31 rest.server.server_node uses rest.message.message_node✕
- Connections
- 1 pair of types, where a type in rest.server.server_node uses a type in rest.message.message_node.
- The types involved
rest.server.server_node.$mol_rest_server→rest.message.message_node.$mol_rest_message
- Direction
- rest.server.server_node uses rest.message.message_node, so a change to rest.message.message_node can break rest.server.server_node, while a change to rest.server.server_node can't break rest.message.message_node.
- Position
- Below the diagonal: rest.server.server_node uses a module listed above it, which is the healthy direction.
38→36 rest.server.server_node uses rest.resource.resource_node✕
- Connections
- 1 pair of types, where a type in rest.server.server_node uses a type in rest.resource.resource_node.
- The types involved
rest.server.server_node.$mol_rest_server→rest.resource.resource_node.$mol_rest_resource
- Direction
- rest.server.server_node uses rest.resource.resource_node, so a change to rest.resource.resource_node can break rest.server.server_node, while a change to rest.server.server_node can't break rest.resource.resource_node.
- Position
- Below the diagonal: rest.server.server_node uses a module listed above it, which is the healthy direction.
39→22 github.issue.issue uses model.model✕
- Connections
- 2 pairs of types, where a type in github.issue.issue uses a type in model.model.
- The types involved
github.issue.issue.$mol_github_issue→model.model.$mol_modelgithub.issue.issue.$mol_github_issue_comments→model.model.$mol_model
- Direction
- github.issue.issue uses model.model, so a change to model.model can break github.issue.issue, while a change to github.issue.issue can't break model.model.
- Position
- Below the diagonal: github.issue.issue uses a module listed above it, which is the healthy direction.
39→33 github.issue.issue uses github.user.user✕
- Connections
- 1 pair of types, where a type in github.issue.issue uses a type in github.user.user.
- The types involved
github.issue.issue.$mol_github_issue_json→github.user.user.$mol_github_user_json
- Direction
- github.issue.issue uses github.user.user, so a change to github.user.user can break github.issue.issue, while a change to github.issue.issue can't break github.user.user.
- Position
- Below the diagonal: github.issue.issue uses a module listed above it, which is the healthy direction.
39→37 github.issue.issue uses github.comment.comment✕
- Connections
- 1 pair of types, where a type in github.issue.issue uses a type in github.comment.comment.
- The types involved
github.issue.issue.$mol_github_issue_comments→github.comment.comment.$mol_github_comment
- Direction
- github.issue.issue uses github.comment.comment, so a change to github.comment.comment can break github.issue.issue, while a change to github.issue.issue can't break github.comment.comment.
- Position
- Below the diagonal: github.issue.issue uses a module listed above it, which is the healthy direction.
40→3 github.repository.repository uses mem.force.force✕
- Connections
- 1 pair of types, where a type in github.repository.repository uses a type in mem.force.force.
- The types involved
github.repository.repository.$mol_github_repository_issues→mem.force.force.$mol_mem_force
- Direction
- github.repository.repository uses mem.force.force, so a change to mem.force.force can break github.repository.repository, while a change to github.repository.repository can't break mem.force.force.
- Position
- Below the diagonal: github.repository.repository uses a module listed above it, which is the healthy direction.
40→22 github.repository.repository uses model.model✕
- Connections
- 1 pair of types, where a type in github.repository.repository uses a type in model.model.
- The types involved
github.repository.repository.$mol_github_repository_issues→model.model.$mol_model
- Direction
- github.repository.repository uses model.model, so a change to model.model can break github.repository.repository, while a change to github.repository.repository can't break model.model.
- Position
- Below the diagonal: github.repository.repository uses a module listed above it, which is the healthy direction.
40→28 github.repository.repository uses github.entity.entity✕
- Connections
- 1 pair of types, where a type in github.repository.repository uses a type in github.entity.entity.
- The types involved
github.repository.repository.$mol_github_repository→github.entity.entity.$mol_github_entity
- Direction
- github.repository.repository uses github.entity.entity, so a change to github.entity.entity can break github.repository.repository, while a change to github.repository.repository can't break github.entity.entity.
- Position
- Below the diagonal: github.repository.repository uses a module listed above it, which is the healthy direction.
40→33 github.repository.repository uses github.user.user✕
- Connections
- 1 pair of types, where a type in github.repository.repository uses a type in github.user.user.
- The types involved
github.repository.repository.$mol_github_repository_json→github.user.user.$mol_github_user_json
- Direction
- github.repository.repository uses github.user.user, so a change to github.user.user can break github.repository.repository, while a change to github.repository.repository can't break github.user.user.
- Position
- Below the diagonal: github.repository.repository uses a module listed above it, which is the healthy direction.
40→39 github.repository.repository uses github.issue.issue✕
- Connections
- 1 pair of types, where a type in github.repository.repository uses a type in github.issue.issue.
- The types involved
github.repository.repository.$mol_github_repository_issues→github.issue.issue.$mol_github_issue
- Direction
- github.repository.repository uses github.issue.issue, so a change to github.issue.issue can break github.repository.repository, while a change to github.repository.repository can't break github.issue.issue.
- Position
- Below the diagonal: github.repository.repository uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 122 | High / Critical |
Roadmap
Top priorities: Adopt pino (or winston) and log at meaningful points in the services you run; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt pino (or winston) and log at meaningful points in the services you run. | +4.3 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +4.3 pts | Medium | Security & performance tooling |
| Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI. | +4.3 pts | Medium | Tooling |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +3.4 pts | Medium | Access Controls |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +3.1 pts | Medium | Text alternatives |
| Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail. | +2.6 pts | Medium | Outbound HTTP resilience |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.6 pts | Medium | Page structure |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. | +1.2 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 61 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 61 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, 375 of 385 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.tsx, .ts) and the coverage collector does support this ecosystem — it drives jest, vitest and mocha — but no package.json in this repository has a `scripts.test`, and none declares a runner the analyzer could start on its own, so it could not tell how this suite is run. Not scored — this is a gap in the analyzer's reading of how the suite is run, not a missing .tsx/.ts runner and not a verdict that this repository runs no tests.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.tsx, .ts) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but no package.json in this repository has a `scripts.test`, and none declares a runner the analyzer could start on its own, so it could not tell how this suite is run. Not scored — this is a gap in the analyzer's reading of how the suite is run, not a missing .tsx/.ts runner and not a verdict that this repository runs no tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifest (package.json) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable. Your package.json IS read in this same run: the frontend dependency lens (R8) parses it for unused declarations, undeclared imports and misplaced production dependencies — what is missing here is the outdated/deprecated/unmaintained signal for those npm packages, not the manifest.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `ambient/ambient.ts`, `data/const/const.ts`, `jsx/jsx.ts`, `model/model.ts`, `object2/object2.ts`, … (+8 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 144 commits in the last 90 days, yet 60 of 104 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 19 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 43 further occurrence(s) are not listed individually; the score already reflects all 83.
- R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 680 further occurrence(s) are not listed individually; the score already reflects all 720.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was $mol_vary_class.pack at 58. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being $mol_html_view.views at 34 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: html/view/view.view.ts ($mol_html_view.views at 34). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with $mol_vary_class.pack (cyclomatic 58), $mol_vary_class.take (cyclomatic 46). — 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 7.5 to about 8.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
26 method(s) exceeded the cognitive complexity threshold of 15; the worst was $mol_vary_class.pack at 63.
What to do
- Bring the 26 bodies over 15 down to 15 or less in Cognitive Complexity — start with $mol_vary_class.pack (cognitive 63), $mol_tag_sieve.ids_tags_filtered (cognitive 49), $mol_sourcemap_builder.add (cognitive 43). — 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 26 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with base.ts, REDACTED, text.view.ts. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with vary.ts (2). — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 55 classes have LCOM4 above 3.
D10 · Test Quality
6 skipped (6 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 6 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: REDACTED (4×27=108); vary/vary.ts (2×46=92); wire/fiber/fiber.ts (2×20=40)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, vary.ts, fiber.ts. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
25 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is style/properties/properties.ts. Counted over 99 of the 729 production source files in this repository: 625 are under the ~2,400-byte size floor this dimension measures over, and the remaining 5 have no attributable history left to measure.
What to do
- Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 53788 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 173 document(s) read across 4 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
1 of 138 judged comments only repeat the code they sit on (0.7 %). 112 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with dts.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
43 % of calls cross a namespace and 0 % go through an interface, but 26 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
127 finding(s): 0 critical, 88 high, 39 medium, 0 low. 62 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 14 file(s) — `ambient/ambient.ts` (line 3), `app/supplies/index.html` (lines 2–10), `data/const/const.ts` (line 7), `jsx/jsx.ts` (line 197), `model/model.ts` (line 5), … (+9 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 26 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (26 issue-level).
- Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 warning-level).
- No action in Static Analysis (SAST) — all 62 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 (62 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D35 · Change Coupling
Strongest change-coupling: encode.node.ts↔encode.ts 100%; encode.ts↔encode.web.ts 90%; code.view.css.ts↔line.view.css.ts 50%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with code.view.css.ts, decode.web.ts. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with encode.ts. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — dom/capture/capture.tsx:22, dom/capture/capture.tsx:109
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — dom/capture/capture.tsx:99
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — button/download/download.view.tsx:17
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — wire/dom/index.html:7
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — app/questions/index.html:2, app/supplies/index.html:2, wire/dom/index.html:1
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×3) — app/questions/index.html:2, app/supplies/index.html:2, wire/dom/index.html:1
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it. (×2) — app/questions/index.html:2, app/supplies/index.html:2
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — REDACTED:17
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — wire/dom/index.html:1
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `[mol_pop_bubble]:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — pop/pop.view.css:51
- `[mol_pop_over]:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — pop/over/over.view.css:2
- `[mol_button]:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — button/button.view.css:24
- `&:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — page/page.view.css.ts:20, link/link.view.css.ts:31
- `&:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — link/link.view.css.ts:35
- `[mol_view]` moves (`transition-property: height, width, min-height, min-width, max-width, max-height, transform, scale, translate, rotate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — view/view/view.css:6
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
C2 · Access Controls
- This repository serves requests — express() (REDACTED:11) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — REDACTED:11
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
GD1 · Unfinished & placeholder code
- A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. — audio/instrument/instrument.ts:6
- A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. — stub/stub.ts:84
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `node` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — audio/instrument/instrument.ts:6
- `mod_ensure` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — build/graph/graph.ts:6
- `event_catch` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — speech/speech.ts:214
- `run` has an empty body — confirm it's an intentional no-op and not an unfinished method. — build/checker/checker.node.ts:80
- `commit` has an empty body — confirm it's an intentional no-op and not an unfinished method. — state/arg/arg.node.ts:76
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
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
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability
- No logging call was found in the 744 JavaScript/TypeScript production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 25 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:11
- `build/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build/package.json:7
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Job `build` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it. — REDACTED:37
What to do
- Run the production rollout in a protected environment, behind a manual approval, or after the tests it must pass, so a bad push is stopped before users get it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — offline/offline.web.ts:51, report/bugsnag/bugsnag.ts:50
What to do
- Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 11 duplicated blocks under the repository root have copies in at least two of the sibling directories 3d, app, bigint, canvas, crypto, crypto2 (+12 more sibling(s) not listed) — 7 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — crypto/sacred/sacred.ts:1
- 8 of the duplicated blocks reported below have copies in at least two of the sibling directories bigint, boolean, dict, enum, every, float (+7 more sibling(s) not listed) under schema/. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — schema/dict/dict.ts:5
- 5 duplicated blocks under plot/ have copies in at least two of the sibling directories bar, graph, group, line, pane — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — plot/group/group.view.ts:25
- 5 duplicated blocks under wire/ have copies in at least two of the sibling directories async, atom, dict, method, plex, set (+3 more sibling(s) not listed) — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — wire/dict/dict.ts:16
- wire/dict/dict.ts:16 · wire/set/set.ts:11 — the two spans are one implementation copied and then locally edited — 243 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — wire/dict/dict.ts:16
- crypto/auditor/auditor.ts:29 · crypto/auditor/auditor.ts:94 — the two spans are one implementation copied and then locally edited — 226 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — crypto/auditor/auditor.ts:29
- state/arg/arg.node.ts:24 · REDACTED:49 — the two spans are one implementation copied and then locally edited — 234 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — state/arg/arg.node.ts:24
- github/issue/issue.ts:114 · github/repository/repository.ts:105 — the 2 copies are spread across 2 files, 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. — github/issue/issue.ts:114
- crypto/sacred/id/id.ts:1 · crypto/secret/id/id.ts:1 — the two spans are one implementation copied and then locally edited — 193 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — crypto/sacred/id/id.ts:1
- crypto/cipher/cipher.ts:39 · crypto/cipher/cipher.ts:79 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — crypto/cipher/cipher.ts:39
- vary/vary.ts:81 · vary/vary.ts:120 — the two spans are one implementation copied and then locally edited — 187 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — vary/vary.ts:81
- wire/plex/plex.ts:4 · wire/solo/solo.ts:4 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — wire/plex/plex.ts:4
- state/local/local.ts:1 · state/session/session.ts:1 — the 2 copies are spread across 2 files, 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. — state/local/local.ts:1
- crypto/sacred/sacred.ts:1 · crypto2/secret/secret.ts:1 — the two spans are one implementation copied and then locally edited — 168 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — crypto/sacred/sacred.ts:1
- wire/dom/dom.ts:77 · wire/dom/dom.ts:116 — 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. — wire/dom/dom.ts:77
- REDACTED:176 · REDACTED:202 — 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. — REDACTED:176
- nav/nav.view.ts:27 · nav/nav.view.ts:63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — nav/nav.view.ts:27
- type/int/int.ts:87 · type/int/int.ts:108 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — type/int/int.ts:87
- crypto2/cipher/cipher.ts:37 · crypto2/signer/signer.ts:37 — the 2 copies are spread across 2 files, 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. — crypto2/cipher/cipher.ts:37
- time/moment/moment.ts:287 · time/moment/moment.ts:324 · time/moment/moment.ts:340 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — time/moment/moment.ts:287
- tree2/text/to/sourcemap/sourcemap.ts:56 · tree2/text/to/string/string.ts:9 — the two spans are one implementation copied and then locally edited — 89 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tree2/text/to/sourcemap/sourcemap.ts:56
- type/case/capital/capital.ts:1 · type/case/lower/lower.ts:1 · type/case/upper/upper.ts:1 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — type/case/capital/capital.ts:1
- 3d/glob/glob.ts:12 · 3d/glob/glob.ts:27 · 3d/glob/glob.ts:42 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — 3d/glob/glob.ts:12
- infinite/infinite.view.ts:9 · infinite/infinite.view.ts:31 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — infinite/infinite.view.ts:9
- memo/key/key.ts:2 · memo/memo.ts:3 — the two spans are one implementation copied and then locally edited — 96 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — memo/key/key.ts:2
- plot/group/group.view.ts:25 · plot/pane/pane.view.ts:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — plot/group/group.view.ts:25
- schema/dict/dict.ts:5 · schema/record/record.ts:4 — the 2 copies are spread across 2 files, 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. — schema/dict/dict.ts:5
- search/search.view.ts:44 · select/select.view.ts:50 — the two spans are one implementation copied and then locally edited — 69 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — search/search.view.ts:44
- REDACTED:228 · time/moment/moment.ts:431 — the 2 copies are spread across 2 files, 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. — REDACTED:228
- 3d/param/param.ts:65 · 3d/param/param.ts:87 — 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. — 3d/param/param.ts:65
- crypto/auditor/auditor.ts:118 · crypto/key/key.ts:125 — the 2 copies are spread across 2 files, 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. — crypto/auditor/auditor.ts:118
- crypto/sacred/sacred.ts:75 · crypto/sacred/sacred.ts:89 — all 2 copies are in the same file, and the CITED SPAN is inside a TYPE DECLARATION, not executable code. There is no function to extract and no call site to call one from, so do not read this as an extract-a-helper row: the collapse a type offers is a generic — name the shape once, parameterised over the part that varies, and have each copy instantiate it. First check what actually differs between the copies: where they are a MATRIX of cases (one entry per input, differing precisely in the case each one pins), the repetition IS the enumeration and collapsing it would delete cases rather than de-duplicate anything — leave those alone. Reported because the copies that are not a matrix drift apart the first time only one of them is edited. — crypto/sacred/sacred.ts:75
- file/file.node.ts:88 · file/file.node.ts:147 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — file/file.node.ts:88
- schema/list/list.ts:1 · schema/maybe/maybe.ts:1 — the 2 copies are spread across 2 files, 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. — schema/list/list.ts:1
- REDACTED:200 · REDACTED:215 · time/moment/moment.ts:403 · time/moment/moment.ts:418 — the 4 copies are spread across 2 files, 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. — REDACTED:200
- time/moment/moment.ts:357 · time/moment/moment.ts:386 — 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. — time/moment/moment.ts:357
- dict/dict.ts:32 · dict/dict.ts:51 — 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. — dict/dict.ts:32
- schema/dict/dict.ts:31 · schema/record/record.ts:23 — the 2 copies are spread across 2 files, 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. — schema/dict/dict.ts:31
- schema/every/every.ts:1 · schema/some/some.ts:1 — the 2 copies are spread across 2 files, 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. — schema/every/every.ts:1
- touch/touch.view.ts:178 · touch/touch.view.ts:190 · touch/touch.view.ts:202 · touch/touch.view.ts:214 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — touch/touch.view.ts:178
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
- $mol_jsx has cyclomatic complexity 37 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — jsx/jsx.ts:22
- (top-level) has cyclomatic complexity 37 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — buffer/buffer.ts:1
- $mol_tree2_from_string has cyclomatic complexity 33 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tree2/from/string/string.ts:4
- event_move has cyclomatic complexity 30 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — touch/touch.view.ts:138
- $mol_compare_deep has cyclomatic complexity 25 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — compare/deep/deep.ts:9
- constructor has cyclomatic complexity 23 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:20
- add has cyclomatic complexity 22 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sourcemap/builder/builder.ts:89
- shift has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — time/moment/moment.ts:163
- make_class has cyclomatic complexity 19 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — style/sheet/sheet.ts:16
- $mol_tree2_to_json has cyclomatic complexity 19 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tree2/to/json/json.ts:4
- has cyclomatic complexity 18 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — view/tree2/to/dts/dts.ts:209
- fresh has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — wire/fiber/fiber.ts:147
- event_eat has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — touch/touch.view.ts:72
- has cyclomatic complexity 17 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — view/tree2/class/props.ts:59
- (top-level) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — type/int/int.ts:1
- $mol_charset_ucf_encode_to has cyclomatic complexity 16 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — charset/ucf/ucf.ts:29
- constructor has cyclomatic complexity 16 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — time/moment/moment.ts:37
- visit has cyclomatic complexity 16 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tree2/text/to/sourcemap/sourcemap.ts:31
- $mol_charset_ucf_decode has cyclomatic complexity 15 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — charset/ucf/ucf.ts:104
- dump_buffer has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vary/vary.ts:202
- event_key has cyclomatic complexity 15 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — nav/nav.view.ts:9
- $mol_crypto2_hash has cyclomatic complexity 14 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crypto2/hash/hash.ts:6
- $mol_tree2_from_json has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tree2/from/json/json.ts:3
- $mol_key has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — key/key/key.ts:6
- $mol_dom_patch has cyclomatic complexity 13 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dom/patch/patch.ts:3
- $mol_reconcile has cyclomatic complexity 13 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — reconcile/reconcile.ts:3
- = has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — view/tree2/to/dts/dts.ts:156
- $mol_tree2_xml_from_dom has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tree2/xml/from/dom/dom.ts:3
- $mol_dom_render_children has cyclomatic complexity 12 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dom/render/children/children.ts:3
- webdav_stat has cyclomatic complexity 12 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — file/webdav/webdav.ts:105
- $mol_conform has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — conform/conform.ts:7
- $mol_charset_decode_from has cyclomatic complexity 11 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — charset/decode/from/from.ts:4
- visit has cyclomatic complexity 11 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tree2/text/to/string/string.ts:7
- from has cyclomatic complexity 11 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:290
- view_find has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — view/view/view.tsx:445
- clone has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dom/capture/capture.tsx:15
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — plot/pane/pane.view.ts:164
R3 · Large Files
- vary/vary.ts has 516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vary/vary.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- 1 file(s) (~21 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package. — schema/schema
- Unreachable from the 4 application, 0 tooling and 238 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
- no import path from any entry point (4 application, 0 tooling, 238 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 (×38) — spell/ru/ru.ts, style/properties/properties.ts, vary/vary.ts, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports
S1 · Web-Security Posture
- This code fixes PBKDF2-SHA-256 at 10,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. (×2) — crypto/sacred/pass/pass.ts:14, crypto/secret/secret.ts:51
- `https://unpkg.com/mol_wire_dom` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — wire/dom/index.html:18
What to do
- Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 2 sites, not one: `crypto/sacred/pass/pass.ts:14` (PBKDF2-SHA-256, 10,000 iterations), `crypto/secret/secret.ts:51` (PBKDF2-SHA-256, 10,000 iterations). Each is a separate decision — fixing only the line this row cites leaves the others in place.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X12 · Unreachable branch
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `$mol_tree2_from_json` is exported and takes `json: any` from its caller, and it calls itself at line 14 (`$mol_tree2_from_json`) with a piece of `json` (and at line 50) — and nowhere in `$mol_tree2_from_json` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `$mol_tree2_from_json` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — tree2/from/json/json.ts:14
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `text` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — style/attach/attach.ts:19
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
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. (×8) — view/view/view.tsx:270, ton/wallet/wallet.ts:34, report/handler/handler.ts:11, …
- `catch (error:any)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — REDACTED:45
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
- ~4.8 `!` null assertions per 1k TypeScript source lines — 302 assertion(s) across the 62308 source line(s) of the 730 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: github/issue/issue.ts (13), build/build.node.ts (10), crypto/auditor/auditor.ts (10). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 46.5 | Weak — gated by R7, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97.6 | Exemplary | Solid. |
| Maturity | 69.9 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 22.6 | Critical — gated by R6, P2, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 35.7 | Weak — gated by D29, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 31.0 | Weak — gated by AC1, AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 25 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- 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; 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: 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability not included — no test command the analyzer could start
- D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- D14 License Compliance — Package manifest not parsed for licence data — analyzer language-coverage gap
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 measured no build unit over this repository's .js, .ts, .tsx source. 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) — 13 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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.
- D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- 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
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — no test command the analyzer could start
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 238 test file(s) reach none of 662 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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
- 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.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: 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. 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.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — 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 — 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
- 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 — 98 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang app/questions/index.html:2
- <html> without a lang app/supplies/index.html:2
- <html> without a lang wire/dom/index.html:1
- Document without a <title> app/questions/index.html:2
- Document without a <title> app/supplies/index.html:2
- Document without a <title> wire/dom/index.html:1
- <img> without a text alternative dom/capture/capture.tsx:99
- Link with no accessible name button/download/download.view.tsx:17
- <input> without a programmatic label wire/dom/index.html:7
- <iframe> without a title REDACTED:17
Serious — 262 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (empty catch) view/view/view.tsx:270
- Swallowed exception (empty catch) ton/wallet/wallet.ts:34
- Swallowed exception (empty catch) report/handler/handler.ts:11
- Swallowed exception (empty catch) func/name/name.ts:17
- Swallowed exception (empty catch) embed/native/native.view.ts:19
- Swallowed exception (empty catch) dump/value/value.view.ts:52
- Swallowed exception (empty catch) dump/value/value.view.ts:96
- Swallowed exception (empty catch) conform/conform.ts:85
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement pop/pop.view.css:51
- Focus outline removed in CSS without a :focus replacement pop/over/over.view.css:2
- Focus outline removed in CSS without a :focus replacement button/button.view.css:24
- Focus outline removed in CSS without a :focus replacement page/page.view.css.ts:20
- Focus outline removed in CSS without a :focus replacement link/link.view.css.ts:31
- Focus outline removed in CSS without a :focus replacement link/link.view.css.ts:35
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2 locations) 3d/param/param.ts:65
- Duplicated block (12 lines × 2 locations) crypto/auditor/auditor.ts:118
- Duplicated block (12 lines × 2 locations) crypto/sacred/sacred.ts:75
- Duplicated block (12 lines × 2 locations) schema/list/list.ts:1
- Duplicated block (12 lines × 2 locations) time/moment/moment.ts:357
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark app/questions/index.html:2
- Page without a main landmark app/supplies/index.html:2
- Page without a main landmark wire/dom/index.html:1
- Hotspot: REDACTED REDACTED:210
- Hotspot: vary/vary.ts vary/vary.ts:339
- Hotspot: wire/fiber/fiber.ts wire/fiber/fiber.ts:147
- TooManyMethods: $mol_file_base file/base/base.ts:3
- TooManyMethods: $mol_view view/view/view.tsx:23
- TooManyMethods: $mol_text text/text/text.view.ts:6
- Duplicated block with local edits (14 matched lines × 2 locations) infinite/infinite.view.ts:9
- Duplicated block with local edits (14 matched lines × 2 locations) memo/key/key.ts:2
- Duplicated block with local edits (14 matched lines × 2 locations) search/search.view.ts:44
- Duplicated block (11 lines × 2 locations) dict/dict.ts:32
- Duplicated block (11 lines × 2 locations) schema/dict/dict.ts:31
- Duplicated block (11 lines × 2 locations) schema/every/every.ts:1
- <canvas> without a text alternative dom/capture/capture.tsx:22
- <canvas> without a text alternative dom/capture/capture.tsx:109
- MethodTooLong: $mol_vary_class.pack vary/vary.ts:49
- MethodTooLong: $mol_vary_class.take vary/vary.ts:339
- Change coupling: code.view.css.ts ↔ line.view.css.ts text/code/code.view.css.ts:1
- Change coupling: decode.web.ts ↔ url.ts base64/decode/decode.web.ts:1
- Hollow method — returns a constant without doing the work build/graph/graph.ts:6
- Hollow method — returns a constant without doing the work speech/speech.ts:214
- Outbound HTTP without resilience offline/offline.web.ts:51
- Outbound HTTP without resilience report/bugsnag/bugsnag.ts:50
- Duplicated block with local edits (37 matched lines × 2 locations) crypto/auditor/auditor.ts:29
- Duplicated block with local edits (37 matched lines × 2 locations) state/arg/arg.node.ts:24
- Duplicated block (31 lines × 2 locations) crypto/cipher/cipher.ts:39
- Duplicated block (31 lines × 2 locations) wire/plex/plex.ts:4
- Duplicated block (17 lines × 2 locations) nav/nav.view.ts:27
- Duplicated block (17 lines × 2 locations) type/int/int.ts:87
- Duplicated block (15 lines × 3 locations) time/moment/moment.ts:287
- Duplicated block (15 lines × 3 locations) type/case/capital/capital.ts:1
- Duplicated block (14 lines × 2 locations) plot/group/group.view.ts:25
- Duplicated block (14 lines × 2 locations) schema/dict/dict.ts:5
- Password key derivation is priced too cheaply crypto/sacred/pass/pass.ts:14
- Password key derivation is priced too cheaply crypto/secret/secret.ts:51
- Animation without a prefers-reduced-motion guard view/view/view.css:6
- No authorization REDACTED:11
- $mol_vary_class.pack (cyclomatic 58) vary/vary.ts:49
- $mol_vary_class.take (cyclomatic 46) vary/vary.ts:339
- $mol_touch.event_move (cyclomatic 30) touch/touch.view.ts:138
- $mol_rest_server.ws_income (cyclomatic 27) REDACTED:210
- $mol_list.view_window (cyclomatic 23) list/list.view.ts:32
- $mol_time_duration.constructor (cyclomatic 23) REDACTED:20
- $mol_sourcemap_builder.add (cyclomatic 22) sourcemap/builder/builder.ts:89
- $mol_regexp.from (cyclomatic 21) REDACTED:290
- $mol_run.spawn_async (cyclomatic 20) run/run.node.ts:46
- $mol_wire_fiber.fresh (cyclomatic 20) wire/fiber/fiber.ts:147
- $mol_tag_sieve.ids_tags_filtered (cyclomatic 19) tag/sieve/sieve.ts:24
- $mol_dump_value.rows_values (cyclomatic 17) dump/value/value.view.ts:58
- $mol_touch.event_eat (cyclomatic 17) touch/touch.view.ts:72
- $mol_time_moment.constructor (cyclomatic 16) time/moment/moment.ts:37
- $mol_vary_class.pack (cognitive 63) vary/vary.ts:49
- $mol_tag_sieve.ids_tags_filtered (cognitive 49) tag/sieve/sieve.ts:24
- $mol_sourcemap_builder.add (cognitive 43) sourcemap/builder/builder.ts:89
- $mol_layout_wrap.down (cognitive 39) layout/wrap/wrap.ts:8
- $mol_time_duration.constructor (cognitive 35) REDACTED:20
- $mol_rest_server.ws_income (cognitive 34) REDACTED:210
- $mol_wire_fiber.fresh (cognitive 34) wire/fiber/fiber.ts:147
- $mol_plot_dot.indexes (cognitive 29) plot/dot/dot.view.ts:9
- $mol_dump_value.rows_values (cognitive 28) dump/value/value.view.ts:58
- $mol_touch.event_eat (cognitive 27) touch/touch.view.ts:72
- $mol_vary_class.take (cognitive 26) vary/vary.ts:339
- $mol_time_moment.constructor (cognitive 24) time/moment/moment.ts:37
- $mol_touch.event_move (cognitive 23) touch/touch.view.ts:138
- $mol_github_model.response (cognitive 22) github/model/model.ts:329
- $mol_graph.acyclic (cognitive 22) graph/graph.ts:87
- $mol_list.view_window (cognitive 22) list/list.view.ts:32
- $mol_dom_point.move_step (cognitive 21) dom/point/point.ts:125
- $mol_plot_mark_hor.visible_indexes (cognitive 21) plot/mark/hor/hor.view.ts:13
- $mol_tree2.select (cognitive 21) tree2/tree2.ts:198
- $mol_regexp.from (cognitive 20) REDACTED:290
- $mol_run.spawn_async (cognitive 20) run/run.node.ts:46
- $mol_video_camera.stream (cognitive 20) video/camera/camera.view.ts:17
- $mol_plot_bar.indexes (cognitive 18) plot/bar/bar.view.ts:4
- $mol_plot_line.indexes (cognitive 18) plot/line/line.view.ts:8
- $mol_time_interval.constructor (cognitive 18) time/interval/interval.ts:17
- $mol_wire_pub_sub.track_next (cognitive 16) wire/pub/sub/sub.ts:44
- REDACTED
- Change-coupling hub: encode.ts → decode.node.ts, decode.web.ts, encode.node.ts, encode.web.ts base64/encode/encode.ts
- Unfinished stub — throws a "not implemented" error audio/instrument/instrument.ts:6
- Unfinished stub — throws a "not implemented" exception audio/instrument/instrument.ts:6
- No structured logging
- Duplication concentrated across 18 sibling directories (11 clone groups) crypto/sacred/sacred.ts:1
- Duplication concentrated across 13 sibling directories (8 clone groups) schema/dict/dict.ts:5
- Duplication concentrated across 5 sibling directories (5 clone groups) plot/group/group.view.ts:25
- Duplication concentrated across 9 sibling directories (5 clone groups) wire/dict/dict.ts:16
- Duplicated block with local edits (46 matched lines × 2 locations) wire/dict/dict.ts:16
- Duplicated block (33 lines × 2 locations) github/issue/issue.ts:114
- Duplicated block with local edits (32 matched lines × 2 locations) crypto/sacred/id/id.ts:1
- Duplicated block with local edits (31 matched lines × 2 locations) vary/vary.ts:81
- Duplicated block (28 lines × 2 locations) state/local/local.ts:1
- Duplicated block with local edits (24 matched lines × 2 locations) crypto/sacred/sacred.ts:1
- Duplicated block (21 lines × 2 locations) wire/dom/dom.ts:77
- Duplicated block (18 lines × 2 locations) REDACTED:176
- Duplicated block (15 lines × 2 locations) crypto2/cipher/cipher.ts:37
- Duplicated block with local edits (15 matched lines × 2 locations) tree2/text/to/sourcemap/sourcemap.ts:56
- Duplicated block (14 lines × 3 locations) 3d/glob/glob.ts:12
- Duplicated block (13 lines × 2 locations) REDACTED:228
- Duplicated block with local edits (12 matched lines × 2 locations) file/file.node.ts:88
- Duplicated block (12 lines × 4 locations) REDACTED:200
- Duplicated block (11 lines × 4 locations) touch/touch.view.ts:178
- Complex function $mol_jsx (cyclomatic 37, cognitive 58) jsx/jsx.ts:22
- Complex function (top-level) (cyclomatic 37, cognitive 38) buffer/buffer.ts:1
- Complex function $mol_tree2_from_string (cyclomatic 33, cognitive 57) tree2/from/string/string.ts:4
- Complex function event_move (cyclomatic 30, cognitive 27) touch/touch.view.ts:138
- Complex function $mol_compare_deep (cyclomatic 25, cognitive 27) compare/deep/deep.ts:9
- Complex function constructor (cyclomatic 23, cognitive 35) REDACTED:20
- Complex function add (cyclomatic 22, cognitive 43) sourcemap/builder/builder.ts:89
- Complex function shift (cyclomatic 21, cognitive 20) time/moment/moment.ts:163
- Complex function make_class (cyclomatic 19, cognitive 30) style/sheet/sheet.ts:16
- Complex function $mol_tree2_to_json (cyclomatic 19, cognitive 30) tree2/to/json/json.ts:4
- Complex function (cyclomatic 18, cognitive 34) view/tree2/to/dts/dts.ts:209
- Complex function fresh (cyclomatic 18, cognitive 27) wire/fiber/fiber.ts:147
- Complex function event_eat (cyclomatic 17, cognitive 27) touch/touch.view.ts:72
- Complex function (cyclomatic 17, cognitive 20) view/tree2/class/props.ts:59
- Complex function (top-level) (cyclomatic 17, cognitive 16) type/int/int.ts:1
- Complex function $mol_charset_ucf_encode_to (cyclomatic 16, cognitive 38) charset/ucf/ucf.ts:29
- Complex function constructor (cyclomatic 16, cognitive 25) time/moment/moment.ts:37
- Complex function visit (cyclomatic 16, cognitive 22) tree2/text/to/sourcemap/sourcemap.ts:31
- Complex function $mol_charset_ucf_decode (cyclomatic 15, cognitive 40) charset/ucf/ucf.ts:104
- Complex function dump_buffer (cyclomatic 15, cognitive 15) vary/vary.ts:202
- Complex function event_key (cyclomatic 15, cognitive 9) nav/nav.view.ts:9
- Complex function $mol_crypto2_hash (cyclomatic 14, cognitive 30) crypto2/hash/hash.ts:6
- Complex function $mol_tree2_from_json (cyclomatic 14, cognitive 16) tree2/from/json/json.ts:3
- Complex function $mol_key (cyclomatic 14, cognitive 13) key/key/key.ts:6
- Complex function $mol_dom_patch (cyclomatic 13, cognitive 22) dom/patch/patch.ts:3
- Complex function $mol_reconcile (cyclomatic 13, cognitive 16) reconcile/reconcile.ts:3
- Complex function = (cyclomatic 13, cognitive 15) view/tree2/to/dts/dts.ts:156
- Complex function $mol_tree2_xml_from_dom (cyclomatic 13, cognitive 13) tree2/xml/from/dom/dom.ts:3
- Complex function $mol_dom_render_children (cyclomatic 12, cognitive 34) dom/render/children/children.ts:3
- Complex function webdav_stat (cyclomatic 12, cognitive 27) file/webdav/webdav.ts:105
- Complex function $mol_conform (cyclomatic 12, cognitive 11) conform/conform.ts:7
- Complex function $mol_charset_decode_from (cyclomatic 11, cognitive 21) charset/decode/from/from.ts:4
- Complex function visit (cyclomatic 11, cognitive 19) tree2/text/to/string/string.ts:7
- Complex function from (cyclomatic 11, cognitive 18) REDACTED:290
- Complex function view_find (cyclomatic 11, cognitive 15) view/view/view.tsx:445
- Complex function clone (cyclomatic 11, cognitive 13) dom/capture/capture.tsx:15
- Complex function (anonymous) (cyclomatic 11, cognitive 9) plot/pane/pane.view.ts:164
- vary/vary.ts: 516 lines of code vary/vary.ts:1
- No test, lint or typecheck script
- Dead file (~17149 LoC) spell/ru/ru.ts
- Dead file (~704 LoC) style/properties/properties.ts
- Dead file (~665 LoC) vary/vary.ts
- Dead file (~544 LoC) view/view/view.tsx
- Dead file (~505 LoC) REDACTED
- Dead file (~477 LoC) time/moment/moment.ts
- Dead file (~425 LoC) file/base/base.ts
- Dead file (~384 LoC) view/tree2/to/dts/dts.ts
- Dead file (~375 LoC) github/model/model.ts
- Dead file (~357 LoC) REDACTED
- Dead file (~356 LoC) state/shared/shared.ts
- Dead file (~346 LoC) wire/fiber/fiber.ts
- Dead file (~341 LoC) text/text/text.view.ts
- Dead file (~333 LoC) view/tree2/to/js/js.ts
- Dead file (~332 LoC) touch/touch.view.ts
- Dead file (~321 LoC) app/report/report.view.ts
- Dead file (~305 LoC) vary/edit/edit.view.ts
- Dead file (~302 LoC) app/supplies/domain/domain.ts
- Dead file (~301 LoC) tree2/tree2.ts
- Dead file (~280 LoC) dev/format/format.ts
- Dead file (~262 LoC) unicode/unicode.ts
- Dead file (~258 LoC) REDACTED
- Dead file (~249 LoC) tree2/js/to/text/text.ts
- Dead file (~246 LoC) graph/graph.ts
- Dead file (~239 LoC) speech/speech.ts
- Dead file (~232 LoC) wire/pub/sub/sub.ts
- Dead file (~230 LoC) plot/pane/pane.view.ts
- Dead file (~222 LoC) jsx/jsx.ts
- Dead file (~216 LoC) file/file.node.ts
- Dead file (~202 LoC) list/list.view.ts
- Dead file (~199 LoC) range2/range2.ts
- Dead file (~196 LoC) style/func/func.ts
- Dead file (~195 LoC) type/int/int.ts
- Dead file (~194 LoC) wire/atom/atom.ts
- Dead file (~192 LoC) dom/point/point.ts
- Dead file (~187 LoC) lang/iso639/iso639.ts
- Dead file (~186 LoC) crypto/key/key.ts
- Dead file (~185 LoC) type/case/case.ts
- Third-party script without Subresource Integrity wire/dom/index.html:18
- JavaScript dependencies are not locked build/package.json:7
- Recursive walk over a caller-supplied document has no depth cap tree2/from/json/json.ts:14
- Untrusted text written into markup unescaped style/attach/attach.ts:19
- Swallowed exception (caught, then discarded) REDACTED:45
Minor — 18 finding(s)
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Empty method body build/checker/checker.node.ts:80
- Empty method body state/arg/arg.node.ts:76
- Duplicated predicate file/file.web.ts:38
- Duplicated predicate form/draft/draft.view.ts:113
- No ADRs found build/package.json:4
- redundant comment view/tree2/to/dts/dts.ts:165
- Scattered collaborators
- REDACTED
- Placeholder literal left in code stub/stub.ts:84
- No ADRs
- No SAST REDACTED:11
- No dependency-update automation build/package.json:7
- Irreversible deploy step: production deploy on every push REDACTED:37
- No changelog
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
Minor — 7 finding(s)
- Skipped (documented): (unnamed test) wire/solo/solo.test.ts:249
- Skipped (documented): (unnamed test) wire/solo/solo.test.ts:382
- Skipped (documented): (unnamed test) wire/solo/solo.test.ts:501
- Skipped (documented): (unnamed test) wire/plex/plex.test.ts:73
- Skipped (documented): (unnamed test) wire/field/field.test.ts:22
- Skipped (documented): (unnamed test) test/test.test.ts:27
- doc comments repeat the names layout/row/row.ts:3
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-92263bbdbd02448280a83cb8ce514c2a/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-92263bbdbd02448280a83cb8ce514c2a/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-92263bbdbd02448280a83cb8ce514c2a/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=4822" --report-format json --report-path /tmp/watchdog-gitleaks-92263bbdbd02448280a83cb8ce514c2a/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-92263bbdbd02448280a83cb8ce514c2a/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 127 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: 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. semgrep could not parse 13 file(s) — `ambient/ambient.ts`, `data/const/const.ts`, `jsx/jsx.ts`, `model/model.ts`, `object2/object2.ts`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |