No scan scheduling or automation #22

New issue

Closed

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

Mark commented

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

Owner

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

Original request: Request: Threat intelligence ingestion from private MISP instance

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: Threat intelligence ingestion from private MISP instance 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 01:48:38 +00:00

Author

Owner

Feature Triage Assessment

Scope: large
Risk: high
Spec Alignment: misaligned
Summary: The issue proposes adding automated security scanning with cron-based scheduling and CI integration to what is fundamentally a React SPA starter template.
Recommendation: Rejected as out of scope. If dependency vulnerability scanning is the goal, add a Dependabot/Renovate config file instead — no new infrastructure, no cron, and stays within the starter-kit remit. The broader proposal (scheduled scans, CI scan jobs) would require building an entire subsystem absent from the project.
Rationale: redlens is explicitly a 'pre-configured React single-page application starter' with shadcn/ui, Vite, Tailwind — it has no scanning service or subsystem to schedule. Adding cron scheduling + CI scan infrastructure would fundamentally change what the project is, bloating a minimal starter template with heavy operational machinery that has zero connection to its purpose. This is a clear spec misalignment.

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

## Feature Triage Assessment **Scope:** large **Risk:** high **Spec Alignment:** misaligned **Summary:** The issue proposes adding automated security scanning with cron-based scheduling and CI integration to what is fundamentally a React SPA starter template. **Recommendation:** Rejected as out of scope. If dependency vulnerability scanning is the goal, add a Dependabot/Renovate config file instead — no new infrastructure, no cron, and stays within the starter-kit remit. The broader proposal (scheduled scans, CI scan jobs) would require building an entire subsystem absent from the project. **Rationale:** redlens is explicitly a 'pre-configured React single-page application starter' with shadcn/ui, Vite, Tailwind — it has no scanning service or subsystem to schedule. Adding cron scheduling + CI scan infrastructure would fundamentally change what the project is, bloating a minimal starter template with heavy operational machinery that has zero connection to its purpose. This is a clear spec misalignment. Labeled `blocked:needs-decision` — unblock on Forgejo to dispatch to the fixer pipeline.

Mark commented

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