No distributed scanning mode #19

New issue

Closed

opened 2026-05-10 16:09:03 +00:00 by Mark · 2 comments

Mark commented

2026-05-10 16:09:03 +00:00

Owner

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

Original request: Request: Automated incident report generation with evidence bundling

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: Automated incident report generation with evidence bundling 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:19 +00:00

Mark commented

2026-05-13 03:23:10 +00:00

Author

Owner

Feature Triage Assessment

Scope: large
Risk: high
Spec Alignment: misaligned
Summary: Wants to add worker nodes and task distribution for distributed scanning.
Recommendation: This is completely misaligned with redlens's purpose as a React frontend starter — it has no scanning subsystem at all. If this is for a different project, file it there. If it must go here, redlens would need a new backend service, message queue, worker orchestration, and coordination protocol, which is a full-scale infrastructure feature.
Rationale: redlens is a React SPA starter with no scanning functionality whatsoever — the spec describes it as a modern UI scaffolding with components, forms, charts, and styling. A distributed scanning mode with worker nodes is an entire infrastructure subsystem that has zero overlap with the project's stated purpose. Scope is large (new service, protocol, orchestration), risk is high (network coordination, security, state management), and it's fully misaligned with the spec.

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

## Feature Triage Assessment **Scope:** large **Risk:** high **Spec Alignment:** misaligned **Summary:** Wants to add worker nodes and task distribution for distributed scanning. **Recommendation:** This is completely misaligned with redlens's purpose as a React frontend starter — it has no scanning subsystem at all. If this is for a different project, file it there. If it must go here, redlens would need a new backend service, message queue, worker orchestration, and coordination protocol, which is a full-scale infrastructure feature. **Rationale:** redlens is a React SPA starter with no scanning functionality whatsoever — the spec describes it as a modern UI scaffolding with components, forms, charts, and styling. A distributed scanning mode with worker nodes is an entire infrastructure subsystem that has zero overlap with the project's stated purpose. Scope is large (new service, protocol, orchestration), risk is high (network coordination, security, state management), and it's fully misaligned with the spec. Labeled `blocked:needs-decision` — unblock on Forgejo to dispatch to the fixer pipeline.

Mark commented

2026-05-15 13:18:19 +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:20 +00:00