volmarg/personal-management-system

Your web application for managing personal data.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on March 26th, 2019
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 346
Total Stargazers: 4,162 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.8 hours
Mean response time: 89.4 days
90th percentile: 12.6 days
Tracked items: 21

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 332 days
Stale 30+ days: 3
Stale 90+ days: 3

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 (4)
  • help wanted (3)
  • feature request (1)
  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Personal Management System is a self-hosted web application for organizing and managing personal data across multiple domains.

The tool addresses the need for a unified, privacy-focused platform to handle diverse personal information without relying on external services. It consolidates functionality typically spread across separate applications—task management, note-taking, financial tracking, password storage, and contact management—into a single dashboard. Built with PHP and Symfony, it runs on your own infrastructure, keeping all data under your control.

The project suits individuals and small teams who prioritize data privacy and want to avoid subscription services or cloud-based alternatives. It works well for those comfortable self-hosting applications and who need a flexible, all-in-one system rather than best-of-breed tools for each function. The application provides a web interface accessible from any browser, making it suitable for personal use across devices without requiring native applications.

Development activity shows consistent engagement with the codebase. The project receives regular commits addressing bug fixes and feature improvements. Pull requests are reviewed and merged, indicating active maintenance. Issues are created and addressed, demonstrating responsiveness to problems and feature requests. The maintainer actively works on the repository rather than leaving it dormant, with ongoing refinement of existing functionality and expansion of capabilities.