Inline SVGs are not separate digital assets. They are part of the HTML document itself.
Technical reasons:
- No file to reference or track (no URL, no file entity)
- The SVG code is stored in the database as part of the content field value
- Scanning would require parsing and extracting markup fragments, which is outside the module's scope
Practical reasons:
- Inline SVGs are typically small icons or decorative elements
- They often come from theme templates, not content entry
- Tracking them would create noise in the inventory without clear compliance benefit