Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

OASIS SARIF TC: Repository for development of the draft standard, where requests for modification should be made via Github Issues

License

NotificationsYou must be signed in to change notification settings

oasis-tcs/sarif-spec

Repository files navigation

Members of theOASIS 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 itscharter).

OASIS TC GitHub repositories, as described inGitHub Repositories for OASIS TC Members' Chartered Work, are governed by the OASISTC 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 fromOASIS Open Repositories, which are used for development of open sourcelicensed 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 viaGithub 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.

Submissionrequest 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'sCONTRIBUTING 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 andparticipate 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 theOASIS Feedback License.

Licensing

Please see theLICENSE 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 repositoryLICENSE 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 aboutOASIS TC GitHub repositories toRobin Cover andChet Ensign. For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the SARIF TC'shome page.

About

OASIS SARIF TC: Repository for development of the draft standard, where requests for modification should be made via Github Issues

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages


[8]ページ先頭

©2009-2025 Movatter.jp