[FRONTEND] Add global error boundary with recovery actions and telemetry hooks

[utksh1]

Problem

SecuScan needs a production-grade improvement in this area: Frontend resilience..

Scope

Implement route-level error boundaries, retry/navigation actions, redacted diagnostic capture, and tests for failing child components.

Acceptance Criteria

• The implementation is focused and does not introduce unrelated UI, docs, lockfile, or formatting churn.
• Security-sensitive behavior has explicit negative tests where applicable.
• Existing tests continue to pass, and new tests cover the main success and failure paths.
• Documentation or configuration examples are updated when operator behavior changes.

Verification

Tests should assert recovery UI, redaction, and route isolation.

Difficulty

Hard, useful issue intended for experienced contributors.

[SaumyaT-21]

Hey @utksh1 ! I'm a GSSoC '26 contributor. I just finished hardening the date utility logic and regression tests for #107 , and this seems like a similar challenge. I'd like to scale that defensive approach to the UI level. I know it’s a 'Hard' issue, but if possible, I'd like to try it out. Would you be open to assigning this to me?

[Sujith-RMD]

Hi @utksh1! I'd like to take on this issue as part of GSSoC 2026.

My plan for the implementation:

Error Boundary component — A class-based ErrorBoundary using componentDidCatch + getDerivedStateFromError, designed for route-level wrapping so a single failing route doesn't cascade. Will expose a fallbackRender prop for custom recovery UI per route.

Recovery actions — The fallback UI will offer "Retry" (resets boundary state) and "Go Home" (programmatic navigation via React Router), so users aren't stranded on a blank screen.

Redacted diagnostic capture — componentDidCatch will sanitize the error object before logging — stripping stack frames that reference auth tokens, vault keys, or URL params that could contain sensitive values — then forward the redacted payload to whatever telemetry hook is wired in (console in dev, configurable callback in prod).

Tests — Will cover: recovery UI renders on child throw, retry resets boundary, redaction strips sensitive patterns from captured diagnostics, and route isolation (one boundary crashing doesn't affect siblings).

Could you assign this to me? Happy to share a draft structure for review before I open the PR.

[gitsofyash]

Hi @utksh1! I'd like to work on this under GSSoC '26.

Here's my implementation plan:

• Error Boundary — Class-based ErrorBoundary using getDerivedStateFromError + componentDidCatch, wrapped at the route level so a crash in one route doesn't affect siblings
• Recovery actions — Fallback UI with a "Retry" button (resets boundary state) and "Go Home" navigation, keeping users unblocked
• Redacted telemetry — Sanitize captured error payloads before forwarding — stripping sensitive patterns (auth tokens, vault keys, URL params) — with a configurable telemetry hook (console in dev, callback in prod)
• Tests — Cover recovery UI rendering on child throw, retry resetting boundary state, redaction stripping sensitive data from diagnostics, and route isolation between sibling boundaries

I'll keep the PR tightly scoped with no unrelated churn. Please assign this to me! 🚀

[vaishnavijha12]

Hi @utksh1

I’d like to work on this issue under GSSoC ’26.

My approach would be to implement a production-grade route-level Error Boundary system with recovery actions and secure telemetry hooks while keeping the PR focused and avoiding unrelated churn.

Planned implementation:

• Add route-level Error Boundaries to isolate crashes between routes

• Implement recovery actions like Retry and Go Home navigation

• Add redacted diagnostic capture to prevent leaking sensitive information in logs/telemetry

• Add comprehensive tests for:

  • fallback UI rendering
  • retry recovery flow
  • route isolation
  • sensitive data redaction

• Ensure existing tests continue to pass

I’ll keep the implementation aligned with the project architecture and accessibility standards.

Could you please assign this issue to me? Thanks!