Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions .github/workflows/shai-hulud-check.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
name: Shai-Hulud Security Check

on:
pull_request:
paths:
- "**/package.json"
- "**/package-lock.json"
- "**/yarn.lock"
- "**/pnpm-lock.yaml"
- "**/bun.lockb"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Include bun.lock in workflow path filters

The pull_request/push path filters only match **/bun.lockb, so dependency updates that touch Bun’s current default lockfile (bun.lock) will not trigger this security scan on PRs or branch merges. That creates a real detection gap where compromised transitive changes in bun.lock are only caught by the weekly schedule or manual runs instead of immediately during code review.

Useful? React with 👍 / 👎.

- ".github/workflows/shai-hulud-check.yml"
push:
branches: [main, master]
paths:
- "**/package.json"
- "**/package-lock.json"
- "**/yarn.lock"
- "**/pnpm-lock.yaml"
- "**/bun.lockb"
- ".github/workflows/shai-hulud-check.yml"
schedule:
- cron: "27 9 * * 1"
workflow_dispatch: {}

permissions:
contents: read

jobs:
scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
- uses: gensecaihq/Shai-Hulud-2.0-Detector@v2
with:
scan-lockfiles: true
fail-on-critical: true
Loading