Skip to content

chore(security): add SCA scan workflow - #2880

Merged
cschetan77 merged 3 commits into
masterfrom
security/add-sca
Nov 4, 2026
Merged

cschetan77 merged 3 commits into
masterfrom
security/add-sca

Conversation

@nirmal-joishi-a0

@nirmal-joishi-a0 nirmal-joishi-a0 commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

✏️ Changes

This pull request adds a security hardening workflow. No functional changes are introduced.

SCA Scan

This PR adds .github/workflows/sca.yml. It uses the Okta-approved SCA workflow from auth0/devsecops-tooling: 'auth0/devsecops-tooling/.github/workflows/sca-scan.yml@e29f26478db18ff0bcbe4bc447a8fbd54fbeec9e'

Required org secrets (must be present)

  • SNYK_TOKEN
  • SIGNAL_HANDLER_TOKEN
  • SIGNAL_HANDLER_DOMAIN

🟠 Declining this workflow

This is an organization-enforced security-hardening workflow, so closing this PR is not enough — the tool treats a plain close as a discard and opens a fresh replacement PR on its next run.

To permanently decline this category, a maintainer must close this PR and add one of these labels to it:

Label Use when
remediation: not-required The category is already handled another way for this repo.
remediation: not-applicable The category genuinely does not apply (e.g. there is no manifest to scan for SCA, or no release/build CI to wire the malware scan into).

Applying a label requires write, triage, or admin access, so the label is a trusted maintainer signal. Once a closed PR carries one of these labels, the tool respects the decline and will not reopen a replacement.

🔮 Type of Change

  • Standard

🔗 References

This change applies a standard automated security-scanning workflow as part of routine repository hardening.

  • I explained why this change is needed.

📖 Documentation

No user-facing changes have been introduced.

  • I reflected this change in the (internal and/or user-facing) documentation, or added an explanation for why no documentation update is needed.

🎯 Testing

⚠️ This workflow runs on this PR. Before merging, confirm that run triggers and passes, and that a green result is not masking a skipped or silently-ignored scan.

  • The PR run has been verified green in this repository's CI (not a skipped/empty result).

🚀 Deployment

  • This change can support multiple releases of the code serving traffic at the same time.

🔥 Rollback

Reverting this PR removes the added workflow file — no further action required.

  • I explained what the rollback for this change will look like.

@nirmal-joishi-a0
nirmal-joishi-a0 requested a review from a team as a code owner October 8, 2026 14:08
@nirmal-joishi-a0

Copy link
Copy Markdown
Contributor Author

@auth0/project-dx-sdks-engineer-codeowner please review the files in the PR. This automated security-hardening workflow is untested in this repo — before merging, confirm it triggers and passes (and is not silently ignoring failures); do not merge on a green result alone.

@nirmal-joishi-a0

Copy link
Copy Markdown
Contributor Author

An internal service ticket has been filed for the owning team to review and merge this PR.

nirmal-joishi-a0 and others added 2 commits November 4, 2026 13:14
Resolves Scorecard Token-Permissions alert. The reusable sca-scan
and scan-log workflows only use actions/checkout.

Co-Authored-By: Claude <noreply@anthropic.com>
@cschetan77
cschetan77 merged commit 26c4d74 into master Nov 4, 2026
5 checks passed
@cschetan77
cschetan77 deleted the security/add-sca branch November 4, 2026 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants