@sentry/node 4.0.0-beta.4

Offical Sentry SDK for Node.js

@sentry/node@4.0.0-beta.4 was published on 2018-07-03. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=6.

All @sentry/node versions · Permanent reference to 4.0.0-beta.4 · Latest release

Package specifications

Version4.0.0-beta.4
License declarationBSD-3-Clause
Published2018-07-03T13:30:38.379Z
Node.js requirement>=6
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size92.01 KiB
Published file count48
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars8769
Repository forks1879

Install @sentry/node 4.0.0-beta.4

npm install @sentry/node@4.0.0-beta.4
pnpm add @sentry/node@4.0.0-beta.4
yarn add @sentry/node@4.0.0-beta.4

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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