launchdarkly-node-client-sdk 1.2.0

LaunchDarkly Client-Side SDK for Node.js

launchdarkly-node-client-sdk@1.2.0 was published on 2019-11-06. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All launchdarkly-node-client-sdk versions · Permanent reference to 1.2.0 · View npm registry JSON · Latest release

Package specifications

Version1.2.0
License declarationApache-2.0
Published2019-11-06T01:06:34.184Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size47.73 KiB
Published file count34
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies66
Repository stars9
Repository forks6

Install launchdarkly-node-client-sdk 1.2.0

npm install launchdarkly-node-client-sdk@1.2.0
pnpm add launchdarkly-node-client-sdk@1.2.0
yarn add launchdarkly-node-client-sdk@1.2.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.

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.

Security-Policy9/10 — security policy file detected
Code-Review8/10 — Found 4/5 approved changesets -- score normalized to 8
Binary-Artifacts10/10 — no binaries found in the repo
Maintained10/10 — 29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies1/10 — dependency not pinned by hash detected -- score normalized to 1
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness