Repository read only partially
Scan rule · RSC-COD-007
- Code quality
- Severity: Medium
Reports that file selection hit the budget limit — absence-based rules stay silent and a GO verdict is ruled out.
Why this matters
A scanner may judge what it has seen — not what it has not seen. In a repository scan this is not a nicety: the most important rule ("no migration enables Row Level Security") is a statement about absence, and it becomes false as soon as a single unread file contains the migration.
That is why a truncated state switches exactly those rules off instead of letting them guess. Positive findings remain untouched: a key that was found stays a key that was found, no matter how many files next to it went unread.
In practice this means: when this finding appears, the result is not worse, it is more honest. You cannot derive "RLS is active everywhere" from this run — that needs a scan with a complete view of the migrations.
Scan tier
- Repo access (deep scan)
How to fix it
Scan the database directory specifically, or review manually, for a complete picture.