Skip to content
Projects

synacktiv/action-octoscan

View on GitHub

synacktiv/action-octoscan has 26 GitHub stars and 0 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-14 18:10 UTC. Last push 2026-11-12.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
Collecting history
in 15 days
Collecting history
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

📦 :octocat: A GitHub Action that performs a security scan of your GitHub Actions.

Security

README.md

Original
📦 :octocat:

action octoscan

A GitHub Action that performs a security scan of your GitHub actions.

This action is based on octoscan


🤸 Usage

Here is a basic example of how to use this action. This will work for both push and pull_request events.

---
name: Octoscan

on:
  workflow_dispatch:
  pull_request:
    paths:
      - '.github/workflows/*'
  push:
    paths:
      - '.github/workflows/*'

permissions:
  security-events: write
  actions: read
  contents: read

jobs:
  octoscan:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - id: octoscan
        name: Run octoscan
        uses: synacktiv/action-octoscan@v1

      - name: Upload SARIF file to GitHub
        uses: github/codeql-action/upload-sarif@v3
        with:
          sarif_file: "${{steps.octoscan.outputs.sarif_output}}"
          category: octoscan

Versions

The action downloads octoscan from its releases when it runs, so synacktiv/action-octoscan@v1 always runs the latest release of octoscan, with nothing to update.

To reproduce a run, pin octoscan with the version input and the action with a commit SHA:

- uses: synacktiv/action-octoscan@<commit sha>
  with:
    version: v0.1.7

The binary is verified with the SHA256SUMS of the release (releases published before they existed are not).

Security results can the be reviewed in the code security tab if you have write access on the target repository: code security

Or directly in the pull request: code security

Customizing

inputs

Inputs are based on the options of octoscan, you can find them here.

The following are optional as step.with keys:

Name Type Description
version String Version of octoscan to run: latest (the default) or a release like v0.1.7.
workdir String Working directory relative to the root directory.
filter_triggers String Scan workflows with specific triggers (comma separated list: "push,pull_request_target" or pre-configured: external/allnopr). Default is external.
filter_run Boolean Search for expression injection only in run shell scripts. Default is true
ignore String Regular expression matching to error messages you want to ignore.
disable_rules String Disable specific rules. Split on ",". Can't be used with enable_rules.
debug_rules Boolean Enable the debug rules. Default is false.
config_file String Config file of octoscan, relative to workdir.
token String Token used to download octoscan from its releases. Default is the github.token.
enable_rules String Enable specific rules, this will disable all other rules. Split on ",". Can't be used with disable_rules.

💡 It's not possible to use enable_rules and disable_rules at the same time.

outputs

The following outputs can be accessed via ${{ steps.<step-id>.outputs }} from this action

Name Type Description
sarif_output String The name of the file containing the sarif output.

Runners

Linux runners only (x64 and arm64). shellcheck is preinstalled on the GitHub-hosted runners, without it the shellcheck rule is skipped with a warning.

Permissions

This Action requires the following permissions on the GitHub integration token:

permissions:
  security-events: write
  actions: read
  contents: read

security-events is used to push the output of octoscan to GitHub code scanning.