hectorqin/reader

Reader is a web-based RSS feed aggregator and reader application that runs on your own server.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 16th, 2026
Created on August 13th, 2021
Open Issues & Pull Requests: 99 (+0)
GitHub issues: Enabled
Number of forks: 5,470
Total Stargazers: 11,017 (+0)
Total Subscribers: 64 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 28.8 days
90th percentile: 69.0 days
Tracked items: 178

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • enhancement (18)
  • bug (4)
  • need-confirm (3)
  • arm (1)
  • documentation (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Reader is a web-based RSS feed aggregator and reader application that runs on your own server.

The tool addresses the need for a self-hosted alternative to centralized feed reading services. It works by allowing users to subscribe to RSS feeds, aggregate them in a single interface, and read content without relying on third-party services. The application provides a web interface for managing subscriptions and consuming feed content, with the ability to deploy it on personal infrastructure.

Reader suits developers and users who want control over their feed reading setup and prefer not to depend on commercial feed services. It works well for individuals or small teams seeking a lightweight, self-contained solution that can run on modest hardware. The project is particularly appropriate for those comfortable with self-hosting and who value privacy and data ownership in their reading workflow.

The project shows active engagement with its user base. Almost all open issues are raised by outside users rather than the core team, demonstrating a substantial base of adopters reporting real-world use. Maintainers typically respond to new issues and pull requests within a few days. Work in the issue tracker is dominated by enhancement requests, bug reports, and issues needing confirmation, reflecting ongoing refinement driven by user feedback and identified problems.