ffc-node

npm

Is ffc-node safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for ffc-node v18.0.0. 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)

ffc-node 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.

ffc-node Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

.env (r).env (r)

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

SMTP_PASSWORD

AGENTS.md for ffc-node

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

ffc-node Documentation & Source Code

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

Frequently asked questions about ffc-node safety

Weekly Downloads

109

Version

18.0.0

License

MIT

Last Scanned

19 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Environment

Accesses: SMTP_PASSWORD

Is ffc-node Safe? | npm Safety Scan - brin