Repository navigation
ci: free security scanning to replace CodeQL - #4
Closed
prabu-openclaw wants to merge 3 commits into
Closed
prabu-openclaw wants to merge 3 commits into
prabu-openclaw wants to merge 3 commits into
Conversation
CodeQL is licensed for open source only unless the org holds GitHub Code
Security ($30/active committer/month), so it cannot legally run against these
private repos - hosted or via the CLI. This adds permissively-licensed
scanners that can:
gitleaks secrets, full history
bandit python SAST, high severity + high confidence only
semgrep OSS multi-language SAST, ERROR severity only
osv-scanner dependency CVEs, advisory only
All the logic lives in scripts/security-scan.sh, which the workflow simply
calls. That means you can run the identical scan locally at any time:
./scripts/security-scan.sh
Local and CI results match by construction, and neither of us is blocked
waiting on the other's machine to learn whether our code is clean.
Runs on the self-hosted Macs, so it costs nothing and does not depend on the
Actions billing state. Switch to ubuntu-latest once billing is healthy.
.gitleaks.toml suppresses only shapes triaged as false positives across the
org (20 findings, 0 real secrets: Swift UserDefaults keys, golden-snapshot
fixture ids, and synthetic PEMs in tests that assert they get blocked). The
allowlist is restricted to dot-separated reverse-DNS values, so sk_live_*,
ghp_*, AKIA* and friends are still reported - verified against planted
credentials. Detection matches gitleaks' stock config on that canary.
Nothing here uploads source code.
added 2 commits
August 15, 2026 12:39
Patch-Hive already had a .github/workflows/security.yml and the first version of this change silently overwrote it. Renaming to free-security-scan.yml so this can never clobber a repo's own security workflow.
The bandit flags did not match the documented intent. -ll -ii means severity and confidence MEDIUM and above, not HIGH -- so the gate failed on Psy-Fi (High: 0, Medium: 9) and Abraxas-Orchestra (High: 0, Medium: 11), neither of which has a single high-severity finding. The gate now runs -lll -iii (high severity AND high confidence). Medium-and- above still runs immediately before it as informational output, so those findings stay visible without blocking a merge.
Contributor
|
Closing: CI red (validate/CodeQL); free-scanner stack never landed. Prefer current org CodeQL baseline + personal tip security posture after sync. Re-open if we intentionally replace CodeQL. |
2 of 4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Related issue or project item
Testing performed
Collaboration checklist