@serverbench/js

npm

Is @serverbench/js safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @serverbench/js v1.5.12. Trust score: 50/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)

@serverbench/js 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.

@serverbench/js Capabilities & Permissions

What @serverbench/js 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.

api.beta.serverbench.iodev.serverbench.iolive.beta.serverbench.iosafe.serverbench.io
Protocols: https, websocket

AGENTS.md for @serverbench/js

Good instructions lead to good results. brin adds @serverbench/js 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 →

@serverbench/js Documentation & Source Code

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

Frequently asked questions about @serverbench/js safety

Weekly Downloads

90

Version

1.5.12

License

ISC

Last Scanned

4 hours ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: api.beta.serverbench.io, dev.serverbench.io, live.beta.serverbench.io...

Is @serverbench/js Safe? | npm Safety Scan - brin