@browserbox/speaker

npm

Is @browserbox/speaker safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @browserbox/speaker v1.0.1. Trust score: 65/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

@browserbox/speaker Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

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.

@browserbox/speaker Capabilities & Permissions

What @browserbox/speaker can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Native Modules

Contains native code that runs outside the JavaScript sandbox.

AGENTS.md for @browserbox/speaker

Good instructions lead to good results. brin adds @browserbox/speaker documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

@browserbox/speaker Documentation & Source Code

For the full @browserbox/speaker README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @browserbox/speaker safety

Weekly Downloads

74

Version

1.0.1

License

(MIT AND LGPL-2.1-only)

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Native

Contains native modules

Is @browserbox/speaker Safe? | npm Safety Scan - brin