@bugsnag/browser 8.0.0-alpha.12

Bugsnag error reporter for browser JavaScript

@bugsnag/browser@8.0.0-alpha.12 was published on 2024-07-31. Its manifest declares 1 runtime dependency 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/browser versions · Permanent reference to 8.0.0-alpha.12 · Latest release

Package specifications

Version8.0.0-alpha.12
License declarationMIT
Published2024-07-31T11:16:20.602Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size536.74 KiB
Published file count9
Package typeNot declared
ES module entryNot declared
Default entrydist/bugsnag.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars898
Repository forks258

Install @bugsnag/browser 8.0.0-alpha.12

npm install @bugsnag/browser@8.0.0-alpha.12
pnpm add @bugsnag/browser@8.0.0-alpha.12
yarn add @bugsnag/browser@8.0.0-alpha.12

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 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