dd-trace 0.29.1

Datadog APM tracing client for JavaScript

dd-trace@0.29.1 was published on 2020-11-27. Its manifest declares 30 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.

Deprecated: The v0.x release line of dd-trace has reached End of Life! Please upgrade to the latest version of dd-trace to continue receiving updates.

All dd-trace versions · Permanent reference to 0.29.1 · Latest release

Package specifications

Version0.29.1
License declarationBSD-3-Clause
Published2020-11-27T18:06:50.431Z
Node.js requirement>=8
Type declarationsBundled declarations
Runtime dependency count30
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size10796.59 KiB
Published file count285
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies129
Repository stars840
Repository forks415

Install dd-trace 0.29.1

npm install dd-trace@0.29.1
pnpm add dd-trace@0.29.1
yarn add dd-trace@0.29.1

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.

Known direct advisories

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 23 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow0/10 — dangerous workflow patterns detected
License9/10 — license file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Packaging10/10 — packaging workflow detected
Fuzzing0/10 — project is not fuzzed
SAST8/10 — SAST tool detected but not run on all commits

Evidence and freshness