sarif-to-comment-action

KO | EN

gitlite — search

#javascript #python #hacktoberfest #ai #android #machine-learning #rust #deep-learning #macos #cli #kubernetes #vue #pytorch #ios

sarif-to-comment-action

(★ 15)

A GitHub action for @security-alert/sarif-to-comment

sarif-to-comment-action 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# sarif-to-comment-action

[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/sett-and-hive/sarif-to-comment-action/main.svg)](https://results.pre-commit.ci/latest/github/sett-and-hive/sarif-to-comment-action/main)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/6080/badge)](https://bestpractices.coreinfrastructure.org/projects/6080)
[![CI Tests](https://img.shields.io/github/actions/workflow/status/sett-and-hive/sarif-to-comment-action/ci-test.yaml)](https://img.shields.io/github/actions/workflow/status/sett-and-hive/sarif-to-comment-action/ci-test.yaml)

This GitHub action converts a SARIF file with security vulnerability findings
into a GitHub pull request comment using the [@security-alert/sarif-to-comment](https://github.com/security-alert/security-alert/tree/master/packages/sarif-to-comment)
NPM package.

This is useful if you have do *not* have access GitHub Advanced Security,
in a private repository or GitHub Enterprise.
You could, for example, post CodeQL results to a GitHub Issue or
PR as a comment.

These are the inputs to action image.

## Inputs

### `sarif-file`

Path to SARIF file to add to PR comment.
Required.

### `token`

Your GitHub Access Token.
For example, `${{ secrets.GITHUB_TOKEN }}`.
Required.

### `repository`

GitHub repository where this action will run, in owner/repo format.
For example, `${{ github.repository }}`.
Required.

### `branch`

Branch the PR is on.
For example, `${{ github.head_ref }}`.
Required.

### `pr-number`

Number of the pull request.
For example, `${{ github.event.number }}`.
Required.

### `title`

Title for the issue.
Default: `SARIF vulnerabilities report`.

### `show-rule-details`

Flag to show or hide rule details.
Default: true

### `dry-run`

If true, do not post the results to a PR. If false, do post the results to the PR.
Required.
Default: false

### `odc-sarif`

If true, the SARIF input is formatted in the
[OWASP Dependency Check](https://owasp.org/www-project-dependency-check/)
dialect and the input file will be modified so that the action can
correctly parse the SARIF. If false, as for CodeQL SARIF, do nothing extra.
Default: false

### `simple`

If true, simplify the output to only give findings grouped by rule
Default: false

## Example usage

Add this action to your own GitHub action yaml file, replacing the value in
`sarif-file` with the path to the file you want to convert
and add to your pull request in this final step, likely the output of a
security scanning tool. There are additional helper steps to determine
the expected values of `url`, `repo`, and `owner` in the
[comment-test.yaml workflow](./.github/workflows/comment-test.yaml).

```yaml
- name: Post SARIF findings in the pull request
  if: github.event_name == 'pull_request'
  uses: sett-and-hive/sarif-to-comment-action@v2.0.1
  with:
    token: ${{ secrets.GITHUB_TOKEN }}
    repository: ${{ github.repository }}
    branch: ${{ github.head_ref }}
    pr-number: ${{ github.event.number }}
    sarif-file: scan/results/xss.sarif
    title: My security issue
    dry-run: false
```

You will need to give you job write permissions for issues for this action to succeed.

If you want to test locally with [`nektos/act`](https://github.com/nektos/act),
you will need to add choose a VM runner with `docker` so the tests work locally with
`act`. Make sure you use an [action VM runner](https://github.com/nektos/act#runners)
that contains the Docker client, like `ubuntu-latest=catthehacker`.

```console
act -P ubuntu-latest=catthehacker/ubuntu:act-20.04 -j test pull_request
```

With a section in your `test` job similar to this:

```yaml
- name: Post SARIF findings in the pull request
  if: github.event_name == 'pull_request'
  uses: sett-and-hive/sarif-to-comment-action@v2.0.1
  with:
    token: fake-secret
    # token: ${{ secrets.GITHUB_TOKEN }}
    branch: 'your-branch'
    pr-number: '1'
    repository: ${{ github.repository }}
    sarif-file: "./test/fixtures/codeql.sarif"
    title: My security issue
    dry-run: 'true' # will not post to PR
    odc-sarif: true
```

### Sample action file

```yaml
# A workflow that posts SARIF results to an issue

name: Your security scan workflow

on:
  pull_request:
    branches: [main]
  schedule:
    - cron: "0 3 * * *"
  workflow_dispatch:

permissions:
  issues: write

jobs:
  issue:
    runs-on: ubuntu-latest
    name: Run the scan that generates a SARIF file

steps:

- name: Checkout
        uses: actions/checkout@v3

# Your actual scanning step here
      - name: Your security scanner that generates SARIF output
        uses: your-favorite/security-scanner@main
        with:
            format: SARIF
            report-path: ./report/scan-findings.sarif

- name: Post SARIF findings in the issue
        uses: sett-and-hive/sarif-to-issue-action@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          repository: ${{ github.repository }}
          branch: ${{ github.head_ref }}
          pr-number: ${{ github.event.number }}
          sarif-file: ./report/scan-findings.sarif
          title: "Security scanning results"
          odc-sarif: false
```

## Running as a composite action

Running this action as a composite action allows to run it on dockerized
self-hosted runners and various operating systems as it does not require
Docker. To run it as a composite action, add `/composite` to the action name:

```yaml
- name: Post SARIF findings in the pull request
  uses: sett-and-hive/sarif-to-comment-action/composite@v1
  with:
    ...
```

Note that this will require node environment to be installed on your machine.
You can install it with [Setup node action](https://github.com/actions/setup-node).

## Testing

There is a simple test that builds and runs the Dockerfile and does a dry run of
`@security-alert/sarif-to-comment` with a test fixture file with known vulnerabilities.

```console
test/test.sh
```

All new functionality must be covered by tests.

### Testing with `bats`

We are migrating to [`bats`](https://github.com/bats-core/bats-core) for testing. The old test script is still available
but will be removed in the future.

To get started locally with bats:

- On Debian/Ubuntu, install it with `sudo apt-get install bats`
- On macOS, install it with Homebrew: `brew install bats-core`
- For other platforms or installation methods, see the [official bats-core installation documentation](https://github.com/bats-core/bats-core#installation)

```console
test/run_tests.sh
```

## Security testing

There is a security test that builds and runs the `trivy` scanner
to test for vulnerabilities in the Dockerfile image.

```console
test/trivy.sh
```

## CI

There are two files that perform different tests on the repository.

[comment-test.yaml workflow](./.github/workflows/comment-test.yaml) uses the
`sett-and-hive/sarif-to-comment-action` action as one would in their own action workflow.

[cit-test.yaml workflow](./.github/workflows/ci-test.yaml) runs the same test
script used to develop the action in this repository, ``test/test.sh`.

There is a security scanning workflow as well, [trivy workflow](./.github/workflows/trivy.yaml),
that scans each day and also scans each PR.
There is a [gitleaks workflow](./.github/workflows/gitleaks-workflow.yaml)
that detects secrets, to keep them out of the repository.

There is also a [review-trivyignore workflow](./.github/workflows/review-trivyignore.yaml)
that runs weekly to review vulnerabilities listed in `.trivyignore` and check if patches
have become available. This helps ensure we don't continue ignoring vulnerabilities after
fixes are released. The workflow creates or updates a tracking issue with findings.

## Contributing

Pull requests and stars are always welcome.

For bugs and feature requests, [please create an issue](https://github.com/sett-and-hive/sarif-to-comment-action/issues).
All new functionality must be covered by tests.
Please follow this [bash style guide](https://google.github.io/styleguide/shellguide.html)
when updating or creating scripts.

1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :star:

sarif-to-comment-action

sarif-to-comment-action 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

sarif-to-comment-action

sarif-to-comment-action 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README