Skip to content

Issues: oasis-tcs/sarif-spec

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

77 Open 469 Closed
77 Open 469 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Add normative statement against case variation of required keys 2.2.0 proposal issue provides a complete proposal to-be-discussed
#681 opened Mar 6, 2025 by sthagen
@sthagen
Investigate information modeling for future SARIF proposal issue provides a complete proposal to-be-discussed to-be-written
#680 opened Mar 6, 2025 by sthagen
@sthagen
1
SARIF should have clearer guidance for sensitive data handling best practices to-be-discussed
#678 opened Feb 18, 2025 by ShiningMassXAcc
@sthagen
1
Collection of example SARIF data for interoperability/testing/reference etc to-be-discussed
#677 opened Feb 16, 2025 by davidmalcolm
@sthagen
What can arguments to placeholders contain? (§3.11.11 and §3.11.15) to-be-discussed
#676 opened Feb 13, 2025 by davidmalcolm
@sthagen
3
Clarify that most keys in SARIF are case-sensitive impact-non-breaking-change propose-to-close No activity from the TC; no "energy" around it; probably not important; or topic for future version. question to-be-discussed
#665 opened Dec 19, 2024 by jsoref
@sthagen
10
"Semantic" markup in SARIF messages question to-be-discussed
#662 opened Oct 9, 2024 by davidmalcolm
@sthagen
8
"Progressive" or "dynamic" SARIF question to-be-discussed
#661 opened Sep 24, 2024 by davidmalcolm
@sthagen
2
How to Convert Json value into Sarif format question
#660 opened Sep 3, 2024 by mohdrashid1
@sthagen
1
Ambiguous interpretation of square brackets in plaintext messages with embedded links (3.11.6)? 2.2.0
#658 opened Aug 19, 2024 by davidmalcolm
1
Is any escaping of URIs within "3.11.6 Messages with embedded links" needed? question to-be-discussed
#657 opened Aug 19, 2024 by davidmalcolm
4
Suspected typo in EXAMPLE 1 of "3.11.6 Messages with embedded links" 2.2.0
#656 opened Aug 19, 2024 by davidmalcolm
1
artifact.sourceLanguage property (§3.24.10) for SARIF itself 2.2.0
#654 opened Aug 9, 2024 by davidmalcolm
RFE: support for capturing chains of macro expansions? to-be-discussed
#650 opened Jul 22, 2024 by davidmalcolm
@sthagen
2
Consider using the "relevant to understanding the result" wording also in notifications/relatedLocation editorial Purely editorial. enhancement impact-documentation-only
#649 opened Jul 11, 2024 by sthagen
@sthagen
Provide prose explaining the use of guids across all occurrences 2.2.0 impact-documentation-only proposal issue provides a complete proposal to-be-discussed
#648 opened Jul 11, 2024 by sthagen
@sthagen
1
sarif 2.1.0 schema url in Schemata stopped working
#646 opened Jul 11, 2024 by jsoref
2
Enhance artifactContent object with optional context property to accompany text property to-be-discussed
#630 opened Apr 5, 2024 by 247arjun
1
Consider adding a generatedOrAugmentedByAI tag to-be-discussed
#625 opened Feb 8, 2024 by michaelcfanning
2
"3.11.6 Messages with embedded links" example mistake editorial Purely editorial. enhancement
#619 opened Jan 6, 2024 by Marcono1234
@sthagen @stacywray
Sourcemaps or #line directives question to-be-discussed
#618 opened Dec 17, 2023 by ratmice
@sthagen
15
SARIF 2.2 Proposal: Add clearer and explicit relationships between guid, correlationGuid, fingerprints, partialFingerprints, and workItemUris result properties. 2.2.0
#615 opened Nov 10, 2023 by ShiningMassXAcc
1
SARIF 2.2 Proposal: workItemUris no longer required to be all or nothing for a run 2.2.0
#614 opened Nov 9, 2023 by ShiningMassXAcc
2
SARIF 2.2 proposal: security-severity field for reportingDescriptors and results 2.2.0
#612 opened Nov 8, 2023 by adityasharad
4
SARIF 2.2 proposal: precision field for reportingDescriptors and results 2.2.0
#611 opened Nov 8, 2023 by adityasharad
3
ProTip! What’s not been updated in a month: updated:<2025-02-16.