willcrichton/flowistry

Flowistry is an IDE plugin for Rust that helps you focus on relevant code.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 22nd, 2026
Created on March 9th, 2021
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 64
Total Stargazers: 3,074 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.0 days
Mean response time: 143.6 days
90th percentile: 194.5 days
Tracked items: 12

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 712 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)
  • platform-support (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Flowistry is an IDE plugin for Rust that analyzes information flow to help developers focus on relevant code.

The tool solves the problem of navigating large functions by determining which pieces of code can influence or be influenced by a selected variable or expression. When you click on a target in the editor, Flowistry fades out all unrelated code, leaving only the portions that have a data dependency relationship with your selection. This approach is grounded in a formal algorithm for modular information flow analysis through ownership, published at PLDI 2022.

Flowistry suits developers reading unfamiliar Rust code, particularly when trying to understand the role of a specific variable or argument within a complex function. The tool integrates directly into VSCode as an extension, making it accessible without additional setup beyond installation from the marketplace. You should be aware of several limitations: the tool does not fully handle interior mutability, focus regions may sometimes include more code than expected, not all code is selectable, and nested functions including closures and async blocks cannot be analyzed together.

Development activity shows consistent engagement with the codebase through regular commits addressing both bug fixes and feature improvements. The project maintains responsiveness to user-reported issues and incorporates feedback into updates. Documentation is thorough, with a detailed FAQ section addressing common questions and known limitations, indicating active communication with users about the tool's capabilities and constraints.