fn-name
npmIs fn-name safe to use?
The latest brin safety scan flagged fn-name v4.0.0 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 65/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
fn-name Has Warnings
Warnings detected due to potential concerns
0
0
0
Risk Indicators
- •Can spawn child processes
brin Recommendations
- →This package has warnings detected. Evaluate the specific concerns before proceeding.
Install with brin add fn-name 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.
fn-name Capabilities & Permissions
What fn-name 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.
AGENTS.md for fn-name
Good instructions lead to good results. brin adds fn-name documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
fn-name Documentation & Source Code
For the full fn-name README, API documentation, and source code, visit the official package registry.
Frequently asked questions about fn-name safety
Install (safety-checked)
Weekly Downloads
Version
4.0.0License
MITLast Scanned
Trust Score
Capabilities
Spawns child processes