@azure/core-client 1.10.0

Core library for interfacing with AutoRest generated code

@azure/core-client@1.10.0 was published on 2025-07-10. Its manifest declares 7 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.0.0.

All @azure/core-client versions · Permanent reference to 1.10.0 · Latest release

Package specifications

Version	1.10.0
License declaration	MIT
Published	2025-07-10T17:54:05.866Z
Node.js requirement	>=20.0.0
Type declarations	Bundled declarations
Runtime dependency count	7
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	1359.65 KiB
Published file count	212
Package type	module
ES module entry	./dist/esm/index.js
Default entry	./dist/commonjs/index.js
Side effects declaration	false
Direct advisories	0
Resolved graph dependencies	13
Repository stars	2301
Repository forks	1408

Install @azure/core-client 1.10.0

npm install @azure/core-client@1.10.0
pnpm add @azure/core-client@1.10.0
yarn add @azure/core-client@1.10.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.

@azure/abort-controller@2.2.0 — direct
@azure/core-auth@1.11.0 — direct
@azure/core-rest-pipeline@1.25.0 — direct
@azure/core-tracing@1.4.0 — direct
@azure/core-util@1.14.0 — direct
@azure/logger@1.4.0 — direct
@typespec/ts-http-runtime@0.3.9 — indirect
agent-base@7.1.4 — indirect
debug@4.4.3 — indirect
http-proxy-agent@7.0.2 — indirect
https-proxy-agent@7.0.6 — indirect
ms@2.1.3 — indirect
tslib@2.8.1 — direct

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.

Code-Review	9/10 — Found 16/17 approved changesets -- score normalized to 9
Maintained	10/10 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
License	10/10 — license file detected
Security-Policy	10/10 — security policy file detected
Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Branch-Protection	5/10 — branch protection is not maximal on development and all release branches
Token-Permissions	9/10 — detected GitHub workflow tokens with excessive permissions
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0
Binary-Artifacts	9/10 — binaries present in source code
Pinned-Dependencies	7/10 — dependency not pinned by hash detected -- score normalized to 7
Fuzzing	0/10 — project is not fuzzed

Evidence and freshness

https://registry.npmjs.org/%40azure%2Fcore-client/1.10.0 — retrieved 2026-10-29T10:02:04.937Z
https://api.deps.dev/v3/projects/github.com%2FAzure%2Fazure-sdk-for-js — retrieved 2026-10-29T07:59:45.919Z
https://api.deps.dev/v3/systems/npm/packages/%40azure%2Fcore-client/versions/1.10.0 — retrieved 2026-10-29T10:02:05.472Z
https://api.deps.dev/v3/systems/npm/packages/%40azure%2Fcore-client/versions/1.10.0:dependencies — retrieved 2026-10-29T10:02:05.494Z