Skip to content

feat(chaining): export attack path as PNG (#5472) - #7578

Draft
Camille Roux (camrrx) wants to merge 1 commit into
mainfrom
issue/5472
Draft

feat(chaining): export attack path as PNG (#5472)#7578
Camille Roux (camrrx) wants to merge 1 commit into
mainfrom
issue/5472

Conversation

@camrrx

Copy link
Copy Markdown
Member

Proposed changes

Testing Instructions

  1. Step-by-step how to test
  2. Environment or config notes

Related issues

  • Closes #ISSUE-NUMBER

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality
  • For bug fix -> I implemented a test that covers the bug

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@github-actions

Copy link
Copy Markdown
Contributor

📖 Documentation check — ✅ Passed

12 functional file(s), 1 doc file(s) changed.

No documentation gaps detected.

@github-actions github-actions Bot added the filigran team Item from the Filigran team. label Aug 24, 2026
@Filigran-Automation Filigran Automation (Filigran-Automation) changed the title feat(chaining): export attack path as PNG(#5472) feat(chaining): export attack path as PNG (#5472) Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

filigran team Item from the Filigran team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant