Our take
Quietno commits in the last 90 days and no release in a year- Activity
- 20
- Community
- 20
- Issues
- 21
- Pull requests
- 21
+2 stars in the last 10 days
- Fewer contributors than 86% of the projects we track
SQLSync addresses a specific and useful need, but its quiet project activity and reliance on one primary contributor make it a higher-risk choice for new production dependencies.
Good fit if
- Your web app needs collaborative, offline-first state backed by SQLite.
- Your team can work with both Rust and Node.js requirements and is comfortable evaluating a project with no recent commits or releases.
- You want to prototype shared structured data across browser tabs or devices, and can engage with the project community if needed.
Look elsewhere if
- Your adoption depends on frequent upstream releases, recent maintenance, or active issue and pull request handling.
- You need a project with a broad contributor base rather than one where most contributions come from one person.
- Your application does not use SQLite-style relational data or does not need offline and collaborative synchronization.
All health signals
| Last commit | 2025-11-19 (11 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 |
| Contributors | 2 (top contributor: 88% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 3 years |
Checked on 2026-10-11 with the GitHub API.
Overview
SQLSync is a Rust-backed wrapper around SQLite for web applications that need shared data to remain usable offline. It synchronizes application state across users, devices, and the edge, aiming to combine local-first interaction with collaborative updates.
It is most relevant when an app's data fits a relational, structured model and users need to read or change that data while connectivity is unreliable. A React library is included, and the project also describes use with structured, file-oriented data such as collaborative documents.
Key Features
- Eventually consistent SQLite data shared across clients.
- Optimistic reads and writes for responsive local interaction.
- Reactive query subscriptions that can notify the application as data changes.
- Real-time collaboration between users and devices.
- Offline-first operation for unreliable network conditions.
- Cross-tab synchronization through a shared web worker.
- A React library for web application integration.
Use Cases
- A team building a collaborative editor can use a separate database for each structured document or file and synchronize changes between participants.
- A web app that must keep working during intermittent connectivity can use local SQLite state and synchronize when clients reconnect.
- Developers running applications at the edge can evaluate SQLSync where network conditions are unreliable and local data access matters.
- Teams with SQLite read replicas can investigate optimistic mutations when they need clients to respond before remote updates complete.
What you need
Detected in the repository
- Node.js (from package.json)
- Rust (from Cargo.toml)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
The repository README points to the getting started guide for adding SQLSync to an application. See the SQLSync repository for the source and current instructions.
Alternatives
- orbitdb: OrbitDB is a decentralized JavaScript database built on IPFS and Libp2p, while SQLSync syncs SQLite-backed application state.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| sqlsync | Rust | Apache-2.0 | 2.9k | Quiet |
| orbitdb | JavaScript | MIT | 8.8k | Quiet |
Considerations
GitHub activity data marks the project as quiet: there have been no commits in the last 90 days and no release in over a year. The measured contributor base is small and concentrated, with most of the code coming from one person; no issues were closed or pull requests merged in the measured 90-day period. These signals do not establish whether the software works for a particular application, but they do increase the importance of testing and planning for maintenance.
The project requires Node.js and Rust according to its package and Cargo manifests. The supplied requirements data does not indicate a test setup. SQLSync is licensed under Apache-2.0, so review that license against your distribution and compliance needs. The README also notes that SQLSync runs in a shared web worker by default, which can make browser debugging less straightforward, and that each execute! call should contain only one SQL statement.
Found this useful?
Share it with someone who would like sqlsync.