Conversation
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
1 participant
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.
Adds rebar to Static Analysis & Linters.
Disclosure: I'm the author.
It fits the scope as a pre-deployment check of the files that configure coding agents.
rebar-securityis a static, deterministic scanner that reads what a repository versions and flags known prompt-injection signatures: hidden Unicode (including in file names and commit messages), terminal control bytes, agent settings files that run commands or widen approval (.claude/settings.json, Codex config, VS Code tasks, devcontainers), MCP server launches that are not allowlisted, agent CLIs invoked with their approval switch off, and GitHub Actions AI steps reachable by untrusted issue/PR text.npx -p github:Navesz/rebar rebar-security .Checked that it isn't already listed, and followed the entry format from CONTRIBUTING.md.