From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Support for SARIF (by SmPL)?
Date: Fri, 26 Sep 2025 15:50:40 +0200 [thread overview]
Message-ID: <c9dab7e4-402b-4f3a-8a10-f7665e38eb1d@web.de> (raw)
Hello,
The Static Analysis Results Interchange Format is published as an OASIS standard.
https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html
Related background information is available.
* Tutorials
https://github.com/microsoft/sarif-tutorials
* Structured Diagnostics
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3358r0.html#static-analyzers
How do you think about to benefit any more from source code analysis
result output in such a standard file format also by the means of
the semantic patch language?
Regards,
Markus
reply other threads:[~2025-09-26 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9dab7e4-402b-4f3a-8a10-f7665e38eb1d@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).