brin
brin

browser-pack

npm

Is browser-pack safe to use?

The latest brin safety scan flagged browser-pack v6.1.0 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)

browser-pack Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • •Can spawn child processes

brin Recommendations

  • →This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add browser-pack 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.

browser-pack Capabilities & Permissions

What browser-pack can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads and writes to the filesystem.

/usr/ (r)/usr/ (rw)

Process Spawning

This package can spawn child processes.

AGENTS.md for browser-pack

Good instructions lead to good results. brin adds browser-pack 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 →

browser-pack Documentation & Source Code

For the full browser-pack README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about browser-pack safety

Weekly Downloads

1.1M

Version

6.1.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Process

Spawns child processes

Is browser-pack Safe? | npm Safety Scan - brin