@bentley/frontend-authorization-client 2.18.0-dev.4

iModel.js Frontend Authorization Client

@bentley/frontend-authorization-client@2.18.0-dev.4 was published on 2021-06-13. Its manifest declares 1 runtime dependency and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

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/frontend-authorization-client versions · Permanent reference to 2.18.0-dev.4 · Latest release

Package specifications

Version2.18.0-dev.4
License declarationMIT
Published2021-06-13T05:34:06.001Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size116.05 KiB
Published file count40
Package typeNot declared
ES module entryNot declared
Default entrylib/frontend-authorization-client.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars738
Repository forks248

Install @bentley/frontend-authorization-client 2.18.0-dev.4

npm install @bentley/frontend-authorization-client@2.18.0-dev.4
pnpm add @bentley/frontend-authorization-client@2.18.0-dev.4
yarn add @bentley/frontend-authorization-client@2.18.0-dev.4

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

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