Frontend lint backlog: 1358 warnings (0 errors) across frontend/src #1743

What

The frontend lint run reports 0 errors and 1358 warnings (npm run lint, run on branch fix/crowdsec-backup-acquisition-tidy, HEAD 1644f82). The warnings are non-blocking but form a large backlog that hides new warnings.

Where

Repository-wide under frontend/src. Most frequent rules in the run:

• import-x/order (import group spacing and ordering), e.g. frontend/src/pages/CrowdSecConfig.tsx:25-26
• unicorn/prefer-ternary and unicorn/no-useless-undefined, e.g. frontend/src/utils/cron.ts:52,75, frontend/src/utils/formatRelativeTime.ts:22
• security/detect-unsafe-regex, e.g. frontend/src/utils/cron.ts:29, frontend/src/utils/validation.ts:10
• testing-library/no-node-access, e.g. frontend/src/pages/__tests__/CrowdSecConfig.spec.tsx:285,288
• react-hooks purity warning, frontend/src/pages/CrowdSecConfig.tsx:113 (Date.now during render)

Evidence

npm run lint summary: 1358 problems (0 errors, 1358 warnings); 228 are auto-fixable with --fix.

Severity

Low.

Suggested approach

1. Run npm run lint -- --fix in a dedicated chore PR and review the import-order and ternary changes.
2. Address the remaining rules by file group (security/detect-unsafe-regex first, since it is a security-linter rule).
3. Consider --max-warnings in CI once the count is near zero, so new warnings fail the build.

Found by

QA gate run for branch fix/crowdsec-backup-acquisition-tidy (HEAD 1644f82). Not caused by that branch: the CrowdSec-touched files carry only a few of these warnings.