Repository navigation
Conversation
Insecure Use of Crypto (1)
More info on how to fix Insecure Use of Crypto in Python. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
|
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
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.
The APE hook read stdin as plain text, but Claude Code sends JSON, so the triage never matched and every prompt, even "ok", got the full spec (~1.2k tokens) injected, which stays in the context. Now: the prompt is read from the JSON, trivial / technical / short follow-up prompts get nothing, the first prompt that needs APE gets the compact block of the spec (~230 tokens) once per session, later ones a one-line reminder. Fail-open kept. Source: claude-config .claude/ape.