brin
brin

nano-spawn

npm

Is nano-spawn safe to use?

The latest brin safety scan flagged nano-spawn v2.0.0 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)

nano-spawn 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 nano-spawn 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.

nano-spawn Capabilities & Permissions

What nano-spawn can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads and writes to the filesystem.

.env (r)node_modules (r).env (r).env (rw)

Process Spawning

This package can spawn child processes.

npm

AGENTS.md for nano-spawn

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

nano-spawn Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about nano-spawn safety

Weekly Downloads

6.0M

Version

2.0.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Process

Spawns child processes

Is nano-spawn Safe? | npm Safety Scan - brin