@sentry/node 10.1.0

Sentry Node SDK using OpenTelemetry for performance instrumentation

@sentry/node@10.1.0 was published on 2025-08-04. Its manifest declares 35 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.

All @sentry/node versions · Permanent reference to 10.1.0 · Latest release

Package specifications

Version10.1.0
License declarationMIT
Published2025-08-04T11:25:33.954Z
Node.js requirement>=18
Type declarationsBundled declarations
Runtime dependency count35
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1113.57 KiB
Published file count385
Package typeNot declared
ES module entrybuild/esm/index.js
Default entrybuild/cjs/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies77
Repository stars8763
Repository forks1875

Install @sentry/node 10.1.0

npm install @sentry/node@10.1.0
pnpm add @sentry/node@10.1.0
yarn add @sentry/node@10.1.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.

Maintained10/10 — 30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Binary-Artifacts9/10 — binaries present in source code
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Fuzzing0/10 — project is not fuzzed
SAST7/10 — SAST tool detected but not run on all commits

Evidence and freshness