Scanning for Malicious VS Code and OpenVSX Extensions #550
abhisek
started this conversation in
Show and tell
Replies: 2 comments
-
|
@Sahilb315 Can you share some examples on how we can scan VS Code and OpenVSX extensions with vet? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Default scan: vet scan --vsxThis command scans all the IDE's extensions To scan specific IDE's: vet scan --vsx --vsx-dir /path/to/ide_extensionsExample :- vet scan --vsx --vsx-dir ~/.vscode/extensions/ --vsx-dir ~/.cursor/extensionsThis command will scan only VS Code & Cursor extensions |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We will use this thread to showcase and collect feedback on how SafeDep vet can scan VS Code and OpenVSX extensions for malicious code.
Note: These two ecosystems are new in our package scanning infra. Currently at experimental stage.
Beta Was this translation helpful? Give feedback.
All reactions