ufrisk/memprocfs

MemProcFS

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 16th, 2026
Created on November 18th, 2018
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 518
Total Stargazers: 4,340 (+0)
Total Subscribers: 87 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.6 hours
Mean response time: 8.4 days
90th percentile: 8.7 days
Tracked items: 96

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 348 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

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

Top labels

  • bug (12)
  • enhancement (10)
  • question (1)

Detailed Description

MemProcFS is a virtual filesystem that exposes memory contents and forensic analysis capabilities as a mountable file tree.

MemProcFS solves the problem of accessing and analyzing system memory in a way that integrates with standard filesystem tools and workflows. Rather than requiring specialized memory analysis software, it presents memory as a navigable directory structure where files represent memory regions, processes, and forensic artifacts. This approach allows users to browse memory contents, extract data, and perform analysis using familiar command-line utilities like grep, find, and cat. The tool supports multiple memory acquisition sources and backends, enabling both live memory analysis and examination of memory dumps.

The project suits security researchers, incident responders, and forensic analysts who need to inspect memory contents without learning specialized memory analysis frameworks. It is particularly valuable for those who want to leverage existing Unix tools and scripts in memory analysis workflows. The virtual filesystem abstraction makes memory exploration intuitive for users comfortable with directory navigation, though it requires understanding of memory layout and forensic concepts to interpret results effectively.

Development activity shows consistent engagement with memory analysis challenges. The project maintains active responses to issues and pull requests, indicating ongoing attention to user-reported problems and feature requests. Work spans multiple areas including support for different memory sources, forensic module development, and compatibility improvements across platforms. The codebase receives updates addressing both core functionality and edge cases in memory parsing and analysis. Contributions come from multiple developers working on distinct areas such as plugin development and platform-specific features, suggesting a collaborative approach to expanding the tool's capabilities.