Skip to content

ci(ci): exclude local sanity harnesses from JS scan - #262

Merged
ElectroCoderX merged 1 commit into
devfrom
chore/codeql-exclude-sanity-harness
Aug 17, 2026
Merged

ci(ci): exclude local sanity harnesses from JS scan#262
ElectroCoderX merged 1 commit into
devfrom
chore/codeql-exclude-sanity-harness

Conversation

@ElectroCoderX

@ElectroCoderX ElectroCoderX commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Security
    • Added CodeQL scanning configuration for JavaScript and TypeScript code.
    • Improved automated security analysis by applying the repository’s scan settings.

js/clear-text-logging taints process.env, so sanity scripts that log public contract addresses were reported as High. Keep scanning sdk/typescript.

Co-authored-by: Cursor <cursoragent@cursor.com>

Signed-off-by: JaCoderX <12550942+JaCoderX@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a3782bd4-a570-40cb-8b7d-e7a498e1916f

📥 Commits

Reviewing files that changed from the base of the PR and between 4637478 and c2505ca.

📒 Files selected for processing (2)
  • .github/codeql/codeql-config.yml
  • .github/workflows/codeql.yml

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The pull request adds a CodeQL configuration file and updates the CodeQL workflow to use it. The configuration excludes sanity harnesses and the LOC-counting script from scans.

Changes

CodeQL configuration

Layer / File(s) Summary
Configure CodeQL scanning
.github/codeql/codeql-config.yml, .github/workflows/codeql.yml
The repository adds CodeQL exclusions for selected scripts. The workflow loads the new configuration file.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to c2505

This localized CI configuration change has no actionable merge-blocking risk remaining; the owner should ensure the documented CodeQL scope matches the intended policy.

Suggested reviewers: jacoderx

Poem

A rabbit checks the scan at night,
Excluded paths stay out of sight.
The workflow reads its config clear,
Clean CodeQL hops from ear to ear.
One tidy burrow, less to fear.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning No pull request description was provided, so the required change summary, scope, testing, and compliance sections are missing. Add a description using the repository template, including the change rationale, scope, selected change type, testing, and required compliance confirmations.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the CI change to exclude local sanity harnesses from the JavaScript CodeQL scan.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/codeql-exclude-sanity-harness

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ElectroCoderX
ElectroCoderX merged commit d2de766 into dev Aug 17, 2026
4 checks passed
@coderabbitai coderabbitai Bot mentioned this pull request Aug 17, 2026
Merged
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.

2 participants