@ledgerhq/context-module 0.0.0-develop-20260406001724

> [!CAUTION] > This is still under development and we are free to make new interfaces which may lead to Device Management Kit breaking changes.

@ledgerhq/context-module@0.0.0-develop-20260406001724 was published on 2026-04-06. Its manifest declares 6 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 @ledgerhq/context-module versions · Permanent reference to 0.0.0-develop-20260406001724 · View npm registry JSON · Latest release

Package specifications

Version0.0.0-develop-20260406001724
License declarationApache-2.0
Published2026-04-06T00:24:58.525Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size3754.06 KiB
Published file count1212
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies45
Repository stars49
Repository forks44

Install @ledgerhq/context-module 0.0.0-develop-20260406001724

npm install @ledgerhq/context-module@0.0.0-develop-20260406001724
pnpm add @ledgerhq/context-module@0.0.0-develop-20260406001724
yarn add @ledgerhq/context-module@0.0.0-develop-20260406001724

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.

Evidence and freshness