v-input-trim
npmIs v-input-trim safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for v-input-trim v0.1.2. 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)
v-input-trim Passed Security Checks
No security concerns detected
0
0
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.
v-input-trim Capabilities & Permissions
What v-input-trim 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 v-input-trim
Good instructions lead to good results. brin adds v-input-trim 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 →
v-input-trim Documentation & Source Code
For the full v-input-trim README, API documentation, and source code, visit the official package registry.
Frequently asked questions about v-input-trim safety
Install (safety-checked)
Weekly Downloads
Version
0.1.2Last Scanned
Trust Score
Capabilities
Spawns child processes