Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No "Scanned Files" Displayed #604

Open
Sof0-0 opened this issue Feb 14, 2024 · 2 comments
Open

No "Scanned Files" Displayed #604

Sof0-0 opened this issue Feb 14, 2024 · 2 comments
Labels
enhancement external Issues that require an external change to resolve

Comments

@Sof0-0
Copy link

Sof0-0 commented Feb 14, 2024

DevSkim scanned tons of files in the repo, and alerts are being reported perfectly fine, but I cannot see how many files were scanned (like CodeQL does for example) Is there any way to configure this?
Screenshot 2024-02-14 at 12 29 02

I would appreciate your help!

@Sof0-0 Sof0-0 added the bug label Feb 14, 2024
@gfs
Copy link
Contributor

gfs commented Feb 14, 2024

I'm not sure what property populates that field. It doesn't appear to be documented in the GitHub documentation for how the code scanning feature parses sarif: https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning. From this other page, it sounds like populating that field may be limited to CodeQL only: https://docs.github.com/en/code-security/code-scanning/managing-your-code-scanning-configuration/about-the-tool-status-page#how-codeql-defines-scanned-files. The results for the files that were scanned appear to be in CSV format, but the Upload Sarif action doesn't provide any argument to provide such a csv: https://github.com/github/codeql-action/blob/v3/upload-sarif/action.yml

@gfs
Copy link
Contributor

gfs commented Feb 29, 2024

I was able to confirm that this feature is currently only available for CodeQL Scanning.

@gfs gfs added enhancement external Issues that require an external change to resolve and removed bug labels Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement external Issues that require an external change to resolve
Projects
None yet
Development

No branches or pull requests

2 participants