Shared Editor Configuration and Extension Security Audit
Check workspace settings and extensions for consistency and risk.
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 shared VS Code settings. The workspace settings file, recommended extensions, tasks and launch files, and formatter and linter settings: [WORKSPACE_FILES]. The team's languages and policies: [LANGUAGES_AND_POLICIES]. Check for settings that conflict between users and the repository, formatters or linters that disagree, extensions that are unnecessary or have broad permissions, tasks that run commands from untrusted sources, and settings that could leak secrets (logging, telemetry, synced settings). Make a table with Item, Concern, Evidence, and Fix. Propose a minimal shared configuration, an extension allow list with reasons, a review process for new extensions (publisher, update frequency, permissions, alternatives), and a note about untrusted workspaces. Draft a short team guide. Mark security and trust features [VERIFY] against current documentation. Do not provide instructions for evading controls. Add a worked review of one extension: publisher, install count and update date taken from its page [VERIFY], permissions it requests, whether it runs code from the workspace, and a simple allow-list decision with the reason. Include an onboarding note: open unfamiliar repositories in a restricted mode.
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.