Gathering detailed insights and metrics for dd-trace
Gathering detailed insights and metrics for dd-trace
npm install dd-trace
Typescript
Module System
Min. Node Version
Node Version
NPM Version
72.9
Supply Chain
97.5
Quality
94.2
Maintenance
100
Vulnerability
87.3
License
JavaScript (99.7%)
Shell (0.12%)
HTML (0.09%)
Gherkin (0.04%)
Dockerfile (0.03%)
TypeScript (0.03%)
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Total Downloads
417,942,839
Last Day
757,680
Last Week
3,770,517
Last Month
16,034,531
Last Year
140,865,725
NOASSERTION License
683 Stars
3,248 Commits
321 Forks
602 Watchers
287 Branches
456 Contributors
Updated on Mar 14, 2025
Minified
Minified + Gzipped
Latest Version
5.41.1
Package Id
dd-trace@5.41.1
Unpacked Size
2.37 MB
Size
561.29 kB
File Count
704
NPM Version
10.8.2
Node Version
20.18.3
Published on
Mar 07, 2025
Cumulative downloads
Total Downloads
Last Day
7.5%
757,680
Compared to previous day
Last Week
-1.8%
3,770,517
Compared to previous week
Last Month
17.3%
16,034,531
Compared to previous month
Last Year
25.7%
140,865,725
Compared to previous year
32
45
dd-trace
: Node.js APM Tracer Librarydd-trace
is an npm package that you can install in your Node.js application to capture APM (Application Performance Monitoring) data. In Datadog terminology this library is called a Tracer. This data is then sent off to a process which collects and aggregates the data, called an Agent. Finally the data is sent off to the Datadog servers where it's stored and made available for querying in a myriad of ways, such as displaying in a dashboard or triggering alerts.
Most of the documentation for dd-trace
is available on these webpages:
Release Line | Latest Version | Node.js | SSI | K8s Injection | Status | Initial Release | End of Life |
---|---|---|---|---|---|---|---|
v1 | >= v12 | NO | NO | EOL | 2021-07-13 | 2022-02-25 | |
v2 | >= v12 | NO | NO | EOL | 2022-01-28 | 2023-08-15 | |
v3 | >= v14 | NO | YES | EOL | 2022-08-15 | 2024-05-15 | |
v4 | >= v16 | YES | YES | EOL | 2023-05-12 | 2025-01-11 | |
v5 | >= v18 | YES | YES | Current | 2024-01-11 | Unknown |
We currently maintain one release line, namely v5
.
For any new projects it is recommended to use the v5
release line:
1$ npm install dd-trace 2$ yarn add dd-trace
Existing projects that need to use EOL versions of Node.js may continue to use these older release lines. This is done by specifying the version when installing the package.
1$ npm install dd-trace@4 # or whatever version you need 2$ yarn add dd-trace@4 # or whatever version you need
Note, however, that the end-of-life release lines are no longer maintained and will not receive updates.
Any backwards-breaking functionality that is introduced into the library will result in an increase of the major version of the library and therefore a new release line. Such releases are kept to a minimum to reduce the pain of upgrading the library.
When a new release line is introduced the previous release line then enters maintenance mode where it will receive updates for the next year. Once that year is up the release line enters End of Life and will not receive new updates. The library also follows the Node.js LTS lifecycle wherein new release lines drop compatibility with Node.js versions that reach end-of-life (with the maintenance release line still receiving updates for a year).
For more information about library versioning and compatibility, see the NodeJS Compatibility Requirements page.
Changes associated with each individual release are documented on the GitHub Releases screen.
Please read the CONTRIBUTING.md document before contributing to this open source project.
ESM support requires an additional command-line argument. Use the following to enable experimental ESM support with your application:
Node.js < v20.6
1node --loader dd-trace/loader-hook.mjs entrypoint.js
Node.js >= v20.6
1node --import dd-trace/register.js entrypoint.js
Note that there is a separate Lambda project, datadog-lambda-js, that is responsible for enabling metrics and distributed tracing when your application runs on Lambda.
That project does depend on the dd-trace
package but also adds a lot of Lambda-related niceties.
If you find any issues specific to Lambda integrations then the issues may get solved quicker if they're added to that repository.
That said, even if your application runs on Lambda, any core instrumentation issues not related to Lambda itself may be better served by opening an issue in this repository.
Regardless of where you open the issue, someone at Datadog will try to help.
If you would like to trace your bundled application then please read this page on bundling and dd-trace. It includes information on how to use our ESBuild plugin and includes caveats for other bundlers.
Please refer to the SECURITY.md document if you have found a security issue.
Please refer to the Node.js Custom Instrumentation using OpenTelemetry API document. It includes information on how to use the OpenTelemetry API with dd-trace-js.
Note that our internal implementation of the OpenTelemetry API is currently set within the version range >=1.0.0 <1.9.0
. This range will be updated at a regular cadence therefore, we recommend updating your tracer to the latest release to ensure up to date support.
No vulnerabilities found.
Reason
security policy file detected
Details
Reason
all changesets reviewed
Reason
30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
packaging workflow detected
Details
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 9
Details
Reason
1 existing vulnerabilities detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
project is not fuzzed
Details
Score
Last Scanned on 2025-03-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More