How owasp/abap-code-scanner works
Main Components
a) Input Layer:
• ABAP Source Code Input Handler
• Configuration Manager (handling config.yml)
• CLI Interface Component
b) Core Analysis Engine:
• Scanner Core
• Check Registry
• Security Check Modules
• Dataflow Analysis Engine (upcoming feature)
c) Output Layer:
• Report Generator
• XLSX Export Module
Input Flow
• ABAP source files entering the system
• Configuration file feeding into the Scanner Core
Processing Flow
• Scanner Core distributing work to various check modules
• Dataflow Analysis Engine interacting with check modules
Output Flow
• Results aggregation
• Report generation in XLSX format
Specific Design Elements
Use these visual elements:
• Blue rectangles for input components
• Green rectangles for processing components
• Yellow rectangles for output components
• Red rectangles for security check modules
Detailed Component Breakdown
Scanner Core:
┌─────────────────────┐
• Scanner Core │
• ┤
• File Parser │
• Check Orchestrator│
• Config Manager │
• ┘
Security Checks Module:
┌─────────────────────┐
• Security Checks │
• ┤
• XSS │
• SQL Injection │
• Dir Traversal │
• Crypto Checks │
• ┘
Integration Points
Clear interfaces between:
• CLI and Scanner Core
• Scanner Core and Check Modules
• Check Modules and Report Generator
• Dataflow Analysis Engine and Security Checks
Technical Details
• Python version requirement (3.9+)
• File extension handlers (.abap, .txt)
• Configuration file format (YAML)
• Report output format (XLSX)
Extensibility Points
Highlight:
• Custom check module integration points
• Configuration extension possibilities
• Report format plugins