AtlasArc
Release notes Install free
All showcases

TypeScript · Artifact-backed analysis

Vue Core Architecture Report

This report imports a project-generated Dependency Cruiser graph as the TypeScript Analysis Source. Its evidence is artifact-backed, distinct from JVM bytecode acquisition.

Open generated report Printable Version
Source folders
31
Dependency edges
94
Cycle groups
8
Chapters
3
Generation
11.620 s
Case brief

Why this report

Vue Core makes the acquisition distinction concrete. AtlasArc did not read JVM output; it imported a Dependency Cruiser JSON artifact generated locally from the pinned TypeScript project.

The standard global report uses source-folder architecture units and the supported artifact metrics to build the same browsable chapter and Printable Version contract used by the JVM examples.

Selected evidence

  • Global architecture model
  • Architecture Overview, Cycle Evidence, and Hotspot Risk
  • One compact map per SCC; an additional map only when its focused node-and-edge evidence is a strict superset
  • Top 100 table rows
Generated contents

Read the evidence

The report index is the canonical entry point. These direct chapter links expose the generated reading order without copying or rewriting its findings here.

  1. 01 Architecture OverviewWhole-model orientation over TypeScript source-folder architecture units.
  2. 02 Cycle EvidenceEight report-model cycle groups derived from the imported dependency artifact.

    To compare this TypeScript project with a Kotlin/JVM project, open Detekt's chapter. Compare Detekt’s Cycle Evidence

  3. 03 Hotspot RiskPrioritisation evidence from the module metrics carried by the artifact.
Start at report index Open Printable Version
Pinned provenance

Analysis basis and integrity

Source revision
b5f8518379b77c3b62a7a9d2b52f6c76cda09bd5
Licence
MIT
Analysis source
Dependency Cruiser 17.4.3 JSON over 12 public package src roots with module metrics
Artifact
731 analyzed modules · 1,951 dependencies · 2,393,542 bytes
Artifact SHA-256
fb065a35d8c36cfe866594a7f952f8dc8bf012dff650e4f80cce5fb25cdb570f
Report selection
Global architecture, compact SCC maps with strict-evidence additional maps, top 100
Generated
2026-07-31T21:30:00Z
Generator
AtlasArc 1.0.1+736db9b9
Output
5 HTML files · 2,499,906 bytes
Portable folder SHA-256
654165ac904b7280a60724e75fdb61de5729b220450d74cea9d27d0fe57267d1
Structural SHA-256
ca3fcf2e8a229d249088006dc2c01e27f7749cdc18ad5585326340085719d3e2
Generation time
11.620 seconds

Output contract

Generated HTML is unchanged

The report folder is published byte-for-byte. This page supplies context and attribution outside that generated output.

Open pinned source revision
Reproduce the analysis basis

  1. Pin the source

    Check out the recorded Vue Core revision and keep the project checkout clean.

  2. Install and verify the project

    Use the recorded Node and pnpm versions. On the Norton-inspected generation workstation, NODE_OPTIONS=--use-system-ca kept TLS verification enabled through the system trust store.

    corepack pnpm install --frozen-lockfile
corepack pnpm build
corepack pnpm check

  3. Generate the architecture artifact

    Run Dependency Cruiser 17.4.3 with TypeScript 5.6.3 over the 12 public package src roots using --no-config, --metrics, --ts-config tsconfig.json, and --exclude __tests__.

  4. Import and report

    Select the generated Dependency Cruiser JSON as the TypeScript Analysis Source, then choose the standard global report with additional cycle maps and top 100 rows. An additional map is emitted only when its focused node-and-edge evidence strictly extends the compact map.

  5. Verify the output

    Compare the artifact, report-folder, and structural SHA-256 values above before publication.

Read with care

Caveats and safeguards

  • The Printable Version keeps its place

    A colour-coded report route stays in the spare margin on wide screens, follows the current chapter, and prints once beneath the dossier header. It is deliberately absent from standalone chapter files.

  • Artifact-backed means artifact-backed

    This report comes from a user-generated Dependency Cruiser JSON file. It does not use the JVM bytecode backend, and its architecture units are labelled source folders.

  • Optional adapters remain visible

    The artifact records 51 unresolved edges for optional server-renderer template engines or React adapters. They are not unresolved local TypeScript imports and are disclosed rather than silently discarded.

  • Dependency metrics follow the artifact

    The report can only use evidence and module metrics present in the imported artifact. It does not claim IntelliJ JVM visibility or PSI complexity semantics for TypeScript.

  • TLS verification stayed enabled

    NODE_OPTIONS=--use-system-ca allowed Node to trust the workstation's Windows certificate chain. The generation process did not disable certificate validation.

Source and attribution

Open-source project. Pinned example.

Vue Core is analyzed from the pinned source revision above under MIT . The project name identifies the analyzed open-source snapshot; publication here does not imply affiliation with or endorsement by its maintainers.

Read the report contract Compare all showcases