Skip to the result

ArchKeel.

Report · UNKNOWN · commit 278a8ebba

Verdict: UNKNOWN

UNKNOWN

6 rules 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
6

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 5 unknown rules: 1 coverage gap in the scan. Causes.
  2. Close the gaps behind 1 unknown rule: the UML target: 9 assessments cannot be decided: absent symbol: the symbol inventory is not complete, closed scope completeness: the member …. Causes.
  3. Every row behind this page: archkeel report --topology --output report.json --format json

Architecture

21 components, 41 modules. 0 with a violation, 2 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

6 rules cannot be decided, from 2 causes. An UNKNOWN rule is not a pass.

1 coverage gap in the scan

5 rules

Close the gaps listed below. A rule is decided when no gap holds it.

Holds API composition:REQUIRES-COMPLETE, Account and authentication:REQUIRES-COMPLETE, Article and comment publishing:REQUIRES-COMPLETE, Persistence and schema lifecycle:REQUIRES-COMPLETE, REQUIRES-COMPLETE

Where and what
Where: 1 of 1 component, 1 gap in all
ComponentGaps
ORM registry and configuration1
What: the kinds of the gaps
KindGaps
source resolution gap1

the UML target: 9 assessments cannot be decided: absent symbol: the symbol inventory is not complete, closed scope completeness: the member …

1 rule

Holds UML-TARGET-a2e40c5592b1b06a

What the core says

the UML target: 9 assessments cannot be decided: absent symbol: the symbol inventory is not complete, closed scope completeness: the member inventory is partial: computed or unsupported member syntax

Components with an exception

Modules, files and imports of each component with an exception

Open a component for its modules and files, and for its imports with file and line. The frame holds no level below a file.

1 of 21 components have a violation or a gap. All tables for 1 component. The others are in the Explorer. Every row: archkeel report --topology --output report.json --format json

WITH GAPS · 1

componentORM registry and configuration2 modules · uses 3 · used by 21 gapUNKNOWN
Modules: 2 of 2
Module FileException
nestjs.realworld.src.entities.generated.tssrc/entities.generated.ts
nestjs.realworld.src.mikro-orm.config.tssrc/mikro-orm.config.ts
Gaps: 1 of 1
ModuleReason
nestjs.realworld.src.mikro-orm.config.tsComputed dynamic_import cannot be resolved
Imports of other components: 4 of 4
TargetImportsFirst evidence
User model and repository1src/entities.generated.ts:7
Article and comment models2src/entities.generated.ts:4, src/entities.generated.ts:5
outside the contract4src/entities.generated.ts:8, src/mikro-orm.config.ts:1, src/mikro-orm.config.ts:2 and 1 more
Tag catalogue1src/entities.generated.ts:6
Imports by other components: 2 of 2
SourceImportsFirst evidence
Nest root module1src/app.module.ts:10
Account application service1src/user/user.service.ts:10