How city-of-helsinki/gdpr-compliance-scanner works
Key Components to Include:
Scanner Core Components
• It to multiple collector modules (represented as a collector subsystem)
• Compliance checker as a separate component
Data Collection Layer
• Storage collectors (cookies, localStorage, sessionStorage, indexedDB, cacheStorage)
• Page data collectors
• Settings collectors
Each should be represented as individual modules within the collectors group
Processing & Analysis
• Compliance checking module
• Rules engine connecting to the HDS Cookie Banner integration
• Error logging system
Output & Reporting
• Report generator component
• Static file server for report hosting
• Report assets (HTML, CSS, JS)
[External Systems]
• ▼
[Scanner Engine] ─────────────┐
• ▼ ▼
[Collectors Layer] [Configuration]
• ▼ │
[Compliance Checker]◄────────┘
• ▼
[Report Generator]
• ▼
[Web Server]
• Blue: Core scanner components
• Green: Data collection modules
• Yellow: Processing & analysis
• Orange: Output & reporting
• Gray: External systems/dependencies
Specific Implementation Details:
• How data flows from the scanner engine to collectors
• How collected data passes through compliance checking
• Demonstrate report generation flow
External Integrations
• Connection to HDS Cookie Banner system
• Website under test
• API endpoints for settings retrieval
Storage Components
• cacheStorage
• cookies
• indexedDB
• localStorage
• sessionStorage
Report Generation Pipeline
Flow from:
• Raw data collection
• Compliance analysis
• Report generation
• Static file serving
Important Considerations:
Asynchronous Operations
• Parallel scanning capabilities
Configuration Flow
• How config/config.js influences different components
• Where URL configurations are processed
Error Handling
• Error logger utility
• Error flow paths
Monitoring & Utilities
• Timer utility
• Domain tracking functionality
• Double lines: Data flow
• Diamonds: Decision points
• Rectangles: Processing modules
• Rounded rectangles: External systems
Remember to include notes about scalability and potential bottlenecks, as this system needs to handle multiple URLs and storage types efficiently.