brin
brin

should

npm

Is should safe to use?

The latest brin safety scan flagged should v13.2.3 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 75/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

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

should Capabilities & Permissions

What should 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.

github.comnarwhaljs.org)nodejs.orgwiki.commonjs.org
Protocols: http, https

Process Spawning

This package can spawn child processes.

AGENTS.md for should

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

should Documentation & Source Code

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

View on npmView Source

Frequently asked questions about should safety

Weekly Downloads

3.4M

Version

13.2.3

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: github.com, narwhaljs.org), nodejs.org...

Process

Spawns child processes

Is should Safe? | npm Safety Scan - brin