No report generation or export

Mark commented

2026-05-10 16:07:14 +00:00

Owner

Closed: This feature belongs to a different project domain than redlens.

Original request: Request: Dynamic topology-aware lateral movement simulation

Per triage review, this issue is misaligned with redlens's project scope. Please re-file against the appropriate project.

Closed: This feature belongs to a different project domain than redlens. **Original request:** Request: Dynamic topology-aware lateral movement simulation Per triage review, this issue is misaligned with redlens's project scope. Please re-file against the appropriate project.

Mark added the

blocked:needs-decision

label

2026-05-12 23:26:21 +00:00

Mark commented

2026-05-13 11:37:23 +00:00

Author

Owner

Feature Triage Assessment

Scope: medium
Risk: low
Spec Alignment: misaligned
Summary: Wants to add PDF, HTML, and SARIF export to a React SPA starter template that has no application logic, no data model, and nothing to export.
Recommendation: Defer — there is no application logic to export from (App.tsx is <div id="app-root" />, sections/ is empty). If redlens evolves into an analysis tool, implement export via a strategy pattern: @react-pdf/renderer or html2canvas+jspdf for PDF, JSX-to-HTML templates for HTML, and a dedicated SARIF serializer if static-analysis domain data emerges. Ship the core domain first.
Rationale: scope=medium because it needs 5-10 files (exporter interface + 3 format implementations + trigger UI). risk=low because it's purely additive with no existing logic to break. spec=misaligned because redlens is explicitly a UI starter scaffolding (README: 'jump straight into building UI'), not an analysis tool — the issue description implies a tool that produces findings/results, but the repo contains zero application domain code, empty sections/, and the latest commits are all scaffolding/CI/doc setup.

Labeled blocked:needs-decision — unblock on Forgejo to dispatch to the fixer pipeline.

## Feature Triage Assessment **Scope:** medium **Risk:** low **Spec Alignment:** misaligned **Summary:** Wants to add PDF, HTML, and SARIF export to a React SPA starter template that has no application logic, no data model, and nothing to export. **Recommendation:** Defer — there is no application logic to export from (App.tsx is `<div id="app-root" />`, sections/ is empty). If redlens evolves into an analysis tool, implement export via a strategy pattern: `@react-pdf/renderer` or `html2canvas`+`jspdf` for PDF, JSX-to-HTML templates for HTML, and a dedicated SARIF serializer if static-analysis domain data emerges. Ship the core domain first. **Rationale:** scope=medium because it needs 5-10 files (exporter interface + 3 format implementations + trigger UI). risk=low because it's purely additive with no existing logic to break. spec=misaligned because redlens is explicitly a UI starter scaffolding (README: 'jump straight into building UI'), not an analysis tool — the issue description implies a tool that produces findings/results, but the repo contains zero application domain code, empty sections/, and the latest commits are all scaffolding/CI/doc setup. Labeled `blocked:needs-decision` — unblock on Forgejo to dispatch to the fixer pipeline.

Mark commented

2026-05-15 13:18:18 +00:00

Author

Owner

This issue describes security-scanning features (distributed scanning, vulnerability correlation, report generation) that belong to a vulnerability analysis tool, not a React SPA starter. redlens is explicitly a frontend UI scaffolding project — it has no scanning subsystem, no data pipeline, and no backend. Closing as filed against the wrong repository.

Mark closed this issue

2026-05-15 13:18:18 +00:00

Rows
Columns

No report generation or export #17

Feature Triage Assessment