chore(deps): bump @noble/ciphers from 1.3.0 to 2.2.0#67
Merged
Conversation
Dep tree changesAddedRemovedUpgraded
Posted by lockfile-diff workflow. |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/noble/ciphers-2.2.0
branch
from
July 8, 2026 02:14
45decaf to
483eedc
Compare
Bumps [@noble/ciphers](https://github.com/paulmillr/noble-ciphers) from 1.3.0 to 2.2.0. - [Release notes](https://github.com/paulmillr/noble-ciphers/releases) - [Commits](paulmillr/noble-ciphers@1.3.0...2.2.0) --- updated-dependencies: - dependency-name: "@noble/ciphers" dependency-version: 2.2.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/noble/ciphers-2.2.0
branch
from
July 8, 2026 02:51
483eedc to
76c0bdd
Compare
Owner
|
Reviewed and verified: full suite passes untouched (sigil is ESM with .js subpaths, so v2's packaging shift is a no-op). Cross-version check done by hand since round-trip tests can't prove it: v1.3.0 and v2.2.0 produce byte-identical XChaCha20-Poly1305 ciphertext for the same key/nonce, and v2 cleanly decrypts a v1-sealed blob — existing keyfiles remain decryptable. Pushed a pinned known-answer vector so future cipher-dep bumps self-verify in CI. |
Same reasoning as the argon2id vector: round-trip tests seal and open with the same library version, so a dependency bump that changed cipher output would pass CI while bricking every keyfile on disk. Vector computed with @noble/ciphers 1.3.0; verified byte-identical (encrypt) and cleanly decrypting under 2.2.0 before this bump merges. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
cdrn
added a commit
that referenced
this pull request
Jul 9, 2026
Notable changes since 0.0.11:
* SECURITY FIX: the ward hooks now honor what the threat model claims.
BIP-39 seed phrases are redacted from tool output (checksum-validated,
so prose is untouched), and secret-named env assignments
(PRIVATE_KEY= / MNEMONIC= / SEED_PHRASE= / SECRET_KEY=) have their
values stripped — so reading a .env no longer leaks key material into
context while keeping ordinary config readable. The path blocker's
deliberate (and tested) choice not to block .env/*.pem is now
documented correctly rather than overclaimed. Reported privately by
Ugur Ozer, AI Risk Management. (#71)
* sigil rpc init — one-command JSON-RPC signing-proxy setup. (#63)
* fix: canonical r/s encoding in signed-tx RLP — a signature whose r or
s had a leading zero byte produced a tx some nodes rejected. (#59)
* fix: portal-qr error correction raised L→M for scan reliability. (#62)
* SECURITY.md added; ESLint + Prettier in CI; Dependabot + refreshed
action pins; TypeScript 6; @noble/hashes + @noble/ciphers on 2.x
(KDF/cipher output pinned by known-answer vectors). (#72, #68, #64, #69, #66, #67)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @noble/ciphers from 1.3.0 to 2.2.0.
Release notes
Sourced from @noble/ciphers's releases.
... (truncated)
Commits
b097e68Release 2.2.0.0c24e29Minor formatting fix7e7ec1eMerge pull request #68 from ChALkeR/patch-25316f58fixup: also in chacha953887ffixup: cleanup ciphPlaintext too98b8578fix: cleanup on salsa tag mismatche160698Merge pull request #67 from ChALkeR/patch-13d91c2aMinor formatting fixes400bea0fix: cleanup in gcm tag mismatch4361ffcRun prettier format on testsMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@noble/cipherssince your current version.