Skip to content

publet-algorithms 0.2.0

Choose a tag to compare

@github-actions github-actions released this 09 Oct 13:12
· 244 commits to main since this release
7d6d6ef

0.2.0 - 2026-10-09

Commit e97457ef710d; release record pub:sha2-256:tke3fnms5df4yjwuipdnhk323syslmiqyreokre5fn4wfqzmdypq.

Changed

  • version::satisfies reads ^X.Y as Cargo does: below 1.0 the minor part is fixed, so ^0.1 no longer admits 0.3.2. Version and Bump are removed; release arithmetic belongs to the semver crate.
  • log::verify_inclusion and log::verify_consistency take sizes and indexes as u64, and membership::Proof carries them as u64, on every target. They come with proofs from peers, whose logs and sets may be larger than a 32-bit or wasm32 machine's usize; a verifier there can now check them. The functions that build proofs keep usize, as they index leaves in memory.

Fixed

  • The crate ships what distribution needs: the Apache-2.0 licence text, crates.io metadata, an include list, and documentation with examples run as doctests, including the crates considered instead and why.
  • The package ships SUPPLY-CHAIN.md: every dependency, whether it runs code at build time, and how its code is vouched for (an imported audit, a trusted publisher, or an exemption with the evidence beside it).
  • Every public function's documentation has an example run as a test, the crate root has an overview, a cookbook and why this crate exists, and docs.rs renders how every item is tested, how each dependency is vouched for, the security policy and the changelog.
  • The crate declared Rust 1.98, the toolchain publet is developed with, though it builds on 1.85, the first release with the 2024 edition. It now declares 1.85, and CI builds it there. docs.rs links the rendered source to definitions.

Security

  • Merkle log proof checking looped forever on a proof claiming more than 2^63 entries, and a consistency proof between sizes above 2^63 shifted a u64 by 64 bits, panicking where overflow is checked; either let a peer stop anyone checking its proofs. Both are fixed. Found by fuzzing.

Internal

  • Test vectors from independent sources, property tests, and two independent implementations as test oracles (ciborium for CBOR, ct-merkle for RFC 6962). Tests only; nothing users run changed.
  • Each change to the public API of publet-core and publet-algorithms is checked against the crate's last release by cargo-semver-checks, and the crate docs gain a Versioning section saying so.
  • tree::Node's docs say why it is exhaustive.
  • The log's absurd-size regression tests also build and run on 32-bit targets.
  • The crates' include patterns are anchored with /, so a file of the same name deeper in a crate can never be packaged by accident; each package's contents are unchanged.

Security checks

  • advisories, licences, bans and sources: cargo deny --locked check --hide-inclusion-graph (cargo-deny 0.20.2) -- advisories ok, bans ok, licenses ok, sources ok
  • supply-chain audits: cargo vet --locked (cargo-vet 0.10.2) -- Vetting Succeeded (54 fully audited, 183 exempted)
  • supply-chain reports current: ./tools/supply-chain-report.py --check && echo 'SUPPLY-CHAIN.md current for every published crate' -- SUPPLY-CHAIN.md current for every published crate
  • RustSec advisory database revision: 7eebec69c352c7191b1f13eb95dd510eeca5d1de (2026-10-09)
  • audits imported from: bytecode-alliance, embark-studios, google, isrg, mozilla, zcash