flowsint

reconurge/flowsint

A modern platform for visual, flexible, and extensible graph-based investigations. For cybersecurity analysts and investigators.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 18, 2026
14 days ago
Ship score
54/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
10K
Forks
1.2K
Open issues
67
Watchers
72
Primary language
TypeScript
Created
Jan 31, 2025
Owner
reconurge · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 210 startups in the directory ship primarily in TypeScript.

Topics

#investigation#osint#python#recon

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Nov 2, 2026 — os_startup 96%, self-hostable 59%, hosted offering 45%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-11-01, found by the weekly discovery job at confidence 0.95. Answered by jev-1.14.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-18This is the badge for reconurge/flowsint, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/reconurge/flowsint.svg)](https://ossean.com/reconurge/flowsint)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.