helloxz/onenav

使用PHP + SQLite 3开发的书签管理系统,将浏览器书签集中式管理,做到一处部署,随处访问。

View on GitHub ↗Jump to charts ↓Open shareable report →

helloxz/onenav has 3k+ stars and 500+ forks on GitHub, is written in JavaScript, and was last pushed on May 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 22nd, 2026
Created on December 13th, 2020
Open Issues & Pull Requests: 44 (+0)
GitHub issues: Enabled
Number of forks: 548
Total Stargazers: 3,139 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.7 hours
Mean response time: 97.7 days
90th percentile: 480.0 days
Tracked items: 29

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

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 (5)
  • bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

OneNav is a bookmark management system that centralizes browser bookmarks through a web-based interface built with PHP and SQLite 3.

The system solves the problem of scattered bookmarks across multiple browsers and devices by providing a single deployment point where bookmarks can be stored and accessed from anywhere. It works by collecting bookmarks into a centralized database that users can access through a web interface, eliminating the need to maintain separate bookmark collections across different browsers or machines.

OneNav suits users who want to consolidate their bookmarks in one place and access them from any device with a web browser. It is particularly useful for those who switch between multiple browsers or work across different computers and want a unified bookmark repository. The lightweight architecture using PHP and SQLite 3 means it can be deployed on modest hosting environments without complex infrastructure requirements.

Development activity shows consistent engagement with the project. The codebase receives regular updates addressing functionality and user-reported issues. The maintainer actively responds to user feedback and incorporates improvements based on community input. Documentation and examples are maintained to help new users get started with deployment and basic usage.