You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Welcome to the m-vis roadmap! Our goal is simple: to make memory debugging accessible, fast, and cross-platform. We are moving from a "tool for quick diagnostics" to a "standard utility for systems engineers."
This issue serves as our tracking board for the remainder of 2026.
High-Level Timeline
Phase
Focus
Key Deliverable
June 2026
Usability & UX
TUI "Watch" Mode & Delta Analysis
Q3 2026
Pipeline & Automation
CI/CD Integration & Data Exporting
Q4 2026
Integrity & Security
Heap Analysis & Security Auditing
Phase 1: June – "TUI Visualization / Improvements"
Goal: Reduce the time it takes for a developer to spot a memory leak.
Modular Architecture Refactor: Migrate to a 4-layer (Core, OS, UI, Types) structure.
Implementation of watch command: Allow real-time tracking of memory allocation.
Delta Analysis: Implement logic to calculate and display memory growth over time.
TUI Polish: Color-coded alerts and keyboard-driven navigation.
Phase 2: Q3 – "CI/CD"
Goal: Integrate m-vis into the standard software development lifecycle (SDLC).
Export Layer: Support for JSON/CSV output formats.
Regression Thresholds: Add flags like --max-leak to fail builds if memory limits are exceeded.
GitHub Actions: Create an official m-vis Action for automated leak detection in PRs.
Phase 3: Q4 – "Expand Memory Analysis"
Goal: Pivot to security-focused memory analysis.
Heap Integrity Checks: Detect common vulnerabilities like "Double Free" and "Use-After-Free."
Security Health Dashboard: Report on OS mitigations (ASLR, NX/DEP) for target processes.
Memory Permission Auditing: Scan process memory regions for dangerous permission combinations (e.g. writable + executable pages).
🤝 How to Contribute
We are actively looking for contributors! Whether you are a Rust systems expert or a UI/UX enthusiast, there is a place for you here.
Check the Issues: Look for tasks labeled good first issue or help wanted.
m-vis 2026 Roadmap
Welcome to the
m-visroadmap! Our goal is simple: to make memory debugging accessible, fast, and cross-platform. We are moving from a "tool for quick diagnostics" to a "standard utility for systems engineers."This issue serves as our tracking board for the remainder of 2026.
High-Level Timeline
Phase 1: June – "TUI Visualization / Improvements"
Goal: Reduce the time it takes for a developer to spot a memory leak.
watchcommand: Allow real-time tracking of memory allocation.Phase 2: Q3 – "CI/CD"
Goal: Integrate
m-visinto the standard software development lifecycle (SDLC).--max-leakto fail builds if memory limits are exceeded.m-visAction for automated leak detection in PRs.Phase 3: Q4 – "Expand Memory Analysis"
Goal: Pivot to security-focused memory analysis.
🤝 How to Contribute
We are actively looking for contributors! Whether you are a Rust systems expert or a UI/UX enthusiast, there is a place for you here.
good first issueorhelp wanted.Your input helps shape the future of
m-vis. Let's build something great.