Windows: deepsec scan fails with 'Invalid filePath: contains backslash'

[TKlerx]

Summary

deepsec scan fails on Windows with:

Invalid filePath: contains backslash

This happens because scanner glob results on Windows can include \ separators, but file record paths are validated as POSIX-style (/) and reject backslashes.

Repro

1. On Windows, initialize deepsec in a project.
2. Run scan:
   npx --yes deepsec@latest scan --project-id <id> (or pnpm deepsec scan ... in .deepsec)
3. Observe failure when matchers start (for me it failed at auth-bypass).

Error

Invalid filePath: contains backslash

Expected

Scan should accept Windows glob output and normalize relative paths consistently.

Proposed fix

Normalize glob-returned relative paths in scanner before using them as record keys/file paths, e.g. relPathRaw.replaceAll(\, /).

I opened a PR with this change:

• https://github.com/vercel-labs/deepsec/pull/107

[TKlerx]

PR is up with a minimal fix: #38

[TKlerx]

This is also fixed in #29 which was there before #38

[cramforce]

This may work now

[TKlerx]

Why did you close this issue? The PR was not merged, yet.
Or do I misunderstand the process/flow?