Add tirith-core for shell command security analysis #63
+461
−74
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
Integrate tirith-core library to analyze shell commands before execution, detecting security threats like: - Homograph attacks (Unicode lookalikes) - Terminal injection (ANSI escapes, bidi controls) - Pipe-to-shell patterns (curl | bash) - Insecure transport and credential exposure The security analysis runs in a separate thread to avoid blocking the async runtime. Commands flagged as dangerous are blocked; warnings are prepended to output for suspicious but allowed commands. Note: Security analysis is skipped in test mode to avoid resource contention with timing-sensitive tests. https://claude.ai/code/session_01JWGY085M4E96QV0R2XPM1CEX
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Integrate tirith-core library to analyze shell commands before execution,
detecting security threats like:
The security analysis runs in a separate thread to avoid blocking the
async runtime. Commands flagged as dangerous are blocked; warnings are
prepended to output for suspicious but allowed commands.
Note: Security analysis is skipped in test mode to avoid resource
contention with timing-sensitive tests.
https://claude.ai/code/session_01JWGY085M4E96QV0R2XPM1CEX