You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
scan-and-report.yml: "Build the commit under test" builds the caller, so every external caller dies at "Run scan" (exit 127) #276
Every repository that calls scan-and-report.yml as a reusable workflow fails at Run scan:
./target/release/panic-attack: No such file or directory
##[error]Process completed with exit code 127.
Observed on hyperpolymath/echidna main: Security Scan run 42351376316, calling scan-and-report.yml@be6ac46.
Root cause
#242 (df96e43, 2026-10-25) answered #212 by replacing cargo install --git … --branch main with:
- uses: actions/checkout@3d3c42e… # v7.0.1 # no `repository:`
- name: Build the commit under testrun: cargo build --locked --release
- name: Run scanrun: ./target/release/panic-attack assail …
Inside a reusable workflow, actions/checkout without repository: checks out the caller. So cargo build builds the caller's crate, echidna in this case, and no panic-attack binary is ever produced.
The step works only when panic-attack calls itself. That is presumably the only place it was exercised.
Proposed fix
Keep the #212 property, building the pinned scanner and never main, by building panic-attack from the reusable's own commit:
- uses: actions/checkout@3d3c42e… # v7.0.1 # caller: the scan target
- uses: actions/checkout@3d3c42e… # v7.0.1 # scanner source at this reusable's commitwith:
repository: hyperpolymath/panic-attackref: ${{ job.workflow_sha }}path: .panic-attack-srcpersist-credentials: false
- name: Build the scanner at the pinned commitrun: cargo build --locked --release --manifest-path .panic-attack-src/Cargo.toml
- name: Run scanrun: .panic-attack-src/target/release/panic-attack assail ${{ inputs.repo_path }} --output scan-result.json
job.workflow_sha is the commit of the called workflow, so a caller pinning @<sha> gets exactly that scanner.
The scan step should exclude .panic-attack-src from the target. Either check it out outside $GITHUB_WORKSPACE, or delete it before scanning, as standards' secret scanner does with its tooling checkout.
Acceptance criteria
An external caller (e.g. echidna's security-scan.yml) reaches Run scan, and the binary exists.
panic-attack's own self-call still builds the commit under test.
The scan report contains no findings from .panic-attack-src.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 9, 2026
🔗 Related PRs
#242 - CI/CD foundation + PR
#241consolidation (coverage, PHP, estate conformance) [merged]📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
fix(ci): give a manual run of scan-and-report.yml its inputs (#287)
fix(ci): repin Security Scan to the panic-attack workflow that builds…