Skip to content

Add Scrutora Scan code-scanning starter workflow - #3361

Open
Nirvahana wants to merge 2 commits into
actions:mainfrom
Nirvahana:add-scrutora-scan
Open

Add Scrutora Scan code-scanning starter workflow#3361
Nirvahana wants to merge 2 commits into
actions:mainfrom
Nirvahana:add-scrutora-scan

Conversation

@Nirvahana

Copy link
Copy Markdown

Adds a starter workflow for Scrutora Scan under code-scanning/.

Scrutora Scan is an offline, compliance-mapped SAST tool (DPDPA, HIPAA, GDPR, PCI-DSS, RBI). It requires no API key and code never leaves the runner; results upload to GitHub Code Scanning as SARIF via github/codeql-action/upload-sarif.

Files

  • code-scanning/scrutora-scan.yml — the workflow (uses Scrutora/scrutora-scan@v1)
  • code-scanning/properties/scrutora-scan.properties.json — metadata
  • icons/scrutora.svg — icon

Follows the third-party contribution format (based on the existing bearer workflow): includes the "not certified by GitHub" header, $default-branch/$cron-weekly placeholders, least-privilege permissions, and fail-on: none so it reports without gating the build by default.

Action: https://github.com/Scrutora/scrutora-scan

Copilot AI review requested due to automatic review settings July 8, 2026 12:51
@Nirvahana
Nirvahana requested review from a team as code owners July 8, 2026 12:51
@github-actions github-actions Bot added the code-scanning Related to workflows that show on the Code Scanning setup page label Jul 8, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new Code Scanning starter workflow and accompanying metadata/icon so users can run Scrutora Scan in GitHub Actions and upload results to GitHub Code Scanning (SARIF).

Changes:

  • Add code-scanning/scrutora-scan.yml workflow to run Scrutora Scan and upload SARIF.
  • Add code-scanning/properties/scrutora-scan.properties.json to register the starter in the catalog.
  • Add icons/scrutora.svg icon for the starter.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 4 comments.

File Description
code-scanning/scrutora-scan.yml New starter workflow for running Scrutora Scan and uploading SARIF to Code Scanning.
code-scanning/properties/scrutora-scan.properties.json Adds starter metadata (name/creator/description/categories/icon binding).
icons/scrutora.svg Adds the Scrutora icon referenced by the properties file.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread code-scanning/scrutora-scan.yml Outdated
Comment on lines +13 to +16
push:
branches: [ "$default-branch" ]
pull_request:
branches: [ "$default-branch" ]
Comment thread code-scanning/scrutora-scan.yml Outdated
Comment on lines +6 to +8
# Scrutora Scan runs an offline, compliance-mapped scan of your code (DPDPA,
# HIPAA, GDPR, PCI-DSS, RBI). No API key is required and your code never leaves
# the runner. Findings are uploaded to GitHub Code Scanning as SARIF.
{
"name": "Scrutora Scan",
"creator": "Scrutora",
"description": "Offline DPDPA, HIPAA, GDPR, PCI-DSS and RBI compliance scanning. No API key, your code never leaves the runner. Results upload to Code Scanning as SARIF.",
Comment thread code-scanning/scrutora-scan.yml Outdated
Comment on lines +35 to +45
- name: Run Scrutora Scan
uses: Scrutora/scrutora-scan@v1
with:
frameworks: dpdpa,hipaa
fail-on: none # report only; set to high/critical to gate the build

- name: Upload SARIF to Code Scanning
if: always()
uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: scrutora.sarif
…op RBI (not in action docs), upload SARIF via action output
@Nirvahana

Copy link
Copy Markdown
Author

Thanks for the review — all four addressed:

  1. Branch placeholders — switched to unquoted $default-branch and added $protected-branches on push, matching the repo convention (e.g. bearer.yml).
  2. RBI claim (workflow header) — removed; the header now lists only DPDPA/HIPAA/GDPR/PCI-DSS, consistent with the action's documented frameworks.
  3. RBI in metadata description — removed for the same reason.
  4. Hard-coded SARIF filename — the scan step now has id: scan and the upload uses the action's output: sarif_file: ${{ steps.scan.outputs.sarif-file }}.

Both files re-validated. Let me know if anything else is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

code-scanning Related to workflows that show on the Code Scanning setup page

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants