@ledgerhq/json-bignumber

JSONBigNumber.parse/stringify handling **all** JSON numbers using BigNumber. Based on Douglas Crockford [JSON.js](https://github.com/douglascrockford/JSON-js) package and [bignumber.js](https://github.com/MikeMcl/bignumber.js) library.

@ledgerhq/json-bignumber@1.1.0 was published on 2021-10-04. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All @ledgerhq/json-bignumber versions · Permanent reference to 1.1.0 · View npm registry JSON

Package specifications

Version1.1.0
License declarationMIT
Published2021-10-04T12:46:19.640Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size315.24 KiB
Published file count16
Package typeNot declared
ES module entrysrc/JSONBigNumber.js
Default entrydist/JSONBigNumber.min.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars11
Repository forks6

Install @ledgerhq/json-bignumber 1.1.0

npm install @ledgerhq/json-bignumber@1.1.0
pnpm add @ledgerhq/json-bignumber@1.1.0
yarn add @ledgerhq/json-bignumber@1.1.0

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.

Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review0/10 — Found 0/25 approved changesets -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness