Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
The truncation warning tells me the scan hit its limit. Nothing in the analyze reference looks like a budget flag, and guessing does not help:
error: unknown option '--max-files'Same for --max-depth. Am I missing the flag name, or is there no way to raise it?
Accepted answer
There is no flag. The budget is fixed at 8000 files and 12 levels of depth, and although the scan options carry those fields internally, the CLI never passes anything through — so there is nothing you can set from the command line or from config.
Open issue. Worth knowing before you go hunting for a workaround: raising the budget alone would not be enough on a large monorepo anyway, and neither would teaching the walk to respect .gitignore — a genuinely large repo exceeds 8000 tracked files on its own. Both have to change together.
So today the only lever you have is the path you point it at. Analyze the app package rather than the workspace root, or a shallow clone if the weight is untracked, and read scan-truncated on the checklist as "the absence findings in this report are unsound".
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.