Empty Results or Missing Issues
Understand why an analysis may return empty results or fewer issues than expected and how to verify correctness.
## Empty Results or Missing Issues
Sometimes an analysis completes successfully but returns no issues or fewer results than expected.
This does not always indicate a problem.
---
## When empty results are expected
Empty results may be correct when:
- The codebase follows enforced policies
- No blocking or high-risk patterns are present
- A diff analysis includes minimal or no changes
- Issues were previously fixed and verified
An empty result can mean low risk.
---
## Diff analysis vs full analysis
Diff analysis only evaluates changed files.
If:
- No risky changes were introduced
- Issues exist outside the diff scope
Then no issues may appear.
Run a full analysis to evaluate the entire repository.
---
## Policy filtering
Policies control which issues are surfaced.
If policies:
- Lower severity thresholds
- Restrict blocking categories
- Emphasize visibility over enforcement
Then fewer issues may appear.
This is expected behavior.
---
## Issue lifecycle and verification
Issues may disappear when:
- Fixes were applied
- Analysis was re-run
- Resolution was verified
Closed issues do not reappear unless reintroduced.
---
## AI contribution and results
AI contribution signals do not create issues by themselves.
If AI-generated code is:
- Safe
- Policy-compliant
Then no AI-related issues will appear.
---
## Common misunderstandings
- Empty results do not mean analysis failed
- TrustScore can remain high with zero issues
- Policy enforcement affects visibility
Interpret results in context.
---
## How to verify correctness
To confirm results:
1. Check analysis type (diff vs full)
2. Review active policy
3. Confirm analysis completed successfully
4. Run a full analysis if unsure
Verification builds confidence.
---
## When to investigate further
Investigate if:
- Results are consistently empty across full analyses
- Expected high-risk issues never appear
- Analysis reports errors or warnings
These may indicate configuration or permission issues.
---
## Next steps
- Permission and access errors
- Analysis configuration
- General FAQ