VS Code Extensions Risk and Necessity Audit (Defensive)
Review installed extensions for security, overlap and value.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit my VS Code extensions as a defensive review of my own tools. List of installed extensions with publisher, install count and last update if known, and what each is used for: [EXTENSION_LIST]. Types of projects and data I work with: [PROJECTS_AND_DATA]. Company rules on extensions: [POLICY]. Explain that an extension runs with the same permissions as I do. Classify each as essential, useful or unnecessary, count by category, and propose a smaller set. Check for unknown or unverified publishers, extensions not updated for a long time, overlapping functions (two formatters), extensions that request network access or run external programs, extensions that read many files, and ones I no longer use. Do not condemn extensions without evidence; mark unknowns. Return a table (Extension, Purpose, Risk, Decision, Reason) and a procedure for approving new extensions: check the publisher, read the description and permissions where available, test in a separate profile, and record it. Mark features such as workspace trust and profiles [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.