When an investigator finishes a session in Flowsint, there is no built-in way to export the selected nodes and edges as a machine-readable file. Exporting is needed for reporting, backup, or feeding data into external tools.
Proposed Solution
Add a right-click context menu option on selected graph nodes (or a toolbar button) that exports the selected nodes + their edges as a JSON file:
This is a small surface-area addition — it reads the already-loaded graph selection and serialises it. No new data model needed.
Use Case
Investigator exports a subset of a graph for a written report or handover
Backup specific investigation sessions as JSON files
Feed selected data into external OSINT tooling
Originally created by @fuleinist on GitHub (Jun 5, 2026).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/177
## Problem
When an investigator finishes a session in Flowsint, there is no built-in way to export the selected nodes and edges as a machine-readable file. Exporting is needed for reporting, backup, or feeding data into external tools.
## Proposed Solution
Add a right-click context menu option on selected graph nodes (or a toolbar button) that exports the selected nodes + their edges as a JSON file:
{
"exported_at": "2026-06-05T14:00:00Z",
"nodes": [...],
"edges": [...]
}
This is a small surface-area addition — it reads the already-loaded graph selection and serialises it. No new data model needed.
## Use Case
- Investigator exports a subset of a graph for a written report or handover
- Backup specific investigation sessions as JSON files
- Feed selected data into external OSINT tooling
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @fuleinist on GitHub (Jun 5, 2026).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/177
Problem
When an investigator finishes a session in Flowsint, there is no built-in way to export the selected nodes and edges as a machine-readable file. Exporting is needed for reporting, backup, or feeding data into external tools.
Proposed Solution
Add a right-click context menu option on selected graph nodes (or a toolbar button) that exports the selected nodes + their edges as a JSON file:
{
"exported_at": "2026-06-05T14:00:00Z",
"nodes": [...],
"edges": [...]
}
This is a small surface-area addition — it reads the already-loaded graph selection and serialises it. No new data model needed.
Use Case