@bitboxswiss/bitbox-api 0.1.0

package/CONTRIBUTING.md

@@ -0,0 +1,129 @@
+# Contributing
+
+This repo is the pure TypeScript port of the BitBox02 browser API. The public
+compatibility reference is the Rust/WASM package in the sibling
+`bitbox-api-rs` checkout, while the protobuf source of truth is
+`bitbox02-firmware/messages`.
+
+## Prerequisites
+
+- Node.js >= 20
+- npm
+- Linux x64 for the downloaded simulator test suite
+
+Install dependencies with:
+
+```bash
+make install
+```
+
+## Common Commands
+
+```bash
+make typecheck         # tsc --noEmit
+make lint              # eslint .
+make test              # unit tests
+make test-sim          # simulator tests
+make build             # build ./dist
+make ci                # full validation pipeline
+
+make sandbox-dev       # browser sandbox at http://localhost:5173
+make sandbox-typecheck
+make sandbox-build
+
+make proto-sync        # copy firmware .proto files into messages/
+make proto-gen         # regenerate TS protobuf bindings
+make proto-reset       # clean, resync, and regenerate protobuf bindings
+make api-fixture-update  # refresh the Rust/WASM API snapshot fixture
+```
+
+`make ci` runs the same validation sequence as GitHub Actions. In CI it installs
+dependencies first, checks protobuf regeneration, runs typecheck/lint/unit
+tests/build/package/sandbox checks, and runs simulator tests on Linux x64
+unless `SKIP_SIMULATOR=1` is set.
+
+## Simulator Tests
+
+Simulator tests live under `test/simulator-*.test.ts` and run through Vitest's
+`simulator` project:
+
+```bash
+npm run test:sim
+```
+
+On Linux x64, the harness downloads and caches the simulator binaries listed in
+`test/simulators.json` under `test/simulators/`, verifies their sha256 hashes,
+and starts the newest listed simulator by default.
+
+Useful environment variables:
+
+- `SIMULATOR=/path/to/simulator`: run a custom simulator binary instead of the
+  downloaded one.
+- `SKIP_SIMULATOR=1`: skip simulator tests in `make ci`.
+
+The simulator listens on fixed TCP port `15423`. Keep simulator suites
+serialized and reuse one simulator process per file.
+
+## Protobuf Workflow
+
+The checked-in `.proto` files under `messages/` are copied from
+`../bitbox02-firmware/messages`, not from the Rust API repo.
+
+When firmware messages change:
+
+```bash
+make proto-reset
+make typecheck
+make test
+```
+
+CI runs `npm run proto:check`, which regenerates bindings and fails if
+`src/proto/gen` would change.
+
+## Compatibility Policy
+
+The package is intended as a drop-in TypeScript replacement for the current
+`bitbox-api` Rust/WASM npm package where methods are implemented.
+
+- Keep the exported function/class/type surface aligned with
+  `../bitbox-api-rs/pkg/bitbox_api.d.ts`.
+- Only relax the API snapshot for deliberate source-compatible TypeScript
+  ergonomics, such as optional callbacks or safer `bigint` input paths.
+- Public errors must keep the `{ code, message, err? }` shape. New public error
+  behavior should go through `src/internal/errors.ts` and match the compatibility
+  taxonomy unless there is an explicit reason to extend it.
+- BTC, Cardano, and BIP85 methods remain compatibility stubs in this iteration.
+  Do not document or test them as implemented until their protocol support lands.
+
+`test/api-snapshot.test.ts` compares the built `dist/index.d.ts` against the
+checked-in `test/fixtures/bitbox_api.d.ts` fixture. To refresh the fixture,
+rebuild the Rust/WASM package in `../bitbox-api-rs` so
+`../bitbox-api-rs/pkg/bitbox_api.d.ts` exists, then run:
+
+```bash
+make api-fixture-update
+```
+
+## Dependency Policy
+
+Runtime dependencies should stay small, browser-safe, and audit-friendly.
+
+- No native runtime modules.
+- No WASM runtime dependency.
+- Prefer the existing `@noble/*` crypto stack over adding wallet-framework
+  dependencies for small utilities.
+- Keep peer dependency ranges intentional; many integrators already have
+  `@noble/*` through wallet/Web3 stacks.
+
+## Sandbox
+
+The sandbox in `sandbox/` is for manual browser testing against real BitBox
+hardware through WebHID or BitBoxBridge:
+
+```bash
+make sandbox-dev
+```
+
+The sandbox aliases `@bitboxswiss/bitbox-api` to `../src/index.ts`, so source edits
+hot-reload without building `dist/`. Browsers cannot connect to the raw TCP
+simulator transport directly; simulator coverage belongs in `npm run test:sim`.

