@visx/vendor
npmIs @visx/vendor safe to use?
The latest brin safety scan flagged @visx/vendor v3.12.0 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 75/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
@visx/vendor 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 @visx/vendor 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.
@visx/vendor Capabilities & Permissions
What @visx/vendor 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 @visx/vendor
Good instructions lead to good results. brin adds @visx/vendor 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 →
@visx/vendor Documentation & Source Code
For the full @visx/vendor README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @visx/vendor safety
Install (safety-checked)
Weekly Downloads
Version
3.12.0License
MIT and ISCLast Scanned
Trust Score
Capabilities
Spawns child processes