Skip to main content

Purpose

Establish a working Snyk dependency vulnerability scanning workflow in any DSOM GitHub repository using GitHub Actions. This skill replaces the permanently deprecated redhat-actions/crda@v1 action whose backend (gw.api.openshift.io) was shut down by Red Hat.

Trigger Conditions

Invoke this skill when:
  • Setting up a new DSOM project on GitHub and requiring CI/CD security scanning.
  • Encountering the error: crda exited with code 1, Unable to reach gw.api.openshift.io.
  • Any redhat-actions/crda workflow is present in .github/workflows/.
  • The user requests dependency vulnerability scanning or SARIF integration.

Quality Gates

  • SNYK_TOKEN is set in GitHub → Settings → Secrets → Actions.
  • requirements.txt (Python), package.json (Node.js), or equivalent manifest exists at repo root.
  • github/codeql-action/upload-sarif@v4 is used (NOT @v3, deprecated Dec 2025).
  • continue-on-error: true is set on the Snyk scan step so SARIF always uploads.
  • Token audit passes: no SNYK_TOKEN value committed to any file.

Step 1, Obtain SNYK_TOKEN

The SNYK_TOKEN is the Snyk account API auth token. It is not the Snyk Project ID.
  1. Log in to app.snyk.io.
  2. Click avatar (top-right) → Account Settings.
  3. Under Auth Tokenclick to show or Generate.
  4. Copy the token value (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
Security Note: Never commit this token to any file. Add it only as a GitHub Secret. The DSOM tools/privacy-guardian.ps1 / .sh will flag tokens in brain files at EOD.

Step 2, Add Secret to GitHub Repository

  1. Navigate to: https://github.com/<owner>/<repo>/settings/secrets/actions/new
  2. Set:
    • Name: SNYK_TOKEN
    • Secret: (paste the token from Step 1)
  3. Click Add secret.

Step 3, Create requirements.txt (Python Projects)

Snyk requires a manifest file to scan. If none exists:
For Node.js projects, package.json is auto-detected. For other ecosystems, see Snyk supported languages.

Step 4, Deploy the Workflow

Create or replace .github/workflows/crda.yml with the following proven template:
Commit and push:

Step 5, Verify Results

After the workflow completes:
  • Go to GitHub → Security → Code scanning to view detected vulnerabilities.
  • The Snyk Project ID (from app.snyk.io) can be used to query results via the Snyk API, it is not needed in the workflow itself.

Known Deprecations & Version Pins


SOURCES


Deep State of Mind (DSOM) For My AI Protocol | Harisfazillah Jamel (LinuxMalaysia) | 2026-07-27 Standard: UK English | DBP-standard Bahasa Melayu Malaysia (Piawai) | GNU General Public License v3.0