Syncwave
Turn plain JSON files into a live data store, two-way synced with your Python objects.
Documentation
Read the docs at https://syncwave.dev/.
A few useful links:
Installation
Install from PyPI.
# uv
uv add syncwave
# pip
pip install syncwave
What Is Syncwave
Syncwave keeps in-memory Python objects and JSON files synchronized, in both directions:
- Change your data from Python (an
append, a dict assignment, a model field update) and the JSON file is updated. - Edit the JSON file, by hand or from another process, and your Python objects are updated in place.
- Every change, from either side, is validated with Pydantic against the store's declared type.
You get persistence with zero setup: no database to install, no ORM, no serialization code. Your data lives in JSON files you can open and edit at any time.
If you know Python type hints and Pydantic models, you already know everything you need.
Requires Python 3.10+.
Versioning
Syncwave is under active development, and until version 1.0, new releases may introduce backward-incompatible changes.
License
Syncwave is licensed under the MIT License.
1 maintainer
Metadata
1 maintainer
Release files for syncwave 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| syncwave-0.3.0.tar.gz | 25.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| syncwave-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 56.6 kB
Release files / syncwave-0.3.0.tar.gz
| Download URL | syncwave-0.3.0.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f84fb2ac02685945c2ff5c4816b14118ec8d8219c0d7b4b93d9b9cbf29c039c7
|
|
BLAKE2b-256 checksum How to use checksums |
e91ae2f677afd1deda96a11751a1352060ee45305f541597486c05fe59064568
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / syncwave-0.3.0-py3-none-any.whl
| Download URL | syncwave-0.3.0-py3-none-any.whl |
|---|---|
| Size | 31.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca101c78f1fe6955b73580a3eb692d9872a989c2eb966cc1f98aa0a8c493a140
|
|
BLAKE2b-256 checksum How to use checksums |
3aae94736d7d64940aa7649d2df699164eff38404d0d65fa881511fe8d1556fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logSecurity for syncwave 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for syncwave-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
