@vscode/vsce
npmIs @vscode/vsce safe to use?
The latest brin safety scan flagged @vscode/vsce v3.7.1 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 85/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
@vscode/vsce 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 @vscode/vsce 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.
@vscode/vsce Capabilities & Permissions
What @vscode/vsce can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads and writes to the filesystem.
Process Spawning
This package can spawn child processes.
Environment Variables
Accesses the following environment variables.
AGENTS.md for @vscode/vsce
Good instructions lead to good results. brin adds @vscode/vsce 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 →
@vscode/vsce Documentation & Source Code
For the full @vscode/vsce README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @vscode/vsce safety
Install (safety-checked)
Weekly Downloads
Version
3.7.1License
MITLast Scanned
Trust Score
Capabilities
Reads & Writes files
Spawns child processes
Accesses: AZURE_CLIENT_ID, AZURE_TENANT_ID, GITHUB_ACTIONS...