cognitive-engineering-lab/aquascope

Interactive visualizations of Rust at compile-time and run-time

View on GitHub ↗Jump to charts ↓Open shareable report →

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

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on September 15th, 2022
Open Issues & Pull Requests: 37 (+0)
GitHub issues: Enabled
Number of forks: 76
Total Stargazers: 3,161 (+1)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.6 hours
Mean response time: 25.0 days
90th percentile: 43.2 days
Tracked items: 25

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 461 days
Stale 30+ days: 16
Stale 90+ days: 15

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 (2)
  • permissions (2)
  • big-project (1)
  • documentation (1)
  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Aquascope is a tool that generates interactive visualizations of Rust programs at compile-time and run-time.

Aquascope addresses the challenge of understanding how Rust's borrow checker analyzes code and how programs execute. It works by creating interactive diagrams that visualize ownership, borrowing, and program state, making the abstract rules of Rust's type system concrete and observable. The tool integrates with mdBook as a preprocessor, allowing developers to embed these visualizations directly into documentation by adding special code blocks to Markdown files.

The tool suits educational contexts and documentation projects where explaining Rust's memory model to learners is important. It works best for teaching materials and books rather than as a development-time debugging tool. The project explicitly identifies itself as research software, which means the interface and feature set may change as the work evolves.

Development on the project is active but measured, with maintainers explicitly welcoming bug reports and contributions while acknowledging the experimental nature of the work. The codebase shows ongoing refinement of core functionality, particularly around the stability of the visualization interface. The team maintains direct communication channels for users encountering difficulties, indicating responsiveness to adoption challenges.