browser-http

npm

Is browser-http safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for browser-http v4.0.2. 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)

browser-http 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.

browser-http Capabilities & Permissions

What browser-http 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.

blog.stevenlevithan.comgithub.comwww.opensource.orgwww.w3.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for browser-http

Good instructions lead to good results. brin adds browser-http 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-http Documentation & Source Code

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

Frequently asked questions about browser-http safety

Weekly Downloads

124

Version

4.0.2

License

MIT

Last Scanned

16 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: blog.stevenlevithan.com, github.com, www.opensource.org...

Process

Spawns child processes

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