BikeControl

Files

T

dtourolleandClaude Opus 5 a042814625 Bump nanoid past the zero-size loop advisory

`npm ci` in the UI started reporting one high-severity vulnerability:
GHSA-2v37-7h3g-55p8, a custom generator called with size 0 spinning
forever. Lockfile-only bump, 3.3.17 -> 3.3.18.

Worth recording that this was never urgent. nanoid arrives as
vite -> postcss, marked `"dev": true`, so it is build tooling and never
reaches dist/. Postcss calls it with a fixed size for source-map ids,
which is not the vulnerable path. npm audit scores the package in
isolation, not the way this project calls it.

`npm run build` still produces the same bundle.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-21 17:38:54 +02:00

src

Never ride a link we did not open, and put a shifter on the other pod

2026-08-20 21:05:40 +02:00

index.html

Core ride logic, FTMS client, FIT encoder and probe CLI

2026-08-05 13:34:27 +02:00

package-lock.json

Bump nanoid past the zero-size loop advisory

2026-08-21 17:38:54 +02:00

package.json

Measure the screen, then decide what fits on it