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.

Sign up for GitHub

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

Jump to bottom

Support recommended security-severity property in SARIF file export #762

Open
graemechristie opened this issue Jan 22, 2024 · 2 comments · May be fixed by #1587
Open

Support recommended security-severity property in SARIF file export #762

graemechristie opened this issue Jan 22, 2024 · 2 comments · May be fixed by #1587
Labels
backlog Important but currently unprioritized enhancement New feature or request

Comments

@graemechristie
Copy link

The current rules in the exported Sarif file do not include the security-severity property. A per the docs below, this is recommended for security rules.

https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#reportingdescriptor-object

Likewise, the precision property is also recommended and used in concert with the security severity to assess the impact of the recorded CVE's.
@cuixq cuixq added the enhancement New feature or request label Jan 22, 2024
@github-actions GitHub Actions
Copy link

This issue has not had any activity for 60 days and will be automatically closed in two weeks

@github-actions github-actions bot added the stale The issue or PR is stale and pending automated closure label Jul 19, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 2, 2024

Automatically closing stale issue

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
@oliverchang oliverchang added backlog Important but currently unprioritized and removed stale The issue or PR is stale and pending automated closure labels Aug 6, 2024
@oliverchang oliverchang reopened this Aug 6, 2024
@mickem mickem linked a pull request Feb 7, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog Important but currently unprioritized enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Added support for severity in sarif report mickem/osv-scanner
3 participants
@oliverchang @graemechristie @cuixq