browsersync

npm

Is browsersync safe to use?

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

Install (safety-checked)

browsersync Passed Security Checks

No security concerns detected

clean
CVEs

1

Threats

0

Install Scripts

0

Risk Indicators

  • MAL-2025-16207: UNKNOWN

browsersync CVE Vulnerabilities (1)

Malicious code in browsersync (npm)

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.

browsersync Capabilities & Permissions

No system capabilities detected for browsersync. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.

AGENTS.md for browsersync

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

browsersync Documentation & Source Code

For the full browsersync README, API documentation, and source code, visit the official package registry.

Frequently asked questions about browsersync safety

Weekly Downloads

4.0K

Version

0.0.1-security

License

ISC

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

CVEs (1)

MAL-2025-16207

Malicious code in browsersync (npm)

Capabilities

No special capabilities detected

Is browsersync Safe? | npm Safety Scan - brin