Repository navigation
Conversation
crypto-bigint 0.5.5 (timing side-channel) is reached via elliptic-curve 0.13.8 <- k256 0.13.4 <- coins-bip32 / coins-bip39 0.13.2. The fix needs crypto-bigint >=0.7.6, which only the semver-major k256 0.14 / coins-bip3x line brings, so cargo update cannot reach it. Accepted temporarily (user decision 2026-10-26) so the tinybus 0.3.6 releases can proceed; remove the entry when the k256 chain is upgraded.
Tiny Sweeper reviewReviewed head: Verdict: Ready for maintainer review · Priority: none Diagnostics and supporting detailsFull summaryPull request purpose (title): chore(deny): ignore RUSTSEC-2026-0387 until the k256 chain is upgraded. Tiny Sweeper completed its review; deterministic results follow. Review snapshot
Completeness: Complete What changedOnly `deny.toml` changes: the empty `ignore = []` under `[advisories]` becomes a list holding one inline table with `id = "RUSTSEC-2026-0387"` and a `reason`, plus a comment describing the crypto-bigint 0.5.5 / k256 0.13.4 / coins-bip3x exposure, the required semver-major fix, and the condition for removing the entry. Licenses, bans, sources, and all code paths are unchanged. Features
Tests
FindingsNo active actionable findings. Before mergeNone. Agent review detailscritique
security
tests
commits
description
Evidence and run details
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Summary
Adds RUSTSEC-2026-0387 to
deny.toml's[advisories] ignorelist, with a comment and areason, somodule-ci / supply-chainpasses again on main.Problem
cargo deny check advisoriesnow fails on every PR, including chore(deps): bump tinybus 0.3.6, tinytools 0.6.0, tinystoragedrivers 2.1.1 #121 (the tinybus 0.3.6 bump).crypto-bigint 0.5.5<-elliptic-curve 0.13.8<-k256 0.13.4(also viaecdsa 0.16.9) <-coins-bip32/coins-bip39 0.13.2<-tinywallet.k256 0.14/coins-bip3xline brings.cargo update -p crypto-bigintcannot reach it.Solution
ignoreentry with an explanatory comment and areason(cargo-deny's{ id, reason }form). It was accepted temporarily by user decision on 2026-10-26, so the tinybus 0.3.6 module releases can proceed.Follow-up