should-format

npm

Is should-format safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for should-format v3.0.3. 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)

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

should-format Capabilities & Permissions

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

AGENTS.md for should-format

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

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

Frequently asked questions about should-format safety

Weekly Downloads

3.4M

Version

3.0.3

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Makes network requests

Is should-format Safe? | npm Safety Scan - brin