field_capture
npmIs field_capture safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for field_capture v1.0.0. Trust score: 50/100. 1 known CVE, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.
Install (safety-checked)
field_capture Passed Security Checks
No security concerns detected
1
0
0
Risk Indicators
- •MAL-2025-44251: UNKNOWN
field_capture CVE Vulnerabilities (1)
Malicious code in field_capture (npm)
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.
field_capture Capabilities & Permissions
What field_capture 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 field_capture
Good instructions lead to good results. brin adds field_capture 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 →
field_capture Documentation & Source Code
For the full field_capture README, API documentation, and source code, visit the official package registry.
Frequently asked questions about field_capture safety
Install (safety-checked)
Weekly Downloads
Version
1.0.0License
ISCLast Scanned
Trust Score
CVEs (1)
Malicious code in field_capture (npm)
Capabilities
Spawns child processes