@trezor/blockchain-link 2.4.1-beta.1

High-level javascript interface for blockchain communication

@trezor/blockchain-link@2.4.1-beta.1 was published on 2025-03-03. Its manifest declares 14 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @trezor/blockchain-link versions · Permanent reference to 2.4.1-beta.1 · Latest release

Package specifications

Version2.4.1-beta.1
License declarationSEE LICENSE IN LICENSE.md
Published2025-03-03T14:51:27.492Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count14
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size199.04 KiB
Published file count88
Package typeNot declared
ES module entryNot declared
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies180
Repository stars1079
Repository forks390

Install @trezor/blockchain-link 2.4.1-beta.1

npm install @trezor/blockchain-link@2.4.1-beta.1
pnpm add @trezor/blockchain-link@2.4.1-beta.1
yarn add @trezor/blockchain-link@2.4.1-beta.1

Runtime dependencies

Peer requirements

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.

Code-Review10/10 — all changesets reviewed
Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License9/10 — license file detected
Dangerous-Workflow0/10 — dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Signed-Releases4/10 — 3 out of the last 5 releases have a total of 3 signed artifacts.
Binary-Artifacts1/10 — binaries present in source code
SAST10/10 — SAST tool is run on all commits
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Fuzzing10/10 — project is fuzzed

Evidence and freshness