git.keepword.net/keepword/keepword
Where Keepword is developed: the code and its history, bug reports, changes and releases. It runs on Keepword’s own Forgejo server.
git clone https://git.keepword.net/keepword/keepword.git Source code
The main repository is on Keepword’s own Forgejo server. GitHub has a mirror that follows it, so you can clone from either.
Where Keepword is developed: the code and its history, bug reports, changes and releases. It runs on Keepword’s own Forgejo server.
git clone https://git.keepword.net/keepword/keepword.git A copy on GitHub that follows the main repository, for anyone who’d rather clone from there. It gets every commit and tag, but releases are only on git.keepword.net.
git clone https://github.com/keepword-net/keepword.git Bug reports, ideas and changes go to the main repository on git.keepword.net. Everything is in Rust, and the design, threat model and formats are written down in DESIGN.md.
Before sending a change, run the checks:
cargo test --workspace
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo fmt --all --check The integration tests run everything over real HTTP on localhost: a node’s whole lifecycle, networks of four, six and twelve witnesses, Bitcoin anchoring against mock services, and a full MPC-TLS notarization between two witnesses.
crates/ | protocol: encoding, attestations, Merkle log, bundles, assignment, quorum |
|---|---|
crates/ | canonicalizer, site rules, diff and silent-edit classifier |
crates/ | HTTP capture, SSRF guard, headless render, WARC export |
crates/ | blob store, SQLite index, log, watchlist |
crates/ | the keepword binary: CLI, peer API, federation, web UI |
crates/ | TLSNotary proof tier (a separate workspace) |
docs/ | design and threat model, installation, running a network |
scripts/ | the installer |