bounds

npm

Is bounds safe to use?

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

bounds 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.

bounds Capabilities & Permissions

No system capabilities detected for bounds. 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 bounds

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

bounds Documentation & Source Code

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

Frequently asked questions about bounds safety

Weekly Downloads

21

Version

4.0.0

License

MIT

Last Scanned

4 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is bounds Safe? | npm Safety Scan - brin