package/LICENSE

@@ -0,0 +1,203 @@
+Copyright 2026 Shift Crypto AG, Switzerland. All rights reserved.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,259 @@
+# @bitboxswiss/bitbox-api
+
+Pure TypeScript library for integrating BitBox02 hardware wallets in browser
+applications.
+
+`@bitboxswiss/bitbox-api` is source-compatible with the current `bitbox-api`
+Rust/WASM package for the implemented surface, but it does not ship WASM and
+does not require a WASM init step.
+
+## Status
+
+- **Implemented:** WebHID and BitBoxBridge transports, Noise XX pairing,
+  Ethereum xpub/address/signing methods, antiklepto, transaction data
+  streaming, EIP-712 typed messages, and `ethIdentifyCase()`.
+- **Stubbed with `code: 'unsupported'`:** BTC, Cardano, and BIP85 methods.
+- **Stubbed with `code: 'not-implemented'`:** `deviceInfo()`,
+  `rootFingerprint()`, `showMnemonic()`, and `changePassword()`.
+  `product()` and `version()` are implemented.
+
+## Installation
+
+```bash
+npm install @bitboxswiss/bitbox-api
+```
+
+`@noble/ciphers`, `@noble/curves`, and `@noble/hashes` are peer dependencies so
+the library does not perturb the crypto dependency graph of wallet/Web3 apps.
+
+- **npm 7+** installs peer dependencies automatically.
+- **pnpm/yarn** peer handling depends on your package-manager version and
+  settings. If your dependency tree does not already include `@noble/*`, add
+  them:
+
+  ```bash
+  yarn add @noble/ciphers @noble/curves @noble/hashes
+  ```
+
+The package is ESM-only.
+
+## Migrating from `bitbox-api`
+
+For currently implemented methods, the intended migration is just the import
+name:
+
+```ts
+import * as bitbox from '@bitboxswiss/bitbox-api';
+```
+
+There is no `init()` call and no WASM loader. Existing Webpack/Vite WASM plugin
+configuration from `bitbox-api` is not needed for this package.
+
+The first TypeScript iteration is Ethereum-focused. BTC, Cardano, BIP85, and a
+few general device helpers are still present in the public type surface for
+compatibility, but currently reject with typed errors as listed in
+[Status](#status).
+
+## Browser Requirements
+
+- WebHID works in Chromium-based browsers in a secure context, such as HTTPS or
+  localhost. Call the connect function from a user action, such as a button
+  click, so the browser can show the device chooser.
+- BitBoxBridge works through the local BitBoxBridge service. It is the fallback
+  used by `bitbox02ConnectAuto()` when WebHID is unavailable.
+- Pairing trust is stored in `localStorage` when available. Clearing site data
+  can require the user to confirm the pairing code again. If `localStorage` is
+  unavailable, pairing trust is kept only for the current JavaScript runtime.
+
+## Connecting and Pairing
+
+```ts
+import * as bitbox from '@bitboxswiss/bitbox-api';
+
+async function connectBitBox(): Promise<bitbox.PairedBitBox | undefined> {
+  try {
+    const onClose = () => {
+      // Clear app state for this BitBox connection.
+    };
+
+    const unpaired = await bitbox.bitbox02ConnectAuto(onClose);
+    const pairing = await unpaired.unlockAndPair();
+
+    const pairingCode = pairing.getPairingCode();
+    if (pairingCode !== undefined) {
+      // Display the code and ask the user to confirm the same code on the BitBox02.
+      console.log('Pairing code:', pairingCode);
+    }
+
+    const bb02 = await pairing.waitConfirm();
+    console.log('Product:', bb02.product());
+    console.log('Firmware:', bb02.version());
+    return bb02;
+  } catch (err) {
+    const typed = bitbox.ensureError(err);
+    if (bitbox.isUserAbort(typed)) {
+      return undefined;
+    }
+    throw typed;
+  }
+}
+```
+
+`BitBox`, `PairingBitBox`, and `PairedBitBox` model a single connection flow.
+After `unlockAndPair()` succeeds, use the returned `PairingBitBox` and stop
+using the original `BitBox`. After `waitConfirm()` succeeds, use the returned
+`PairedBitBox` and stop using the `PairingBitBox`. Reusing consumed or closed
+objects throws `code: 'invalid-state'`.
+
+If `unlockAndPair()` or `waitConfirm()` fails, the underlying transport is
+closed. Reconnect before retrying.
+
+Call `bb02.close()` when your app is done with the device. `close()` is
+idempotent and invokes the `onClose` callback supplied to the connect function.
+
+## Ethereum Usage
+
+Keypaths can be strings such as `m/44'/60'/0'/0/0` or number arrays. Chain IDs
+are `bigint` for most Ethereum methods. EIP-1559 transaction objects accept
+`number | bigint` for source compatibility, but `bigint` is preferred when the
+value may exceed JavaScript's safe integer range.
+
+```ts
+const keypath = "m/44'/60'/0'/0/0";
+const chainId = 1n;
+
+if (!bb02.ethSupported()) {
+  throw new Error('This BitBox02 does not support Ethereum');
+}
+
+const xpub = await bb02.ethXpub("m/44'/60'/0'/0");
+const address = await bb02.ethAddress(chainId, keypath, true);
+```
+
+Transaction byte fields are big-endian `Uint8Array`s without a `0x` prefix.
+Returned signature byte fields are plain `number[]` arrays, matching the
+runtime shape of the old WASM package. Pass `ethIdentifyCase()` for the
+optional recipient case hint when you derive the transaction from a hex address
+string.
+
+```ts
+function hexToBytes(hex: string): Uint8Array {
+  const body = hex.replace(/^0x/i, '');
+  if (body.length % 2 !== 0 || !/^[0-9a-fA-F]*$/.test(body)) {
+    throw new Error(`invalid hex length: ${hex}`);
+  }
+  const out = new Uint8Array(body.length / 2);
+  for (let i = 0; i < out.length; i += 1) {
+    out[i] = Number.parseInt(body.slice(i * 2, i * 2 + 2), 16);
+  }
+  return out;
+}
+
+const recipient = '04f264cf34440313b4a0192a352814fbe927b885';
+const signature = await bb02.ethSignTransaction(
+  1n,
+  keypath,
+  {
+    nonce: hexToBytes('1fdc'),
+    gasPrice: hexToBytes('0165a0bc00'),
+    gasLimit: hexToBytes('5208'),
+    recipient: hexToBytes(recipient),
+    value: hexToBytes('075cf1259e9c4000'),
+    data: new Uint8Array(),
+  },
+  bitbox.ethIdentifyCase(recipient),
+);
+
+console.log(signature.r, signature.s, signature.v);
+```
+
+For EIP-1559, `chainId` is part of the transaction object:
+
+```ts
+await bb02.ethSign1559Transaction(keypath, {
+  chainId: 1n,
+  nonce: hexToBytes('1fdc'),
+  maxPriorityFeePerGas: hexToBytes('3b9aca00'),
+  maxFeePerGas: hexToBytes('04a817c800'),
+  gasLimit: hexToBytes('5208'),
+  recipient: hexToBytes(recipient),
+  value: hexToBytes('075cf1259e9c4000'),
+  data: new Uint8Array(),
+});
+```
+
+Personal messages are signed with the standard Ethereum message prefix on the
+device:
+
+```ts
+const msg = new TextEncoder().encode('hello bitbox');
+await bb02.ethSignMessage(1n, keypath, msg);
+```
+
+EIP-712 typed messages are passed as JavaScript values. `use_antiklepto`
+defaults to `true` when omitted.
+
+```ts
+await bb02.ethSignTypedMessage(1n, keypath, typedData);
+```
+
+## Typed Errors
+
+All public API entry points reject with, or can be normalized to, this shape:
+
+```ts
+type Error = {
+  code: string;
+  message: string;
+  err?: any;
+};
+```
+
+Use `ensureError()` at API boundaries:
+
+```ts
+try {
+  await bb02.ethAddress(1n, keypath, true);
+} catch (err) {
+  const typed = bitbox.ensureError(err);
+  if (bitbox.isUserAbort(typed)) {
+    return;
+  }
+  console.error(typed.code, typed.message);
+}
+```
+
+Common client-facing codes include:
+
+- `could-not-open`: the device or bridge connection could not be opened.
+- `user-abort` / `bitbox-user-abort`: the user cancelled in the browser or on
+  the device.
+- `invalid-type`, `keypath-parse`, `chain-id-too-large`: invalid host inputs.
+- `communication`, `noise`, `noise-config`, `pairing-rejected`: transport,
+  pairing, or encrypted-channel failures.
+- `version`: the connected firmware is too old for the requested method.
+- `unsupported` / `not-implemented`: public compatibility methods that are not
+  wired in this TypeScript iteration.
+
+## Sandbox and Development
+
+The repository includes a browser sandbox for manual testing with real
+hardware:
+
+```bash
+make install
+make sandbox-dev
+```
+
+Open the printed Vite URL, usually `http://localhost:5173`.
+
+For build, test, simulator, protobuf, and contribution workflow details, see
+[CONTRIBUTING.md](CONTRIBUTING.md).
+
+## API Compatibility
+
+`test/api-snapshot.test.ts` compares the built TypeScript declarations against
+`../bitbox-api-rs/pkg/bitbox_api.d.ts` when the reference checkout is present.
+The guard keeps the public surface drop-in compatible while still allowing
+deliberate source-compatible TypeScript widenings, such as optional close
+callbacks and safer `bigint` chain ID paths.

package/package.json

@@ -0,0 +1,79 @@
+{
+  "name": "@bitboxswiss/bitbox-api",
+  "version": "0.1.0",
+  "description": "A pure TypeScript library to interact with BitBox hardware wallets.",
+  "license": "Apache-2.0",
+  "type": "module",
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist",
+    "README.md",
+    "CONTRIBUTING.md",
+    "LICENSE"
+  ],
+  "sideEffects": false,
+  "engines": {
+    "node": ">=20"
+  },
+  "scripts": {
+    "build": "rm -rf dist && tsc -p tsconfig.build.json",
+    "typecheck": "tsc --noEmit",
+    "lint": "eslint .",
+    "test": "vitest run --project unit",
+    "test:sim": "vitest run --project simulator",
+    "proto:sync": "cp ../bitbox02-firmware/messages/*.proto messages/",
+    "proto:gen": "buf generate",
+    "proto:check": "buf generate && git diff --exit-code -- src/proto/gen",
+    "sandbox:dev": "vite --config sandbox/vite.config.ts",
+    "sandbox:typecheck": "tsc -p sandbox/tsconfig.json",
+    "sandbox:build": "vite build --config sandbox/vite.config.ts"
+  },
+  "devDependencies": {
+    "@bufbuild/buf": "1.68.3",
+    "@bufbuild/protoc-gen-es": "2.11.0",
+    "@eslint/js": "10.0.1",
+    "@ethereumjs/rlp": "10.1.1",
+    "@noble/ciphers": "1.3.0",
+    "@noble/curves": "1.9.1",
+    "@noble/hashes": "1.8.0",
+    "@stylistic/eslint-plugin": "5.10.0",
+    "@types/node": "25.6.0",
+    "@types/react": "18.3.12",
+    "@types/react-dom": "18.3.1",
+    "@vitejs/plugin-react-swc": "4.3.0",
+    "eslint": "10.2.1",
+    "react": "18.3.1",
+    "react-dom": "18.3.1",
+    "typescript": "6.0.3",
+    "typescript-eslint": "8.59.0",
+    "vite": "6.4.2",
+    "vitest": "4.1.5"
+  },
+  "keywords": [
+    "bitbox",
+    "bitbox02",
+    "hardware-wallet",
+    "ethereum",
+    "typescript"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/BitBoxSwiss/bitbox-api-ts"
+  },
+  "homepage": "https://bitbox.swiss/",
+  "dependencies": {
+    "@bufbuild/protobuf": "2.11.0"
+  },
+  "peerDependencies": {
+    "@noble/ciphers": "^1.3.0",
+    "@noble/curves": "^1.2.0",
+    "@noble/hashes": "^1.8.0"
+  }
+}