No scan scheduling or automation

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: Adaptive honeypot deployment based on scan results

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: Adaptive honeypot deployment based on scan results 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:09:29 +00:00

Author

Owner

Feature Triage Assessment

Scope: large
Risk: high
Spec Alignment: misaligned
Summary: Wants to add cron-based scheduling and CI-triggered scanning for continuous security monitoring.
Recommendation: Close as misaligned — this issue describes a security/infrastructure scanning feature for a backend or CI/CD system, but redlens is a frontend React SPA starter with no scanning subsystem, no backend, and no concept of 'scans.' File against the correct repo or create a new project for security scanning infrastructure.
Rationale: redlens is a React 19 / TypeScript / Vite 7 SPA starter — purely frontend, no backend, no scanning, no data pipeline. The issue asks for 'scan scheduling,' 'continuous security monitoring,' and 'cron-based scheduling with CI integration,' which are completely orthogonal to redlens's purpose. This is either filed against the wrong repo or describes an entirely different product. Even the suggested fix (cron + CI integration for scans) doesn't map onto anything in the existing codebase. Marked large/high because implementing this would mean spinning up an entirely new backend service with scheduling infrastructure, which is a full project, not an addition to this SPA starter. Spec is misaligned because redlens has no scanning domain in its README, features, milestones, or architecture.

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 cron-based scheduling and CI-triggered scanning for continuous security monitoring. **Recommendation:** Close as misaligned — this issue describes a security/infrastructure scanning feature for a backend or CI/CD system, but redlens is a frontend React SPA starter with no scanning subsystem, no backend, and no concept of 'scans.' File against the correct repo or create a new project for security scanning infrastructure. **Rationale:** redlens is a React 19 / TypeScript / Vite 7 SPA starter — purely frontend, no backend, no scanning, no data pipeline. The issue asks for 'scan scheduling,' 'continuous security monitoring,' and 'cron-based scheduling with CI integration,' which are completely orthogonal to redlens's purpose. This is either filed against the wrong repo or describes an entirely different product. Even the suggested fix (cron + CI integration for scans) doesn't map onto anything in the existing codebase. Marked large/high because implementing this would mean spinning up an entirely new backend service with scheduling infrastructure, which is a full project, not an addition to this SPA starter. Spec is misaligned because redlens has no scanning domain in its README, features, milestones, or architecture. 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:19 +00:00

Rows
Columns

No scan scheduling or automation #18

Feature Triage Assessment