Skip to the result

ArchKeel.

Report · UNKNOWN · commit 74bc1cc4b

Verdict: UNKNOWN

UNKNOWN

1 rule cannot be decided

A violation is a fact of this run. An unknown rule is not a pass.

Rules PASS
0
Rules FAIL
0
Rules UNKNOWN
1

Stated assumption: code outside the scan roots hands in no global or platform object and replaces no global, and addresses that a framework renders from data hold no javascript: code

NEXT

  1. Close the gaps behind 1 unknown rule: the UML target: 3 assessments cannot be decided: closed scope completeness: the facts state no complete module inventory, relationship …. Causes.
  2. Every row behind this page: archkeel report --topology --output report.json --format json

Architecture

1 component, 2 modules. 0 with a violation, 0 with an open gap. This page shows one part of the system: its typescript modules. Another part has its own run and contract; a system document joins the parts into one page. Open a box to see its parts; As-Is, Target and Diff switch the view.

Skip the Explorer

Component dependencies

How to read this report

Components are declared responsibility and ownership boundaries, not classes or files. Packages here are namespace groups; they do not prove a directory or __init__.py. Modules represent source units: in Python, normally a .py file, including __init__.py. Details shows recorded file paths and separates the view group from the code container. Component roles describe architecture responsibilities; an interface node describes a language interface, such as a Python Protocol.

Gold and the component glyph mark architecture boundaries. Blue document glyphs mark modules; grey folder glyphs mark namespace groups. Classes use purple compartments, interfaces use teal circles, enumerations use pink compartments. Functions use ƒ and methods use (). Visibility: + public, − private, # protected, ~ package, ? unknown. These conventions do not claim Python access enforcement. Border verdicts and edge styles are separate from element types. Mixins appear as their own classifier and use a directed edge distinct from inheritance. Use the relationship legend to filter edges.

As-Is uses observed source facts with declared boundaries for navigation. Target uses independent declarations; missing file paths remain undeclared. Diff uses recorded Core assessments. Select for details; double-click, press Enter or Open selected to explore one level. Breadcrumbs include the kind. Drag the background to pan; use Zoom or Fit overview to change scale. Arrows run from source to target. Allowed component imports are permissions, not proof of a call or import.

Worth a look

Legend

Unknown

1 rule cannot be decided, from 1 cause. An UNKNOWN rule is not a pass.

the UML target: 3 assessments cannot be decided: closed scope completeness: the facts state no complete module inventory, relationship …

1 rule

Holds UML-TARGET-a2e40c5592b1b06a

What the core says

the UML target: 3 assessments cannot be decided: closed scope completeness: the facts state no complete module inventory, relationship endpoints cannot be identified uniquely