Verification tools - #217
Merged
Merged
Conversation
…nalysis Add Go-aware tools that follow module resolution instead of relying on blind grep searches, reducing false positives and wasted tool calls: - check_module: traces go.mod replace → vendor → actual symbol calls - check_go_version: compares Go toolchain version against stdlib fix versions (one-shot answer for stdlib CVEs) - is_test_only: detects test files/packages to filter non-production code - check_build_tags: reads //go:build constraints for platform-specific code - list_entry_points: finds all main()/init() entry points in the repo - check_transitive_deps: shows direct vs transitive deps with import chain Update verification prompt to prioritize specialized tools over grep_code and restructure investigation checklists accordingly. Extend GoModEdit struct with Module and Require fields for richer go.mod parsing. Signed-off-by: Vinu K <kevy.vinu@gmail.com>
Five changes to prevent the scanner's verdict from influencing Claude's
independent assessment:
1. Remove agrees_with_scanner, rename claude_assessment to IsVulnerable
- Claude reports its own verdict; agreement computed in code
- Frontend now shows Claude's IsVulnerable directly
2. Strip FixCommands and Symbols from UsedImports in prompt JSON
- These fields leaked the scanner's conclusion before Step 5
3. Move call traces from upfront data to Step 2
- Claude investigates independently in Step 1, then cross-checks
against scanner traces in Step 2
4. Add devil's advocate step (Step 4) before final assessment
- Forces Claude to argue against its own hypothesis
5. Change check_go_version to output neutral version data
- Shows "current=X, fix=Y" instead of "PATCHED"/"VULNERABLE"
Signed-off-by: Vinu K <kevy.vinu@gmail.com>
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.
No description provided.