Counts over all violations.
Core files with at least one violation.
Number of analyzed core files.
Violations per severity.
Number of all violations.
Distinct shared modules imported.
Analysis metadata.
Duration of the analysis in milliseconds.
Whether the impact assessment ran.
Root path of the analyzed project.
Human-readable summary for LLM consumption.
Core-to-shared violations found.
Core file that imports from the shared layer.
Violation id: <filePath>:<line>:<importedModule>:<importedItem>.
OptionalimpactAssessment?: {Impact of changing the import; only with includeImpactAssessment.
Risk of a breaking change, derived from the reverse dependencies.
Files under src/ that import the core file.
Reasons for the risk level.
Non-relative imports of the core file, without @angular and
@shared modules.
Imported name, with as <alias> when aliased.
Module specifier of the shared module.
Line of the import declaration.
Violation message.
Optionalmetadata?: Record<string, unknown>Violation type and the imported name and alias.
error without impact assessment or with HIGH risk, warning with
MEDIUM or LOW risk.
Suggested refactoring.
Result from the analyze-core-to-shared tool.