Skip to content

Detect report types from content and accept SARIF - #108

Merged
BacchusJackson merged 3 commits into
mainfrom
cursor/report-types-4e64
Oct 23, 2026
Merged

BacchusJackson merged 3 commits into
mainfrom
cursor/report-types-4e64

Conversation

@BacchusJackson

@BacchusJackson BacchusJackson commented Oct 23, 2026 •

Copy link
Copy Markdown
Member

Fixes #97
Fixes #98
Fixes #99
Fixes #80

Report type now comes from the file contents. The filename is only used when the contents do not say what the file is. That fixes CycloneDX reports with grype in the name being read as Grype.

SARIF 2.1.0 reports can be listed, validated, and bundled. Severity limits use security-severity when the tool sets it, and the SARIF level otherwise. Rule ids can be allowed or denied in the config, same shape as the CVE lists.

Any CycloneDX JSON BOM with vulnerabilities is listed and validated the same way. Grype, Trivy, and other producers share that path. A missing severity string falls back to the CVSS score.

Trivy JSON and osv-scanner JSON from main use that same content detection. The filename is the fallback when a file is ambiguous, including an empty {"results":[]}.

Open in Web Open in Cursor 

Report type now comes from the file contents. The filename is only used when the contents do not say what the file is.

SARIF 2.1.0 reports can be listed, validated, and bundled. Any CycloneDX JSON BOM with vulnerabilities uses the cyclonedx rules, whichever tool wrote it.

Fixes #97
Fixes #98
Fixes #99
Fixes #80

Co-authored-by: Bacchus Jackson (BJaX) <BacchusJackson@users.noreply.github.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Deploying gatecheck-website with  Cloudflare Pages  Cloudflare Pages

Latest commit: 1cbaf15
Status: ✅  Deploy successful!
Preview URL: https://66b5f771.gatecheck-website.pages.dev
Branch Preview URL: https://cursor-report-types-4e64.gatecheck-website.pages.dev

View logs

@BacchusJackson

Copy link
Copy Markdown
Member Author

Code looks good to me. This conflicts with main now that #107 (Trivy) landed, so CI hasn't run yet. Can you merge main in, make sure Trivy JSON goes through the new content detection, and push?

cursoragent and others added 2 commits October 23, 2026 13:11
Trivy and osv-scanner JSON are recognized from their contents, same as the other report types. The filename is only used when the contents are ambiguous.

Fixes #97
Fixes #98
Fixes #99
Fixes #80

Co-authored-by: Bacchus Jackson (BJaX) <BacchusJackson@users.noreply.github.com>
Windows cannot delete a temp config while the decoder still has it open.

Co-authored-by: Bacchus Jackson (BJaX) <BacchusJackson@users.noreply.github.com>
@BacchusJackson
BacchusJackson merged commit fd83a1e into main Oct 23, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants