Closes #24. **A game name could move a recording out of the library.** `MoveClipToGameAction` joined whatever came in as `targetGame` onto the videos root, so `..\..\Somewhere` was a folder outside it and the clip was renamed there. `services/gameFolder.ts` refuses a name holding a separator, a drive colon, a control character, a leading dot (the scan would never see the clip again), a trailing dot or space (Windows drops them), or a device name; the route answers 400 with the reason, and the action checks the resolved folder sits directly inside the root anyway, because one guard is a single point of failure on the line that moves a recording. Refused rather than cleaned, unlike `safeName`: this is a name somebody typed, and filing their clip under a different spelling is a surprise. **A tag rule could hang the library.** Compiling a regular expression the user wrote is the feature, so it is not escaped. What is refused now is the shape that backtracks without end, a quantified group that already contains a quantifier (`(a+)+`), plus anything over 200 characters. `tagPatternProblem` in `src/shared` is the one answer the route and the DTO both use. The 34 rules in the real library all pass (checked read only). Rules already saved are not touched. **Two linear trims for two quadratic ones.** `/^'+|'+$/` in the search tokeniser and `/\.+$/` on an export's name retry from every position of a long run that does not end the string. `utils/trimChar.ts` is a loop; a test holds it under 50 ms on 200,000 dots. `tests/unit/main/codeScanning.spec.ts`, 38 cases. `npm run check` green. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Commits

Commits on Sep 22, 2026

fix(security): the desktop code scanning alerts