@bugsnag/node 5.2.0

Bugsnag error reporter for Node.js

@bugsnag/node@5.2.0 was published on 2019-01-21. 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 @bugsnag/node versions · Permanent reference to 5.2.0 · Latest release

Package specifications

Version5.2.0
License declarationMIT
Published2019-01-21T11:25:40.609Z
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 size196.30 KiB
Published file count14
Package typeNot declared
ES module entryNot declared
Default entrydist/bugsnag.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies56
Repository stars898
Repository forks258

Install @bugsnag/node 5.2.0

npm install @bugsnag/node@5.2.0
pnpm add @bugsnag/node@5.2.0
yarn add @bugsnag/node@5.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.

Maintained10/10 — 30 commit(s) and 0 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
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
License10/10 — license file detected
Signed-Releases8/10 — 5 out of the last 5 releases have a total of 5 signed artifacts.
Fuzzing0/10 — project is not fuzzed
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Binary-Artifacts10/10 — no binaries found in the repo
SAST10/10 — SAST tool is run on all commits

Evidence and freshness