@cosmjs/crypto 0.29.1

Cryptography resources for blockchain projects

@cosmjs/crypto@0.29.1 was published on 2022-10-09. Its manifest declares 7 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This uses elliptic for cryptographic operations, which contains several security-relevant bugs. To what degree this affects your application is something you need to carefully investigate. See https://github.com/cosmos/cosmjs/issues/1708 for further pointers. Starting with version 0.34.0 the cryptographic library has been replaced. However, private keys might still be at risk.

All @cosmjs/crypto versions · Permanent reference to 0.29.1 · Latest release

Package specifications

Version0.29.1
License declarationApache-2.0
Published2022-10-09T14:35:00.023Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count7
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size135.39 KiB
Published file count44
Package typeNot declared
ES module entryNot declared
Default entrybuild/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies18
Repository stars699
Repository forks411

Install @cosmjs/crypto 0.29.1

npm install @cosmjs/crypto@0.29.1
pnpm add @cosmjs/crypto@0.29.1
yarn add @cosmjs/crypto@0.29.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review3/10 — Found 3/8 approved changesets -- score normalized to 3
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
Packaging10/10 — packaging workflow detected
SAST10/10 — SAST tool is run on all commits
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2

Evidence and freshness