Skip to content
OASIS SARIF TC: Repository for development of the draft standard, where requests for modification should be made via Github Issues
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Agendas
Documents Update TOC on provisional draft docx and HTML. Apr 24, 2019
EditorsReports #388: Resolve dup of #391. Apr 20, 2019
Schemata Add v2.0.0-csd.2.beta.2019-01-24.1 schema Feb 24, 2019
Tool Samples Remove SWAMP Tools\tool_results_with_paths.txt Jan 29, 2018
meetings fixed two typos / vim leftovers in minutes draft - kudos to Laurence Nov 30, 2017
CONTRIBUTING.md create static boilerplate CONTRIBUTING file Sep 14, 2017
LICENSE.md
README.md update with link to Issues Sep 21, 2017
Workflow.md FIx #67: Clarify approval process in Workflow.md Nov 3, 2017

README.md

README

Members of the OASIS Static Analysis Results Interchange Format (SARIF) TC create and manage technical content in this TC GitHub repository ( https://github.com/oasis-tcs/sarif-spec ) as part of the TC's chartered work (i.e., the program of work and deliverables described in its charter).

OASIS TC GitHub repositories, as described in GitHub Repositories for OASIS TC Members' Chartered Work, are governed by the OASIS TC Process, IPR Policy, and other policies, similar to TC Wikis, TC JIRA issues tracking instances, TC SVN/Subversion repositories, etc. While they make use of public GitHub repositories, these TC GitHub repositories are distinct from OASIS Open Repositories, which are used for development of open source licensed content.

Description

The purpose of the SARIF TC is to define a standard output format for static analysis tools, which will be called the Static Analysis Results Interchange Format (SARIF). This GitHub repository supports development of the draft SARIF standard. Requests for modification should be made via Github Issues.

A static analysis tool is a program that examines programming artifacts in order to detect problems, without executing the program. Software developers use a variety of static analysis tools to assess the quality of their programs. To form an overall picture of program quality, developers must often aggregate the results produced by all of these tools. This aggregation is more difficult if each tool produces output in a different format. A standard output format would make it feasible for developers and teams to view, understand, interact with, and manage the results produced by all the tools that they use.

Submission request from David Keaton (SARIF TC Co-Chair): we expect to populate this repository from the existing one found here: https://github.com/sarif-standard/sarif-spec.

Contributions

As stated in this repository's CONTRIBUTING file, contributors to this repository are expected to be Members of the OASIS SARIF TC, for any substantive change requests. Anyone wishing to contribute to this GitHub project and participate in the TC's technical activity is invited to join as an OASIS TC Member. Public feedback is also accepted, subject to the terms of the OASIS Feedback License.

Licensing

Please see the LICENSE file for description of the license terms and OASIS policies applicable to the TC's work in this GitHub project. Content in this repository is intended to be part of the SARIF TC's permanent record of activity, visible and freely available for all to use, subject to applicable OASIS policies, as presented in the repository LICENSE file.

Further Description of this Repository

[Any narrative content may be provided here by the TC, for example, if the Members wish to provide an extended statement of purpose.]

Contact

Please send questions or comments about OASIS TC GitHub repositories to Robin Cover and Chet Ensign. For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the SARIF TC's home page.

You can’t perform that action at this time.