@bentley/backend-itwin-client 2.9.7

Clients for various Bentley Services used by iModel.js at the backend

@bentley/backend-itwin-client@2.9.7 was published on 2020-12-09. Its manifest declares 10 runtime dependencies and 8 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=10.16.0 <13.0.

Deprecated: This package has reached end of life and is deprecated. Please refer to our support policy, https://www.itwinjs.org/learning/api-support-policies/, and changelog, https://www.itwinjs.org/v3/changehistory/3.0.0/#package-name-changes.

All @bentley/backend-itwin-client versions · Permanent reference to 2.9.7 · Latest release

Package specifications

Version2.9.7
License declarationMIT
Published2020-12-09T21:33:06.267Z
Node.js requirement>=10.16.0 <13.0
Type declarationsBundled declarations
Runtime dependency count10
Peer requirement count8
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size292.48 KiB
Published file count94
Package typeNot declared
ES module entryNot declared
Default entrylib/backend-itwin-client.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies119
Repository stars738
Repository forks248

Install @bentley/backend-itwin-client 2.9.7

npm install @bentley/backend-itwin-client@2.9.7
pnpm add @bentley/backend-itwin-client@2.9.7
yarn add @bentley/backend-itwin-client@2.9.7

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.

Maintained10/10 — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Code-Review5/10 — Found 17/29 approved changesets -- score normalized to 5
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Binary-Artifacts9/10 — binaries present in source code
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness