@azure/cosmos-sign

Utility for signing Azure Cosmos keys

@azure/cosmos-sign@1.0.2 was published on 2018-12-18. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @azure/cosmos-sign versions · Permanent reference to 1.0.2 · View npm registry JSON

Package specifications

Version1.0.2
License declarationMIT
Published2018-12-18T20:23:51.508Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size10.98 KiB
Published file count13
Package typeNot declared
ES module entryNot declared
Default entry./lib/node.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars7
Repository forks6

Install @azure/cosmos-sign 1.0.2

npm install @azure/cosmos-sign@1.0.2
pnpm add @azure/cosmos-sign@1.0.2
yarn add @azure/cosmos-sign@1.0.2

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
Code-Review0/10 — Found 0/29 approved changesets -- score normalized to 0
Maintained0/10 — project is archived
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy10/10 — security policy file detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness