Skip to content

### JSON report totalIssues reflects capped count, not actual #3178

Closed

Description

@adamaltman

JSON report totalIssues reflects capped count, not actual

Medium Severity

When --max-problems is set, generateReport passes only the capped prioritized slice to outputJsonFormat. Inside that formatter, totalIssues: problems.length then reflects the capped count rather than the true total. The table format correctly receives all problems for counting and only the capped set for display, but JSON and SARIF consumers see a totalIssues that understates the real problem count, with no way to know problems were hidden.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit e5dbdb5. Configure here.

Originally posted by @cursor[bot] in #3080 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions