zu1k/book-searcher

Easy and blazing-fast book searcher, create and search your private library.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 10th, 2026
Created on November 24th, 2022
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 310
Total Stargazers: 6,303 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 0.1 hours
90th percentile: 0.1 hours
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

book-searcher is a full-text search application for building and querying a private digital library of books.

The tool addresses the problem of efficiently searching across large personal book collections by providing a lightweight, self-hosted search engine. It allows users to index books and perform fast full-text queries against their private library without relying on external services. The approach centers on simplicity and speed, enabling rapid indexing and retrieval operations.

The project suits individuals and small organizations wanting to maintain searchable archives of their own book collections with minimal infrastructure overhead. It is designed for users who prefer self-hosted solutions over cloud-based alternatives and need straightforward indexing and search capabilities without complex configuration. Those considering adoption should expect a focused tool optimized for the core task of book discovery within a personal library rather than a feature-rich platform with advanced analytics or social features.

Development activity shows consistent engagement with the codebase through regular commits addressing bug fixes and incremental improvements. The project maintains responsiveness to user-reported issues, with maintainers actively triaging and resolving problems. Pull requests receive timely review and integration, indicating an active development cycle. The maintainer demonstrates willingness to accept community contributions while maintaining code quality standards.