Repo brief: willcrichton/flowistry

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T04:40:41.810Z · commit 8e30d4acbe5f

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 5d ago
• 4 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Flowistry is a Rust IDE plugin that performs information flow analysis to identify which code statements can influence or be influenced by a specific piece of code you click on. It visualizes data and control dependencies by fading out irrelevant code, helping developers focus on the subset of a function that matters for a given task. The core engine (in crates/flowistry/src/infoflow/ and crates/flowistry/src/mir/) analyzes Rust's MIR (Mid-level Intermediate Representation) to compute these dependencies. Monorepo with crates/flowistry/ as the core analysis library and crates/bench_utils/ for benchmarking infrastructure. The main logic is split into three modules: mir/ (MIR traversal and…

Start here

Open these first:

• crates/flowistry/src/lib.rs — Main library entry point that exports the public API and orchestrates the core analysis modules for information flow…
• crates/flowistry/src/infoflow/analysis.rs — Core information flow analysis implementation that determines dependencies between code locations—every feature relies on…
• crates/flowistry/src/mir/engine.rs — MIR analysis engine that processes Rust's intermediate representation; foundational for all backward slice and dependency…
• crates/flowistry/src/infoflow/dependencies.rs — Defines dependency tracking data structures and algorithms that answer 'does X affect Y?' queries used throughout the…
• crates/flowistry/src/mir/aliases.rs — Alias analysis for tracking which memory locations may refer to the same data—critical for precision in information flow…

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/willcrichton/flowistry.git
cd flowistry
cargo build --release
cargo test

Note: requires Rust nightly (rustup required, as specified in Makefile.toml and Cargo.toml workspace dependencies).

Daily commands:

cargo build
cargo test
cargo run --example example

Benchmarks run via cargo bench (configured in Cargo.toml with [profile.bench] debug = true). The example at crates/flowistry/examples/example.rs demonstrates the API.

Key cautions & unknowns

• Small team — 4 contributors active in recent commits
• Single-maintainer risk — top contributor 94% of recent commits
• Nightly Rust pinned to 2026-05-01: workspace dependencies pin to a specific rustc nightly date; updating Rust requires explicit Cargo.toml changes and may break MIR analysis due to compiler internals shifting.…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.