Add --export-json for structured verification results
#4472
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
…o add runner results
…n-handler # Conflicts: # kani-driver/src/main.rs
…schedule the schema for harness metadada util func.
…kani-output into feat/json-handler
…s_runner.rs to minimize dependency
This reverts commit a2e7757.
Feat/json handler
Member
|
Thank you for your contribution! I notice that you include an RFC document in your pull request, but I think the expectation is that an RFC (a request-for-comment!) is submitted as a PR of its own to solicit discussion before coming up with a major new feature or change. You don't need to close this PR, but I think it would be useful to separately have a discussion on this topic as the specific JSON structure is a one-way-door for future changes to it would risk breaking other tools. |
fix: format frontend code and fix json file not found error
Author
|
Thank you for your suggestion! We discussed with Rajath about this and user can opt in using the flag so hopefully nothing will be broken. |
fix: update cbmc for minimal changes, delete redundant changes
- Implement MCP server to integrate Kani with AI assistants - Add tools: verify_rust_project, verify_unsafe_code, explain_kani_failure, generate_kani_harness - Add Kani output parser - Enable Amazon Q to run Kani verification via MCP protocol
Update: MCP Integration with Amazon Q CLI
Revert "Update: MCP Integration with Amazon Q CLI"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Add opt-in JSON export (--export-json ) to emit structured verification results (metadata, per-harness outcomes, CBMC stats).
Improves Kani by enabling reliable machine-readable output for external tools and applications.
Context: Current output is human-readable only, which blocks robust automation and integrations.
Manual tests:
• Run cargo kani --export-json out.json
• With multiple harnesses: counts in summary match executed harnesses.
Resolves #2572
Resolves #2636
Resolves #2574
Resolves #2562
Resolves #1194
Resolves #1219
Resolves #1045
Resolves #598
Resolves #3357
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.