The GitHub Action for DevSkim
Перейти к файлу
Gabe Stocco 93f77b4320
Update build.yml
2022-10-19 09:31:30 -07:00
.github/workflows Update build.yml 2022-10-19 09:31:30 -07:00
CODE_OF_CONDUCT.md Initial CODE_OF_CONDUCT.md commit 2020-07-14 17:04:23 -07:00
Dockerfile Updated docker image to .NET 6 #10 (#11) 2022-10-19 09:20:48 -07:00
LICENSE Updating LICENSE to template content 2020-07-14 17:04:26 -07:00
README.md Add required quotes to ignore-globs (#9) 2022-09-26 12:14:02 -07:00
SECURITY.md Initial SECURITY.md commit 2020-07-14 17:04:29 -07:00
action.yml Add ignore glob option 2021-10-21 20:38:45 +00:00
entrypoint.sh Use the bath path feature to root results to the github workspace even when a subpath is specified. 2021-10-25 22:02:48 -07:00

README.md

DevSkim

DevSkim is security linter that highlights common security issues in source code.

The DevSkim GitHub Action outputs a sarif file compatible with GitHub's Security Issues view.

Usage

Add DevSkim to your GitHub Actions pipeline like below.

    - uses: actions/checkout@v2
    - uses: microsoft/DevSkim-Action@v1
    - uses: github/codeql-action/upload-sarif@v1
      with:
        sarif_file: devskim-results.sarif

You can also specify a number of options to the action.

    - uses: microsoft/devskim-action@v1
      with:
        directory-to-scan: path/to/scan
        should-scan-archives: false
        output-filename: devskim-results.sarif
        output-directory: path/to/output (appended to $GITHUB_WORKSPACE)
        ignore-globs: "**/.git/**,*.txt"

Features

  • Built-in ruleset highlighting common security issues in source code
  • Support for scanning code contained in archives
  • Information and guidance provided for identified security issues
  • Broad language support including: C, C++, C#, Cobol, Go, Java, Javascript/Typescript, Python, and more.

Main Project

The DevSkim engine powering this GitHub Action is also available here as a Cli and as IDE extensions for Visual Studio and Visual Studio Code.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.