hydrusnetwork/hydrus

A personal booru-style media tagger that can import files and tags from your hard drive and popular websites. Content can be shared with other users via...

View on GitHub ↗Jump to charts ↓

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

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on February 19th, 2013
Open Issues & Pull Requests: 826 (+0)
GitHub issues: Enabled
Number of forks: 206
Total Stargazers: 3,237 (+0)
Total Subscribers: 65 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 128.5 days
90th percentile: 241.2 days
Tracked items: 348

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 89% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 2 days, while "system:user-interface" waits about 3 months. 76% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 47% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 211
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 717 days
Stale 30+ days: 198
Stale 90+ days: 183

Recent activity

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

Top labels

  • feature-request (229)
  • bug (199)
  • system:user-interface (34)
  • system:duplicates (14)
  • system:keybinds (10)
  • system:searching-sorting (10)
  • system:api (9)
  • system:media-viewer (8)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Hydrus is a personal media tagger that organizes and manages image and video files with a booru-style tagging system. It runs as a desktop application and lets you build a searchable database of media from your local drives and popular websites, then optionally share collections with others through peer-to-peer servers.

The tool solves the problem of managing large personal media libraries without relying on centralized cloud services. It works by importing files into a local database where you assign tags, ratings, and metadata to each item. The tagging system supports hierarchical tag relationships, allowing you to organize content by multiple dimensions simultaneously. Search queries combine tags with boolean logic to find exactly what you need. The application handles duplicate detection and can fetch tags automatically from external sources when importing.

Hydrus suits anyone building a personal archive who wants full control over their data and doesn't want to depend on third-party services. It works well for managing collections too large or sensitive for cloud storage, or for users who prefer self-hosted solutions. The peer-to-peer sharing model means you can exchange curated collections with trusted users without uploading to a central server. This approach is fundamentally different from cloud-based alternatives that store your media on company servers.

Development on the project shows consistent, focused activity with regular updates addressing both core functionality and user-reported issues. The maintainer actively incorporates user feedback and implements feature requests that align with the tool's scope. Bug fixes and improvements arrive in a steady cadence rather than sporadic bursts. The codebase receives ongoing maintenance to handle edge cases and improve stability across different operating systems and file types.