Install Hyphae 3.0.0
Every path below ends at the same tagged source commit,
24bce1accdff8d14127797afe6f237a57c1cd4f3, published as
release-v3.0.0-crates. Pin the exact version and verify
before you trust a binary.
From crates.io
The CLI is a single published crate:
cargo install hyphae-cli --version 3.0.0 --locked
A clean install of that command completed from crates.io on
2026-09-04 and reported product hyphae, engine
3.0.0, API v1, disk format
2, native directory format 1, and
product API version 1.
Embedding the engine
To embed Hyphae in a Rust application, pin exact versions on the three library crates rather than a caret range — the workspace is released as one version across 24 crates and a mismatched set will not build:
[dependencies]
hyphae-engine = "=3.0.0"
hyphae-query = "=3.0.0"
hyphae-native-product = "=3.0.0"
A temporary application with exactly these three dependencies
generated a fresh lockfile and built with cargo build --locked
against the published registry state.
The complete crate graph
All 24 crates are published at 3.0.0, each with
.cargo_vcs_info.json bound to the same source commit,
in publication layer order. registry_sha256 matched
intended_sha256 for every one after download and
comparison against the freshly packaged source.
| Crate | SHA-256 |
|---|---|
hyphae-core | d80bcb933390d28ba39cc4ec9e0cc8add3ab711ce0ed6059c8ffb2d16db3b473 |
hyphae-native-types | 52b8223283041487410ad8b867f3f1f04ff71a16614e75ad61f68f22d0a7ed8d |
hyphae-native-ann | 09502b6469605b28ded5294db94223c67bbcb7cd981e501cd38002c5632debd2 |
hyphae-native-catalog | 36b65d34b9aa4f2cb006ad44f534f9899a323e855cf980cd45ed4a96106962a7 |
hyphae-native-mvcc | 8ec5a522a8c3c023bc42cb976babf73cb16180c09bbc1b31115f98a036ebcbd3 |
hyphae-native-pages | 36e84929c10d53edb028abc336b3b8cc7f18e66e647f2c9641f35af087fd8e59 |
hyphae-native-records | 27d66441370a6ab376dc81105da82c178692045c34e562933cd6a94713966027 |
hyphae-native-wal | 11c171c7e17767cb91b562865954ee9d6dbbcca58e8008abe4e54eb472d84861 |
hyphae-query | 7f887d860ee7ed8f85c74427ecf6daadbec0bf013cf2985e1b1716d1c3abbc15 |
hyphae-contracts | 66dfed1bc6616a2b631054b4087d416d62d795f86bbc58e2f28964a7dce24b9b |
hyphae-native-blobs | 5f5bb03f5a9f66ca84e4ba33b6434992abd49e596b98fcb0fccf3ee38134a08b |
hyphae-native-btree | 44e88f55d9b0ff9aff0bc415afa41cdfb643996728eda19f27783b6e7df407d0 |
hyphae-native-manifest | 2acf0ed04f4d7761176030f44625ced85c1cae43415e891168d3e6ba5865043c |
hyphae-retrieval | 7de6627baa717c05db4a673c1ba4155e2ea28feceaea19af9be7a9b4da03e0a8 |
hyphae-native-runtime | 524da085b6d0925ff731f67ad6ededf191cacf54cfb0b1a0db79a666a42b6e49 |
hyphae-storage | f974598301634f3d19a947770f5b5b38d5a8432ac8ebba5ecf391092a51a5308 |
hyphae-engine | 091e3877d3c947e2599631af1d842d9da062e06956733ba5b9fe129aa54aca06 |
hyphae-native-product | 53f15fbb756b8609f6a7b521d52cc4f6849c188d7df965fef1a0dd57714c0b91 |
hyphae-native-protocol | f06d3bb1029fd4f127ae1cbb5c722df3dae020b974e9b74fc39341c69011f2a0 |
hyphae-client | d073b69978e54036d8b74274761ecf0d0b42bf373ccc7fe8159bc67c71368c9d |
hyphae-native-daemon | b2014cf433080d1546e9e00cf36ccf705c7e1af7122c93ec3efa481d2b70ddb1 |
hyphae-server | d78a46ac925267b98902080e62ea29fefb55372ab1926900f43dfbf3bfd29818 |
hyphae-cli | 7627323f5b6f3616eefc3f054f9da0852d700e98c05c437a45f5d799ff97a39c |
hyphae-pliegors | b31f38f0e7e4abf012ded3267ac40e179a7ec33248beb183d073951db08c900e |
Source: docs/release/receipts/3.0.0.md, “crates.io receipts”.
Signed release archives
The GitHub release release-v3.0.0-crates
carries 38 assets: one archive per platform, SHA256SUMS,
two SBOMs, a release-evidence manifest, a required-checks report,
and a Sigstore bundle plus SLSA/SBOM attestation for every one of
those files.
| Platform | Archive | SHA-256 |
|---|---|---|
| Linux x64 | hyphae-3.0.0-x86_64-unknown-linux-gnu.tar.gz | f1c69fa2f37ea7122e6f63e94cc01aecd33258b2d2b483dfc45dfc9727550a38 |
| macOS x64 | hyphae-3.0.0-x86_64-apple-darwin.tar.gz | 95facd7be6b06b1f676c008894286d0c015faf060bac9ea1abe14d494bf49de6 |
| macOS arm64 | hyphae-3.0.0-aarch64-apple-darwin.tar.gz | 03f44de4592b4c8e06754864ff307780efe8286addb9359ad051c46fb533ae6c |
| Windows x64 | hyphae-3.0.0-x86_64-pc-windows-msvc.zip | 406dc93f4a2e80f18f9a3bf3f5c04c2a8350fa3afd58e9f29f9322c24686a278 |
| SBOM (CycloneDX) | hyphae-release-v3.0.0-crates.cdx.json | 460093bcbe2943e4803e48225b624a41ff44599f98d028a39f2b23486fde472d |
| SBOM (SPDX) | hyphae-release-v3.0.0-crates.spdx.json | c146fde572531fe665f8a2b1460035cb9deb251b95cb95ca65568865009ee209 |
Source: docs/release/receipts/3.0.0.md, “Primary release asset checksums”.
Verify before you run it
Verbatim from the maintainer verification guide, replacing VERSION and TARGET with the values above.
1. Checksums. Download every file named in SHA256SUMS into the same directory, then:
sha256sum --check SHA256SUMS Every listed archive and SBOM must report OK.
2. Keyless signature. Cosign 3.1.1 or later:
cosign verify-blob \
--bundle hyphae-VERSION-TARGET.tar.gz.sigstore.json \
--certificate-identity \
'https://github.com/Hyphae-Research-Foundation/hyphae/.github/workflows/release.yml@RELEASE_WORKFLOW_REF' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
hyphae-VERSION-TARGET.tar.gz Repeat for SHA256SUMS, both SBOMs, every provenance predicate, and the two report files.
3. Release-evidence binding. From a checkout of the exact source commit:
git checkout --detach COMMIT
git fetch --force --no-tags origin \
'+refs/tags/vVERSION:refs/hyphae/verify-tag'
TAG_OBJECT="$(git rev-parse refs/hyphae/verify-tag)"
TAG_TARGET="$(git rev-parse 'refs/hyphae/verify-tag^{commit}')"
python packaging/release_evidence.py verify \
--directory /path/to/downloaded-release \
--manifest /path/to/downloaded-release/hyphae-vVERSION.release-evidence.json \
--commit COMMIT \
--tag-object "$TAG_OBJECT" \
--tag-target "$TAG_TARGET" 4. Build provenance and SBOM attestations. SLSA provenance v1, keyed to the exact archive digest:
cosign verify-blob-attestation \
--bundle hyphae-VERSION-TARGET.tar.gz.intoto.sigstore.json \
--type slsaprovenance1 \
--certificate-identity \
'https://github.com/Hyphae-Research-Foundation/hyphae/.github/workflows/release.yml@refs/tags/vVERSION' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
hyphae-VERSION-TARGET.tar.gz The archive also carries .spdx.attestation.sigstore.json and .cyclonedx.attestation.sigstore.json bundles — verify with the same identity and --type spdxjson or --type cyclonedx.
5. Inspect and smoke-test. Extract into an empty directory and confirm it contains one executable plus LICENSE, LICENSE-DOCUMENTATION, LICENSE-POLICY.md, NOTICE, README.md, and THIRD_PARTY_NOTICES.md:
tar -xzf hyphae-VERSION-TARGET.tar.gz
./hyphae-VERSION-TARGET/hyphae version --json The reported product must be hyphae and engine_version must equal the tag without the leading v.
Source: docs/release/verification.md.
Build from source
git checkout release-v3.0.0-crates
cargo build --release --locked -p hyphae-cli
The tag targets the reviewed merge commit
24bce1accdff8d14127797afe6f237a57c1cd4f3
(source tree 52bdbb3ea7cd8d12e2cbd6cbe5f53cbcaa80d0ff).
Building against the workspace Cargo.lock with
--locked reproduces the same dependency graph the
release evidence was generated from.
What is source-only
The TypeScript and Python clients and the JavaScript framework
integrations remain source-only in the 3.0.0 release. Their
3.0.0 source manifests and local package audits do
not constitute npm or PyPI publication — build them from the
repository at the same tag rather than expecting a registry
package.
Supported versions
Report a suspected vulnerability through GitHub private vulnerability reporting on this repository, not in a public issue, discussion, pull request, or chat log.
| Version | Supported |
|---|---|
3.0.0 | Yes — current release line |
2.2.0 | Security fixes only, until the next 3.x minor is released |
| Older 2.x, 1.x, 0.x | No |
Source: SECURITY.md.