limit-spawn

npm

Is limit-spawn safe to use?

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

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

limit-spawn Capabilities & Permissions

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

Process Spawning

This package can spawn child processes.

node

AGENTS.md for limit-spawn

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

limit-spawn Documentation & Source Code

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

Frequently asked questions about limit-spawn safety

Weekly Downloads

36.6K

Version

0.0.3

License

MIT

Last Scanned

1 day ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes