@bugsnag/browser
npmIs @bugsnag/browser safe to use?
The latest brin safety scan flagged @bugsnag/browser v8.8.1 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 85/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
@bugsnag/browser Has Warnings
Warnings detected due to potential concerns
0
0
0
Risk Indicators
- •Can spawn child processes
brin Recommendations
- →This package has warnings detected. Evaluate the specific concerns before proceeding.
Install with brin add @bugsnag/browser to automatically apply these checks before installation.
This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.
@bugsnag/browser Capabilities & Permissions
What @bugsnag/browser can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Network Access
This package makes network requests.
Process Spawning
This package can spawn child processes.
AGENTS.md for @bugsnag/browser
Good instructions lead to good results. brin adds @bugsnag/browser documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
@bugsnag/browser Documentation & Source Code
For the full @bugsnag/browser README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @bugsnag/browser safety
Install (safety-checked)
Weekly Downloads
Version
8.8.1License
MITLast Scanned
Trust Score
Capabilities
Connects to: developer.mozilla.org, docs.bugsnag.com, foo.com...
Spawns child processes